Re: [Nuke-users] email nuke_users list vs forum nuke_users list

[adam jones]

cheers mate

subscription to the forum it is then

regards
-adam


> On 9 Feb 2017, at 2:12 PM, Frank Rueter|OHUfx  wrote:
> 
> They are not connected and it's supper, super, super frustrating.
> Afaik the "official" one is the forum now, so no guarantee that Foundry folks 
> will be on the mailing lists anymore. At least that is what I have been told 
> in the past.
> 
> I really wish the forum and mailing list were finally folded together and one 
> could either use email or the web interface to interact with it.
> 
> I tend to only post to the mailing list cause it's nice and efficient, but 
> try to answer in the forum as well.
> 
> 
> frank
> 
> On 9/02/17 2:53 PM, adam jones wrote:
>> Dear all
>> 
>> I do recall this has been discussed prior but if some one could recap me as 
>> I am a little confused.
>> 
>> Are the two lists connected or should I be looking at both to get my eye 
>> over all posts regarding nuke?
>> 
>> And should they not be connected does the forum nuke_users list send out 
>> emails when new posts come the forums way?
>> 
>> regards
>> -adam
>> 
>> 
>> ___
>> 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

___
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

Re: [Nuke-users] email nuke_users list vs forum nuke_users list

[Frank Rueter|OHUfx]

They are not connected and it's supper, super, super frustrating.
Afaik the "official" one is the forum now, so no guarantee that Foundry 
folks will be on the mailing lists anymore. At least that is what I have 
been told in the past.


I really wish the forum and mailing list were finally folded together 
and one could either use email or the web interface to interact with it.


I tend to only post to the mailing list cause it's nice and efficient, 
but try to answer in the forum as well.



frank

On 9/02/17 2:53 PM, adam jones wrote:

Dear all

I do recall this has been discussed prior but if some one could recap me as I 
am a little confused.

Are the two lists connected or should I be looking at both to get my eye over 
all posts regarding nuke?

And should they not be connected does the forum nuke_users list send out emails 
when new posts come the forums way?

regards
-adam


___
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

[Nuke-users] email nuke_users list vs forum nuke_users list

[adam jones]

Dear all

I do recall this has been discussed prior but if some one could recap me as I 
am a little confused.

Are the two lists connected or should I be looking at both to get my eye over 
all posts regarding nuke?

And should they not be connected does the forum nuke_users list send out emails 
when new posts come the forums way?

regards
-adam


___
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

Re: [Nuke-users] Clicking on a node doesn't always open the properties panel

[Andrew Mumford]

With the mouse right ? I've always had an issue with Wacom pen if node wasn't 
previously open in properties tab ..
With the mouse not seeing that on Win 10 or OSX.
---
Andrew Mumford

On Feb 08, 2017, at 11:01 AM, Josh Imbruglia  
wrote:

I'm wondering if anyone else is experiencing an issue in Nuke 9/10 where double 
clicking on a node doesn't always open the properties tab. If you cut and paste 
it back into the node graph it then opens the property tab again.

It's driving myself and many other artists crazy and just wanted to see if it 
was a common issue others have encountered.

Thanks!
Josh
___
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

Re: [Nuke-users] Clicking on a node doesn't always open the properties panel

[Igor Majdandzic]

Nope, haven't experienced it yet. But thanks for the workaround.I'm on win10Send from the RoadIgor MajdandzicCompositor, TD, Supervisor@Chimney FrankfurtAm 08.02.2017 8:47 nachm. schrieb Josh Imbruglia :I had a feeling it wasn't just me, glad to see that the copy and paste workaround will save you some time too.Thanks for the reply, wondering if anyone else has workarounds or fixes.CheersOn Wed, Feb 8, 2017 at 7:26 PM, Bruno-Pierre Jobin  wrote:I have come across that issue a few times too. Didn't know about the cut and paste. I usually just restarted Nuke but I would love to get a better solution.On Wed, Feb 8, 2017 at 2:01 PM, Josh Imbruglia  wrote:I'm wondering if anyone else is experiencing an issue in Nuke 9/10 where double clicking on a node doesn't always open the properties tab. If you cut and paste it back into the node graph it then opens the property tab again.It's driving myself and many other artists crazy and just wanted to see if it was a common issue others have encountered.Thanks!Josh
___
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-- Bruno-Pierre Jobin

___
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

Re: [Nuke-users] Clicking on a node doesn't always open the properties panel

[Josh Imbruglia]

I had a feeling it wasn't just me, glad to see that the copy and paste
workaround will save you some time too.

Thanks for the reply, wondering if anyone else has workarounds or fixes.

Cheers

On Wed, Feb 8, 2017 at 7:26 PM, Bruno-Pierre Jobin 
wrote:

> I have come across that issue a few times too. Didn't know about the cut
> and paste. I usually just restarted Nuke but I would love to get a better
> solution.
>
> On Wed, Feb 8, 2017 at 2:01 PM, Josh Imbruglia <
> the.factory.sm...@gmail.com> wrote:
>
>> I'm wondering if anyone else is experiencing an issue in Nuke 9/10 where
>> double clicking on a node doesn't always open the properties tab. If you
>> cut and paste it back into the node graph it then opens the property tab
>> again.
>>
>> It's driving myself and many other artists crazy and just wanted to see
>> if it was a common issue others have encountered.
>>
>> Thanks!
>> Josh
>>
>> ___
>> 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
>>
>
>
>
> --
> Bruno-Pierre Jobin
>
> ___
> 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

