-
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.
-
Videoon 3/16/2023
Vegas 32 (Full Range) Mode Does Not Correctly Decode Sony SLOG3
@Wolfgang S. I misunderstood the point you were trying to make regarding levels. I regret the error.
-
Videoon 3/15/2023
Vegas 32 (Full Range) Mode Does Not Correctly Decode Sony SLOG3
I trust Vegas in 8-bit mode and I trust the Sony LUT. So that look is what I would consider "correct" (meaning, the log file has been accurately decoded as a starting point for your grade/look). I have shown you the use of the 8bit legacy mode instead of the 8bit full mode was the reason for the difference to the ACES mode. A clear error, because the slog3 footage does not follow the legal range but the full range in most cases. And even more important: the Sony-LUT has also been designed for full edited
-
Videoon 3/14/2023
Vegas 32 (Full Range) Mode Does Not Correctly Decode Sony SLOG3
I am. I use ACES to get DPX Image sequence out of Vegas, needed for DCP creation. DCP player then perfectly matches Vegas's preview. Export In 32 bit float doesn't. With TIFF there's also a mismatch, and 8 bit for me is a meh anyway...😂 I know there are people who have to use ACES for industry reasons/collaboration, but if you have a choice, I think there are better/more modern options
-
Videoon 3/14/2023
Vegas 32 (Full Range) Mode Does Not Correctly Decode Sony SLOG3
I trust Vegas in 8-bit mode and I trust the Sony LUT. So that look is what I would consider "correct" (meaning, the log file has been accurately decoded as a starting point for your grade/look). Resolve is too widely used to get this wrong, so you can trust that also (albeit with Resolve's slightly different color space handling). The Vegas 32/FR implementation is definitely askew, esp again if you work with footage with the right shades of green in it. Have no idea why GPU on/off makes a difference, but clearly it does. That would confirm to me that you are seeing a bug rather than just a "small difference." If you're going to use SLOG3 in Vegas, my recommendation would be to use Vegas 32/Video Levels and the Sony LUT as your starting point. I'm not a fan of ACES even when it's working correctly. :)
-
Videoon 3/11/2023
So Confused, and ready to throw in the towel.
@Wolfgang S. Vegas' 32-bit Full Range mode is flat-out broken for working with SLOG3, at least for the media I've tried. At some point I may try to post about that on the VP20 issues thread, but there are more issues than I have time to report. As far as the color grading tools being outdated, look at what the (free) competition offers: That's just one tiny aspect of Resolve's tools! This is simply wrong, the slog and vlog workflow works in Vegas. What do you think that I do since years with my FS7 or EVA1 10bit log footage? 👍 I'll detail this out in the VP20 bug thread. 32FR improperly decodes SLOG3/SGamut3 footage. But I will need a little time. Note that I'm referring to Vegas in 32FR mode. In 32 video levels mode, provided you stay away from the broken plugin chain fx, you can properly decode SLOG3 using the LUT filter. You should have no trouble seeing the difference if you switch between the two modes (properly configured). Sorry to go off-topic!
-
Videoon 3/11/2023
Having Problems with VEGAS 20? (Only users of V20 Build 326, Please)
For both VST2 & VST3, Sonible plugins like Smartlimit don't store their settings when you close and reset Vegas -- it they go back to their default state, and your custom settings are lost. You only get the settings applied if you render out before you close the program. This one bites particularly hard because Smartlimit is so useful for getting the loudness targets right for your deliverables, and Vegas crashes/glitches require frequent restarts. originally mentioned here: https://www.vegascreativesoftware.info/us/forum/vegas-pro-resets-sonible-vst3-plugins-on-close-restart--139710/
-
Videoon 3/10/2023
So Confused, and ready to throw in the towel.
The grading of 10bit slog3 can be done with Vegas, and I do not see why the the color grading portal is outdated (it has been developed in the last to upgrades). True, there are still some bugs in the HDR workflow, but you can grade the different log formats like slog or vlog in an appropriate way. Examples see here: https://www.vegascreativesoftware.info/de/forum/render-to-4k-make-artefacts-and-random-dropping-frames--139806/?page=2#ca874207 @Wolfgang S. Vegas' 32-bit Full Range mode is flat-out broken for working with SLOG3, at least for the media I've tried. At some point I may try to post about that on the VP20 issues thread, but there are more issues than I have time to report. As far as the color grading tools being outdated, look at what the (free) competition offers: That's just one tiny aspect of Resolve's tools!
-
Videoon 3/10/2023
Having Problems with VEGAS 20? (Only users of V20 Build 326, Please)
Adding any VST3 from the Ozone RX10 Advanced suite to an audio clip at the clip level instantly causes Vegas to freeze. Vegas was able to auto-generate an error report, which I sent to Magix, when I killed the app via the task manager.
-
Videoon 3/7/2023
So Confused, and ready to throw in the towel.
I've been a more than loyal customer since audio-only V1. Tonight when I click on Vegas to launch, nothing happens. Last night I finished rendering a project with minimal issues. I removed one static image (jpg) and replaced it with another image (jpg) At that point, I could not render the project. It would hang at 7% stuck on that particular image which was the exact same type of file and size. Both were small screenshots. Both had the same exact effect and preset. It seems it's always the smallest of things, still continuous crashes, being unable to get Vegas to even start, that keeps me from being able to be productive. I don't want to use DaVinci, I'm too vested in Vegas, but lately, feeling like a don't have much of a choice. I don't know what's going to happen. I am encouraged by some of the shifts in the communication from above regarding Vegas' long-standing problems, but I really doubt the Magix team has the resources or capability to rebuild this app using modern code/tools, which is what is required (there are still dependencies going back to unsupported versions of C++, for goodness sakes!). And even if you could magically rebuild Vegas with sound architecture: it's 2023! Many of Vegas' tools are wildly outdated (just try doing some color work with 10-bit SLOG3, if you want to see how far behind Resolve VP20 is). So, it is hard to be hopeful. But I will still keep rooting for Vegas until they pry it from my cold dead fingers. :) w/regard to your issue, I always save multiple versions of my veg files, numbered so I can keep track of them, at every major edit/change. Because I've had this happen too: you do something (who knows what) and the project refuses to open, and there's no way to recover hours/days of work. Sorry for the hard times. Hope you get your file to open!
-
Videoon 3/7/2023
Having Problems with VEGAS 20? (Only users of V20 Build 326, Please)
Here is a link to my thread on an issue with the project media bin: https://www.vegascreativesoftware.info/us/forum/please-fix-the-context-menus-in-the-project-media-bin--139970/ Thanks to some help from other forum users, you should have no trouble replicating this
-
Videoon 3/7/2023
Please Fix the Context Menus in the Project Media Bin
For the purposes of replicating this, walter & bitman figured it out -- it matters where you click. If the view is set to list or details, everything is fine (I think). Switch to thumbnails and right-click on a highlighted (selected) item in the media bin *on the frame rather than the actual preview portion of the icon* and the context menu items will be grayed out.
-
Videoon 3/6/2023
Please Fix the Context Menus in the Project Media Bin
@ALOFeel free to tag that post as the solution that helped you the most - or if you're not happy with the sitation, copy and paste your first post into the thread:https://www.vegascreativesoftware.info/us/forum/vegas-pro-feature-requests--134374/or include the words "Feature request" in your title - so the developers will find it. @bitmanThanks for checking - your findings are meticulous though! er...I don't think this a feature request, or that the issue is solved?? You've both corroborated a bug in the Project Media bin
-
Videoon 3/6/2023
Please Fix the Context Menus in the Project Media Bin
@ALO @VEGASDerek @walter-i. I can finally reproduce the issue! Walter nailed it, but it takes more than just clicking on the frame to reproduce: the file name of the video is also important; more specific, the length of the file name must be rather short in order to reproduce. Longer names (which have a larger " name box" on the GUI work OK). Short names have a smaller hit box and if clicked outside the name field hitbox (e.g. on the bottom right of the frame) do not register a highlight. @walter-i. @bitman thank you!
-
Videoon 3/5/2023
Please Fix the Context Menus in the Project Media Bin
I just downloaded and installed VP20 on a clean user account on a completely different machine. I was able to immediately replicate the issue. Not sure what else to say.
-
Videoon 3/5/2023
A Little Sony Humor
Some thoughts on the Catalyst Browse stabilization approach (specifically regarding the FX30): The stabilization is okay. There is no horizon leveling, and it certainly doesn't work magic when for example I try walking and shooting directly ahead or to the side. The workflow bites. All we need is one more step in our editing process to make our lives more complicated. It's time consuming, you have to render to an intermediate which creates its own problems, you have to guess the crop level and then re-render if you're not happy with the result -- does anyone really want to have to do this for hundreds of clips? The resolution hit is considerable. Yes, you can choose your crop level, but if I select a crop to roughly match my in-camera stabilization modes (standard and active w/a wide-to-tele OSS lens), there is NO comparison in terms of resolution. In-camera stabilization gives a more aesthetically pleasing stabilization, and a vastly superior result in terms of retained resolution (even vs active mode). Thank goodness, right? I do think gyro stabilization is a very important technology, as GoPro has more than proved, and I will hope that either the FX30 in update or a future camera model will fully support this as an in-camera option rather than forcing us to use a Sony Creative Software app as an intermediate step.
-
Videoon 3/5/2023
32-Bit Video Renders Brightness Flickering
@ALO Thanks for bringing this problem to our attention. I am able to reproduce it as you initially described. Yes this is a bug and I will add a report to our defect tracking system so it can be fixed in a future release. As others recommended, it would be best to use the color curve section of Color Grading instead of the classic Color Curves plugin in 32-bit projects. @VEGASNeal1 unfortunately I have been able to replicate this problem with 10-bit 422 4k XAVC HS (HEVC) 60P 100 Mbps footage shot on a Sony FX30. In this new case, the issue occurs when the Color Curves fx is preceded by a levels fx and a Color Correction (Secondary) fx with a chrominance adjustment. This issue may be a little deeper than it first appears. Please PM me if you want a project file and source clip. This is also occurring in 32-bit Full Range projects with the media and project settings otherwise as described in the quote above :( I'll add more details and maybe a clip & sample VEG file to download in the coming week
-
Videoon 3/4/2023
A Little Sony Humor
What language were you expecting? A human one? :)
-
Videoon 3/4/2023
A Little Sony Humor
Actually Browse did the same thing on start. I googled it. You just have to restart the program and then everything is legible. Because...Sony! :)
-
Videoon 3/4/2023
Having Problems with VEGAS 20? (Only users of V20 Build 326, Please)
OK, here is the workflow that causes me the most trouble: Get a GoPro Hero 11. Set as follows RES | FPS -- 5.3K 30 10-Bit -- On Bit Rate -- High Shoot clips of varying lengths. For me, usually in the range of 10 seconds to (rarely) 2 minutes each. Add about a hundred of these to a blank Vegas timeline on one track. Vegas proxies --> Off I edit in 8-bit legacy (video levels), set to UHD, usually with preview set to Best-->Full. Note that my system is capable of playing back these files individually without stuttering. It's when a large number of them are on the timeline that the stability issues are the most severe. I typically add chain-based fx to each clip at the clip level in the following order: Color Corrector (Secondary), Levels, Curves, Color Corrector (Secondary), Sharpening. These fx are used as follows: (1) color correction using chrominance (2) Levels conformed to full range, (3) add saturation and contrast (4) add targeted/range-limited saturation (ie, no sat boost to shadows or highlights, maybe focused around a specific hue like blue to avoid touching skin tones) and (5) a modest sharpening boost. Using this workflow and performing simple edits (tweaking the fx, trimming the clips on the timeline, rearranging the clips on the timeline, ripple-editing) you should have no trouble recreating the severe issues Vegas has in contending with a large number of HEVC clips on the timeline. This would include repeatedly hanging, crashing, "not responding," or failing to close properly (which leads to the program failing to start properly). Main System: A current Dell XPS laptop i9-12900HK 2.5GHz 32G RAM NVidia GeForce RTX 3050 Ti driver version 31.0.15.2824 studio/enterprise Windows 22H2 Build 22621.1265
-
Videoon 3/3/2023
Please Fix the Context Menus in the Project Media Bin
Here's a screen capture of the issue. *sometimes* this happens, and sometimes it doesn't, and unfortunately I can't figure out how to guarantee it happens. But it happens most of the time. You might have to click around a bit and move the cursor in the timeline. The Vegas code base is truly like a big old haunted house. Lot of ghosts in there! There's also something weird going on with the explorer window, but I'll save that for another day...
-
Videoon 3/3/2023
Export 16-bit PNG?
yeah I can export a 16-bit TIFF sequence using image sequence-render, but not the save snapshot button. ?
ALO
Offline, Last login 11/16/2023, Member since 10/26/2016