Place a single 3D HD MVC file on the timeline, at least 15 minutes long, then set Produce to make an AVC 3D HD file.
Before starting the render, open Windows task manager and select performance to monitor what happens during the render process.
For me, everything starts well, all 8 threads at 100% and about 30% RAM is used, but slowly, the Cached RAM usage rises, the available RAM drops and the overall Physical memory usage rises to about 96%, at which point the CPU's activity drops to around 30% and a little of the RAM becomes available again, and back up goes the CPU.
This continues, as the overall processing slows down, projected completion gets longer and longer. Eventually, the RAM usage hits 99%, leaving no resource for anything and Windows processes freeze and the file Production fails at that point.
If you leave everything alone, the system recovers, but the file is truncated at the freeze up point, so not the full length.
It appears that PD10 is simply mauling the system without any limiting and depriving evrything else of resources - could this be related to the phantom file failures and vision freezes that are being reported?
if I do the same with 2D sources or even just a 2D destination AVC file, CPU usage drops to 70% and RAM usage never rises above 20% - all good.
Soooo, is the 3D renderer uncapped, and able to kill the system?
Anyone able to test this at all?
Paul
i7 920 300GB Samsung system drive, GTX285 6GB RAM - no other software -
This message was edited 2 times. Last update was at Feb 21. 2012 03:01