Q: Intermediates & alpha channels

Former user wrote on 1/12/2020, 11:04 AM

Hi Vegas Forum,

First post here, although I frequently lurk and have learned a lot from this board. Thanks for all of the information and experience that has been shared.

System specs: Vegas Pro 17 (build 387), Windows 10 Pro, x64, NVIDIA GeForce GTX 1060 6GB.

I’ve got a somewhat basic couple of questions about rendering to intermediates with alpha channels:

In one current project, I’ve got a simple PNG image-sequence on a track, and each of the PNG files contains an alpha-channel (naturally). There are graphics in the center of the frame, with the outside clipped to transparency. Very short, about 32 seconds.

Usually when I’m setting up these types of image sequences, I’ll drop a Vegas Solid Color media generator beneath the animation (which is muted before rendering), to be able to monitor the results with a color (cyan) other than a black background. At this stage, the alpha-channels in the image sequence enable track transparency, and it’s possible to see any track layer beneath.

Often when I’m rendering to an intermediate, I’m using the Magix Intermediate 422, usually 1080p, 30 fps. Since this intermediate type renders to MOV media (I presume, different from Apple Quicktime MOV, which is obsolete on Windows, but, as we know, works with alpha-channels), one would expect them to have alpha channels available in the rendered files, however…

Alpha-Channels:

When I render the 422 intermediate file though, load it onto a track, right-click on the video event and open its Properties dialog, on the Media tab, there is a drop-down selector for Alpha channel, and regardless of which is selected there – Straight (unmatted), Premultiplied, etc. – the areas of the video event that should be transparent using the alpha-channel, remain black.

Qs:

Is it in fact possible to use the Magix 422 intermediate format, to create video that includes the alpha-channels of the original pre-rendered media?

Are there possibly some rendering settings that could be tweaked to ensure that the video is actually getting rendered with the alpha-channel?

It would be extremely useful to be able to achieve this without having to install the old obsolete Quicktime codecs, which was the way I used to do this on Windows 7. Without some native method within Vegas Pro though, I’m unlikely to use QT.

Thanks in advance for any advice,

O

 

Comments

Marco. wrote on 1/12/2020, 11:19 AM

I think the current Intermediate/ProRes alpha channel support is for 4444 import only.

Musicvid wrote on 1/12/2020, 12:14 PM

I would use Happy Otter Scripts and render to UT 422, which supports Alpha, and has slightly better file size than ProRes.

Another option is to enable Quicktime 7 in the Deprecated tab, and install DNxHD/DNxHR which support Alpha, and are right on par with ProRes..

 

john_dennis wrote on 1/12/2020, 12:46 PM

"It would be extremely useful to be able to achieve this without having to install the old obsolete Quicktime codecs..."

It's possible to have a graphic overlay with transparency without rendering to an intermediate. In Project Media, replace your intermediate file with the Vegas project that you used to create it. It's called nesting. I do it that way all the time. Since I learned about nesting first, it was a long time before I ever used an intermediate with an alpha channel.

Some interesting reading on alpha channel.

Nesting Your Way to Greatness - The Movie

Former user wrote on 1/12/2020, 1:55 PM

Thanks for your replies.

@Musicvid I'll research where to get the installers for these other options, as I have been curious about what else might be available. Anything that is not obsoleted on Windows 10 would be very interesting. I'm curious what the difference will be in the rendered file sizes, since the Magix 422 (which looks great BTW) creates such large files.

@john_dennis Yes, this is what I'm currently, and typically forced to do, is to build and drop a VEG project file into the primary editing project. It works really well where the nested project is simple, but it's when it is of a greater complexity, then combined with other layered tracks of video, that it can become a strain on the computer. In this scenario, I would often prefer to render it to the intermediate.

It would be great to see this added to the Magix 442, or otherwise use some of the others mentioned by Musicvid, and hope too that their file sizes might be a bit smaller. I'll let you know how this works.

