-
randomly losing realtime – causes
The standard causes I’ve found for non-realtime playback were:
- – too compressed codec (bought new machine to solve)
- – unrendered dissolves (set to auto-render)
- – forgot monitor on the wrong graphics card.
- – software scopes enabled (though set to non-existent second monitor)
But even still, I find that some days the box works realtime, and some days it doesn’t, even on the same project. Just now I was getting 16fps on an NTSC project.
I rebooted the system, and it was fine again.
I’m incorporating a fresh boot into the start of every session.
Anyone else experiencing similar results? -
19 Replies
-
Hi.
What about some details of your system ?
CPU speed, what type of gpu, io speed and how filled it is etc.
More detailed is the question more detailed answer you get.
—
Margus
-
Late 2010 Octo mac pro.
gtx285/120
Rocketraid – 800Mbps
DL Extreme 3+
6Gb Ram -
I have had the same issues using the linux and mac versions.
I do a restart and sometime a full reboot to clean up the problem.
I try to stick with .dpx or .cin frames on the resolve.
The program was written for dpx / frame based files. It likes them best.
If I need real time playback I convert everything to dpx and put it on my fast fibre.A few things that might cause this..
-Auto cache.On home system I have done this a few times. I hit the keyboard short cut and did
not realized it. It will be slow until the cached frames have written. (cache converts to dpx
frames) If your cache is not mapped to your fast stroage it will also cause it to run slow.dwooldridge@mac.com
check me out at https://www.facebook.com/pages/Davinci-Resolve-Colorist/117363011609028?ref=…. -
I had issues with the rocket raid.. I was getting crazy high read right numbers but very inconsistent playback. It surged– fast slow. I tested a friends 16 drive fibre chassis (benchmarked much slower read write speeds but my playback speed was fixed.) No fast slow issues..
I picked up two chassis, 32 drives, two fc switches and fc card.Darin Wooldridge
Colorist / Technical Strategist
818-653-3918-cell
dwooldridge@mac.com
check me out at https://www.facebook.com/pages/Davinci-Resolve-Colorist/117363011609028?ref=…. -
Thanks Darin, here’s the consolidated troubleshooting list.
- too compressed codec (bought new machine to solve, or use DPX)
- unrendered dissolves (set to auto-render)
- forgot monitor on the wrong graphics card.
- software scopes enabled (though set to non-existent second monitor)
- Auto cache accidentally rendering in bg.
- cache directory set to a slow drive
- Wrong resolutions on the timeline or output format page.
- RAID issue unrelated to Resolve (do a diskspeed test to check)
- system needs a fresh reboot (a frequent solution)
Let me know if there’s anything else to add.
-
Looks good..
I have a very long list. I am however going to hold off on publishing it.
Seems my “vintage” 2008 8 core mac might be the problem??Someone has been kind enough to offer me brand new 8 and 12 core fully loaded boxes to test with.
When this happens I will publish my findings.Darin Wooldridge
Colorist / Technical Strategist
818-653-3918-cell
dwooldridge@mac.com
check me out at https://www.facebook.com/pages/Davinci-Resolve-Colorist/117363011609028?ref=…. -
Oh yea the scopes. They are not worth using. The sdi output does not match the internal scopes when set hd legal. The 64_940 mapping happens after the internal scopes.
They also slow the performance and will never run real time.I build an external sdi touchscreen scope. Love it..
Darin Wooldridge
Colorist / Technical Strategist
818-653-3918-cell
dwooldridge@mac.com
check me out at https://www.facebook.com/pages/Davinci-Resolve-Colorist/117363011609028?ref=…. -
While it meets the specs, some more RAM might be helpful.
Director of the Institute of Media Research (IMF) at Braunschweig University of Arts
-
The internal scopes eats up your performance – it’s not worth using if you’re after real time playback.
I have an early 2009 with the basic 2.26GHz setup.. 6GB RAM, GT120+GTX285, Decklink HD Extreme 3D and RocketRAID eSATA with a 4TB array in RAID0 to gain as much speed as possible.
The few times I hit the wall in regards of performance is with RED RAW at medium or full quality, 2K and 4K DPX. SD and HD (24, 25, 30 and 50fps) in any format has been no problem.
I sometimes find it necessary to switch on and off the proxy mode because the controls get a bit slow over time. Switching proxy on/off fixes this though.
-
I think RR could be bad seed here as it tends to give you dropped frames.
Ask Bob Zelin on SAN forum here on cows.
For test populate all available bays with empty drives, lets say 2 tb ones.
Stripe them together and use it to playback something.
You should get some 300 MB sec with 3 drives.If it plays nicely then RR is bad by design or by unit.
—
Margus
Reply to this Discussion! Login or Sign Up