Adjustment Events on Don't Work on Most Blend Modes on Tracks. VP22

ghostt wrote on 9/21/2024, 10:05 AM

Build 122, as well as previous builds of Vegas 22, and 21, but works on first build of Vegas 21, build 108.

Placing an Adjustment Event onto a track with a blend mode (dodge,burn,darken,overlay,cut,multiply mask,subtract) will either do nothing, or if there's pan-crop on the adjustment event it will break the preview making it black (using the behavior on a dodge track as an example)

Alternatively on older versions of VP21 (in this example, VP21 build 108), doing this will act as if you placed a duplicate of the layer below, as it should. Allowing you to pan-crop and apply effects on different blend modes

Comments

Vextoh wrote on 9/21/2024, 10:17 AM

I have also been experiencing this issue, would be great if this would be looked into.

Steve_Rhoden wrote on 9/21/2024, 12:21 PM

@ghostt  No, that's not how an adjustment layer should function. There should be no duplicate of the layer below. Look at how an adjustment layer functions in After Effects.

@Vextoh This has already been looked into very thoroughly.

How it was earlier in VP21 build 108, was not fully how an adjustment layer should properly function.... At an overwhelming request by a majority of Vegas users and in collaboration with the Vegas developers, numerous adjustments and tests were carried out over many months to improve and refine this new feature...... How it functions now in Vegas 22 and last build of Vegas 21 is how an Adjustment Layer should be.

ghostt wrote on 9/21/2024, 12:53 PM

Sorry what? You do realize I'm saying they don't function at ALL on a track with a blending mode applied. You can't tell me seriously that putting an adjustment event on a DODGE blending mode, would make the preview black? A dodge blending mode doesn't even display black in any normal circumstances so how would it display black in the preview. Adjustment events have no use on blending layers in the current state if this is how they are "meant" to work

lan-mLMC wrote on 9/21/2024, 2:26 PM

According to other industry standard software such as Adobe After Efdects, the adjustment event is only used to apply FX to the lower track. It's best to put it on a separate track.

And you shouldn't apply blend mode to it. Because it does not have any effective pixels.

ghostt wrote on 9/21/2024, 2:38 PM

The way it functioned previously it "did" though, and had a actual practical function by allowing you to mix effects in different ways, this didn't effect the other normal functions of adjustment events, it was useful and worked fine. For example, in vegas, you can add a adjustment event with pan-crop on it, then set the adjustment event to 50% opacity which will easily and efficiently create a ghosting effect, in prior versions not only would this work fine, you could also place the adjustment event onto a blended layer which would then make the ghosting effect follow whichever blending mode you have applied.

Not only that, if they truly had "no effective pixels" in vegas in practice, the effect of putting it on a dodge layer wouldn't black out the video, it would do nothing. There is a issue here.

ghostt wrote on 9/21/2024, 3:17 PM

This is how it behaves in After Effects. This is exactly what it doesn't do in vegas, it just blacks out the preview. Now, it USED to do this it the previous builds of Vegas 21 exactly as I explained in the original post, so please explain to me how I'm wrong

LdM_Edit wrote on 9/22/2024, 5:16 AM

One of the things I like about VEGAS Pro is how flexible it is. I don't feel so constrained by the interface to work in a particular way. In coherence with that, and regarding the issue of this thread, I think it would be nice if the user had the option to choose whether adjustment events works the way they do now, or how they did initially. Even better if this could be changed at the event level. Something like a "Use compositing mode" button. I don't know if that is possible.

ghostt wrote on 9/22/2024, 7:24 AM

This isn't really a one or another type of issue, they work the exact same way outside of just not working on blend layers. Like I mean exactly the same, in the current state you are only missing out on a possible use of adjustment events that worked normally in prior builds

ghostt wrote on 9/22/2024, 8:49 AM

what

ghostt wrote on 9/22/2024, 8:50 AM

can you give me an example of a issue that would come from fixing adjustment events on blend layers

Dexcon wrote on 9/22/2024, 9:05 AM

As a new forum member, you may be unaware that you can edit a comment within half an hour after posting that comment thus avoiding the need to add a new comment to add to the previous comment. For example, your comment of "what" could have been edited to:

what ... can you give me an example of a issue that would come from fixing adjustment events on blend layers

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

ghostt wrote on 9/22/2024, 9:42 AM

Even better, here is how it behaved in Vegas 21 Build 108, and for comparison I've also placed the comparison to how they behave "According to other industry standard software such as Adobe After Efdects"


@ghostt  No, that's not how an adjustment layer should function. There should be no duplicate of the layer below. Look at how an adjustment layer functions in After Effects.

@Vextoh This has already been looked into very thoroughly.

How it was earlier in VP21 build 108, was not fully how an adjustment layer should properly function.... At an overwhelming request by a majority of Vegas users and in collaboration with the Vegas developers, numerous adjustments and tests were carried out over many months to improve and refine this new feature...... How it functions now in Vegas 22 and last build of Vegas 21 is how an Adjustment Layer should be.

