Vegas Pro BUG with handling Prores Timecode

ion-marin wrote on 10/3/2019, 1:28 PM

I recently had a big problem importing in Resolve a vegas generated XML. I was getting a ton of timecode errors and eventualy after days of reasearch i figured out why.

The XML project was populated with Prores 422 footage and seems like Vegas is not able to read the proper timecode within prores files, and just assumes timecode 0:0:0:0 for all takes within the timeline. Atfer exporting the XML file it also disregards the prores files embeded timecode, and just asumes :0:0:0:0 value. And so you get a worthless XML file which you can't use it properly in another NLE.

While researching this issue, i found out that other people had exactly the same problem, years ago..... from Sony vegas 10 version at least...

So if this is a old, known issue, Why doesen't Magix fix it? And if this issue wasn't fixed for so many years, is there hope that it will ever be fixed?

Comments

NickHope wrote on 10/3/2019, 1:47 PM

Which version of Vegas are you using? In VP10 ProRes was decoded by Quicktime, but in recent versions it's decoded by the native MAGIX ProRes/Intel HEVC decoder.

If your issue occurs with the native decoder, and the issue is decoder-dependent, it might be possible to work around it by disabling the native decoder so that Quicktime is used. You could even do that temporarily to get the XML file out, then switch back to the native decoder if it gives you better performance.

Kinvermark wrote on 10/3/2019, 6:47 PM

XML import / export is quite tricky. Not just (or necessarily) Vegas's fault. Lot's of variables here.

Generally, you can see if Vegas is reading the source timecode by looking at the event properties:

So it does read this mp4, but not all mp4's. Most mov files seem OK, but depends on the source. What always works are proxies or intermediates rendered from Resolve itself (I like cineform.)