BurnStarR DLL (32 bit) hangs

[NostalgiaNerd]

I have an issue with X9.5 in that when importing .MOV files, BurnStarR DLL just seems to hang at around 35% CPU.

The only way to allow VideoStudio to continue past importing the .MOV and opening the file is to kill the BurnStarR process.

After this point VideoStudio then fails to recognise further .MOV files and throws a "File Format mistmatch" error.

[aljimenez]

It appears X9.5 can't interpret your .MOV file. I do not know what BurnStarR.dll does, but the key here is to help you get this file into X9.5 A quick workaround may require you to convert this .MOV file into something X9.5 can read. There are a number of programs to convert video files; one good one is Format Factory (just be attentive when installing it as it tries to install lots of other programs during its installation).

If you want more direct help with this .MOV file you have, please post the properties of this file, and if you could share a small version of the video, others here could try it and further determine what the problem is and perhaps get Corel a sample to determine if a fix would be possible.

[NostalgiaNerd]

I'm currently converting my files to MP4s, but it's a pain the the bum.

It happens with all MOV files I have, from various sources. Doesn't seem to be limited to certain files produced by my camera.

I believe Burnstarr.dll was introduced by Corel in X4 and assists with file conversion.

I've attempted to re-install VS, I've removed and re-installed Quick Time components, but no avail.

[Ken Berry]

I assume the QT components you reinstalled include the very latest version of the QT codec, not just an older one you had installed previously...?

[NostalgiaNerd]

Yes. To be honest, I was just clutching at straws. There should be no reason why the codecs were altered.

This had been an intermittent problem in the past, but a computer re-boot solved the issue. Now, it seems to be here to stay.

No other media playback or interaction is affected on the computer, it purely seems to be with this Burnstarr component.

[NostalgiaNerd]

OK, I think I've resolved the issue.

It appears that Stardock Fences was causing some sort of conflict - I have no idea why - and uninstalling this application seems to have restored the VS - QT link via this intermediary program.

If you encounter any similar issues, it may be worth uninstalling any recent programs.