-
Videoon 8/22/2023
VEGAS Pro 21 Build 108 General Discussion
VP21 -- what is up with the lagginess? Just trying to add an fx hangs up the program for a long time. In my case this appears to be directly related to the use of the Flicker Control fx when set to the "timelapse" present and when "calculate" has been performed. Completely bogs VP down afterward. Note that Flicker Control (as in VP20) still affects per-channel brightness, meaning it introduces a color shift (bad), and in VP21, clicking the "?" for help directs you to the new online system, where Flicker Control help can no longer be found (also bad). I'm also seeing lag issues with some VSTs but will need to do more testing before I post anything.
-
Videoon 6/11/2023
Vegas Pro Crashes a Lot on Every System I've Tried
I think you're right. Life is too short. It is time for me to move on.
-
Videoon 6/11/2023
Vegas Pro Crashes a Lot on Every System I've Tried
VP20 is, right now, chock full of issues. This is entirely understandable, given VP's age and development life cycle (including multiple owners), and the fact that it is (I believe) currently built/dependent on an old, unsupported version of C++. If you've found a way to use Vegas without encountering those issues in your own workflows, I envy you. I do think anyone who claims they never encounter stability issues or broken features within Vegas is likely being a little selective about what they're reporting, but you're right--that is a speculation.
-
Videoon 6/10/2023
Flicker Control Fx Looks Broken
OK, let me make an impassioned plea for why this plugin is useful. Deflicker, Neat Video, and FlickerFree are all paid plugins that address flicker--but they are hard to use and come at terrible render time costs (ie, 10X). For situations in which you're dealing with complex flicker, yes, that's what you have to turn to. But for the very common situation in which you're working with footage shot on a camera using auto exposure, and that produces visible brightness jumps every time the camera adjusts its exposure on a static scene (like GoPro), the Vegas fx does a good job eliminating that, and VP Flicker Control is very light on render times. It's a very useful plugin--or it would be if it worked. Note that it is listed as 32-bit compatible, so it appears to be broken in at least two dimensions.
-
Videoon 6/10/2023
VEGAS Pro Feature Requests
On the efficiency front, if you have the fx plugin window open, I think it would be logical for the plugin window to always show the fx chain for the current, active (selected) clip on the timeline, in the same way that the color grading panel shows the controls for the active clip. In the example below, the fx window would show the fx chain for whichever clip the user click on. This would prevent the frequent situation I encounter in which I'm not sure which clip the fx window is showing, and I mistakenly make an edit to another clip's fx chain thinking I'm working on a different clip. I haven't been able to think of a reason why the current behavior would be desirable. When is it ever valuable to edit one clip's fx settings while looking at a different clip?
-
Videoon 6/7/2023
Vegas Pro Crashes a Lot on Every System I've Tried
There are plenty of people here who will attest that Vegas on their machine as they use it is stable. I assume they're not all being dishonest--but I also assume they have very specific workflows with very Vegas-friendly codecs and they don't tend to try new things. My experience is somewhat different. I have never used any app, from paid to freeware (and I've probably used thousands), that crashes with such frequency and ferocity, in so many different ways, across so many different versions. So, without disputing the experience of those for whom "Vegas works," I think it would be perfectly reasonable to switch to something like Resolve, which is better in many ways, and be done with it. If you're going to stick around, I think you need to make peace with the idea that Vegas will probably forever remain an aging app patched within an inch of its life unless the developer abandons it or the IP is somehow purchased by a company with a great deal more resources. They do make incremental improvements here, but usually at the cost of introducing new issues. Ultimately, you have to decide what you can live with. Maybe I'm just old and cranky, but I hate the idea of giving up the ease and speed of Vegas's timeline editing and adapting to Resolve's way of doing things. Which is a long way of saying, you'll have more of the same with VP20.
-
Videoon 6/7/2023
Help With Color Grading Panel Controls
Interesting but not exactly what I'm looking for. What I'd like is to be able to click into the text box below the sliders and then use (for example) the up/down arrow keys or the +/- keys to increment the values. @VEGASDerek note that the numberkey controls, while super cool, are going to be useless for anyone who edits in-the-field on a laptop (like me). Since I'm making a shopping list here, it would also be useful if there were a click-and-hold bypass control on each color wheel so that I could do an immediate A/B comparison of that specific wheel's effect (rather than having to use the reset button and Control-Z).
-
Videoon 6/6/2023
Help With Color Grading Panel Controls
That's helpful -- thank you. Are there any keyboard shortcuts for incrementing the values?
-
Videoon 6/3/2023
No MP3 VP20 Build 403
Okay, I got MP3 back. Apparently to reset the program you need to hold crtl+shift and double-click a desktop shortcut. Trying that with a start menu shortcut doesn't work. Fantastic.
-
Videoon 5/30/2023
In my video renders I get very random sporadic black frames
if you are rendering in 32-bit and using the color curves fx, see: https://www.vegascreativesoftware.info/us/forum/32-bit-video-renders-brightness-flickering--138356/
-
Videoon 5/11/2023
Build 403 Explorer Issues, Match Media not Remembering
I have noticed strange things going on in the explorer window for several versions now, but with Vegas you've got to choose your battles...
-
Videoon 5/4/2023
VP20 403 Hanging on VST Scan
Obviously it's a busy day. I don't use any of the built-in Magix VST's, so disabling them is fine for me, but it would be odd if I'm the only one who sees that dialogue box. Clean install on clean install of Windows 11.
-
Videoon 5/4/2023
VP20 403 Hanging on VST Scan
clicking "abort" repeatedly, then unchecking all the Magix VST's (in preferences --> VSTs) seems to be a workaround
-
Videoon 5/3/2023
NEW Vegas Pro build (402/403) !
Getting the Splash screen when I click the start icon for 402, but then the program just vanishes and nothing happens. No process to kill in task manager. I wonder if they were trying to fix the "Vegas Won't Start" issue ? Restarting my machine doesn't help. Looks like I'm reverting...
-
Videoon 4/30/2023
No Hevc in Pro20? Crashes when importing. Today won´t even start
My recommendation would be to allow Vegas to create proxies (or create them manually) @ALO ? can you not create proxy? By "manually" I just meant if automatic proxy creation is off, and you have an existing project, you can right-click the media in the project media bin and select "create proxy". I'll update my sig, although I use multiple machines :)
-
Videoon 4/29/2023
No Hevc in Pro20? Crashes when importing. Today won´t even start
I continue to experience a great deal of stability issues in the current build using a variety of HEVC formats. My recommendation would be to allow Vegas to create proxies (or create them manually) and only edit in 8-bit mode. Rendering in 32-bit is tricky--some of the fx plugs are broken w/respect to HEVC, so you may just want to render out in 8-bit for now and hope the developers release something that works better with HEVC and 32-bit soon.
-
Videoon 3/31/2023
Is Deinterlace Broken in VP20/370?
Ok, this is weird. It's not the camera. If I drag the interlaced clip into an empty (new) timeline, it deinterlaces properly (I use "interpolate") when I switch project properties to progressive. But if I drag a GoPro 5K HEVC clip onto an empty timeline *first*, and then add my interlaced clip, it won't deinterlace. So looks like more HEVC Vegas woes here. I'll play around with this some more and see if I can come up with something that will be easy to replicate Edit: this also happens w/HEVC footage from my FX30, and 8-bit H264 from my RX100
-
Offtopicon 3/31/2023
Adobe is #3
Also note that Adobe is not a small company. If they're flying these people to SF for a junket, that tells you how seriously they care about what the YT crowd is saying about their product, and about Resolve.
-
Offtopicon 3/31/2023
Adobe is #3
my point would be, at least within this circle (which is not trivial--those are influencers with a great many followers), Vegas is not currently part of the conversation. And that's not a good thing.
-
Videoon 3/28/2023
Is Deinterlace Broken in VP20/370?
I don't believe anyone mentioned GPU. Did the read the responses? Yes, it wasn't relevant. Looks like this is happening only with footage from one specific camera. I've deinterlaced in photoshop so that solves the immediate problem. Maybe will send problematic clip to developers
-
Videoon 3/28/2023
Is Deinterlace Broken in VP20/370?
Reason that you set/change the media properties? Let it as it be. makes no difference. GPU on/off/auto makes no difference either
-
Videoon 3/18/2023
Having Problems with VEGAS 20? (Only users of V20 Build 326, Please)
In 32-bit full range mode w/ACES (view transform) enabled and GPU either off or in hybrid (Intel) mode, Vegas does not correctly display SLOG3 media, as described here: https://www.vegascreativesoftware.info/us/forum/vegas-32-full-range-mode-does-not-correctly-decode-sony-slog3--140150/
-
Videoon 3/16/2023
Vegas 32 (Full Range) Mode Does Not Correctly Decode Sony SLOG3
Ok, but who wants to work really with disabled GPU? Especially with the 32bit mode and ACES? I don't myself, but in my case, I was using hybrid (Intel) mode so that my fx would update in real time when I make adjustments, which is why I noticed the issue. In any case, I think it's for the developers to deal with (or not) at this point. The clips I linked to are all from the same shoot -- SLOG3 on a Sony A7SIII, I believe. Don't think it matters -- should be replicable with any 10bit SLOG3.
-
Videoon 3/16/2023
Vegas 32 (Full Range) Mode Does Not Correctly Decode Sony SLOG3
Here is another clip from the YT channel with more greens in it. I am testing this with my GPU on/off. I believe you'll find this is a better example of what I'm describing: 32 FR w/GPU off: That's unacceptable. 32 FR w/GPU on: That looks properly decoded to me. 8-bit (legacy) with the Sony LUT applied and a studio-to-computer levels correction: The colors match. There are some differences, but you could absolutely work with this in 8-bit mode if you wanted to.
ALO
Offline, Last login 9/20/2023, Member since 10/26/2016