How do I get a 422 ProRes proxy file rendered in Vegas 19 (latest update) to drop on the timeline? Currently I just get the red circle with the line through it when I try to drop it on the timeline. Any pointers?
@j.razz hmm i just did that no problem, I just used the ProRes 422 default settings, did your file play ok in a player after it was rendered out, ?
there's a tool called MediaInfo, download it, it's free https://mediaarea.net/en/MediaInfo After downloading, right click on the media in your Windows folder, open MediaInfo, choose Text from the View option, select all, copy & paste in a comment here or copy the MediaInfo window & paste using the arrow button at the top of a new comment to add pictures, ,
The issue was the QuickTime deprecated feature not being on. I remember reading on this a while back when I was looking into the Ninja Atomos systems, but didn't recall where to look or where to find the right QT executable. Looks like it's already built into Windows 11 and I just had to turn it on in Vegas.
As a follow-up, the Atomos allows for output to DNxHD (as well as ProRes). Is there a similar toggle for that?
I don't get why it's different either- here is mine:
General Complete name : C:\Users\Roger\Desktop\Untitled.mov Format : QuickTime Format/Info : Original Apple specifications File size : 71.2 MiB Duration : 14 s 97 ms Overall bit rate mode : Constant Overall bit rate : 42.4 Mb/s Encoded date : UTC 2022-07-12 01:07:14 Tagged date : UTC 2022-07-12 01:07:14 Writing library : Apple QuickTime
Video ID : 1 Format : ProRes Format version : Version 0 Format profile : 422 Proxy Codec ID : apco Duration : 14 s 97 ms Bit rate mode : Constant Bit rate : 40.9 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:2 Scan type : Progressive Bits/(Pixel*Frame) : 0.822 Stream size : 68.7 MiB (96%) Writing library : magx Language : English Encoded date : UTC 2022-07-12 01:07:14 Tagged date : UTC 2022-07-12 01:07:14 Color primaries : BT.709 colour_primaries_Original : BT.709 Transfer characteristics : BT.709 transfer_characteristics_Origi : BT.709 Matrix coefficients : BT.709 matrix_coefficients_Original : BT.709
Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 14 s 97 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 2.58 MiB (4%) Language : English Encoded date : UTC 2022-07-12 01:07:14 Tagged date : UTC 2022-07-12 01:07:14
Of course, Quicktime isn't needed to decode ProRes in VP 19- I never installed it and it is not enabled in deprecated features. Under media/ properties you can see that it is decoded with so4compound as expected:
General Name: Untitled.mov Folder: C:\Users\Roger\Desktop Type: ProRes 422 Proxy Size: 72.95 MB (74,700,833 bytes) Created: Tuesday, July 12, 2022, 10:07:14 AM Modified: Tuesday, July 12, 2022, 10:07:24 AM Accessed: Tuesday, July 12, 2022, 10:07:41 AM Attributes: Archive
Here's what I have for my So4 Compound Plugin settings in the hidden internal menu. What do you guys have? Hold down Shift when you open Options to see it at the bottom of the dropdown. You can search for So4.
Do not mess with so4compound in internal menus unless you are trying to break things. You can access it on preferences/ file io if you need to enable a legacy decoder.
You want to leave that set to true always. Don't adjust that in internal settings, as you can do that instead in preferences by enabling or disabling legacy AVC and HEVC decoders in file i/o settings. Best to not use legacy decoders unless you have to.
In Google Chrome for me when you click on CodecsLE_2.7.3_Win nothing happens so i had to open it in Microsoft Edge,
Downloaded & installed the Avid Codecs,
couldn't find them as in his vid, 🤔 one of the comments say they couldn't find them either after installing, so did as he suggested, i didn't uninstall Vegas tho, I deleted everything from C:\Users\name\AppData\Local\VEGAS Pro\19.0 to make Vegas reload plugins etc.. & removed & reinstalled Quicktime, (the link i posted above)
Still couldn't find them but looked in Customize Template & there's a bunch of Avid stuff inc DNxHD
This is what that render produced 🤷♂️
😂😂😂🤦♂️ PS if i'd watched his vid further the ones that show are his custom Templates, he must have gone into Customize Template & chosen DNxHD . Doh! 🤸♂️😂
Unlike ProRes, DNxHD does require Quicktime to be installed and enabled in deprecated features. I'd avoid it as it has severe limitations in Vegas and too many clips will be displayed as all black.
Former user
wrote on 7/11/2022, 9:17 PM
@j.razz Yes no prob, I'll share one for you, I know nothing of this kind of file & apart from choosing DNxHD i left everything as default.
@RogerS why does yours say 2 above a 2, the default is 2 above a 1 ?
this is mine, i don't go into Internal n mess with stuff
@j.razz When the file is on the timeline Properties - Plug-In Name: qt7plug.dll Folder: C:\Program Files\VEGAS\VEGAS Pro 19.0\FileIO Plug-Ins\qt7plug Format: QuickTime 7
I have the qt7plug.dll in the directory same as you @Former user, but I am unable to drag that file onto my Vegas timeline as it gives me the red circle with the line through it. ProRes can now be dragged to my timeline and play.
Having said that, I will more than likely just leave it alone now that I can utilize ProRes.
Former user
wrote on 7/11/2022, 9:42 PM
@j.razz Did you install Quicktime? I wonder if you need to have those Avid codecs i installed as well 🤷♂️🤔
PS. if ProRes now works for you as you say no need 👍🤸♂️
I'm off to bed, it's 3.40am, glad you're sort of sorted 👍
I did not (at least not anytime soon). It shows that it was last updated back in June for the quicktime plugin.
And yes, I'm sure those files are necessary- I didn't try to install them given ProRes works and that is what I'll be working in. I was just curious. Thanks for the help @Former user
Why does yours say 2 above a 2, the default is 2 above a 1 ?
I don't know actually. I tried searching online and don't see an explanation anywhere. Maybe it's a thing with systems that have integrated + dedicated GPUs? File i/o is set to defaults and I ran so4detect again and it didn't change.