Playback performance

Hi,

Impossible to have a smooth playback performance even worst than the V14.3 ... ;-(

Just some GH5 4K 60 FPS with some slow motion with nearest mode. I try with / without cache with & without optimized media cannot have a full 25 fps playback more arround 18.

I have a 3930K cpu (6 cores) 32GB ram one 1070 gtx and one 1060gtx.

What can I do ?? Is my computer to slow ?

Latest windows, latest nvidia drivers.

[Peter Chamberlain]

6 core is far too slow. Try making optimized media.

Been wondering myself what kind of Workstation BM expects. Although I dig the 15 beta release with all improvements very much, performance is worse across the board.

I'm on an overclocked system with Ryzen 7@ 3.9Ghz, 32GB RAM, GTX 1080oc, fast SSD...
With 15 I also cannot playback HD clips, and if I apply any sort of color correction or FX, or worse touch anything within the new Fusion tab, it gets basically unusable. Rendering Cache in Fusion, using optimized media etc. helps little to none. Exporting is 10 times slower than before, I was exporting faster than realtime in previous versions, now it's at 6fps max.

I expected all of this to be a "beta" issue - but the answer of BM here in this thread worries me a little. Again, what kind of PC do you expect? i9 18core with 3 Quadros?

Btw Resolve 15 never uses more than 20% of my CPU and on some operation I notice 0% GPU usage.

6 core is far too slow. Try making optimized media.

Hmm... I only have 2 cores more in my machine, but have a single Titan Xp rather than 2 GTX cards (and different one, too). I'd say it might be some lack of optimization caused by the presence of 2 different GPU cards (1060 & 1070) in one system - with my hardware, I have now the Beta 15 flying! Full, solid green 50 fps (not to mention 25 fps, with UHD@25p projects)..

Piotr

Hi,

Impossible to have a smooth playback performance even worst than the V14.3 ... ;-(

Just some GH5 4K 60 FPS with some slow motion with nearest mode. I try with / without cache with & without optimized media cannot have a full 25 fps playback more arround 18.

I have a 3930K cpu (6 cores) 32GB ram one 1070 gtx and one 1060gtx.

What can I do ?? Is my computer to slow ?

Latest windows, latest nvidia drivers.

Hi.

@Mikael: You ask what you can do? I never see it done on a 6,5 year old CPU, but only on the newest i7 8700K CPU. Have you considered to Overclock the CPU and change the cooling to a Liquid cooled one. I will expect it may be will require a new cabinet to?
Here is a link to a i7 8700K, but I don't know how high you can overclock a 3930K?

I expect you use the Free version of Resolve. And I don't know if the video from your GH5 in 4K is one if the formats that can benefit from the Hardware Decoding/Encoding in the Studio only version. Look into it and if it does do it cost 299 USD to upgrade.

But the first thing to do, must be to try to remove the 1060gtx. I have not seen using two Different GTX recommended since version 12.5

@Manuel: You write 'Been wondering what kind of Workstation BM expects'

Acording to tha new DaVinci Resolve 15 Configuration Guide do the recommend a Intel HEDT system or a AMD Threadripper:

http://documents.blackmagicdesign.com/D ... _Guide.pdf

BMD just rewrote it and now use modern Motherboards compared the ones used in the old manual. Thanks for that.

Regards Carsten.

I noticed Resolve 15 defaults image scaling to smoother (at least on my installation). I think this can affect performance on some machines.

6 core is far too slow. Try making optimized media.

Hello Peter,

Hmmm....I disagree with your response in the sense that most users on a "good" workstation are using 4-core CPU's for the most past (6700's i7 and such). The latest 8700 i7 is 6-core and gets a pretty damn good benchmarks.

Also he's got a 1070 and 1060 which should also help quite a bit, one with 8Gb of vram and the other with 6.

I used to use a 3930k and I assure it's no slouch of a CPU.

If you're saying that now a Resolve minimal system is at least an 8-core Xeon that is not particularly reassuring for the growing user base who will also want to stay mobile as much as possible (i.e. limited to 2 or 4 cores).

What gives?


P.S.

To the original poster, I would ask if the GH5 footage is an intra codec or an all-i codec from that camera? It will make a substantial difference in playback performance. I edited a music video recently which was partially shot on a GH5 with the old codec and I had to cache a great deal of shots in order to get reasonable playback.

Hi.

Two things had happen in the last weeks. BMD has released a new Configuration Guide for Resolve 15 and Intel has launched new Mobile 6 core CPU's.

Hello Peter,

Hmmm....I disagree with your response in the sense that most users on a "good" workstation are using 4-core CPU's for the most past (6700's i7 and such). The latest 8700 i7 is 6-core and gets a pretty damn good benchmarks.

