Quicktime and MOV files

[MikeA]

I am getting the error noted by others concerning MOV files. Basically, I cannot do any editing using MOV files at present. I used to have a camera with MTS files. The old ones from that camera come into VS beautifully. But any attempt to load a MOV file to the timeline, or to link to a missing MOV file, will crash the program if you keep trying. Therefore, for me, VS is useless! The error refers to Quicktime 64 bit and also C++. What gives!

(I thought I was back on track. I fixed the MS update issue (VS now starts). I discovered that my video hard disk crashed about the same time as the MS error (got a new one). And I repaired the boot sector on my primary drive (computer starts). All is good - Yes? NO! I can't use VS!)

M

[skier-hughes]

DO you have the latest version of Quicktime installed?
Are these files that used to work or are these new files that you haven't used in VS before?
There are literally hundreds of different types of MOV files, (MOV is actually just a wrapper not a file type), so if they are new, maybe they don't work with VS!

[MikeA]

Just updated Quicktime to 7.7.9. And Yes - I was able to pull in these files without a problem until the recent MS update etc. I have a project now that loads that is full of the MOV files. But now I cannot start a new one with any of the MOV files or link to a MOV file in that project that was later moved to a different folder. I also have a completed project that used MOV files from the same source. Now there is an instant error box as soon as I click on a filename and VS aborts.

Thanks for the response.

[MikeA]

Wow! Got a reply from Corel technical help. It is this -

"Thank you for contacting Corel Technical Support. Kindly try to click the Ignore option in the screenshot provided, this option will ignore the assertion and continue running the program."

I had to click a couple of times on the Ignore button, as noted. Then the MOV file loaded onto the timeline. So VS is usable, although a bit cumbersome. Makes me happier.

M

[MikeA]

I replied asking about whether there would be a fix or what version of Quicktime is OK (I am now using 7.6 but was using 7.7.9) but my questions were ignored.

[MikeA]

I discovered that clicking on the Ignore button does get me past the error intrinsic in loading MOV files. However, as I began to use the program again, two other errors came about. First - when I played the video by pressing the space bar the same error box came up time after time. And, secondly, there was no sound. I checked my audio external to VS and all was OK. The audio window didn't show the usual audio spectrum within each clip as is usually seen. So, right now I have limited functionality. I have sent my complaint to tech support. Will update when there is news to share.

[Ken Berry]

When you right click on the .mov file in the timeline, what does it say under Properties about the format of the audio part of the clip?

[lata]

Hi guys

Corel provided a hot fix for earlier mov issues replacing a Dll file.
I think it is part of SP3, but wont harm trying replacing the file anyway, you can always revert back to original file.

Download from my one drive.

http://1drv.ms/24gLl4s

[MikeA]

Sadly - did not work. I am waiting for technical support. My puzzle is how this happened and whether anyone else is having the same trouble. I could proceed independently but what to do - remove the two Windows updates? What version of Quicktime to have? Uninstall and re-install VS?

[SoNic67]

Rename those files as ".mkv".

[MikeA]

I fixed it. I removed the two MS updates. I was confused. I thought the VS hot fix would fix the problem, but I guess not. With the two MS updates removed I can load MOV files, play them, and see the sound. All is normal. No error boxes. By the way - I see there was a C++ update on 2/11. Not sure what that means if anything.

I wonder what the implications are of not having the two MS updates?

Thanks for trying.

[TonyP]

Good for you. It seems that M$ has messed up a few things with their updates, leaving to people to figure out what the heck went wrong. Glad you are back in business!

[DixieMaddog]

CorelVSX8Support.txt

(7.02 KiB) Downloaded 300 times

MikeA: I've had the exact same experience with Win 7 , VS X8, and the MOV files. Hot_Fix_2 did resolve the Will Not Load problem caused by the two now infamous updates, KB3126587 and KB3126593. But, I could not use MOV files without uninstalling these updates. I tried the most current version of Quicktime and several others, no good.
lata: I tried the hotfix from pre-VS 8.5 that you kindly made available. But, unfortunately it did not work either.
So...I've been working without those two Win 7 updates. Now, that I've finished that particular job, I'm again trying to resolve the nagging MOV file problem.
I could convert the files to another format, but that's time consuming.
SoNic67: Bingo! renaming the MOV files to MKV worked for me. That's my simplest solution so far. Thanks, Buddy.
Now I'm working with all my Windows Updates in place.
************
The attached text file is the transcript of my experience with Corel's tech support on this whole issue. Unbelievable.

[MikeA]

Very interesting and just like my experience with VS, Windows, and with Corel help. Seems they wouldn't touch the Quicktime/MOV issue even though I put direct questions in my communications to them about it. I got an email today from some top guy in Corel. Said the hotfix would solve the problem. Clearly it doesn't sort the MOV issue. But I am left in a quandary - my VS 8.5 works OK now in Win 7 (even though I did something with overlays that caused the program to shut down two days ago). BUT - I don't have the two MS Windows updates. What does that mean for security and future protection? The Corel email said 2 choices - update to Win 10 or buy VS 9. OK - but would VS run slower in Win 10? (If not, I don't mind updating, though I don't need any of the Win 10 crap - my computer is for video editing only). Buying the update to 9 is a possibility. But - will it run OK in Win 7? And, since I just upgraded to 8.5 from 7, why should I pay more for a program that is faulty?! I've used VS for years, and admired its stability and the way it always works (nearly) the way I expected. Now this. It's upsetting!