tanguero
Junior Member
VideoStudio X8 Ultimate on Win7 64-bit
Posts: 35
|
Post by tanguero on Apr 29, 2024 18:55:03 GMT
While I've used VS X8 for some years now without encountering problems that didn't have a workaround, this is the first time I've encountered this one. I guess since I'm trying it for the first time with a video from an Olympus camera that saves as .MOV instead of my usual Canon that saves as .MP4.
Anyway, when attempting to import the .mov video (either into a library or the timeline), I get a Windows error "BurnStarR DLL has stopped working" with really the only option of closing the DLL. VS X8 continues to work and continues to let me import .mp4 files. The file in question is 1080p 29.97 fps nothing unusual about it. Problem is 100% reproducible. My machine is Win7 64-bit.
Google shows me an old forum post that matches BurnStarR that possibly addressed that issue, but I cannot get a cached copy and while the archive.org site probably has it, it doesn't let me search for it. Maybe someone remembers that issue and can shed some light? Seems hard to believe that .mov files don't work with VS (though given that .mov comes from Apple, maybe not so surprising, though why would any camera maker choose a proprietary format that they don't even own?). And I have at least 3 or 4 programs on my PC that open .mov files just fine (including WinX Video Convertor, VLC, 5K Player, Machete, and probably more, so it seems to be a VS-specific issue). Thanks.
|
|
|
|
Post by Candive on Apr 29, 2024 20:49:06 GMT
|
|
tanguero
Junior Member
VideoStudio X8 Ultimate on Win7 64-bit
Posts: 35
|
Post by tanguero on Apr 29, 2024 23:16:00 GMT
Hi Candive, definitely helpful as a starting point--thanks for digging those up. But first question: How did you manage to find the posts?? I couldn't get the search within the archive.org mirror to work, and since there are 613 pages of post indices, even a web browser text search would be too tedious! Would be good to know how to search the old posts more efficiently ...
Returning to the matter at hand, I'll try the following and update if I get anything useful:
1. Install any old QT I happen to have installed (Windows Programs and Features claims I don't have it installed but I'll do a more thorough search);
2. Install the newest version of QT [ugh] and see if that helps.
Other than that, the only other concrete suggestion in the old posts (which was more or less an admission of defeat), is to recode externally to something else since the problem is ONLY with .mov. And maybe someday I'll upgrade to a later version of VS--sad that 2023 may be the last--and perhaps that will fix it.
Now, some additional information: A search on my C: drive for BurnStarR.dll comes up with multiple copies (7 total, one for each language, each with slightly different file sizes!) all under the Corel Video Studio Ultimate installation directory. The file is from 2015 (with copyright from 2007(!), signed by Corel Corporation, and the description includes "Product name Ulead Burn Now" and "Legal trademarks Ulead Systems, Ulead Burn.Now is a registered ..."
So maybe not a QT issue at all. Can someone check if a later version of VS still uses this file? This en-US version is of size 843 KB (864,056 bytes). Since it's lived since 2007, it may still be in use now, even if no one alive knows what it does at this point! But since I assume any number of people have used .mov files successfully while a few have had this problem, even since X4 (references in the posts you sent me the links too), there definitely seems to be some other mysterious interaction going on, but would seem to be hard to nail down.
|
|
davidk
Junior Member
Posts: 27
|
Post by davidk on Apr 29, 2024 23:30:19 GMT
Hi Tanguero,
There is a note from ken B in that archive about the correct/latest Qt components. For a long time, that Apple codec was part of the OS (win 7?), and thus not VS. With the progression of OS versions, the QT codec for .mov was removed from the OS, and thus you need a separate codec installed to get .mov to work correctly. You can still get them: there are notes on that in the forum or the admins could advise.
|
|
tanguero
Junior Member
VideoStudio X8 Ultimate on Win7 64-bit
Posts: 35
|
Post by tanguero on Apr 29, 2024 23:53:17 GMT
Hi David, yes, Item 2 in what I was going to try (install latest QT) was a reference to that post. There are no suggestions for specific codecs there, just the suggestion to "try the latest version of QT" and since I don't have QT installed at all (I uninstalled it years ago since it was problematic, and never missed it until now), that will be one of my attempts. Wish I could just point to one of the other codecs that I clearly have from the other software I mentioned that has no problems with QT.
|
|
|
|
Post by Candive on Apr 30, 2024 6:19:42 GMT
Hi Candive, definitely helpful as a starting point--thanks for digging those up. But first question: How did you manage to find the posts?? I couldn't get the search within the archive.org mirror to work, and since there are 613 pages of post indices, even a web browser text search would be too tedious! Would be good to know how to search the old posts more efficiently ... There really isn't a simple search. The simple answer is; I'm currently sick with the flu and had a bit of time on my hands.  Basically I did a google search on "VideoStudio BurnStarR DLL" and the results indicated a date when this issue was discussed on the old forum.  Then I went to the Wayback Machine and started rapidly clicking to the page which contained the date range I was looking for.  |
|
tanguero
Junior Member
VideoStudio X8 Ultimate on Win7 64-bit
Posts: 35
|
Post by tanguero on Apr 30, 2024 15:30:14 GMT
Thanks for doing that manual search for me. It indeed set me on the right track (even if it was only to discourage me from going down the rabbit-hole of QuickTime!).
Update: After looking into (re-)installing QuickTime, I decided not to go that route since (a) it's deprecated and in fact no longer supported and (b) while I can't remember the details, I do remember having all sorts of other annoying problems with QT on my system which is why I uninstalled it in the first place some years ago, and decided that I didn't want to rediscover that frustration. :-)
The above given that I came up with a reasonable solution, which is to convert the .mov to .mp4. Of course, that was only a solution if I could do this quickly and losslessly, i.e., change only the container keeping the embedded video unaltered. And after some googling and experimenting, I came up with a workflow that does what I need, so I'm documenting it here in case it helps others:
1. Use Avidemux for lossless reencoding from mov to mp4. I had an old version from 2016 still on my computer which worked fine, though there is a much more recent version from about 2022. Incidentally, the audio could not be mapped losslessly since the original was PCM at 1536 kb/s (which I guess .mov supports but .mp4 doesn't); however, Avidemux was happy to convert it for me into .aac (at 154 kb/s CBR), while leaving the video alone. (Ffmpeg can do the same on a command line, and is probably what Avidemux uses behind the scenes anyway.)
2. Confirmed with MediaInfo that the before and after conversion was lossless on the video (in addition, it happened too fast and with too little CPU use to be a video reencode).
3. Confirmed that VideoStudio X8 can now import the rewrapped .mp4 just fine.
The only minor glitch is that something about the .mp4 created this way is not compatible with the Windows Explorer thumbnail generator (as all my other .mp4s are), so I can't see the video thumbmail (nor could I with the .mov files) on these Avidemux-generated .mp4s in Windows, but I can live with that and it's not a VS issue anyway (the VS library shows the thumbnails just fine).
|
|
Basically I did a google search on "VideoStudio BurnStarR DLL" and the results indicated a date when this issue was discussed on the old forum.
