
- Posts: 221
- Joined: Sun Jun 14, 2015 10:00 am
I apologise if this has been suggested - and /or is a feature that I have not reached yet in the manual.
DELIVERY CRASH :
+) Can you implement TRANSACTIONAL LOGGING in Deliveries please -
Eg after each whole clip is rendered out and / or every 5 (timeline) seconds of output footage.
When DELIVERY CRASHES - There should be at ability to RESTART the DELIVERY from the CRASH point.
+) Without being able to RESTART the delivery process - I could not RISK another failure 5 hours into RENDERING the whole footage in one go - and am currently DELIVERING on a INDIVIDUAL CLIP basis (with output set at UNCOMPRESSED 10bit RGB) so that I can manually replace the clips in the Timeline with the uncompressed footage - All to be able to render the whole TIMELINE in one go without crashing.
+) If DELIVERY could recover - I would only have lost at most 30 mins (if only 1 clips had to be re-rendered) and not 5 Hours.
+) You might even find more end users willing to adopt Beta version of your codebase (as a recoverable crash is far less frustrating that having to render the whole TIMELINE again).
If you do this option - I would recommend that on STARTUP of a Project - that 'continue Delivery Render' is an option that users are presented.
MISC 1) Rather than be be met with an Empty screen when Resolve Crashes - BM could get more insight into the crashes if you ask the User if they will like to submit a crash log there an then (with the ability to add comments before sending). [UPDATE] Margus indicates there is a Crash Report Window in the thread below (I may have missed this - and have not been greeted with a crash window so far)
MISC 2) If there is no Crash Error message (or number) shown to the users on Startup - it is difficult for users to search for that explicit crash on this Forum.
AJ
DELIVERY CRASH :
+) Can you implement TRANSACTIONAL LOGGING in Deliveries please -
Eg after each whole clip is rendered out and / or every 5 (timeline) seconds of output footage.
When DELIVERY CRASHES - There should be at ability to RESTART the DELIVERY from the CRASH point.
+) Without being able to RESTART the delivery process - I could not RISK another failure 5 hours into RENDERING the whole footage in one go - and am currently DELIVERING on a INDIVIDUAL CLIP basis (with output set at UNCOMPRESSED 10bit RGB) so that I can manually replace the clips in the Timeline with the uncompressed footage - All to be able to render the whole TIMELINE in one go without crashing.
+) If DELIVERY could recover - I would only have lost at most 30 mins (if only 1 clips had to be re-rendered) and not 5 Hours.
+) You might even find more end users willing to adopt Beta version of your codebase (as a recoverable crash is far less frustrating that having to render the whole TIMELINE again).
If you do this option - I would recommend that on STARTUP of a Project - that 'continue Delivery Render' is an option that users are presented.
MISC 1) Rather than be be met with an Empty screen when Resolve Crashes - BM could get more insight into the crashes if you ask the User if they will like to submit a crash log there an then (with the ability to add comments before sending). [UPDATE] Margus indicates there is a Crash Report Window in the thread below (I may have missed this - and have not been greeted with a crash window so far)
MISC 2) If there is no Crash Error message (or number) shown to the users on Startup - it is difficult for users to search for that explicit crash on this Forum.
AJ
Last edited by Antony Newman on Thu Jun 28, 2018 4:03 pm, edited 2 times in total.
Resolve Studio : v16.1.2.026
Mac Pro (2013) : Catalina 10.15.3 : 3.0GHz 10-Core/64GB
Dual AMD FirePro D700 6GB
RRX : TB2 (Sonnet Echo Express III-D)
Camera : Monstro VV : 8K R3D : 4K UHD Timeline
Cache : Sys SSD / Clips & PJ : Areca 24TB
Mac Pro (2013) : Catalina 10.15.3 : 3.0GHz 10-Core/64GB
Dual AMD FirePro D700 6GB
RRX : TB2 (Sonnet Echo Express III-D)
Camera : Monstro VV : 8K R3D : 4K UHD Timeline
Cache : Sys SSD / Clips & PJ : Areca 24TB