Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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 :)

New Beta 4 Redcine-X with NVIDIA CUDA decode

Jarred Land

Jarred Land

Fire Chief
Staff member
Joined
Dec 27, 2006
Messages
10,644
Reaction score
33
Points
10
New Beta 4 Redcine-X with NVIDIA CUDA decode just landed.

RED engineers have outdone themselves once again. I had an initial target of full 8K @ 24fps. They took that target... and stomped it.

This new build is seeing 33fps on a single 2080ti card. Full 8k @ 33fps. That's pretty insane.

Windows only.

https://www.red.com/downloads/optio...dcDpUrzVgwsDYsKGjXX0mthiXc0Gv2DOOdi4i4axv2cvU

RELEASE NOTES

REDCINE-X Professional BETA Build V51.0.0 – Windows (64-Bit) Build
SYSTEM REQUIREMENTS
64-bit Windows Vista or later
1GB hard drive space
8GB RAM (recommended)
2GB GPU Video RAM (when using GPU acceleration)
4GB GPU Video RAM (when using GPU R3D decompression)
CHANGES IN THIS BUILD
Added: Memory improvements to perform GPU decoding. Memory requirement has been reduced to 4GB for full GPU decoding and playback.
Added: Speed improvements on GPU decoding and the IPP2 Image Pipeline.
Added: Multi-GPU support for windowed display. (Full screen support is not fully implemented.)
Fixed: Red tint occasionally showing up on the right side of frames in multi-GPU environments.
Fixed: Green tint frames showing up in multi-GPU environments when GPU Decode was disabled.
Fixed: Stuttering issues.
Fixed: Histograms and Scopes not working.
Fixed: REDCINE-X PRO crashes when switching from the Export tab to the Edit tab.
Fixed: Exports with the film post effect enabled fails if the source resolution was lower than export resolution.
Fixed: RED Player crash when loading a clip.
Fixed: Chroma Noise Reduction UI incorrectly disabled when it should be enabled.
Enhanced: REDCINE-X PRO discovery and utilization of new NVIDIA CUDA cards.
Enhanced: REDCINE-X PRO and RED Player Viewer Window FPS display.
NOTES & KNOWN ISSUES
Image Noise Reduction Panel
Chroma Noise Reduction in IPP2 (On/Off) [Full Demosaic Only]
To add/remove panels, right-click the panel area, and select the panel you want from the drop-down menu that displays
Multi-GPU full screen playback results in alternating rendered and black frames.
Some machines with more than one GPU installed are experiencing significant FPS slow downs. The FPS slow downs can get worse if both GPU cards are selected for use with REDCINE-X PRO.
CUDA Rendering with Post Effects enabled can cause display issues.
Corruption in the RCX GUI's Viewer Window when SDI/HDMI output external video output and CUDA GPU decode are enabled (SDI output works).
Some 5k and 6k clips show decompression artifacts at 1/8th and 1/16th.
Occasionally, first frame in viewer may be displayed abnormally.
CHANGES IN BETA 3
Added: Accelerated R3D decompression on supported NVIDIA CUDA GPUs
Added: Image Noise Reduction Panel:
Chroma Noise Reduction in IPP2 (On/Off) [Full Demosaic Only]
Flashing Pixels (Off, Mild, Medium, Strong) (Ref: Image 4 in Appendix) [Full Demosaic Only]
NOTE: To add/remove panels, right click-on panel area to reveal drop down to select appropriate panel (Ref: Image 5 in Appendix)
Added: HDR support for select AJA and Blackmagic Design devices
Added: Viewer Window IPP2 / Primary Development Only view toggle
Added: REDline CDL export
Added: REDline Primary Development Only export
Added: Startup splash screen
Enhanced: Cleaned up the default REDCINE-X Pro Home Page
Enhanced: ProRes 4444 XQ no longer restricted to just log output
Enhanced: ProRes encoder now sets Rec.2020 and HDR-2084 metadata
Enhanced: Creative 3D LUT ALT-key Preview mode lock
Fixed: RMD file Creative 3D LUT fixes
Fixed: Marker loading issues

Note: RED ROCKET-X support requires driver 2.1.31.0 and firmware 1.4.1.16 or higher.
Note: NVIDIA Cuda acceleration requires compute capability 2.0 or higher capable GPU on Mac with the latest NVIDIA Cuda Driver.
Note: NVIDIA/AMD OpenCL acceleration requires OpenCL 1.1 or higher capable GPU.
 
Awesome. Will be trying it with the 1080 for 5k shots, but am looking to upgrade very soon.
 
Beta 4 running on my test project with lots of 8K 5:1 material w/ dual NVlink Titan RTX cards is hauling butt on my last workstation build. I'll load it up in the notebooks, but this is damn impressive.
 
Screaming fast but with plenty of bugs when outputting to external display with a decklink mini monitor 4k
 
Jarred Land said:
New Beta 4 Redcine-X with NVIDIA CUDA decode just landed.

