.MOV container problems in Vegas Pro 17

Clay-Zaccaglini wrote on 6/19/2020, 1:52 AM

Why does Magix think .mov files are obsolete and always related to Quicktime which they are doing away with? It is my understanding that .mov is just a container, and codec can vary in containers. For instance, my new Atomos Ninja V recorder uses .mov containers with DNxHR codex. Does not work in Vegas but it works without any problems in the free version of DaVinci Resolve. Same thing with 2 of my new action action cameras that also use the .mov container, but it works great in DaVinci Resolve. Vegas Pro also does not have Prores support for Windows while some other video editors do. What can I actually use Vegas Pro 17 for? Does not work at all for my Atomos Recorder without some third party tweaks or at all on my action cams. I can do a couple tweaks for my Atomos with the DNxHR codex installed separately from Avid, but I can't get video on action cameras to work (audio only). I feel like Vegas is a little behind the times.

Comments

Dexcon wrote on 6/19/2020, 2:23 AM

In VP17, go to the Deprecated Features tab under Options/Preferences and check the "Enable the Quick Time plugin". You should then be able to use .mov files in Vegas Pro 17.

Marco. wrote on 6/19/2020, 2:43 AM

For most of the current used MOV types Vegas Pro 17 doesn't need Quicktime anymore because it has it's own decoder. Vegas Pro 17 actually supports ProRes for both import and export.

Clay-Zaccaglini wrote on 6/19/2020, 2:54 AM

Marco, I have not been able to get ProRes video from my Atomos Ninja V to work on my Windows 10 machine. Are you referring to Mac? Also, Atomos .mov files will not work in Vegas unless you turn on deprecated quicktime and install the codec from Avid. I also had to install the codec pack from K-Lite. Took me days to figure it out, but it is still not 100% reliable and crashes occasionally. I also had to make some minor changes in the Internal settings to somewhat stabilize it. Thanks for responding.

Clay-Zaccaglini wrote on 6/19/2020, 2:59 AM

Dexcon, I have enabled the deprecated feature, and I found a way to get DNxHR .mov files to work (you have to install the codex which is not in Vegas from Avid & K-Lite). It will not work out of the box, and deprecating .mov as Quicktime in Vegas was not thought out well (those are features that Vegas is eventually going to remove). DNxHR is not a Quicktime codec. There are also some tweaks required in the Internal tab. Lastly, I have not been able to get video to work in my 2 action cams that use .mov containers, Gopro and Akaso. Audio works, but video does not even show up in the timeline. Any suggestions will be greatly appreciated. Thanks for your kind response.

Dexcon wrote on 6/19/2020, 3:35 AM

Re GoPro, my GoPros are set to record .mp4 so, unfortunately, I haven't any suggestions re .mov there. As I rarely use .mov files, others on the forum may be able to offer help.

Are you referring to Mac?

Re Vegas Pro 17, this is most unlikely given that there is no Mac version of Vegas Pro - it's designed for Windows.

diverG wrote on 6/19/2020, 3:51 AM

Maybe use Happy Otter 'import assist'. There is a trial available plus the writer is most helpful. Certainly take a look at it.

Beware the k-lite codec pack does not create further problems in due course.

altarvic wrote on 6/19/2020, 4:41 AM

Why does Magix think .mov files are obsolete and always related to Quicktime which they are doing away with?

MOV format is not obsolete, unlike the QuickTime library for Windows.

I think MAGIX should develop its own library to work with MOV format and QuickTime codecs

Clay-Zaccaglini wrote on 6/20/2020, 1:29 AM

Not sure why ProRes was not working in my Vegas Pro 17 since I bought it late last year, and don't believe everything you read on the Internet. Maybe it was one of the updates in Vegas Pro 17, but ProRes is now working. I can now edit all my ProRes video from my Atomos Ninja V in Vegas Pro 17. It takes a lot longer to render than the files recorded in DNxHR codec, but the quality is better with more detail.

Concerning my 2 action cameras that record in mov containers and H.265 codec, it turns out that my hardware decoder was set to Intel QVS instead of Nvidia which I have (go options/preferences/io file). Not sure how that happened, but the recent upgrade did make a lot of strange changes which did require me to do a full Vegas reset.

Thanks everybody for all your help and support. The community is always supportive, and all of you guys are all really awesome. Hope I can help somebody too.