"Proper Exposure" from Photoshop, from over 10 years ago:
" Brightness/Contrast applies proportionate (nonlinear) adjustments to image layer"
"When Use Legacy is selected, Brightness/Contrast simply shifts all pixel values higher or lower when adjusting brightness. Since this can cause clipping or loss of image detail in highlight or shadow areas, using Brightness/Contrast in Legacy mode is not recommended for photographic images"
the "nonlinear" is the key there. The Vegas "exposure" adjustments is linear, AKA, the "legacy" mode.
i use scripts to automate plugins to "fix" this deficiency, since, forever.
Photoshop updated their adjustment a decade ago, to a better (and "correct") method. A proper "exposure" slider should be in Vegas Levels and CC since day one.
If my coding skill were... 3000 times better, i would do a plugin myself.
I am also late to give early feedback on VP17, I took my time to test most of the new features and benchmark. Let me tell you I love this release, I will definitely use a lot of the new features. The developers, testers, architects and Gary have done a good job with this release. I get the impression reading some of the posts over the last year users may think some of the VP16 new features are less impressive/useful than VP17, but I am sure VP16 was a necessary step towards VP17.
The new color grading looks awesome, and a bit overwhelming as I am not the greatest colorist. I need to learn more I suppose, I mostly used in the past an "auto contrast" plugin for boosting the vibrance and that's it.
As for the bad, the VP17 Boris plugin debacle, I was fortunate not to have issues, probably because I had the full latest Continuum installed. I did ran into a reproducible crash, not everyone will suffer from it, and there is a work-around, see dedicated post https://www.vegascreativesoftware.info/us/forum/v17-always-crashes-on-opening-vp-after-closing-vp-with-a-saved-project--116732/
I also see a number of VP17 complaints (again) in the posts with a dynamic RAM configuration default or other than 0 when rendering with NVIDEA, well this is my all-time Vegas gripe (13/14/15/16, and now 17 as well???!!!). Common guys what is going on with that? I had also had issues with this on former Vegas versions, on different hardware (different PC's I build with different videocards … ).
@gary-rebholz
Facebook what is that? I can state this since I do not have a facebook account, and probably never will. Maybe unfortunate to miss out company stuff, but I can live with that. Who still knows what the relation between a pencil and a cassette is? Or has used a fax machine lately? Who will still use Facebook 10 years from now?
But I am deviating, one thing I still miss, is a way/template to render in one go using NVIDEA HW acceleration video and 5.1 audio, and not rendering 2x (e.g. 1x audio ac3 and 1x video) and merging/muxing it together with some external tooling. I want to do this in one go within Vegas. And I am not talking about blue ray 5.1
"Proper Exposure" from Photoshop, from over 10 years ago:
" Brightness/Contrast applies proportionate (nonlinear) adjustments to image layer"
"When Use Legacy is selected, Brightness/Contrast simply shifts all pixel values higher or lower when adjusting brightness. Since this can cause clipping or loss of image detail in highlight or shadow areas, using Brightness/Contrast in Legacy mode is not recommended for photographic images"
the "nonlinear" is the key there. The Vegas "exposure" adjustments is linear, AKA, the "legacy" mode.
i use scripts to automate plugins to "fix" this deficiency, since, forever.
Photoshop updated their adjustment a decade ago, to a better (and "correct") method. A proper "exposure" slider should be in Vegas Levels and CC since day one.
If my coding skill were... 3000 times better, i would do a plugin myself.
Hi, malowz!
The "Gamma" slider in "VEGAS Levels" will give you what you want. 🙂
Gamma is different, it affects a different part of the curve with a different power function as most modern exposure adjustments do.
I am testing V17 and there is some issue, GPU acceleration is not available. In Vegas 16 my GTX1060 is used without any problems.
Why is GTX1060 missing in Vegas17 ?? Thank you.
SOLVED
Which driverversion for that card are you using?
Gamma is different, it affects a different part of the curve with a different power function as most modern exposure adjustments do.
Well, add a nice S shaped curve (Color Curves) afterwards...and get away just like that. 😇
j-v: Funny ... I was on last version, but after some Windows update, the drivers step back to version 388.73.
So after new driver installation, GPU acceleration is available. Thank you.
Apologies for bumping an old thread.
@malowz explained his clever exposure adjustment workflow in this comment (more than 10 years ago) and raised it again here. For anyone interested in this, it's worth reading the ensuing discussion on those threads.
I imagine it would be fairly straightforward to engineer that chain of 3 existing FX into a single new "Exposure" FX and/or Color Grading Panel control.
Check the Exposure control in the Independent Controls section of the Input/Output tab on the new Color Grading panel. This is the logarithmic adjustment the original poster noted as missing. The individual Gamma adjustments for each channel on the Color Channels tab can also be helpful. The math is a little different because we're not inverting the way it's been suggested in this discussion (I can't take credit for knowing this...the developers only make me look smart!), but does it give you what you need regardless?
Gary, the exposure control in the Color Grading panel isn't logarithmic but a linear multiply math. It just rotates a linear luma curve around its zero point.
@gary-rebholz Hopefully this video explains.
I'll just add that there is room in that "Independent Controls" section of the CGP to add an exposure control like this.
Yes, Nick, the given Explosure control does exactly same thing and uses same linear math as the Gain controls do.
Yes, you guys are right, of course. I misunderstood what the devs were telling me was going on. Sorry for the confusion. Despite my thickness, we do understand what you're asking for.
Am looking forward to the AMD functionality returning in the first upgrade to 17.
Has anyone tried DPX 10 bit, both in and out for unity?
Am looking forward to the AMD functionality returning in the first upgrade to 17.
It never left... it just wasn't added for GPU decode yet because the dev team didn't feel it was stable and fast enough yet.
I upgraded today. It looks like the biggest update in the last few years. The new features are very useful.
Good job Magix!
[...] I get tired of explaining the complete and utter frustration of the program not saving your position when you close the program (seems like a simple thing) so you don't have to go find where you were just working.....[...]
Oh man, would that be a time saver or what. I have about a dozen projects on the go at any one time and having the program open where I left off in any particular project? The amount of time I spend re-orienting myself to a particular project makes me weep for the time flying away... I would LOVE Vegas to save project state upon close (even an option setting)!
OMG, I'm still on VP15 and would have upgraded to 17 in a heartbeat if this was a feature!
Squeaky wheel gets the grease... keep requesting it, I'm sure the devs are listening.
[...] I get tired of explaining the complete and utter frustration of the program not saving your position when you close the program (seems like a simple thing) so you don't have to go find where you were just working.....[...]
Oh man, would that be a time saver or what. I have about a dozen projects on the go at any one time and having the program open where I left off in any particular project? The amount of time I spend re-orienting myself to a particular project makes me weep for the time flying away... I would LOVE Vegas to save project state upon close (even an option setting)!
OMG, I'm still on VP15 and would have upgraded to 17 in a heartbeat if this was a feature!
Yes, but that is a feature, should they do so (and let's, please) that they'll never advertise, because it is like a no-brainer. It might cause embarrassment. I mean, seriously, these developers DON'T actually USE this program, and that is the shame of all of this. I mean, they can't - it's impossible - and let these sort of "duh" features just get bypassed year after year. Don't get me started. 'Hamburger menu' is their idea of slick..... not trying to be disrespectful, but if people actually USED the program, I wouldn't be commenting like this.
Note to Mathias and Magix: - do HIRE some people that use the program in a serious, complex way, in-house "user consultants" or something. I mean, people that composite and not just butt clips together with some transitions.
Since you seem to know what they should address, why don't you lay out some feature requests to help guide them along? Criticism is worthless if you don't include the constructive side of it. What changes would better suit you?
To think that the developers don't use the program is on the verge of being disrespectful, even if you say: "not trying to be disrespectful". I personally know that they are using the software and in my opinion it is not understandable nor okay to insinuate otherwise. I appreciate @fr0sty for trying to take a step back and getting the conversation on a constructive level.
@zdogg If you want to have a constructive discussion about an existing function or a special feature request you can create a new thread. This helps us the most because we can see how other users react to your suggestions. If that's not for you, you can direct message me. I will then forward your ideas internally.
Regardless, I think that we heard A LOT of opinion (positive and negative) about the first impressions. We have observed the discussion very closely and gained good insights. Nevertheless, we should move on from this thread. This is why I'm closing the thread.
So for now, thank you all for your comments! 🙂✌️