RED engineers have outdone themselves once again. I had an initial target of full 8K @ 24fps. They took that target... and stomped it.

This new build is seeing 33fps on a single 2080ti card. Full 8k @ 33fps. That's pretty insane.
Click to expand...

Impressive, what is the compression ratio?
 
Andriy Trofymenko said:
Screaming fast but with plenty of bugs when outputting to external display with a decklink mini monitor 4k
Click to expand...

Would you say it is this known issue (bolded)?

NOTES & KNOWN ISSUES
Image Noise Reduction Panel
Chroma Noise Reduction in IPP2 (On/Off) [Full Demosaic Only]
To add/remove panels, right-click the panel area, and select the panel you want from the drop-down menu that displays
Multi-GPU full screen playback results in alternating rendered and black frames.
Some machines with more than one GPU installed are experiencing significant FPS slow downs. The FPS slow downs can get worse if both GPU cards are selected for use with REDCINE-X PRO.
CUDA Rendering with Post Effects enabled can cause display issues.
Corruption in the RCX GUI's Viewer Window when SDI/HDMI output external video output and CUDA GPU decode are enabled (SDI output works).
Some 5k and 6k clips show decompression artifacts at 1/8th and 1/16th.
Occasionally, first frame in viewer may be displayed abnormally.
 
Hi yes it's noted. My apologies I am new to this. Where do I report issues if needed?
 
Steven Yaeger said:
Our target was 24 FPS with a Full Frame 8k, 5:1 compression clip.
Click to expand...

And you reached 33 fps, 8k, 5:1 playback on a single RTX2080ti? That is very impressive.

Especially when you consider the puget only reached (23 fps, must be a typo)..25fps, 8k 9:1 playback on a single RTX2080ti combined with a i9-9960x in Davinci Resolve.
https://www.pugetsystems.com/labs/articles/DaVinci-Resolve-15-NVIDIA-Titan-RTX-Performance-1328/

Does this also mean that RCX has a superior de-bayer(~30% faster) compared to Davinci Resolve ?
 
Misha Engel said:
And you reached 33 fps, 8k, 5:1 playback on a single RTX2080ti? That is very impressive.

Especially when you consider the puget only reached (23 fps, must be a typo)..25fps, 8k 9:1 playback on a single RTX2080ti combined with a i9-9960x in Davinci Resolve.
https://www.pugetsystems.com/labs/articles/DaVinci-Resolve-15-NVIDIA-Titan-RTX-Performance-1328/

Does this also mean that RCX has a superior de-bayer(~30% faster) compared to Davinci Resolve ?
Click to expand...

Misha, this is utilizing the new GPU Decode Acceleration from Nvidia which Puget hasn't tested yet and hasn't been updated via SDK in 3rd party applications.

And yes, at the moment at full debayer playback RCX is literally superior to everything with the new tech, that is until it's implemented in other programs likely in a couple months.
 
Phil Holland said:
Misha, this is utilizing the new GPU Decode Acceleration from Nvidia which Puget hasn't tested yet and hasn't been updated via SDK in 3rd party applications.

And yes, at the moment at full debayer playback RCX is literally superior to everything with the new tech, that is until it's implemented in other programs likely in a couple months.
Click to expand...

I know, in Resolve the 2080ti only has to de-bayer and is around 30% behind RCX New Beta 4 where it has to decode+debayer, it must be a typo or some other mistake in pugets testing because the GTX1080ti was already capable of debayering 8k 25 fps (de-bayering wasn't the problem with previous gen GPU's).
 
Misha Engel said:
I know, in Resolve the 2080ti only has to de-bayer and is around 30% behind RCX New Beta 4 where it has to decode+debayer, it must be a typo or some other mistake in pugets testing because the GTX1080ti was already capable of debayering 8k 25 fps (de-bayering wasn't the problem with previous gen GPU's).
Click to expand...

Compression ratio matters. I need to go back through their tests to see what was done at the different types of 1/2 and full.
 
Misha Engel said:
I know, in Resolve the 2080ti only has to de-bayer and is around 30% behind RCX New Beta 4 where it has to decode+debayer, it must be a typo or some other mistake in pugets testing because the GTX1080ti was already capable of debayering 8k 25 fps (de-bayering wasn't the problem with previous gen GPU's).
Click to expand...