Marco. wrote on 1/12/2020, 2:06 PM

A further option is to use CineForm AVI which supports alpha channel export in Vegas Pro.

Musicvid wrote on 1/12/2020, 2:07 PM

@Former user

File Size, PSNR (Shadow Noise) and SSIM (Structural Simililarity) comparisons are all included in my chart for your perusal. ymmv.

Former user wrote on 1/12/2020, 2:10 PM

@Marco. Thanks, I'll check this out too, but with AVI, especially uncompressed, the file sizes can get very large.

@Musicvid Yes, thanks for the great chart, which I've downloaded to my work drive. Very good information.

Musicvid wrote on 1/12/2020, 2:19 PM

You may not know that UT and Magic YUV are the new generation of AVI, no comparison whatsoever to Uncompressed -- in fact, 99% smaller. Don't get hung up over last century's technology.

Marco. wrote on 1/12/2020, 2:20 PM

Though only CineForm RGBA 4444 supports the alpha channel, there are six levels of compression. It's not uncompressed.

Between the highest and the lowest CineForm quality choices the compression ratio varies between about 4:1 and 16:1 (for the RGB versions).

Former user wrote on 1/12/2020, 3:33 PM

@Musicvid Seems Happy Otter Scripts are still in beta; will wait on the final release (already involved in a number of ongoing beta-testing projects).

I've downloaded and installed the Avid Codecs, but they are not visible in Vegas Pro 17. No doubt it's a paths issue, so I'll need to dig deeper to figure out where the installer placed the files, then where to move them so they will appear in VP17's Render As dialog.

@Marco. I was able to find my way to the CineForm-SDK on GitHub, and downloaded the cineform-sdk-master archive. It seems a bit non-trivial to install this on Windows so that it can be used to encode from VP17. When I've got more time for a deep-dive, I'll try to figure it out.

Marco. wrote on 1/12/2020, 4:25 PM

I'm not sure if this still is the way to go but I once installed CineForm just by installing the GoPro Studio software.

fifonik wrote on 1/12/2020, 4:50 PM

I did exactly as @Marco. mentioned a few years ago.

Last changed by fifonik on 1/12/2020, 4:51 PM, changed a total of 2 times.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 5700X, RAM: G'Skill 32 GB DDR4@3200, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer

Former user wrote on 1/12/2020, 4:55 PM

@Marco. It appears that GoPro Studio has been discontinued some time ago, and now they have the newer GoPro Quik. It's a complete unknown (and therefore an even deeper dive down the rabbit hole to find a solution), if this will install the codecs, and if they will be available from within VP17's Render As dialog. I'll give it a try to see.

Any ideas about the paths where codecs should be placed on Windows 10, for them to be usable inside VP17? After installing the Avid codecs, it's unclear how to get them working, although I've activated the deprecated QT in preferences. Surely this is installed somewhere that VP can't use it.

Kind of unfortunate that something so seemingly trivial, is completely unavailable in VP17, but alas, such is life.

Chief24 wrote on 1/12/2020, 5:12 PM

@Former user

Try this link from Derek Moran's (Dr. Zen - MovieStudioZen.com) tutorial. I believe he even updated the location for the GoPro Studio software, which should be something like (2.5.3.xxx or 2.5.9.2658). Watch AND read his tutorial. At his site, he also has a tutorial on installation of DNxHD/DNxHR with the QuickTime installer.

Self Build: #1 MSI TRX40 Pro Wi-Fi w/3960X (be Quiet! Dark Rock Pro TR4) @ stock; 128GB Team Group 3200 MHz; OS/Apps - WDSN850X PCI-e 4.0x4 4TB, Documents/Extras - WDSN850X PCI-e 4.0x4 4TB; XFX AMD Radeon 7900XTX (24.12.1); Samsung 32 Inch UHD 3840x2160; Windows 11 Pro 64-Bit (24H2 26100.2894); (2) Inland Performance 2TB/(2) PNY 3040 4TB PCI-e on Asus Quad M.2x16; (2) WD RED 4TB; ProGrade USB CFExpress/SD card Reader; LG 16X Blu-Ray Burner; 32 inch Samsung UHD 3840x2160.

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS (Happy Otter Scripts); DVD Architect 7.0 (100);