Yes, this is how they should function.

According to other industry standard software such as Adobe After Efdects, the adjustment event is only used to apply FX to the lower track. It's best to put it on a separate track.

And you shouldn't apply blend mode to it. Because it does not have any effective pixels.

 

RogerS wrote on 9/22/2024, 12:23 PM

@ghostt The old implementation of Adjustment Events was completely broken for any Fx that moved pixels around: https://www.vegascreativesoftware.info/us/forum/error-vegas-pro-21-adjustment-event-and-picture-in-picture--142173/#ca896499

ghostt wrote on 9/22/2024, 2:13 PM

@ghostt The old implementation of Adjustment Events was completely broken for any Fx that moved pixels around: https://www.vegascreativesoftware.info/us/forum/error-vegas-pro-21-adjustment-event-and-picture-in-picture--142173/#ca896499

Never did I say I wanted the "old implementation" I'm saying the current implementation does not behave as an adjustment event should, or does, in other software (ex After Effects)

also, it DID work correctly in the old implementation, as opposed to what @lan-mLMC and @Steve_Rhoden said.

This is unrelated to the issue

RogerS wrote on 9/22/2024, 4:49 PM

The current implementation may well have a bug that emerged from fixing this serious issue with the old implementation that made adjustment events useless for many Fx. So it's likely related to the issue.

ghostt wrote on 9/22/2024, 5:08 PM

The current implementation may well have a bug that emerged from fixing this serious issue with the old implementation that made adjustment events useless for many Fx. So it's likely related to the issue.

Yeah it definitely does have a bug of some sort

That's all I wanted to report, but then I was told I was wrong about the basic functions of a adjustment layer/event in Vegas and in After Effects. Let alone by a moderator on the forum lmao

Thank you for actually considering what I have to say and I hope this can be forwarded to some developers and fixed in an update as in the end we all want a better software for us all to use

Steve_Rhoden wrote on 9/22/2024, 5:48 PM

@ghostt Yes, That is exactly what i told you.... Because how it functioned in Vegas 21 build 108 is not how an adjustment layer functions.

ghostt wrote on 9/22/2024, 5:59 PM

@ghostt Yes, That is exactly what i told you.... Because how it functioned in Vegas 21 build 108 is not how an adjustment layer functions.

haha, please look at my other replies with the youtube videos for a comparison 👍

actually here they are again
Vegas 21 build 108
After Effects (what you compared it to)

Notice how they work the same, now if you would like to, please try the same thing in Vegas 22 and let me know how it turns out (it will do nothing, or break the preview, which is not correct)

RogerS wrote on 9/22/2024, 6:19 PM

I did a quick test of this in 22.122.

If the track with the adjustment event has add, source alpha, screen, lighten, difference applied the blend mode doesn't do anything.

If hard light or difference squared the blending mode does something.

Every other mode is just pure black.

If I delete the adjustment event the result in these other modes is also pure black so I think they aren't taking the adjustment event into account when doing the calculation?

This couldn't be how it was intended to function.

ghostt wrote on 9/22/2024, 6:24 PM

I did a quick test of this in 22.122.

If the track with the adjustment event has add, source alpha, screen, lighten, difference applied the blend mode doesn't do anything.

If hard light or difference squared the blending mode does something.

Every other mode is just pure black.

If I delete the adjustment event the result in these other modes is also pure black so I think they aren't taking the adjustment event into account when doing the calculation?

This couldn't be how it was intended to function.

Yeah also not sure if you tried this already but also, I believe pan-crop on the adjustment event will cause a black screen on most if not all of the blend modes (besides default) I can't remember exactly but I know it does it on dodge, burn, darken, and subtract for sure

RogerS wrote on 9/22/2024, 6:52 PM

In my quick test I didn't see a difference with pan/crop used or not. I used inverse as the adjustment event Fx as it's obvious what it does.

ghostt wrote on 9/22/2024, 7:04 PM

In my quick test I didn't see a difference with pan/crop used or not. I used inverse as the adjustment event Fx as it's obvious what it does.

Got it yeah, in my test a adjustment event with no fx and pan-crop applied seemed to make the video black, maybe try the same setup? Dodge with a adjustment event with no fx (not sure if it matters, but its the same as the test I did on the old build of vegas in the youtube video) and some pan-crop applied, then maybe cycle through the other blending modes

Thank you for testing it on your end

RogerS wrote on 9/23/2024, 1:35 AM

You're right. I think this is an additional issue, as soon as you hit pan/crop the image breaks and it goes black. Restore to defaults and the image returns.

My guess here is that nobody thought to crop an adjustment event (not really sure when that would be useful to do, so maybe the functionality should just be disabled?)

I put pan/crop back to normal and then just added invert and it also goes black with the dodge blending mode:

I can see how a track blending mode + adjustment event could be useful so think this should be fixed vs disabled.