32 bit mode is always more taxing. So, do your workflow like this. Make all your cuts in 8 bit mode, and then when you go to color it, switch it to 32 bit mode.

I've been using Vegas since 2000, so I've been doing this for many years but BRAW is 14-bit. The entire point is that you can change ISO/white balance/color temp etc. and this can have a huge effect on deciding which takes you want and don't want during the cutting process. I've doing the cut so far in Resolve and will continue to do so but I prefer the Vegas UI but until BRAW is fully support and new audio engine with 32-bit support and 64-bit VST engine support, I will have to do my feature film editing elsewhere.

Resolve has this workflow built in and can play back realtime full rez 4K at full color depth. So can Premiere. Vegas BRAW cannot (yet). Sure you could do it that way but you might at well shoot ProRes instead if you are not going to fully use BRAW.

Any time you need to see what a shot looks like in 32 bit mode, it's just a matter of turning it on or off in project settings. Do your shot selection in 32 bit, figure out which ones you want to keep and cut, then when actually editing it all together on the timeline, run it in 8 bit.

I'd love to see 32 bit mode work at a faster framerate as well, but until it does, it isn't that difficult to work around.

Any time you need to see what a shot looks like in 32 bit mode, it's just a matter of turning it on or off in project settings. Do your shot selection in 32 bit, figure out which ones you want to keep and cut, then when actually editing it all together on the timeline, run it in 8 bit.

I'd love to see 32 bit mode work at a faster framerate as well, but until it does, it isn't that difficult to work around.

Well it obviously depends on your definition of difficult. I don't think you get the issue here at all. I've used 32-bit mode in Vegas for many years but shooting raw is completely different situation that taking advantage of bit depths for color correction. Right now, Vegas has zero facility to play back clips at full speed unless you made proxies (I shot 20TB for my feature, not going to happen). You can look at your 14-bit raw files either look at 8-bit playback at around 20fps or 4fps to see what you shot. If you do even basic editing (some dissolves, LUTS), it's dropping even slower so it's not usable at this point IMO.

And you can't actually access (from what I can find) the actual raw features - changing ISO/white balance/color temp etc. I assume that will come later in the beta process as again, that is the primary advantage to shooting raw.

But right now I'm trying to determine what card(s) are fastest and if any shipping card get 24fps playback of 4K (or great) BRAW files as this feature is in beta.

"And you can't actually access (from what I can find) the actual raw features - changing ISO/white balance/color temp etc."

Sure you can:

"And you can't actually access (from what I can find) the actual raw features - changing ISO/white balance/color temp etc."

Sure you can:

Not coming up here, maybe a bug?

"And you can't actually access (from what I can find) the actual raw features - changing ISO/white balance/color temp etc."

Sure you can:

Nevermind, my bad it's working now after a restart of the app, I think the window was getting lost behind on my dual monitor setup. Changing the setting does drop the frame rate another bit too even in 8-bit. I'm still curious who can get 24fps playback on what system.

Also keep in mind this support is still in beta form, and there are further performance improvements planned for VEGAS as well.

I guess you just looked at the wrong place. It's where the RED Raw settings are available, too - the clip's context menu via the Project Media window: "File Format Properties".

I found it, but nothing happened until I restarted. It's a problem I've had with Vegas for many years with certain windows not coming up on my dual monitor setups especially after an update.

Also keep in mind this support is still in beta form, and there are further performance improvements planned for VEGAS as well.

i realize you are trying to be helpful but that is literally the first words of my initial post above lol. again, the thread title is about who is getting 24fps playback - that's my primary question at this point.

"the thread title is about who is getting 24fps playback"

It's on my Acer Swift 3x after one playback buffer cycle. On the first go it's 16-18 fps (for 6k source clips).

I get about 12fps on that same clip, draft quarter quality on my zenbook pro duo 32gb rtx 2060 i9 9980hk setup.

