My Vegas Pro 19 does not open video file .mov (4K frame rate 25, or 2K frame rate 30). It opens only a sound track from those video files. It works fine with .mov 1080p video.
General Complete name : C:\_tmp\20170725_034142.MOV Format : MPEG-4 Format profile : QuickTime Codec ID : qt 0000.00 (qt ) File size : 74.6 MiB Duration : 10 s 400 ms Overall bit rate : 60.2 Mb/s Encoded date : UTC 2017-07-25 03:41:42 Tagged date : UTC 2017-07-25 03:41:42 Writing library : icat Comment : QuickTime 6.0 or greater
Video ID : 1 Format : JPEG Codec ID : jpeg Duration : 10 s 400 ms Bit rate : 60.1 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 25.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Compression mode : Lossy Bits/(Pixel*Frame) : 0.290 Stream size : 74.5 MiB (100%) Language : English Encoded date : UTC 2017-07-25 03:41:42 Tagged date : UTC 2017-07-25 03:41:42
Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-40-2 Duration : 10 s 325 ms Bit rate mode : Constant Bit rate : 128 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 161 KiB (0%) Language : English Encoded date : UTC 2017-07-25 03:41:42 Tagged date : UTC 2017-07-25 03:41:42
Now I am getting error "The file you are loading does not support efficient editing. Please transcode the file into a more suitable editing format such as MAGIX AVC/AAC MP4". It does not allow to add those .mov files.
1. dragging from Windows Explorer to VEGAS Timeline - does not work. 2. dragging from VEGAS Explorer to VEGAS Timeline - works(!) 3. File > Import > Media... - works(!)
Is the legacy since-long-deprecated QT7 really still needed by Vegas to handle MOV files? I thought by this time, they would have added native support for it (to get rid of that bug with the maximum amount of MOV files a project can handle, among other things).
I thought by this time, they would have added native support for it
My understanding is that Apple withdrew Windows support for QT many years ago - it could have been as long ago as 2016. Some years ago on the forum, a Vegas staff member commented that QT was relegated to deprecated so that those who needed QT could enable it - removing it from general availability in Vegas Pro was to avoid any difficulties that might arise by including a no longer supported codec in Vegas Pro.
Is the legacy since-long-deprecated QT7 really still needed by Vegas to handle MOV files? I thought by this time, they would have added native support for it (to get rid of that bug with the maximum amount of MOV files a project can handle, among other things).
It isn't helpful to think Quicktime= MOV files. AVC and HEVC are decoded natively as is ProRes.
Other formats still use this deprecated QuickTime plugin and I hope more popular ones are also moved to a native decoder soon.
As "johnebaker" commented in a post either on this forum or the Magix Community Forum - Quicktime is still required for MOV files where the Format ID is identified as JPEG or PNG encoded video, it is no longer required for MOV h.264/AVC encoded import.
Testing with Vegas Pro 19 now, deprecated QT Plugin NOT enabled, selecting File > Import > Media... for an iPhone-recorded video with AVC and AAC:
This file is an unsupported format (Details: "File J:\Videos\20220329-172119.mov could not be opened.")
Mediainfo on that file gives me:
Complete name : 20220329-172119.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.00 (qt )
File size : 11.1 MiB
Duration : 2 s 33 ms
Overall bit rate mode : Variable
Overall bit rate : 46.0 Mb/s
Encoded date : UTC 2022-03-29 15:21:19
Tagged date : UTC 2022-03-29 15:21:21
Writing library : Apple QuickTime
com.apple.quicktime.location.accuracy.ho : 9.420457
com.apple.quicktime.location.ISO6709 : +55.7101+013.2243+070.009/
com.apple.quicktime.make : Apple
com.apple.quicktime.model : iPhone SE (2nd generation)
com.apple.quicktime.software : 15.3.1
com.apple.quicktime.creationdate : 2022-03-29T17:21:19+0200
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2 s 32 ms
Bit rate : 45.7 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 30.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.184
Stream size : 11.1 MiB (99%)
Title : Core Media Video
Encoded date : UTC 2022-03-29 15:21:19
Tagged date : UTC 2022-03-29 15:21:21
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 2 s 30 ms
Source duration : 2 s 90 ms
Bit rate mode : Variable
Bit rate : 186 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 46.1 KiB (0%)
Source stream size : 47.5 KiB (0%)
Title : Core Media Audio
Encoded date : UTC 2022-03-29 15:21:19
Tagged date : UTC 2022-03-29 15:21:21
Other #1
Type : meta
Duration : 2 s 33 ms
Other #2
Type : meta
Duration : 2 s 33 ms
Bit rate mode : Variable
Duration_FirstFrame : 633
Duration_LastFrame : 233
Other #3
Type : meta
Duration : 2 s 33 ms
Bit rate mode : Variable
Of course, repackaging the file in e.g. an MP4 container will make Vegas like it, but sort of one of the main perks with Vegas from my point of view is being able to work with the original files and not having to bloat the storage with intermediate format copies to make the video editor happy.
But would QT (still) be the only option to make Vegas read this MOV container?
It should open using so4compound plugin and QT plugin would do nothing for this type of file. If it imported I'd right-click on media and look at it in properties.
I'm surprised it doesn't open- can you do as EricLNZ requests and upload it to Google Drive, Dropbox, Box, or somewhere else? Just a few second sample is fine.
Sure! The previous file being my son skateboarding and perhaps nothing he wanted shared in public, I created a new short clip with the same device and settings. Available here:
If under preferences, file i/o "enable legacy AVC decoding" is unchecked it should open with so4compound.
It opened without issue here and works with Intel hardware decoding.
Former user
wrote on 3/31/2022, 7:31 AM
Sure! The previous file being my son skateboarding and perhaps nothing he wanted shared in public, I created a new short clip with the same device and settings. Available here:
You can also try other basics like updating graphics drivers with help/driver update in Vegas. Really AVC files should import and play with few exceptions.
@RogerS, I did the reset. That did not change the outcome. As for graphics drivers, I cannot see how that could or should affect a program's ability to read a container format? Right now running Vegas in a Linux-hosted VirtualBox virtual Windows 10 machine (as I do with Vegas 12.0 all the time). Yesterday when I tried it on a regular native Windows 10 PC, it gave me the very same results. So the not-working-at-all experience is very consistent here, unfortunately.
@d97jro Hi, i have no prob importing that file with 'QT Plugin NOT enabled', or am i missing something?
That is indeed very strange. I have made sure I have exactly the same setup on that tab (with the legacy GPU box ticked), Vegas is restarted and was previously reset too, but nope, the file cannot be opened. I also tried having the movie clip to import on a local drive (although I don't see the reason since Vegas never had issues with mapped network devices, good to rule things out though) but that makes no difference.
Graphics drivers can affect decoding as Vegas uses the GPU for that in current versions (see preferences, file i/o). Vegas works with Intel, AMD and NVIDIA on bug fixes and compatibility improvements.
I'm using Intel decoding and Gid is presumably using NVIDIA (so that leaves AMD as maybe not supporting this file?)
For the non-virtual machine where it didn't work, what was the CPU and GPU? What was file i/o set to for AVC and hardware decoder? I don't know where to start with troubleshooting for a virtual Windows 10 machine but this file should at least work on a real one.
Former user
wrote on 3/31/2022, 8:25 AM
That is indeed very strange. I have made sure I have exactly the same setup on that tab (with the legacy GPU box ticked),
I know in this we're turning off QT plugin but have you got Quicktime installed?
& can you go to your icon at the top, click it - My Profile, & fill in your Signature with your Vegas version, Windows version & system specs, CPU, GPU, RAM etc. this will then show at the bottom of the comments
I don't know where to start with troubleshooting for a virtual Windows 10 machine but this file should at least work on a real one.
If it were not to work in a virtual machine (which Vegas 12.0 does, flawlessly—or at least as well as on a native Windows PC) that would absolutely be a dealbreaker to me. I will do a third experiment with another (native) Windows computer tonight and if that doesn't work either, I guess getting a contemporary version of Vegas would turn out to be quite useless for me, unfortunately.