However, I believe it only happens when I have multiple Nukes open. When I have just one up, it’s solid.
Anyone verify? Or maybe this will help someone.
what is the best way to bring avchd footage to nuke ?
Thanks
Is anyone else experiencing, like, major cache issues? I haven’t had this problem before 6.3v2, but I’m not sure if it’s just me, or if it’s a memory issue (which I upgraded, recently) or disk issues (I just bought an SSD to serve as my OS disk, but all my caches are on a RAID)…
Pretty much, what’s happening is, every so often, in the viewer, the frame will start to render, and then at an indeterminate point, it’ll just fill the rest of the frame with some other frame, randomly. And then, once that’s cached, the frame is stuck like that. I have to go to another frame, clear my disk cache, clear my buffers, update my buffers, reload my read node, and go back to the frame in question… and if the frame needs to re-render for any reason (scaling in the viewport, changing a parameter, etc), I have to cross my fingers and hope it doesn’t happen again… because, more often than not, it does.
And it’s not just one particular frame that this happens to – it can happen to any frame, from any sequence, from any location on any drive. And it’s not just in the viewer – I’ve rendered precomps that end up with corrupt frames. It happens with a clean install of Nuke, no plugins or gizmos or python scripts. It happens eventually after I reboot. It happens whether or not I lay a diskcache node on. It happens regardless of whether I’m using aggressive caching. It happens with image sequences, quicktime movies, and raw red footage. It happens without warning. It happens regardless of viewer bit-depth, or whether or not I guide Nuke to utilize the GPU. It. won’t. stop. happening.
But… I’ve searched around the internet, and I’m beginning to think that this happens only to me… so… not totally sure if it’s Nuke or what. But I’ve been troubleshooting this crap for the past week so frequently that I’m barely getting work done, and I am really – really – really frustrated.
Anyone? Wanted to check to see if anyone else was having issues before bothering The Foundry.
I’ve experienced this issue as soon as I migrated to Nuke 6.3.
The newly created node will pop further down away from the last node I want the newly created to connect to. Sometimes, even out of the screen space allotted for the node graph.
I’ve tried creating new nodes via tab creation or the menu but the issue remains.
spec: NukeX 6.3v2, Win 7 x64, dual screen.
Is there a corresponding parameter in the pref that I can change to fix this behavior?
Thanks,
Jason
I dont know why, I worked on one shot in one day look like 20-30 time or more it’s fucking boring for me
anybody know how to fix it I cant belive why it’s just me :bomb:
My system
1. Mac Pro 3,1 OS X 10.6.8 64bit
– Xeon Quad Core 2 CPU
– Ram 16 GB
– Quadro 4000 for mac
– Stripe Raid with WD Black 6Gb/s X 3 disk
2. Hackintosh OS X 10.6.8 64bit
– i7950
– Asus Sabertooth X58
– G-Skill 12GB 1600Mhz
– ATI HIS 5770
– Stripe Raid with WD Black 6Gb/s X 3 disk
3. PC Window 7 Ultimate 64bit
– i7950
– Asus Sabertooth X58
– G-Skill 12GB 1600Mhz
– GTS450 1GB
– 1 TB WD Black 6Gb/s
It’s just Linux that I never use it 😀
i have a basic question
i want to view 2 clips that i imported when one clips ends the second one starts in the same timeline.
Thanks
First it asks for how many threads I want to use.
I have a mac pro 2010 8 core so how many threads do I have total?
How many should I use not use you think?
Second can I close my script down that has the write node in it thats rendering in the bg?
Third is there any good plugins that has a batch render option?
Thanks
This is site is run by Sascha Endlicher, M.A. during ungodly late night hours. Wanna know more about him? Connect via Social Media by jumping to about.me/sascha.endlicher.