I did tests of 6K and it's fine with a proxy workflow on my laptop. Switch to best full for grading.

That is the best way to go about it, proxy in 32 bit when editing, flip the preview quality to best when you need to color and play with the raw metadata settings.

I dont have a BRAW cam, so its nothing for me, but out of curiosity i tested it with 4K footage (THIS)

And normaly i dont work with with proxy. So what am i doing wrong:
BRAW_4K_Unchanged

BRAW_4K_BrightnessContrast

BRAW-proxy_4K_Unchanged

BRAW-proxy_4K_BrightnessContrast

My first assumtion was, that the effects got embeded into the proxy, because i changed contrast and brigthness and some very minor tweaks in the colorwheels, BEFOR creating the proxy. But then BRAW-proxy_4K_Unchanged should match BRAW_4K_BrightnessContrast if i turn of the effects in the preview, but as we can see in the screenshot it does not match. So either the proxy of BRAW footage cant be very accurate or its just that the BRAW decoding is very beta. At least this would be absolute unusable for editing. Or maybe its just that the proxy HAS to be created before ANYTHING is added in terms of effects?

Did some BRAW testing without proxies using the Rock Band multicam footage downloaded from the BMD web page. It's a pretty big zip. Didn't do any editing other than doing multicam cuts and seeing if I could play it smoothly. While I was at it I did a capture of it then added narration with the new text to voice thingy. I'll probably never evade Blade Runner or captcha with my new voice, but it's probably an improvement. Just uploaded my little demo run:

Did some BRAW testing without proxies using the Rock Band multicam footage downloaded from the BMD web page. It's a pretty big zip. Didn't do any editing other than doing multicam cuts and seeing if I could play it smoothly. While I was at it I did a capture of it then added narration with the new text to voice thingy. I'll probably never evade Blade Runner or captcha with my new voice, but it's probably an improvement. Just uploaded my little demo run:

What CPU and GPU?

Lol, not bad Howard-Vigorita, ..... I tell you this, i am kinda pleased with this text to speech new feature, because i've tried plenty over the years, and that sounded better than most.... With some additional precise audio editing tweaks, i can get exceptional and believable voice over results from this thing.

Did some BRAW testing without proxies using the Rock Band multicam footage downloaded from the BMD web page. It's a pretty big zip. Didn't do any editing other than doing multicam cuts and seeing if I could play it smoothly. While I was at it I did a capture of it then added narration with the new text to voice thingy. I'll probably never evade Blade Runner or captcha with my new voice, but it's probably an improvement. Just uploaded my little demo run:

What CPU and GPU?

I assume this one in his sig?

Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics & integrated Intel UHD630)
 

What CPU and GPU?

Was my first test project with a newly built machine with an 11900k cpu I just finished today. The gpu is a Vega64 that I pulled from my oldest setup. I also ran it on the 9900k machine. It's kind of odd because I don't see very high cpu utilization on either machine (about 25%) or any gpu encode or decode. But a lot of gpu copy. Up around 60% on the Vega64. Odd part is I only get about 15 fps on a 9900k machine, similarly low cpu utilization, and about 55% copy utilization on it's Radeon VII which is a faster gpu with 2x the memory.

With Braw it appears that the proxy is not updated in any way based on changes to the raw. The proxy is useful for getting real-time playback but not for judging color or exposure. Here Vegas created the proxy on import and then I loaded up the raw controls. The raw editing itself was quite pleasant and I'm happy with the results.

The proxy is useful for getting real-time playback but not for judging color or exposure.

Which is missing the point of its existence, does it not?

No, a proxy makes files that are unable to playback in realtime playable for editing (cutting). I never judge files for color correction using the proxies and always check my work with best/full on a full-screen second display.

The lack of a link between the color space and look of the raw file and proxy files is a problem, but as this is a beta I expect they will do something to address it. Now you can at least work with BM Raw without resorting to external software.