Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

RED + NVIDIA Announce Realtime 8K R3D GPU Decoding

He's not saying single-core i9. He's saying single Core-i9. Does that make sense? Just one CPU. In this case, that CPU is an i9. So just one i9. Or the full title, one Core i9. Blame Intel for putting "Core" in the product title.

Aha..., that must be it. Still don't know Jarred's defenition of cheap and since an i9 is always single socket, I got confused.

For laptop users it has to work on an i9 because that is the highest specced laptop you can get today (even half res would be great).
A small overclocked i9-9700x is twice as fast, has twice the memory bandwith and 4 times the PCIe-3 bandwidth for GPU, compared to the highest specced laptop processor(that often throttles in a laptop) and an eGPU over TB3.
 
Fantastic news. It is such a joy to look at the 8k videos. Anything to make them faster to playback would be great.

3) Davinci Resolve seems to really struggle with 8k videos. Works super fine with 5k and 6k, but 8k I can only playback in quarter debayer . Saw several similar reports on the Davinci forum. Apparently it was better with 14.1. This could have been fixed in the final 15 that was released yesterday, but I checked a few weeks ago and the problem was still there.

Using Windows 10.

Best,
Andreas

Have you tried to turn of HT (hyper threading)?.
Since version 14.1 Resolve only scales to max 32 threads under windows (haven't tried 15 yet).

This is bad news, what worried me more is the reaction from Dwaine Maggert (Blackmagic employee) in this thread https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=70646 , Is Blackmagic Desing becoming the new Adobe ? by adding more features that don't work and making their software slower. I really hope they fixed it in Resolve 15. I don't want to switch again.
 
Really hope Apple can knock it out of the park with the new Mac Pro. Sure hope they listened to Jarred.

I hope for all the apple users that you're right. On the other hand they are pushing ProResRAW which is only 12 bit and therefore can be de-bayered with fp16(twice as fast as fp32 and half the memory on the same GPU).
De-bayering 5.7k ProResRAW(12 bit) on a $ 400 GTX1070ti(Vega 56) will need roughly the same time as de-bayering 5.5k.R3D(16 bit) on a $ 3.000 TitanV.

Apple is doing pretty well in the consumer market, which is big, has high margins and is very forgiving towards Apple.
 
How well will this work with Fortnite?

I know some of you are thinking it ;)
 
RED said it wasn't possible because they started encrypting their R3D's, so only way to read them was through their SDK. Many years ago, Assimilate had a beta of Scratch that did GPU-space wavelet decode, but RED didn't want cheap GPU's pulling the rug out from under their pricey Rockets... You can read white papers from more than ten years ago about GPU wavelet decode, it's not that fuckin' hard to implement. Thanks Red, for FINALLY doing the right thing!
 
RED said it wasn't possible because they started encrypting their R3D's, so only way to read them was through their SDK. Many years ago, Assimilate had a beta of Scratch that did GPU-space wavelet decode, but RED didn't want cheap GPU's pulling the rug out from under their pricey Rockets... You can read white papers from more than ten years ago about GPU wavelet decode, it's not that fuckin' hard to implement. Thanks Red, for FINALLY doing the right thing!

Wavelet decoding is a very light task, even for CPU's. You can decode CineformRAW 4k 16 bits on 1core+1thread running at 4 GHz. CineformRAW 8k 16 bits can be decoded on a i7-7700k, R5-2600x or faster. De-bayering, NR, etc.. needs real parallel compute power hence GPU's with a lot of fp32, memory and memory bandwidth (Quadro RTX 6000 24GB, quadro RTX 8000 48GB and the quadro GV100 32GB).
 
Less than an hour before we get to see some updates on the consumer side of things. Looking forward to it!
 
This is more a code thing than a hardware thing. The results of our incredible software engineers working with Nvidias incredible software engineers we now have wavelet decode AND debayer working on GPU.. The new hardware helps of course but we are breaking 24fps on current cards with CUDA. The release of this is tied to the new hardware but everyone on NVIDIA will eventually win...

That's pretty awesome -- I figured something like this was in the works, but being able to offload the wavelet decode onto current GPUs in addition to new ones was more than I'd hoped for :)

Out of curiosity, is the new implementation able to use multiple GPUs, and if so do they need to be symmetrical?
 
He's not saying single-core i9. He's saying single Core-i9. Does that make sense? Just one CPU. In this case, that CPU is an i9. So just one i9. Or the full title, one Core i9. Blame Intel for putting "Core" in the product title.

Agreed, it's somewhat confusing branding that dates back to when processors with more than one core were kind of an oddity. :)
 
This is bad news, what worried me more is the reaction from Dwaine Maggert (Blackmagic employee) in this thread https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=70646 , Is Blackmagic Desing becoming the new Adobe ? by adding more features that don't work and making their software slower. I really hope they fixed it in Resolve 15. I don't want to switch again.

I don't see how that should be a cause for worry, since he concluded with a request for more info so that he could attempt to reproduce the problem in order to fix it.

That said, I've mostly found 15 to be faster than 14. Especially later in the beta cycle.
 
I don't see how that should be a cause for worry, since he concluded with a request for more info so that he could attempt to reproduce the problem in order to fix it.

That said, I've mostly found 15 to be faster than 14. Especially later in the beta cycle.

Have you tried it with more than 16c/32t ?, the last post in the BMD thread was May 02, 2018. Haven't seen any new info on this matter since then.
When an issue is fixed, it's always nice to know, maybe it's just a windows issue, lot's of software scales great on linux, I would like some answers from BMD.
 
Have you tried it with more than 16c/32t ?, the last post in the BMD thread was May 02, 2018. Haven't seen any new info on this matter since then.
When an issue is fixed, it's always nice to know, maybe it's just a windows issue, lot's of software scales great on linux, I would like some answers from BMD.

Not yet -- I don't have access to that many cores right now. I have read reports from quite a few colorists with some pretty high spec machines that Resolve 15 has been working very well for them though.

It would be interesting to see how well Resolve performs with a 32-core ThreadRipper2 in Linux vs Windows. I have a feeling that the results would be somewhat embarrassing for Microsoft. :)
 
It would be interesting to see how well Resolve performs with a 32-core ThreadRipper2 in Linux vs Windows. I have a feeling that the results would be somewhat embarrassing for Microsoft. :)

Looking at some benchmarks from phoronix, windows is kind of an embarrasment.
 
Looking forward to that 2080Ti

Me too. Just preordered two. It sounds like (and I'm hoping) the "code thing" is the real magic behind a lot of the performance boost and real-time playback of 8k. Not sure which pieces of the architecture are responsible for any of the R3D video stuff, but looking forward to real-time 8k nonetheless.
 
Back
Top