Checking in one of the other Puget tests (specifically the 2070 one: https://www.pugetsystems.com/labs/a...-15-NVIDIA-GeForce-RTX-2070-Performance-1264/), the 2080 Ti does seem to be hitting 25fps on that 25fps 8K clip, so that 23 could be a typo. Alternatively, the test that reads 23fps is using an Intel 16c/32t 9960x, whereas the system in the 2070 test uses a 32-core Threadripper. Since the CPU is often the limiting factor in the current R3D decode implementation, that could explain the difference.

So there's a few things to consider about the difference between Puget's test and the current RCX implementation. First, Puget's test sets the playback speed to the clip's native frame rate, so we don't know if that 25fps is a cap, or if there's still overhead. Second - since the existing R3D decode implementation is still CPU-limited, it's unlikely that 23/25fps figure in the Puget tests represents 100% GPU utilization.
 
This build is soooooo much better than the last. Now I can view 5k footage at full rez with my older system using a GTX Titan X. It uses less of it's memory too. About a third. Excellent work guys!

There is still about the same amount of stuttering as previously however. Interestingly, the stuttering is about the same regardless of resolution and the GPU is not running out of steam. For 1/2 and 1/4 rez, once it buffers enough memory, it's running at less than 50% GPU processing power. Also, the instantaneous frame rate is dancing around between 22 and 24+ fps. On older versions of Redcine X Pro, once the memory has enough time to buffer, playback is butter smooth and the instantaneous frame rate is rock solid. It just couldn't handle full at all, or even half resolution without buffering into memory first.

There is also still some occasional momentary ghosting, most noticeably off the sides of buildings against the sky. This does not appear on older non-GPU decoding versions of Redcine X Pro (but did appear in the previous beta of this one), so it's definitely not on the footage itself.

I'm also seeing some occasional bugs with viewing the footage on a separate monitor if I start that up before running the footage, but I haven't quite worked out what the sequence of making this particular bug happen. Maybe someone else here has seen that.

Perhaps all this is a function of me not yet using RTX technology, and I do intend to upgrade. I just wanted to see how much more improved it was on GTX, and it is. I think it's getting close.

I will send a report to RED Support to see if I can help at all but just wondered if anyone else is seeing some of this so we can all help.
 
Mike Smith said:
This build is soooooo much better than the last. Now I can view 5k footage at full rez with my older system using a GTX Titan X. It uses less of it's memory too. About a third. Excellent work guys!

There is still about the same amount of stuttering as previously however. Interestingly, the stuttering is about the same regardless of resolution and the GPU is not running out of steam. For 1/2 and 1/4 rez, once it buffers enough memory, it's running at less than 50% GPU processing power. Also, the instantaneous frame rate is dancing around between 22 and 24+ fps. On older versions of Redcine X Pro, once the memory has enough time to buffer, playback is butter smooth and the instantaneous frame rate is rock solid. It just couldn't handle full at all, or even half resolution without buffering into memory first.

There is also still some occasional momentary ghosting, most noticeably off the sides of buildings against the sky. This does not appear on older non-GPU decoding versions of Redcine X Pro (but did appear in the previous beta of this one), so it's definitely not on the footage itself.

I'm also seeing some occasional bugs with viewing the footage on a separate monitor if I start that up before running the footage, but I haven't quite worked out what the sequence of making this particular bug happen. Maybe someone else here has seen that.

Perhaps all this is a function of me not yet using RTX technology, and I do intend to upgrade. I just wanted to see how much more improved it was on GTX, and it is. I think it's getting close.

I will send a report to RED Support to see if I can help at all but just wondered if anyone else is seeing some of this so we can all help.
Click to expand...

What is your screen refresh rate? I assume you need to have in even numbers with playback frame. Like having the screen set to 30Hz and playback 25p or such will normally create studdering.
 
Björn Benckert said:
What is your screen refresh rate? I assume you need to have in even numbers with playback frame. Like having the screen set to 30Hz and playback 25p or such will normally create studdering.
Click to expand...
No, it's not that. I can start up the same footage in an older, non-GPU decoding version of Redcine X Pro and it runs butter-smooth. Same PC. Same monitor(s). Same footage. Same frame rates. Of course the older version cannot handle the resolutions that Beta 4 can. But if I'm willing to let the older version buffer into memory at, say, 1/2 or 1/4 rez, the playback is very smooth. As is the intantaneous frame rate indication below the screen. Not so on Beta 4 where it wanders about, sort of in sync with the stuttering.
 
If I run half debayer it takes 6.8GB of GPU RAM according to Task Manager. Quarter is about 4.2GB. If I try fullress it either goes very slowly or it crashes
MSI 75 Titan laptop with full 1080 GTX 8GB and hexa 4.3GHz. So Redcine takes 5.8GB for half debayer since 1GB is reserved for other software.
So it seems it is running out of memory on fullres.

Another thing I note is that it only uses 11GB for the cache, even though it is set to use 52GB. So the cache is very short.
Andreas
 
Last edited:
Mike Smith said:
This build is soooooo much better than the last. Now I can view 5k footage at full rez with my older system using a GTX Titan X. It uses less of it's memory too. About a third. Excellent work guys!

...

I will send a report to RED Support
Click to expand...

Thanks Mike!

This beta version was obviously optimized for higher playback speeds. A side effect of that optimization is potential stuttering when the system isn't capable of hitting the target FPS. We know of a few ways we can compensate for this. To help decide which way (or ways) to use, we've added additional information to this version's log files.
 
Last edited:
You must log in or register to reply here.
Back
Top