Sadly I can’t replicate this with this method. I have seen the crash, plenty, 
but for my spec there’s no solid “do a, b and c and it’ll crash”. That’s what 
TF would need in a bug report. =/

Cheers


-- 
Henrik Cednert
cto | td | compositor

Filmlance International
www.filmlance.se

> On 2 maj 2016, at 20:15, Marten Blumen <mar...@gmail.com> wrote:
> 
> Yeah - that hardware preference fixed it only for a bit. After some minutes 
> it froze the machine that needed a hardware reset.
> 
> Driver 346.02.03f05
> 
> Thanks!
> 
> On 2 May 2016 at 22:36, Henrik Cednert <n...@irry.com <mailto:n...@irry.com>> 
> wrote:
> Cool.I’ll raise this on the side as well.
> 
> Regarding driver version. In () after that number you wrote is one on the 
> form 346.##.##X##. What does your say?
> 
> Cheers
> 
> -- 
> Henrik Cednert
> cto | td | compositor
> 
> Filmlance International
> www.filmlance.se <http://www.filmlance.se/>
> 
>> On 2 maj 2016, at 09:11, Marten Blumen <mar...@gmail.com 
>> <mailto:mar...@gmail.com>> wrote:
>> 
>> Looks like unchecking the hardware preference GPU 'expand 3 to 4 channels' 
>> might have solved it. Worth testing.
>> 
>> On 2 May 2016 at 17:16, Marten Blumen <mar...@gmail.com 
>> <mailto:mar...@gmail.com>> wrote:
>> Cool - yep it's a MacPro 5,1. Cuda 7.5.26, Driver 10.5.2, OsX 10.10.5, and 
>> whatever the current latest is for 10.11.5 beta.
>> 
>> Easily happens with iPhone H.264 footage, in the timeline trim the clip, 
>> click drag on the left clip edge, as the preview window appears NS will 
>> freeze within a few seconds.   Upon rebooting the Console.app will show some 
>> 'killGpu' commands, which should be the GPU timeout protection.
>> 
>>  
>> 
>> On 2 May 2016 at 17:01, Henrik Cednert <n...@irry.com 
>> <mailto:n...@irry.com>> wrote:
>> 
>> Interesting. Reported similar issues in beta but thought it was my machine 
>> and stopped them from chasing it down. MacPro5,1? What cuda and driver 
>> version?
>> 
>> Do you have a case that's easily  replicable that I can try here? I never 
>> found a way to consistently provoke it to do this. 
>> 
>> MacPro 5,1, titanX, cuda 7.5.21, gpu driver 346.02.03f04 at my end. 
>> 
>> If you get a bug logged, can you post that number here?
>> 
>> Cheers
>> 
>> --
>> Henrik Cednert
>> cto | td | compositor
>> 
>> Filmlance International 
>> Cell +46 (0)704 71 89 54
>> www.filmlance.se <http://www.filmlance.se/>
>> 
>> On 02 May 2016, at 04:03, Marten Blumen <mar...@gmail.com 
>> <mailto:mar...@gmail.com>> wrote:
>> 
>>> Yep - Cuda is up to date.  NukeX is running fine. I'll see how the support 
>>> tickets go.
>>> 
>>> Cheers!
>>> 
>>> On 2 May 2016 at 13:37, Deke Kincaid <dekekinc...@gmail.com 
>>> <mailto:dekekinc...@gmail.com>> wrote:
>>> I’m using it fine.  I get the normal Nuke crashes but it crashes a lot less 
>>> then 9.0v8.  They fixed most of the El Cap crash bugs during the beta.  Did 
>>> you update your cuda drivers?
>>> 
>>> On Sun, May 1, 2016 at 4:50 PM, Marten Blumen <mar...@gmail.com 
>>> <mailto:mar...@gmail.com>> wrote:
>>> Is anyone successfully running Nuke Studio on OsX 10.10/11?
>>> 
>>> Getting GPU hangs and machine hard-restarts whilst testing it with simply 
>>> H.264, DPX and Exr clips, on a Gtx 980. 
>>> 
>>> 
>>> Thanks!
>>> 
>>> _______________________________________________
>>> Nuke-users mailing list
>>> Nuke-users@support.thefoundry.co.uk 
>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>>> 
>>> 
>>> _______________________________________________
>>> Nuke-users mailing list
>>> Nuke-users@support.thefoundry.co.uk 
>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>>> 
>>> _______________________________________________
>>> Nuke-users mailing list
>>> Nuke-users@support.thefoundry.co.uk 
>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>> _______________________________________________
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk 
>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>> 
>> 
>> _______________________________________________
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk 
>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
> 
> _______________________________________________
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk 
> <mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ 
> <http://forums.thefoundry.co.uk/>
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
> 
> _______________________________________________
> 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

_______________________________________________
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

Reply via email to