strange playback issue

w10 / 1709
14.2
DCi2kScope timeline
RED +EXR sources
source cached to DNxHR444_HDR
ACEScct with some OFX and NR

color page = 22Fps
edit page = 23.98Fps
Deliver page = 18Fps

taskmangler shows similar stats no matter what page i'm on;
CPU = 17->30%
GPU = 9 ->12%
Disk = 8 -> 12%

not a big deal, doing some tweaks to a show unattended, so no producer induced stress...
i've not seen this machine ever have an issue playing back anything tho
the same DRP imported onto a machine with much less horsepower runs fine

How's your cache drive performance?
Are you playing to 2k projection or hd?

- cache drive is 12 x 4Tb WD REDPro's on SAS, speed test shows something north of 1500 on a bad day, above that most days
- taskmangler shows disks running between 8 and 12% of capacity, varies as the timeline runs past 4k and 6k sources
- all cached to DNxHR444_HDR,
- nothing comeing from the server where the cam orig and VFX all live, 0% there
- playing back to HD on a monitor for this, output is set to match the timeline, so the edge of the raster is cut off
- i/o card is a Decklink4k something.. ahh you may be on to something, i just loaded the latest decklink driver (10.10 i think) Friday afternoon on this machine, but the z800 that can play this back cleanly is still on 10.7...

*edit - i tested setting the output scaleing to HD, and it plays properly in all pages - with the same CPU/GPU/Disk use in taskmangler, so that's workable for today

end game;
z820 (2x2690v2/2x1080Ti/128g/SAS/Decklink4k with10.10)
cannot playback what a
z800 (2x5680/1x1080/96g/SAS/DecklinkHD with 10.7 ) can...

both are well under their respective limits, the z820 at around 12% total resources used, the z800 at near 60% of resources for the same project / timeline

might roll back the driver on Monday

[Rohit Gupta]

Make sure your output resolution matches your Decklink video raster for optimum performance. Output resolution is set to timeline resolution by default, but can be changed in project settings (3rd tab I think).

Make sure your output resolution matches your Decklink video raster for optimum performance. Output resolution is set to timeline resolution by default, but can be changed in project settings (3rd tab I think).

If you don't do that, in other words if the outputresolution is 2048x858 instead of 1920x1080, you force the data to go back to the gpu once had been processed, effectively killing the throughput in half.

makes sense if the Decklin does not do it's own scaling.. makes the faster readback of the Quadro usefull?

still the GPU's were basicly ideling acording to taskmanager, never above 12% useage, vram is stable at around 3g in use,

even if it was processing twice there's a ton of headroom there for that

and nothing changed in system use according to taskmangler when i switched output scaleing from passthrough -to- scale to match the decklink's raster of 1080

when i change the decklink to DCi2k i still get the slow playback, likely due to the timeline not matching the Decklink's raster, and there's not an option for scope there as expected...

in future i'll set a scope project to DCi2k full and window to scope i guess, then i can keep timline and Decklink rasters matching