- Posts: 2740
- Joined: Tue Nov 11, 2014 6:48 pm
- Location: Vancouver, Canada
- project is UHD, 23.98, 1x 30 sec and 1x60 sec spots, YRGB
- machine is a z800/k2200/96gig/SAS array/w7Ultimate/12.5.b34
- sources are R3D's on a HFS drive... looooooong takes
- workflow was to conform a Pr XML on a z800, move the DRP and source media drive to a z820, source cache, grade, and move the new DRP + media drive back to the z800 for outputting a Pr round trip
- I avoided my NAS in this case as the project was supposed to be in and out in a few hours, and media manageing 380gig of source media needed to my NAS was going to take too long, seemed to be kinda overkill
- render settings were force debayer to highest, not to use caches, this is typical of my workflow, and i have output a fair amount of shows in the last months on 12.5 b.x without issues on this machine
- when i started the render the first 12 clips worked perfectly, and then the software hung, "time to complete" kept creeping up and there was no movement in taskmanager and the local disk array was silent
- killed Resolve in taskmanager, and restarted, when i selected the last two shots to render seperatly i saw the following;
(there's a normal looking talking head underneath that gak btw..)
- this wacko look displayed identicaly on my broadcast mon and external scopes.
- after several attempts to render it seems that it is independant of the target codec/file type, independant of the timeline raster.
- but here's the weird thing.. the outputs are completly fine when checked in either a new Resolve project or in MC, it's only (only?) the monitoring that seems to be massivly screwed up
- the GPU. although a bit wimpy is not over heating, and even seems not to be using all it's limited cuda cores or RAM, the CPU's are not working all that hard either, there's some OFX in some of the shots, but deleting them made no diffrence.
- machine is a z800/k2200/96gig/SAS array/w7Ultimate/12.5.b34
- sources are R3D's on a HFS drive... looooooong takes
- workflow was to conform a Pr XML on a z800, move the DRP and source media drive to a z820, source cache, grade, and move the new DRP + media drive back to the z800 for outputting a Pr round trip
- I avoided my NAS in this case as the project was supposed to be in and out in a few hours, and media manageing 380gig of source media needed to my NAS was going to take too long, seemed to be kinda overkill
- render settings were force debayer to highest, not to use caches, this is typical of my workflow, and i have output a fair amount of shows in the last months on 12.5 b.x without issues on this machine
- when i started the render the first 12 clips worked perfectly, and then the software hung, "time to complete" kept creeping up and there was no movement in taskmanager and the local disk array was silent
- killed Resolve in taskmanager, and restarted, when i selected the last two shots to render seperatly i saw the following;
- lsd render.00086400 copy.jpg (297.63 KiB) Viewed 2184 times
(there's a normal looking talking head underneath that gak btw..)
- this wacko look displayed identicaly on my broadcast mon and external scopes.
- after several attempts to render it seems that it is independant of the target codec/file type, independant of the timeline raster.
- but here's the weird thing.. the outputs are completly fine when checked in either a new Resolve project or in MC, it's only (only?) the monitoring that seems to be massivly screwed up
- the GPU. although a bit wimpy is not over heating, and even seems not to be using all it's limited cuda cores or RAM, the CPU's are not working all that hard either, there's some OFX in some of the shots, but deleting them made no diffrence.