Hey Charley, On 5 June 2015 at 10:52, Charles Bedwell <[email protected]> wrote:
> Pretty sure I see this error often in 9.05. > You mean this error I assume "QClipboard :: event(class QEvent *) Cowardly refusing to send clipboard message to hung application". The bug we fixed related to reads, not writes, unfortunately. We will investigate. Outputting preview quicktimes is often a bit of a nightmare, especially > H.264's. Firstly the output bitrate always defaults to 90, secondly the > codec options always pops up under the Nuke window, thirdly it seems very > easy for either the bitrate, keyframes or FPS to become corrupted, > sometimes I open the codec options and there is a massive number in there, > eg. Keyframe every [8487262734] frames. > You guys are on Windows, right? We have several bugs logged against h264 on Windows and our creative specialists are continually pestering me about them, so we're looking at the scheduling for fixing these issues as well as improving our Quicktime auto-test framework. In the meantime you should find that writing out Apple ProRes gives you better stability and performance as they use the newer 64-bit in-process writers - we're unable to write h264 in this way, although we can *read* h264 using mov64. Also, with mov64 the advanced options are all in the Writer's Node-panel so you don't need to go to the IPC helper options. Some times the codec options wont open, and when you click on it the FPS > slider drops to 0. Restart nuke to fix. "Worker process failed" in terminal. > I have reproduced the codec-options not loading and the key frame issue you mention above - although I get a "worker-process already stopped" pop-up - I have no problems rendering out ProRes via mov64 and it's faster (at least for my noddy, bright pink developer footage). Weird. > +1 yup, sorry about that. But it is getting much better/saner. F. > > > On 5 Jun 2015, at 10:31 am, Frank Harrison <[email protected]> > wrote: > > On 5 June 2015 at 10:05, Simon Björk <[email protected]> wrote: > >> "QClipboard :: event(class QEvent *) Cowardly refusing to send >> clipboard message to hung application" >> >> I get this a lot even in Nuke9.0v6. And I mean a lot. If I look at the >> terminal after working for a few hours I often have something like 5-10 >> lines of this message. Quite annoying. Are you saying it has to do with >> Quicktimes? >> > The issue we fixed was associated with the Quicktimes using the old > reader, yes. > > Which Nuke-edition are you using, studio or nukex? Also, are you using > 9.0v6? > This e-mail and any attachments are intended only for use by the > addressee(s) named herein and may contain confidential information. If you > are not the intended recipient of this e-mail, you are hereby notified any > dissemination, distribution or copying of this email and any attachments is > strictly prohibited. If you receive this email in error, please immediately > notify the sender by return email and permanently delete the original, any > copy and any printout thereof. The integrity and security of e-mail cannot > be guaranteed. > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > > > > P Please consider the environment before printing this email. > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > -- Frank Harrison Senior Nuke Software Engineer The Foundry Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 Web: www.thefoundry.co.uk Email: [email protected]
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