I believe that the 6 core i7 8700 can only be considered if it is Overclocked to around 5.0 GHz on Liquid cooling.

Also he's got a 1070 and 1060 which should also help quite a bit, one with 8Gb of vram and the other with 6.

As I understand it is the performance now equal to the slowest if you use two different GTX Graphics card. The faster card will wait for the slowest to finish its frame.

I used to use a 3930k and I assure it's no slouch of a CPU.

The i7 8700K is around 33% faster that the 3930K. And the i7 8700K is not a recommend by the Configuration manual for Resolve 15.
The new recommendation is ether a Intel 10 or 12 Core CPU of the HEDT line or a 16 core AMD Threadripper:

http://documents.blackmagicdesign.com/D ... _Guide.pdf

If you're saying that now a Resolve minimal system is at least an 8-core Xeon that is not particularly reassuring for the growing user base who will also want to stay mobile as much as possible (i.e. limited to 2 or 4 cores).

None except you is saying that the Resolve minimal system is at least an 8-core Xeon. In the configuration manual for Resolve 15 says ether Intel 10 or 12 Core CPU of the HEDT line or a 16 core AMD Threadripper

And Mobile is not limited to 4 core any more . Try to google i7 8750H. It is the new Intel 6 core 12 thread mobile processor.

Regards Carsten.

I have now the Beta 15 flying! Full, solid green 50 fps (not to mention 25 fps, with UHD@25p projects)..

Piotr

Same here Piotrze.
The footage:
- UHD
- 800% speed gain (timelapse)
- tracker in Fusion tab
- frame stabilization with this tracker information

And it's running almost real time on GTX 980Ti !!

v14 - would blow my PSU with this scene.

Huge improvement in V15 but you have to use a solid GPU.
Great Work BMD!

I have such a problem.
When the audio is relatively long, the davinci resolve operation and response will be slow, and the scaling track response is slow and takes a long time to respond. When the video length exceeds 1 hour, or up to 3 hours, the audio waveform loading will be very slow, but the audio can be smoothly loaded on the Fairlight panel. Is there any solution?

ok I bought a 2690 v2 10 cores cpu. Ok it'snt newest cpu but common 10 cores should be enough to playback realtime ...

So no difference at all when I apply some retime process, nearest or optical flow and when I cache this, still impossible to play it realtime.....

I unplug one graphic card, it seems better. Thanks for the suggestion. I'll continue my testing.

None except you is saying that the Resolve minimal system is at least an 8-core Xeon. In the configuration manual for Resolve 15 says ether Intel 10 or 12 Core CPU of the HEDT line or a 16 core AMD Threadripper

And Mobile is not limited to 4 core any more . Try to google i7 8750H. It is the new Intel 6 core 12 thread mobile processor.

Regards Carsten.

Precious. So basically the rest of us who have been using Resolve quite nicely on our 4-core machines are supposed to suddenly trash our machines because Blackmagic has decided that we're 6 cores short?

I call BS. Regardless what the new configuration guide calls for, Resolve runs perfectly fine on my 6700k and I seriously doubt Premiere users who also operate easily on 4-core CPUs will be persuaded to make the jump if it requires a minimum 10-core configuration.

