Thanks Henrik and everyone else. At the moment I have Studio running on a dedicated machine which is solely used to create/render/export comps and manage the project, while all the other machines run Nuke.
I could get rid of all the clips in between the VFX shots but it's likely we will be asked to pick up shots that have been removed which would be a bit of a headache (and frankly I shouldn't have to resort to this). The Centos idea is interesting. I may ask one of our engineers to give that a go in the new year and see how it performs. I have emailed support about this a couple of days ago but have yet to hear back. But to be honest I did go over this with them (via about 20 emails) several months ago. Charlie On 16 Dec 2015, at 7:24 am, Henrik Cednert <n...@irry.com<mailto:n...@irry.com>> wrote: CAUTION EXTERNAL EMAIL Yes. We use it, or rather try to use it, for long form and 45-60 min episodicals. The quicker you accept that it's not usable for this the better of you are. Sadly. They say that nS10 will improve this enormously but today it's a disaster. It's been like this for day one and I and others have loudly complained but without luck so far. Please send your experience to support so they can log it and so that these issues are up voted. Some people have resorted to work in reels instead of whole timelines. That's not something I'll ever do though. Wouldn't fit my working style and would only mean. I would have 4 projects open at the same time, which wouldn't help. A few of my "workarounds": * only conform the VFX shots. Never conform the whole timeline. If needed for review, conform a few shots before and after VFX. * never copy all cuts to the reference media. We export reference into our comps but we only slice up the parts where there's VFX shots. NS chokes with many cuts/items. Also play with different formats of your reference. Noticed that codec of your reference and also the codec of the audio in it can affect performance a lot. Not sure what's the best though. If you find out, let me know. =) * save a lot because it crashes a lot. * also, even though it can take a good 10 minutes to restart it... Do it regularly since a restart of it normally tends to give you 30-40 mins of less lockups, until it have leaked and filled your memory again. * if there's something like 'Sudu purge' or other memory purge solution for Windows, try that. Monitor your memory and see how it's used. Even with 128 GB RAM it will eventually come to a halt but it'll give you a few more minutes at least. Also, have a few spare keyboards handy. Have out of frustration hulk smashed a few myself. The marketing of nS doesn't really reflect the reality of it atm. =/ Cheers -- Henrik Cednert cto | td | compositor Filmlance International Cell +46 (0)704 71 89 54 www.filmlance.se<http://www.filmlance.se> On 15 Dec 2015, at 18:45, Charles Bedwell <charles.bedw...@encorepost.com<mailto:charles.bedw...@encorepost.com>> wrote: Is anyone out there having terrible performance issues with Nuke Studio when in the timeline? I have done a conform on a show roughly 90 minutes in length and am going through shots preparing notes, making comps, tagging, setting reference media etc and every 1-2 minutes I'm getting about a 30 second lockup. Just now after I had left the workstation untouched for an hour I selected a shot and added a note and it locked up for a minute while I was typing it out. I've noticed creating a comp from a clip can take an extended period of time (many minutes) while a single core on the PC is at 100% with the other 23 sitting idle. Is there anyone successfully using Nuke Studio for long form? I had engineers from the Foundry visit a while ago looking at lookups when creating comps but I never heard back from them. Disabling shot thumbnails hasn't made any difference. There is no way anyone can work like this for any length of time! Charlie 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 Nuke-users@support.thefoundry.co.uk<mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users DO NOT open attachments or click on links from unknown senders or unexpected emails _______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk<mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 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 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
