Is R3D playback in Premiere Pro CC using a single core or multi-threaded?

[Michael McCaffrey]

Is R3D playback in Premiere Pro CC using a single core or is it multi-threaded?

I do not have a red rocket or anything. I am looking at options for the new Mac Pros and the 12-core Mac Pro scores fast for multi-threaded operations but the worst for single core benchmarks (bc its only 2.7ghz per core), whereas the 4, 6 and 8 core Mac Pros have faster clock speeds of 3-3.7ghz.

Red says their SDK is designed for single core operations, but they are unsure about Adobe's engineering in Premiere. So, if my 12-core Mac is using one 2.66ghz core to decode and playback .R3D's then the jokes on me I guess. And if so, who in the world at Red decided not to support multicore decoding of R3D files!??!?!

 

[David McGavran]

Is R3D playback in Premiere Pro CC using a single core or is it multi-threaded?

I do not have a red rocket or anything. I am looking at options for the new Mac Pros and the 12-core Mac Pro scores fast for multi-threaded operations but the worst for single core benchmarks (bc its only 2.7ghz per core), whereas the 4, 6 and 8 core Mac Pros have faster clock speeds of 3-3.7ghz.

Red says their SDK is designed for single core operations, but they are unsure about Adobe's engineering in Premiere. So, if my 12-core Mac is using one 2.66ghz core to decode and playback .R3D's then the jokes on me I guess. And if so, who in the world at Red decided not to support multicore decoding of R3D files!??!?!

We use multiple cores for Red Decoding We are clever like that. Can't yet say what the performance difference is on the new Mac Pro.

Cheers

Dave

 

[Christopher*Seguine]

That is a little misleading. Currently, using cpu decode, R3d decoding is single threaded - a single r3d frame = a single thread.

Premiere CC launches (16) 32bit red import tasks, guessing that it is cacheing ahead 16 frames to try and make up for the red single threaded sdk limitation.

Obviously not as efficient as taking a single frame and splitting it up into 16/32/64/xx pieces
For example, jumping to a new part of a clip there is a pause, scrubbing has lag, etc.

based on my experience you would still be better off with the 12-core machine, but you have to set your expectations.

I have 4x e5-4650 processors, 64 cores @3ghz. An epic 5k FF clip 5120x2700 5:1 uses about 65% cpu usage at HALF resolution. Full resolution is 100% usage and very jerky playback.
This is with the latest 7.1 update which greatly increased r3d cpu decode performance.
At Half resolution Premiere is using about 24GB of ram, at full 64GB of ram - I think its currently limited to max at 64GB.
So the 64GB ram limit on the new mac I see as a problem.
If r3d decoding gets moved to the GPU then things will be much better.



David, is there a setting that can be changed to increase the number of import server tasks above 16 or this hard coded in Premiere? I have 64 cores, I get best performance if I disable hyper-threading bringing it down to 32, I think if I could increase the # of red import server tasks to 32 I would get better performance with hyper threading enabled.

We use multiple cores for Red Decoding We are clever like that.

 

[David McGavran]

That is a little misleading. Currently, using cpu decode, R3d decoding is single threaded - a single r3d frame = a single thread.

Premiere CC launches (16) 32bit red import tasks, guessing that it is cacheing ahead 16 frames to try and make up for the red single threaded sdk limitation.

Obviously not as efficient as taking a single frame and splitting it up into 16/32/64/xx pieces
For example, jumping to a new part of a clip there is a pause, scrubbing has lag, etc.

based on my experience you would still be better off with the 12-core machine, but you have to set your expectations.

I have 4x e5-4650 processors, 64 cores @3ghz. An epic 5k FF clip 5120x2700 5:1 uses about 65% cpu usage at HALF resolution. Full resolution is 100% usage and very jerky playback.
This is with the latest 7.1 update which greatly increased r3d cpu decode performance.
At Half resolution Premiere is using about 24GB of ram, at full 64GB of ram - I think its currently limited to max at 64GB.
So the 64GB ram limit on the new mac I see as a problem.
If r3d decoding gets moved to the GPU then things will be much better.



David, is there a setting that can be changed to increase the number of import server tasks above 16 or this hard coded in Premiere? I have 64 cores, I get best performance if I disable hyper-threading bringing it down to 32, I think if I could increase the # of red import server tasks to 32 I would get better performance with hyper threading enabled.

We start to see degradation over a certain amount of cores. Depending on disk reads etc. So we hardcoded this. We are constantly working with Red to come up with ways to make this all faster

Cheers

Dave

 

[Michael McCaffrey]

We start to see degradation over a certain amount of cores. Depending on disk reads etc. So we hardcoded this. We are constantly working with Red to come up with ways to make this all faster

Cheers

Dave

So.. Dave you said "We use multiple cores for Red Decoding" but Christopher said "Currently, using cpu decode, R3d decoding is single threaded - a single r3d frame = a single thread." So I'm still not sure what the answer is here. If I were to spend the extra $4,000 to go from a new quad-core mac pro to a 12-core mac pro, will the additional cores be utilized for R3D playback in Premiere?

 

[luigivaltulini]

I've been working recently on my R3D files 5kHD 4800x2700 4:1
Have installed latest update 7.1 cc in my system win 7 hp z820 dual 8 core , now I can edit in full Debayer smoothly. Do not believe it but now I can do it.
I tried a 1 Titan, 1 gtx 690 but with these video cards can not go more than half debayer .. Since I am using the AMD 7990 everything is going too fast really to Davinci Resolve. I am very surprised given the cost of the $ 650 card.
So I assume that the new mac pro with the ATI needs to go fast ..

 

[Michael Jarvis]

We start to see degradation over a certain amount of cores. Depending on disk reads etc. So we hardcoded this. We are constantly working with Red to come up with ways to make this all faster

Cheers

Dave

Hey Dave, whats your thoughts on this review and Adobe's interaction with the new Mac Pro. I imagine you guys are working on things. Any possible update so I can plan for possible upgrades in the near future. Thanks .

http://www.youtube.com/watch?app=desktop&persist_app=1&v=26cqeqem2Ew