X8 and X9 .mov clip import generates file format mismatch

[Davidk]

I have a selection of background clips (most are .mov, some are .mp4) that I've used periodically in project files for years, dating back to X6. Currently I have x8, X9, X10 and 2018 versions installed.

In a project series that I began some time ago when X9 was the "current" release, I began to create a new vsp with X9 loaded (v 19.7.0.12), and found that my background videos no longer worked - generated a file mismatch error for .mov clips when trying to import. See screenshot here

The .mp4 files in the same folder imported fine.

Analysis
The clips affected (the ones I tested with) played fine in media player.
I checked the programs and features page of windows 7 - QT codecs installed.
Tried the same import under X8 - same error.
Tried the same import under X10 and Vs2018 - import worked fine in both versions. Made a vsp under 2018 and imported a .mov clip OK, and saved as an X9 vsp. Opened X9, and when opening that saved vsp the background clip showed as a re-link. Trying to re-link failed in same way as import did.

Summary
.mov clips will not import under X8 and X9: file format errors reported.
.mov clips will import OK under x10 and vs2018.
the QT codecs for .mov are installed. Prior vsp using the background clips worked fine under X6/X7 - I have the rendered results on file but those versions are not installed any more.

Ordinarily, I like to complete project series using the same VS version, but that's not going to be possible it seems.

Can anyone indicate what might have caused nominally fully patched versions of X8 and X9 to not import .mov files now?

[asik1]

It's part of VS's charm,
what used to work fine in the past might not work at all in the future.

[Davidk]

Did some more work on this.
Used Handbrake to convert the .mov file I was most interested in to mp4. Conversion proceeded Ok. Then opened X9 and imported that mp4 file into the X9 timeline. Import OK. Play file OK.

Seems obvious that X8 and X9 have lately - possibly as a result of patches - have lost the connection to the QT codecs essential to run .mov files. These are not current releases but there must be many users out there with those versions who haven't upgraded for which this is a time bomb waiting to happen.

[asik1]

recently I tried to import few mov's with alpha and couldn't.
I forgot I uninstalled QT at all as it keeps crashing VS's QTbridge file
When it hit me , I reinstalled QT and the mov's worked fine in my 19.2
(the mov's worked fine with no QT installed on other very low scale & basic NLE )

[lata]

Hi David

Two things to consider, importing clips to timeline and re-linking clips.
After you converted using Handbrake did you import the clips or re-linked the clips.

Where files import ok to the timeline, yet same files cause a re-link issue to me would indicate a problem with the project VSP file and not the actual video file.

[Davidk]

Hi Trevor,
I tried it both ways, in several different versions. Same result each time.
The image I originally posted was from using X9 to open the vsp created in x10 and saved as an X9 file (you can see the black and white bars of the relink indicator in the clip time as part of the image beside the message box.

However, to demonstrate further, here's 3 images of the .mov file I most wanted to work with (I tried it with other .mov files too, and got the same result in all the related versions - errors in X8 and X9, Ok in X10 and 2018):
1. Importing the .mov file into X9, freshly opened and no other items in any track (the original errors occurred with items in the main timeline , overlay and text tracks, but testing after that was only in the 'clean' timeline and tracks condition)

I've composed the screen shot to indicate the empty timeline, and show the existence in the nav panel of the file (40163.mov) immediately above the error box saying file mismatch.

2. Opening the created vsp (using X10 where opening a .mov file was NOT an issue and saved in X9 format) in X9.

And here you can see more clearly both the re-link indicator bars in the timeline and the re-link message box saying the 40163.mov file doesn't exist, when the nav panels clearly show it.

3. And lastly the properties of the 40163.mov file, necessarily obtained using a working x10

None of these things happen with .mov files tested with x10 or Vs2018. I think the circumstances clearly demonstrate that there's something amiss in the processing of .mov files in X8 and X9, regardless of whether it's a file import, or the opening of an existing vsp.

[asik1]

David, if you upload 40163 , I'll test it on my 19.2.
I might update VS momentarily to 19.xx as I plan to re-image soon so I'll be back to my favorite 19.2

[Davidk]

I generally try to avoid uploading files, because it takes so long on the miserable ADSL2 links most aussies inc me have. However,
the 40163.mov file mentioned in the thread is here on OneDrive:
https://onedrive.live.com/?id=F258AB298 ... 2984C226A1

It took about 85 minutes to upload the 15sec, 285Mb file.

[asik1]

I generally try to avoid uploading files, because it takes so long on the miserable ADSL2 links most aussies inc me have. However,
the 40163.mov file mentioned in the thread is here on OneDrive:
https://onedrive.live.com/?id=F258AB298 ... 2984C226A1

It took about 85 minutes to upload the 15sec, 285Mb file.

D/L isn't quick ... ~0.6Mb. and not ~13.
You could upload smaller file that bare the same problem.
I'll test in an hour.

[lata]

Thanks David

Can you also provide the VSP that is causing the Mismatch.
If you rename the VSP to use .txt then you can attach to your post.

sample
“Test Project.vsp.txt”

Thoughts

Using Windows Explorer If you rename the video file to 40163a.mov, then try to import to VS as your first image above????

[asik1]

So... mixed results on 19.2
I can load it OK and play it

But , soon as I try to peek it's properties VS crashes on uvqt.vio file.
Problem signature:
Problem Event Name: APPCRASH
Application Name: vstudio.exe
Application Version: 19.2.0.4
Application Timestamp: 570e478d
Fault Module Name: uvqt.vio
Fault Module Version: 19.0.0.200

Mediainfo shows the codec is jpeg at 4:2:2 , I would convert that to more usable file and never look back.

[lata]

Hi Asik

I have not had any problems running that video sample, 2018 or X9, X8

trying different things to replicate david's issue but always shows ok, as does properties, no problem viewing those

The video does not have an audio stream but does not seem to be an issue?

[Davidk]

Hi guys,
Thanks for all the suggestions.
Trevor - renaming as 40163a.mov made no difference; import to x9 caused the same error.
The vsp you asked for is

Trip travel_x9.VSP.txt

(17 KiB) Downloaded 282 times

This is the one I created under x10, and it worked fine. Saved it as an X9 vsp, closed x10, opened x9 and opened this file. re-link error as reported displayed.

[asik1]

I had to mod internally the vsp first (to be opened in 19.2) but then I was able to relink the mov

[lata]

Hi

I have not been able to replicate this problem, the project and the video file works ok on my pc.
Yes i have to re-link but that is normal.
I notice that the overlay / decoration clips are from 2018 samples, yet you say the project was made with X10, not that the location of those clips would affect the Mov.

If you run the “Trip travel_x9.VSP” does it still fail for you?