Sound Forge Audio Studio 15; ACID Music Studio 11; SonicFire Pro 6.6.9 (with Vegas Pro/Movie Studio Plug-in); DaVinci Resolve (Free) 19.1.3

#2: Gigabyte TRX50 Aero D w/7960x (Noctua NH-U14S TR5-SP6) @ stock; 128GB Kingston Fury Beast RDIMM @4800 MHz; OS/Apps - Seagate Firecuda 540 2TB PCI-e 5.0x4; Documents/Extras/Source/Transcodes - 4TB WDSN850X PCI-e 4.0x4; 4TB Inland Performance PCI-e 3.0x4; 2TB Inland Performance PCI-e 4.0x4; BlackMagic PCI-e Decklink 4K Mini-Recorder; ProGrade USB SD & Micro SD card readers; LG 32 Inch UHD 3840.x2160: PowerColor Hellhound RX Radeon 7900XT (24.12.1); Windows 11 Pro 64-Bit (24H2 26100.2894)

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS; DVD Architect 7.0 (100); Sound Forge Audo Studio 15; Acid Music Studio 11

Canon EOS R6 MkII, Canon EOS R6, Canon EOS R7 (All three set for 4K 24/30/60 Cinema Gamut/CLog3); GoPro Hero 5+ & 6 Black & (2) 7 Black & 9 Black & 10 Black & 11 Black & 12 Black (All set at highest settings - 4K, 5K, & 5.3K mostly at 29.970); Sony FDR AX-53 HandyCam (4K 100Mbps XAVC-S 23.976/29.970)

Musicvid wrote on 1/12/2020, 5:19 PM

You many be reluctant to try recommended solutions because of appearances, not quantified testing.

Cineform, Happy Otter scripts, UT, Magic, Avid LE, the AVI wrapper in general, all include professional, open source solutions that, unlike ProRes 422, support Alpha, and are being suggested here by professionals.

Do let us know when you find yours.

Former user wrote on 1/12/2020, 5:46 PM

@Chief24 I read through the second article and watched the video about the Avid codecs DNxHD/DNxHR, which was informative, and confirmed that in the VP17 Render As dialog, the QuickTime option is simply not available after installation - which was to-the-letter identical to what they demonstrated - although, as above, I've made certain that the deprecated "Enable the QuickTime plugin" is checked in Preferences/Deprecated Features. This was the first thing I tried on Musicvid's suggestion. Tried everything above including rebooting the PC, but to no avail.

I'll read/watch the other as time permits.

Former user wrote on 1/12/2020, 6:37 PM

Good news: I was able to get the CineForm codec working with alpha-channel. Did a few test renders, and the quality is pretty nice on the higher quality settings. Thanks for everyone's help. Most appreciated.

Musicvid wrote on 1/12/2020, 7:42 PM

Feel free to mark one of the replies as The Solution, if you wish.

joost-berk wrote on 1/13/2020, 1:55 PM

@Former user to create Alpha-channel video's I still use the QuickTime 7 component. Enable it in Preferences/Depricated Features. I do not wan't to use QT7, but I have to. Because with the Animation settings you can create nice alpha's that are decent in file-size/quality.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

fr0sty wrote on 1/13/2020, 4:20 PM

Happy Otter Scripts is still in beta, but it works very well and is highly recommended to be installed on any system that runs Vegas. Basically it is a fully functional app that happens to currently be free because waaag doesn't quite feel it is ready to come out of beta, but many of us have been using it for a long time now, mostly without issue. The functionality it adds is amazing.

You can also use it to render out higher quality deliverable formats.

Last changed by fr0sty on 1/13/2020, 4:22 PM, changed a total of 4 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Former user wrote on 1/15/2020, 6:17 PM

