by Alan Maiden on Nov 22, 2011 at 12:04:15 pm
Can anyone tell me why now on Smoke 2012 software a progressive timewarp has to render the clip!
Previously if you did a progressive timewarp either faster or slower it would just double up frames or throw frames away and the timewarp would be instant. Now it seems to actually reprocess the clip, an possible even generate new frames within the smoke I would guess. This can be very frustrating when timewarping an HD clip of 3 minutes.
Re: Timewarping by Alan Maiden on Nov 22, 2011 at 4:00:19 pm
It has never rendered progressive timewarps in the past. It has always treated them like repeat frames or frame cutting so no processing and no new media written to its stones. It has only come about since the 2012 upgrade!
The behaviour has been changed since we introduced the Source Grading workflow with Lustre in Smoke 2012 Extension/SAP 1. We now need to explicitely render the frames to be able to exchange them with Lustre through WireTap.
If you are not interested in this workflow, you can set an environment variable so the old behaviour is restored:
1. Open a terminal
2. write the following line: defaults write ~/.MacOSX/environment DL_DISABLE_NOOP_SOFT_FX_OPTIMISATION 0
1. Be sure to be logged as the software
2. Open a shell
3. write the following line: nedit .cshrc
>>> A text editor will open
4. In the text editor, add the following line: setenv DL_DISABLE_NOOP_SOFT_FX_OPTIMISATION 0
In both case, it is easier to close all the windows and start the application again (MAC) and from another shell (Linux)
Re: Timewarping by Alan Maiden on Nov 25, 2011 at 2:32:46 pm
Thank you for this. I have just received exactly the same from Autodesk and it is brilliant. It fixes the rendering of progressive timewarps so they no longer render, saves so much time.
On a similar note, I believe there is a similar script to fix lighting between 2011 and 2012 software. I don't suppose you've come across that one have you, I can't find it.