How do I apply different adjustment layers to different tracks?

Cliff Etzel wrote on 4/23/2018, 9:14 PM

I'm trying to figure out how I can apply an adjustment layer to one track without it affecting the others. I could do that in Premiere Pro no problem but I can't seem to figure out how to do this in Vegas Pro 14.

I have a track of clips I want to apply a chain of plugins to. That I have already done. Now I want to apply a different adjustment layer to another group of clips on another video track without it affecting the clips beneath it - I can't seem to find any info on how to accomplish this - ANYONE?

Comments

Former user wrote on 4/23/2018, 9:56 PM

Vegas does not have adjustment layers. Without knowing what plugins you are using, it is hard to give any advice.

Cliff Etzel wrote on 4/24/2018, 12:38 AM

I'm applying a LUT via VisionColor, Neat Video and Vegas Vignette and possibly Levels

GJeffrey wrote on 4/24/2018, 1:12 AM

Add your fx at track level. This only affect one track at a time

NickHope wrote on 4/24/2018, 1:59 AM

If it's applied at track level, the VisionColor LUTPlugin suffers the same bug as the VEGAS LUT Filter does in VP15. You'll get a jump in levels at the end of a fade rather than a graceful fade to nothing.

Not a problem if you're not using opacity or fades at all, but if you are then it's better to apply it as a media FX or event FX. Copy > Paste Event Attributes can help with that if you do it before applying other stuff to the target events.

Expect the VisionColor plugin to be really really slow.

With VEGAS it's important to understand how you can apply FX at any or all of media level, track level, event level or project level.

Cliff Etzel wrote on 4/24/2018, 12:28 PM

If it's applied at track level, the VisionColor LUTPlugin suffers the same bug as the VEGAS LUT Filter does in VP15. You'll get a jump in levels at the end of a fade rather than a graceful fade to nothing.

Not a problem if you're not using opacity or fades at all, but if you are then it's better to apply it as a media FX or event FX. Copy > Paste Event Attributes can help with that if you do it before applying other stuff to the target events.

Expect the VisionColor plugin to be really really slow.

With VEGAS it's important to understand how you can apply FX at any or all of media level, track level, event level or project level.

Thanks Nick - the primary reason I asked so that I wasnt' constantly unticking the LUT plugin while editing. With regards to the order - What is the best standards of practice for doing this?

OldSmoke wrote on 4/24/2018, 12:42 PM

If it's applied at track level, the VisionColor LUTPlugin suffers the same bug as the VEGAS LUT Filter does in VP15. You'll get a jump in levels at the end of a fade rather than a graceful fade to nothing.

Not a problem if you're not using opacity or fades at all, but if you are then it's better to apply it as a media FX or event FX. Copy > Paste Event Attributes can help with that if you do it before applying other stuff to the target events.

Expect the VisionColor plugin to be really really slow.

With VEGAS it's important to understand how you can apply FX at any or all of media level, track level, event level or project level.

Thanks Nick - the primary reason I asked so that I wasnt' constantly unticking the LUT plugin while editing. With regards to the order - What is the best standards of practice for doing this?

If you do a general LUT across all media, why not do in Catalyst Browse prior to ingesting the footage into Vegas for editing? LUT plugins in Vegas are really slow aside from Magix own in VP15.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Cliff Etzel wrote on 4/24/2018, 12:49 PM

If it's applied at track level, the VisionColor LUTPlugin suffers the same bug as the VEGAS LUT Filter does in VP15. You'll get a jump in levels at the end of a fade rather than a graceful fade to nothing.

Not a problem if you're not using opacity or fades at all, but if you are then it's better to apply it as a media FX or event FX. Copy > Paste Event Attributes can help with that if you do it before applying other stuff to the target events.

Expect the VisionColor plugin to be really really slow.

With VEGAS it's important to understand how you can apply FX at any or all of media level, track level, event level or project level.

Thanks Nick - the primary reason I asked so that I wasnt' constantly unticking the LUT plugin while editing. With regards to the order - What is the best standards of practice for doing this?

If you do a general LUT across all media, why not do in Catalyst Browse prior to ingesting the footage into Vegas for editing? LUT plugins in Vegas are really slow aside from Magix own in VP15.

I"m still getting a hang for all this in Vegas now. I've spent the better part of 4 days comparing VP14 with Premiere Pro CS6 and Resolve 14 - lets just say, Premiere is bloated, slower to work in, has more bugs and renders are mind numbing. Rendering out the same timeline in Vegas Pro takes 1/3 the time as long as I don't use the Vegas2Handbrake script with it's associated audio drift issues I recently discovered.

I'll look at the option of adding LUT's to my clips before importing into Vegas Pro (I don't normally use LUTS but I'm shooting more flat and neutral and was wanting a quick solution for adding contrast and skin tone back to my current projects clips). Thanks for the idea of doing that.

fr0sty wrote on 4/25/2018, 12:57 AM

"If you do a general LUT across all media, why not do in Catalyst Browse prior to ingesting the footage into Vegas for editing?"

It adds yet another encode step to the editing process, reducing quality and increasing production time, I prefer to edit in the native format I shot in when possible.

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

NickHope wrote on 4/25/2018, 7:12 AM

If it's applied at track level, the VisionColor LUTPlugin suffers the same bug as the VEGAS LUT Filter does in VP15. You'll get a jump in levels at the end of a fade rather than a graceful fade to nothing.

Not a problem if you're not using opacity or fades at all, but if you are then it's better to apply it as a media FX or event FX. Copy > Paste Event Attributes can help with that if you do it before applying other stuff to the target events.

Expect the VisionColor plugin to be really really slow.

With VEGAS it's important to understand how you can apply FX at any or all of media level, track level, event level or project level.

Thanks Nick - the primary reason I asked so that I wasnt' constantly unticking the LUT plugin while editing. With regards to the order - What is the best standards of practice for doing this?

It all depends what you're doing and which works best for your workflow style.

Personally I never add any FX at media or project level. I nearly always do it all at event level. Sometimes at track level if, to state the obvious, I want all the events on a track to be affected. But then I personally don't use LUTs at all because:

  1. I don't shoot log or other flat profile where the application of a generic LUT to everything might be appropriate.
  2. Most of my stuff is underwater and therefore all over the place in terms of levels, color balance etc., and needs fixing on an event-by-event basis (but usually starting with a preset).
  3. I prefer to just use Color Curves, and have been quite happy with results when I've mimicked LUTs with Color Curves (here was an example). Admittedly I'm only working with 8-bit. In fact I believe that if you use good practices with Color Curves (e.g. controlling the whole curve with just the 2 end tangents, so you get a nice smooth curve) then you can improve on many off-the-shelf "look" LUTs, many of which do pretty silly things with your footage.

If nothing else you can approximate a LUT with a Color Curves or other FX and then use it a bit like a proxy, being much more performant than the Vision Color plugin, then swap it out for the LUT at render time if you really want.

Which LUT are you using? Pls share link if you're allowed. I could attempt to mimick it with Color Curves or other effects.

OldSmoke wrote on 4/25/2018, 7:28 AM

"If you do a general LUT across all media, why not do in Catalyst Browse prior to ingesting the footage into Vegas for editing?"

It adds yet another encode step to the editing process, reducing quality and increasing production time, I prefer to edit in the native format I shot in when possible.

I don’t agree with that assessment. The increased production time is alan rd off by the increased render time in the NLE, building of proxies if the native format doesn’t work well or the LUT plugin is slow especially with 4K and 10bit.

You may be right that quality is decreased but to what extend and it also depends on the codec used.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)