Good to know. Better performance for the monitor output is probably a good thing to have. Especially now when Nuke seem to end up in more TVC oriented projects where clients might expect immediate response and real-time playback. Stuff that you don't necessarily need when comping away on a longer project where you can judge comps in context on other systems. What also would be great is if the viewer/caching could get even better. I know work has been done there and performance have been improved. But it doesn't feel perfect. Not sure if there is anything more that can be done?
On Tue, Mar 22, 2011 at 11:48 AM, Chris Bevan <[email protected]>wrote: > Hi all, > > [Disclaimer: this information may be out of date as I haven't been on the > Nuke team for a while, but odds are it's still reasonably accurate] > > Nuke's monitor output was only really written for viewing individual > frames, and not optimised for real-time playback unfortunately. Feel free > to send a request to support if real-time playback is important to you, > though - the more people who want it, the higher priority the fix, after > all. I'd always wanted to spend time making it faster myself, but we just > didn't have the opportunity back then. > > Turning on monitor output also means a few viewer optimisations, such as > GPU processing, have to be turned off, so that means things will generally > be a bit slower in that case. The reason for that is because we need the > final processed data to send to the monitor output card from the CPU rather > than the GPU. > > Sorry that's not the best news, but hopefully it's useful to know. > > - Chris > > >
_______________________________________________ Nuke-users mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