Re: [Nuke-users] Clicking on a node doesn't always open the properties panel

[Bruno-Pierre Jobin]

I have come across that issue a few times too. Didn't know about the cut
and paste. I usually just restarted Nuke but I would love to get a better
solution.

On Wed, Feb 8, 2017 at 2:01 PM, Josh Imbruglia 
wrote:

> I'm wondering if anyone else is experiencing an issue in Nuke 9/10 where
> double clicking on a node doesn't always open the properties tab. If you
> cut and paste it back into the node graph it then opens the property tab
> again.
>
> It's driving myself and many other artists crazy and just wanted to see if
> it was a common issue others have encountered.
>
> Thanks!
> Josh
>
> ___
> 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
>



-- 
Bruno-Pierre Jobin
___
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] Clicking on a node doesn't always open the properties panel

[Josh Imbruglia]

I'm wondering if anyone else is experiencing an issue in Nuke 9/10 where
double clicking on a node doesn't always open the properties tab. If you
cut and paste it back into the node graph it then opens the property tab
again.

It's driving myself and many other artists crazy and just wanted to see if
it was a common issue others have encountered.

Thanks!
Josh
___
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

Re: [Nuke-users] frame sequence range detection

[Michael Hodges]

Fantastic.  Thanks so much Gabor.

You’ve saved me twice now:)


Michael


> On Feb 8, 2017, at 4:23 AM, Gabor L. Toth  wrote:
> 
> Hi!
> 
> Welcome! :) Here is the latest version of my script, it should work with 
> expressions, we also use that often. It is used just selecting the readnodes 
> and executing the script. We use it many times so it is tied to a hotkey, I 
> think this is better than having buttons on each node. 
> 
> Hope it helps
> Gabor
> 
> 
> On Wed, Feb 8, 2017 at 2:35 AM, Michael Hodges  > wrote:
> 
> I’ve begun to answer my own question and I think I’m pretty close on this.
> 
> I’ve started to adapt a script I found from Gabor Toth (thanks Gabor!) and 
> hopefully this will help others as well.
> 
> I put a python button on the read node that contains the script below which 
> replaces the frame ranges correctly.
> 
> The reason I used a button is that it was an easy way to see if it would 
> work, and two, I couldn’t really figure out how to configure the command to 
> the specific node on demand.
> 
> 
> 
> Three questions:
> 
> 1.  Is a button the a good way to achieve this?  I thought it might be best 
> to have it hardwired on the node as it will be buried in one or more gizmos 
> (that may be created procedurally) and I didn’t trust my Python chops to 
> isolate it from the other read nodes in the script
> 
> 
> 2.  Assuming that this is the best approach how would I activate the button 
> press from another node?
> 
> 
> 3. Since the “file” value is generated by an expression ( in my case: [value 
> Controller.ClipPath] the real path isn’t being resolved to the script and 
> fails.  It does work as expected with a text path.  Would a different 
> expression technique work or do I have to create some additional python magic?
> 
> 
> 
> Thanks!
> 
> 
> Michael
> 
> 
> 
> 
> 
> import nuke
> import os
> import os.path
> import math
> import glob
> import re
> 
> n = nuke.thisNode()
> 
> 
> seqPath = n.knob('file').value()
> if seqPath is not None and re.match('.*\.%0.*', seqPath):
> indx = seqPath.find('%0')
> pattern = '%0' + seqPath[indx + 2] + 'd'
> seqPathMask = seqPath.replace(pattern, '*')
> print ''
> print 'PathMask: %s' % (seqPathMask)
> seqDir = os.path.dirname(seqPath)
> print 'Directory: %s' % (seqDir)
> if os.path.exists(seqDir):
> files = os.listdir(seqDir)
> #print files
> 
> #sorting files
> filteredFiles = glob.glob(seqPathMask)
> filteredFiles.sort()
> if len(filteredFiles) != 0:
> (firstFileName, ext) = 
> os.path.splitext(filteredFiles[0])
> firstFileTags =  firstFileName.split('.')
> 
> sfs = firstFileTags[-1]
> print 'Extension: ' + ext
> sf = int (sfs)# converted to int
> print "Start frame: %s" % (sf)
> 
> (lastFileName, ext) = 
> os.path.splitext(filteredFiles[len(filteredFiles)-1])
> lastFileTags =  lastFileName.split('.')
> efs = lastFileTags[-1]
> ef = int (efs)
> print "End frame: %s" % (ef)
> 
> n.knob('first').setValue(sf)
> n.knob('last').setValue(ef)
> else:
> print 'No matching files in this directory! 
> Skipping...'
> else:
> print 'Warning! Directory doesnt exist: ' + seqDir
> else:
> pass
> 
> 
> 
> 
> 
> > On Feb 7, 2017, at 11:16 AM, Michael Hodges  > > wrote:
> >
> > Is there a way to detect/update the frame range of an image sequence ( 
> > Example_File.#.dpx) in a read node?
> >
> > I’ve got some expressions that can change the input file within a gizmo 
> > read node but then I’m stuck with the previous file’s values.  I understand 
> > that this may be end up having to be a some sort of python file-counting 
> > callback but I want to check first if there is a way of doing it within 
> > Nuke.
> >
> >
> > Thanks,
> >
> > Michael___
> > 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/ 
> 
>