and again I don't know why impossible to have a smooth playback, very far from it. on the beta 6

[Peter Chamberlain]

and again I don't know why impossible to have a smooth playback, very far from it. on the beta 6

Did you try making optimized media?

yes I did

Is someone succeding to have smooth playback on 4K GH5 footage ? Is what kind of computer ? Thanks
My gpu hit 97% just reading without effect, and with optimized media. GTX 1070. What can I do ?

Retiming with optical flow is extremely demanding, whether you're using h.264 camera original or optimized media. Poor real time playback isn't surprising. My system is similar to your old one: with Prores HQ 24p HD footage I get under 9 fps with retime speed set to 50% and optical flow enabled.

Caching the clip is the solution. If caching isn't working for you either, I'd look to disk speed. The cache disk may not be able to keep up with the caching format you've chosen.

When I do my test I don't bench on clip with effect like I said so no Optical flow... And even without anything cannot have a smooth playback.

GTX 1070 is old for you ?

I discover something ...

For me it's a bug but waiting for your opinion.

I use clip like i said before 4k 60fps
I use a timeline at 24fps.
I said it wasn't smooth on playback without effect.
So my clip plays realtime.
BUT it appears than you apply in your setting retime process to optical flow
Even if you don't retime your clip
It's very slow
so i change to nearest in the inspector
And now it's fine.
And if I use optical flow on standard faster it play good,
But I use it on standard better it's chunky.

It's not possible to use standard faster and at the export it use the better automatically ?

For me Optical flow shoud kick in only if you go below under 100% and if you have the little speedometer icon on your clip ?

What do you think ?


And additionnal question what graphic card is able to handle retime process and color correction and flare for full smooth playback ?

Thanks

Optical Flow is a very demanding process and actually DR is one of the faster programs when it comes to this.

It's always needed if you change the speed of any footage to a value other than 2x or 4x and so on, where dropping frames is enough (i.e. nearest).

Even a Titan-X is not doing it in realtime for 4K, and nevertheless it doesn't always look good. Nothing beats shooting the needed number of frames in camera…

It's always needed if you change the speed of any footage to a value other than 2x or 4x and so on, where dropping frames is enough (i.e. nearest).

The is the part that is killing him!

I don't get it. Dropping a 50p clip into a 25p timeline when set to 'nearest' is super fast here.

I don't get it. Dropping a 50p clip into a 25p timeline when set to 'nearest' is super fast here.

He is going from 60 to 24!

Well as I explain Earlier, my footage is 60p my timeline is 24p, but it play realtime, so it's NOT a conform from 60p to 24 NOT making half slower. So yes still don't understand why optical flow kick in, since I don't have the retime control icon

If you put 60 fps into a 24 fps timeline, some kind of retiming must kick in (unless you want slo-mo).

So, just switch to another algorithm in the project settings under "Master Settings" > "Retime process". If I remember well, that setting sticks.

BTW, Optical Flow is using quite a bit of CPU power too, not only GPU. Since decoding GH5 footage shot in 10 bit 4:2:2 is CPU only, that clip hammers on your CPU. Which load do see when looking at CPU activity? Might be an option to transcode that clip.

why should it kick in ? when I play one of this clip in davinci by double cliking on it, I don't have retime process it play at 24p and play fine ...

so should be the same in the timeline.

Hmm, I still don't get it, maybe it's the heat today.

AFAIK the GH5 doesn't have the project setting vs real fps like BM's cameras. So, your clip is either 60 fps or 24 fps. If it is 60 fps, how can it play at 24 fps in a viewer by double-clicking? It should play at 60 fps then (or probably stutter if your computer is not super fast).

Yes, you can conform it to 24 under "Clip Attributes" and that plays smoothly as a slo-mo for me, both in a viewer or in an UHD timeline, on a quite moderate i5 3,8 GHz. Faster than that, yes, it starts to stutter, even 25 is close to the limit. So, how exactly do you observe that difference between playing smoothly or not?