@Musicvid Perhaps a matter of semantics, but personally speaking, The Solution, would ideally be the ability to do this natively within Vegas without needing to install extra codecs and software, while other options one might characterize as The Workaround. Coming from an audio, graphic-design and video editing background though, I'm no stranger to The Workaround workflow, but really appreciate the elegance of more integrated solutions.

@joost-berk Since I was unable to get VP17 to recognize the Avid codecs, I did resort to installing QT as well, which is something I would've preferred to have avoided. If I may ask, what kinds of settings are you typically using to get decent quality, while keeping the rendered file sizes smaller?

@fr0sty Thanks for the additional information and encouragement to explore HOS. I'll try to check it out soon. I'm curious if when you have this installed on your system, if HOS options are available in VP17's, Render As, dialog, or is their use something that must run in parallel with Vegas? Forgive the question, but I truly have no idea about how this works yet.

Thanks again to everyone for their help. It's greatly appreciated.

Musicvid wrote on 1/15/2020, 7:25 PM

The Solution, would ideally be the ability to do this natively within Vegas without needing to install extra codecs and software, while other options one might characterize as The Workaround.

You may be idealizing. Vegas natively supports a number of essential commercially licensed codecs; they cost us a lot of buck$ in our price of purchase. Those licensure agreements are legally binding, often heavily forbidding parallel use of GNU/GPL solutions, except by user download. The other solution is for Magix to write its own code, as it has with ProRes, which still adds to our final cost.

So, would you actually prefer a higher purchase price for Vegas as opposed to the minor inconvenience of adding free third-party open source solutions to fill out the repertoire? Welcome to video editing.

My comment, however, was not about the product, but about your peer forum users, who volunteer their time without reservation. I know Marco is already pleased he was able to facilitate your "workaround," without expecting even an "attaboy." But thoughtfulness as a way of life around here is something we constantly work on, prior expectations notwithstanding. Welcome to the forums; I'm sure that your inquiring nature will make you a valuable asset to our effort.

joost-berk wrote on 1/16/2020, 3:16 AM

@Musicvid Check this settings. These also apply in 3840x2160 and up to 60fps (don't forget to adjust the keyframe settings to match your frame-rate)

This works fast for me, and with moderate file sizes.

First install QT7 (Typical), reboot and start VP17, then in the Render As.. dialog you'll see QuickTime 7 and create a template by clicking "customize" button.

Good luck!

EDIT: TURN "COMPRESSED DEPTH" TO: "32 bpp color" to actually make the Alpha channel work.

Last changed by joost-berk on 1/16/2020, 3:21 AM, changed a total of 1 times.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Musicvid wrote on 1/16/2020, 8:07 AM

I don't really have a need for Animation, Uncompressed, or PNG solutions using QT32.

Yes, they all support Alpha, but are large, unwieldy, and in the case of Animation, which is not lossless, uses inefficient RLE encoding, causing baked-in rounding errors and visible blue ramp banding. It's yesterday's lunchmeat afaiac.

Magic YUV and UT are both far smaller, and mathematically superior AVI alternatives.

You can test this for yourself by downloading the Belle-Nuit Chart, rendering out Uncompressed and Animation samples, and comparing the blue ramp lines in the Vegas Vectorscope. Overall, it's not better than 4:2:2 IMO.

The only .MOV w/Alpha intermediate codecs still on my list are DNxHD / HR and Cineform, which are decent alternatives to ProRes 422 using the Size/Noise/Quality criteria in my chart above, although even they didn't make the cut for other techy logistical reasons.

Archived reading on my 2011 tests are here.

https://www.vegascreativesoftware.info/us/forum/seven-mathematically-lossless-codecs-legacy-article--112259/

And th newer round here.

https://www.vegascreativesoftware.info/us/forum/uncompressed-vs-sony-yuv-vs-magic-yuv-the-shootout--113650/