it play real time and on top the screen there is a green dot written 24. So I don't have the answer to that. For me it play at the 60fps speed, real time, and skip some frame to display it at 24 fps and make real time.

For me not playing smoothly is the clip freeze for half second every 2 second.

But if there its written 24, how can it be 60 fps?

I don't know ... try yourself you'll see. I cannot explain better.

Well, I tried, and all works as expected here. Let's try to get to the bottom of this systematically:

When the clip is selected in the Media page, what is the number of fps in the header of "Metadata" in the lower right?

If you open the clip in MediaInfo (free), what is shown in the second page for the bit depth (8 or 10 bit) and the chroma subsampling (4:2:0 or 4:2:2)?

What is your timeline set for?

In the media Tab :
https://imgur.com/Mtl2lL4

playing also in the media tab :
https://imgur.com/jRxdGgG

In the edit tab:
Double clicking on the clip :
https://imgur.com/GGqEk3P

Playing normal in the timeline with Optical flow activated on standard better, and actually it's a lot worst than that it freeze every second.:
https://imgur.com/AQJLgEE

The clip in the timineline as you can see without retime compare to the one on the left with retime :
https://imgur.com/zkX6PRm

And if I put on standard faster or nearest, it's fine, but for me it's a bug, optical flow shouldn't kick in if no retime applied.

Thanks

1. Your clip is 59.94 fps and your timeline is 24 fps. That doesn't divide by whole numbers. So, some kind of retiming will always kick in, that's completely normal and unavoidable. Not a bug.

– If you set the retime process for your project (all the way down in Master Settings) to "Nearest" or "Blend", there will be no optical flow kicking in. Promised. Nearest is realtime, but there'll always be some stuttering in fast motion (with a few exceptions, like 60 fps in a 30 fps timeline).

– In the Edit Viewer, Resolve is trying to keep audio playing without hiccups at the cost of picture stuttering.

– In the color tab you can see your real playback speed, which will be less than 24 fps for anything but a monster machine if optical flow is active.

And now the one million dollar question: Did you shoot for slo-mo or was 59.94 an error?

If for constant slo-mo, go to the "Clip Attributes" and set your clip to 24 fps. Put it into the timeline without any retiming. It will play smoothly in perfect quality slo-mo.

If you need ramping plus optical flow, cache the clip or invest into a really fast machine. The best optical flow is Twixtor, which even won a technical academy award, and its even slower. Resolve has a pretty good balance between speed and quality, in DR 15 you even have more choices.

Ok but you didn’t answer the question why when I double click on the clip it plays 24fps without problem and in the timeline it play with problem. What is the difference ? Optical flow is for retiming I Don’t retime. So shouldn’t kick in.

If the clip was playing at 24 fps in the Media page, it were a bug, since from your own screen shot the clip is shot in 59.94.
But there isn't any bug, since your next screen shots shows it playing at just that rate!
No conversion, no speed problem.

But your timeline is set to 24, so it needs conversion. Why don't you try my suggestion at least one time?
Change the frame rate in "Clip Attributes"!

Ok but you didn’t answer the question why when I double click in the edit tab on the clip it plays 24fps without problem and in the timeline it play with problem. What is the difference ? Optical flow is for retiming I Don’t retime. So shouldn’t kick in.

Your suggestion isn’t my need

I give up.
Slowing down from 60 fps to 24 fps with my method works perfectly fine for me on a much weaker machine without any optical flow or any retiming algorithm whatsoever.
If you insist on doing it your way, live with it.

I re encode the footage form 60 to 24p put it in the timeline with no effect but in parameters with optical flow set to standard better, and as the same other test it freeze in the timeline but work fine by double clicking in the edit page. So some optical flow kick in and shouldn't. So now you see even with your method it doesn't work. If i put something else like Standard faster or nearest, yes my machine can handle so no prob.

Don't worry to give up. Only the BM Product manager, could say, for me it's a bug, for you it'sn't.