Re: [Nuke-users] pfGlitchy - Student gizmo feedback

[Thomas Volkmann]

Just skipped through the video for now, but it looks very nice. Definitely going
to remember it when I need something like this!
Greetings from Söderhamn!
 
/Thomas

> Peo Fogelström  hat am 6. März 2017 um 15:55
> geschrieben:
> 
>  Hi everyone,
> 
>  I was recommended by my awesome compositing teacher (Misho Ristov) to e-mail
> this list to get some much needed feedback regarding a gizmo I created as a
> personal project as part of my education.
> 
>  I've uploaded it to Nukepedia and made a video for it as well that can be
> found in the description.
> 
>  I have asked around in class and as well on the Foundry groups on Facebook
> for feedback but I've yet to receive anything. Seeing as I'm a first year
> student with only a few months of experience of NUKE I'm not 100% confident in
> how to assess my own work. Especially this kind since we haven't had any
> education regarding it. I'm just personally into that kind of part of NUKE at
> the moment.
> 
>  Anyway... thanks in advance for any and all comments and feedback.
>   
>   
>   
>  http://www.nukepedia.com/gizmos/filter/pfglitchy_bv05
> 
>  /Peo, aspiring VFX-artist
>  ___
>  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] Camera "Read from File" scripting issues

[Thomas Volkmann]

Works like a charm!!
Thanks!
 
 

> Ben Dickson <ben.dick...@rsp.com.au> hat am 2. März 2016 um 13:46 geschrieben:
>
>
> Try cam.forceValidate() after setting read_from_file to True
>
> On 02/03/16 23:04, Thomas Volkmann wrote:
> > Hi,
> > I want to load an Alembic camera via script and disable 'read from file'
> > straight away, so that I can change values for 'near' and 'far'.
> > Problem is, that Nuke doesn't read in the Alembic file when I disable
> > 'read_from_file' within the same script.
> > Basically I do:
> >
> > 1. cam = nuke.toNode("Camera")
> >
> > 2. cam.knob('file').setValue()
> >
> > 3. cam.knob('read_from_file').setValue(True)
> >
> > 4. cam.knob('read_from_file').setValue(False)
> >
> > Steps 2 and 3 are interchangeable, the result is the same: I don't get
> > the animation curves
> >
> > Any ideas for a workaround? Otherwise the user will just have to run a
> > second script afterwards..
> >
> > cheers,
> >
> > Thomas
> >
> >
> >
> > ___
> > 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
> >
>
> --
> ben dickson
> 2D TD | ben.dick...@rsp.com.au
> rising sun pictures | www.rsp.com.au
>___
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] Camera "Read from File" scripting issues

[Thomas Volkmann]

Hi,
 
I want to load an Alembic camera via script and disable 'read from file'
straight away, so that I can change values for 'near' and 'far'.
Problem is, that Nuke doesn't read in the Alembic file when I disable
'read_from_file' within the same script.
Basically I do:

1. cam = nuke.toNode("Camera")

2. cam.knob('file').setValue()

3. cam.knob('read_from_file').setValue(True)

4. cam.knob('read_from_file').setValue(False)

 

Steps 2 and 3 are interchangeable, the result is the same: I don't get the
animation curves

Any ideas for a workaround? Otherwise the user will just have to run a second
script afterwards..

 

cheers,

Thomas___
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] Change Read-Path depending on Write-node?

[Thomas Volkmann]

Exactly what I'm looking for.
Thanks!!
 
/Thomas
 

> Hugo Léveillé <hu...@fastmail.net> hat am 11. Februar 2016 um 13:13
> geschrieben:
> 
>  There is multiple solution to this.
>   
>  One would probably be the beforeRender callback where the write node would
> modify the path of the read node. You could also save a .py template with some
> placeholders and use the sys,argv to fill your placeholders. So you would
> always use the same .py file but depending of the argurment that you provide
> in the command line, Nuke would render to your desired location without saving
> a script
>   
>  But I would start with the beforeRender callback. Just put a simple function
> that modify the path of the read.
>   
>   
>   
>  --
>Hugo Léveillé
>   
>   
>  On Thu, Feb 11, 2016, at 07:00, Thomas Volkmann wrote:
> 
>  > >  Hi,
> >   
> >  let's say I have a couple of sequences that shall all run through  the
> > same nodesetup and then get written to a new location.
> >  What is your typical setup for this?
> >  At the moment we do it with linked switches, but if you want to send
> > stuff to the renderfarm, you have to save a scene for every switch setting.
> >   
> >  I was wondering if Nuke is aware of which write node is active, and
> > have the Read-node load the footage accordingly.
> >  Basically:  
> >  if Write1:  all [SHOT] tokens in all Read-filepaths get replaced with
> > "sh001" (you define that stuff in a text node, or it is the Write-name, or
> > whatever)
> >  if Write2:  all [SHOT] tokens in all Read-filepaths get replaced with
> > "sh002"
> >  and so on...
> >  (manually set a default while you are working and no write is active)
> >   
> >  Would that be possible somehow? (Maybe there is a much better solution
> > that I don't know about?)
> >   
> >  cheers,
> >  Thomas
> >  ___
> >  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
> > 
> >  >   
> 

 

> ___
>  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] RotoPaint vs Roto

[Thomas Volkmann]

This is why I use a single window spread over two monitors as a layout.
Unfortunately since Nuke9 it doesn't get saved properly anymore (scales to just
one screen). So first thing when launching Nuke is always resizing the window
over both monitors I hate it (even more as it worked just fine in Nuke8!) :/
 

 Charles Bedwell charles.bedw...@encorepost.com hat am 29. April 2015 um
 13:26 geschrieben:
 
  I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05
 and Windows 7.
   
  When hovering the mouse over the viewer and tapping A I get to see the alpha.
 If I type R I get a read node. G for Grade. B for Blur. It's a little
 inconsistent in how it works. If the mouse is back over the DAG (without
 clicking anything) and I type A nothing happens.
   
  I would prefer if the mouse is over the viewer and I type R G B A Y or M I
 get to view the appropriate channel. Not just the Alpha.
 
   
   
  On 29 Apr 2015, at 12:01 pm, Daniel Hartlehnert dah...@gmx.de
 mailto:dah...@gmx.de  wrote:
 
 I remember i had the same behavior on windows too. Its because i
always put the viewer into a separate window to move it onto the
second monitor.
   Good tip for the linux setting though, thanks.
  
   Am 25.04.2015 um 16:08 schrieb Howard Jones:
  
  
   Just a thought…
If you have floated the viewer, on a mac you will have to click
   on it but on linux as long as you set focus follows mouse in the Xwindows
   settings it should work.
Otherwise you should have been ok.
 
H
   
   
 On 25 Apr 2015, at 13:22, Daniel
Hartlehnert dah...@gmx.de mailto:dah...@gmx.de 
wrote:


 On 1 April 2015 at 17:04, Daniel Hartlehnert
 dah...@gmx.de mailto:dah...@gmx.de  wrote:
 
 Because it also means to constantly click in the viewer
 before pressing A to make sure it has the focus. 
 You don't need to click in the viewer, just have the mouse
 hovering over it.
  
 Somehow that never worked for me. Maybe its an OS thing? I
was working on Linux at that time.
 ___
 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

 ___
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
   
  

 ___
   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
  


 

 ___
  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] The forums are moving

[Thomas Volkmann]

+1
Already subscribed to the google-groups...
 

 Fredrik Averpil fredrik.aver...@gmail.com hat am 5. Februar 2015 um 08:25
 geschrieben:
 
  So many have now commented on this so I don't know if another email just adds
 to the spam factor or not...
 
  I also prefer mailing lists before forums. Because:
   
  - I subscribe to a number of mailing lists (I count 9 here now), which would
 translate to a number of forums. I simply don't have the time to go into
 multiple forum sites, dive into the topics and sub-topics – unless I have a
 specific issue.
   
  What this means is I do visit forums, but not to contribute to a community or
 answer someone's question, but to ask for help.
   
  With a mailing list. it is much easier for me to parse the constant flow of
 topics as well as contribute, as I can scroll through subjects and pick the
 ones that I find interesting. I read and sometimes comment, and in that sense
 contributing to the community. Honestly, I learn tons from the mailing lists
 I'm subscribed to since it's just so easy to take it in.
   
  Of course there are times when I won't have time to parse the steady flow of
 mailing list topics. But I wouldn't have had time for forums either.
   
  Then I also use Stack Overflow. Which is nothing like a mailing list or a
 forum, in its traditional sense. But it has interesting mechanics which I
 think a support forum should have. Heck, Google is using Stack Overflow
 instead of creating their own support forums. Take Google Compute Engine on
 Stack Overflow for example. I got help directly from the developers on a few
 things there. But it's designed to work only if you want to gain points by
 answering questions or if you need to ask a question – or in that case,
 because the company wanted to provide support. There's no friendly chitchat on
 Stack Overflow, and there shouldn't be. It's not a community, it's a support
 forum.
   
  I'm not opposed moving these lists to a forum, but I hope that it will offer
 the possibility to act as a mailing list as well, or at least I will probably
 just show up when I am facing a tricky issue that I need to solve. Which means
 I'm going to treat it like Stack Overflow - or a support forum. Not a
 community.
  And if that is what is going to happen, I'm sure the ones thinking like me
 will join in on a regular mailing list, complementing the forum.
   
   
 
  Regards,
  Fredrik
   
   
  ___
  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] decent mov format on linux

[Thomas Volkmann]

Is this true for ffmpegReader, too? I tried to build it for a whole day, and it
compiled without error, but it wasn't working in Nuke...drove me crazy. I ended
up blaming it on my limited skills and/or a wrong setup (although I made sure I
have the right gcc available).


 Jimmy Christensen ji...@ghost.dk hat am 4. April 2014 um 07:48 geschrieben:


 Speaking of the compile of ffmpeg in Nuke. In Nuke 8 it seems the
 ffmpegWriter examples are not based on the actual writer compiled in
 Nuke. Previously it was possible to use that example to re-compile the
 plugin. Will the source for the ffmpegWriter be released for Nuke 8?

 Hilsen
 Jimmy Christensen
 Developer
 Ghost A/S

 On 03/04/14 14:53, Deke Kincaid wrote:
  I don't think our ffmpeg is compiled against x264 as it requires a
  licensing fee for commercial use so I don't think there are any h264
  codecs in our ffmpeg writer. Unfortunately I'm on a mac right this sec
  so I can't check as there are lots of codecs in there.
 
  --
  Deke Kincaid
  Creative Specialist
  The Foundry
  Skype: dekekincaid
  Tel: (310) 399 4555 - Mobile: (310) 883 4313
  Web: www.thefoundry.co.uk http://www.thefoundry.co.uk/
  Email: d...@thefoundry.co.uk mailto:d...@thefoundry.co.uk
 
 
  On Thu, Apr 3, 2014 at 8:43 AM, Elias Ericsson Rydberg
  elias.ericsson.rydb...@gmail.com
  mailto:elias.ericsson.rydb...@gmail.com wrote:
 
  Using the default in nuke does usually not cause a problem with
  playback. Otherwise I usually go for h264 as a codec for mov containers.
 
  Cheers,
  Elias
 
  3 apr 2014 kl. 09:03 skrev Howard Jones mrhowardjo...@yahoo.com
  mailto:mrhowardjo...@yahoo.com:
 
  
   What's a decent all round format on Nuke Linux for creating movs.
  
   On mac I use photo-jpeg, but without testing each format on Linx
  I don't know which one would be similar.
  
   Thanks in advance of not having to run that test :)
  
   Howard___
   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
  ___
  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
 
 
 
 
  ___
  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] Linux read DNxHD Quicktimes

[Thomas Volkmann]

The main issue that I'm having is that Nuke/Hiero doesn't play DNxHD at all on
linux. That's no problem when using Nuke, because as mentioned before you
wouldn't want to work with that.
But not being able to use HieroPlayer right now is a real bummer!!  Especially
since these Quicktimes play just fine in every other application on my system :/

cheers,
Thomas


 Ben Woodhall woodh...@thefoundry.co.uk hat am 3. April 2014 um 12:45
 geschrieben:
 
  In case it helps, QuickTime (mov) support has had a major overhaul using the
 Apple QuickTime libraries on Mac and Windows in Nuke 8.0.  Unfortunately this
 doesn't affect Linux as support for ffmpeg is limited.
 
  Feel free to send any stability or colour fidelity issues that you find with
 movs to support and we can look into them.  As Nathan says, many of the codecs
 have stability problems.  We have found quite a few with settings which don't
 work on various platforms.  In our overhaul for 8.0 we have avoided known
 issues with DNxHD on Mac and Windows and provided additional user controls to
 avoid stability problems.
 
  Thanks,  Ben
 
  On 28/03/2014 17:45, Nathan Rusch wrote:
 
 The best solution is to not use MOVs in Nuke. There are numerous
stability problems with various codecs, especially on Linux.
  
   -Nathan
  
   From: Thomas Volkmann mailto:li...@thomasvolkmann.com
   Sent: Friday, March 28, 2014 10:34 AM
   To: Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk
   Subject: Re: [Nuke-users] Linux read DNxHD Quicktimes
  
   So what is the workaround?  I just tried using the system libraries,
  but that gave me a segmentation fault :/
  
   Nathan Rusch nathan_ru...@hotmail.com
   mailto:nathan_ru...@hotmail.com hat am 28. März 2014 um 18:27
   geschrieben:
   
 Nuke’s ffmpegReader plugin has certain codecs blacklisted, some
   because of licensing issues and others for unknown reasons. DNxHD is
   definitely on that list in 7.0, and even though the plugin has changed in
   8.0, there is still a codecBlacklist.h file included that I can only
   assume still contains DNxHD.
 -Nathan
 From: Thomas Volkmann mailto:li...@thomasvolkmann.com
 Sent: Friday, March 28, 2014 9:29 AM
 To: Nuke user discussion
   mailto:nuke-users@support.thefoundry.co.uk
 Subject: Re: [Nuke-users] Linux read DNxHD Quicktimes
 Didn't know about that one, thanks.
 But unfortunately Nuke continues to give me unsupported codec :/
   
  Py Fave pyf...@gmail.com mailto:pyf...@gmail.com hat am 28.
  März 2014 um 17:09 geschrieben:
 
 
  add ffmpeg: in loader url ?
 
  ffmpeg:/home/user/myvideo.mov
 
 
 
 
  2014-03-28 15:18 GMT+01:00 Thomas Volkmann
  li...@thomasvolkmann.com mailto:li...@thomasvolkmann.com :
   Hi,
   my Nuke and HieroPlayer installations (Fedora20) are not able to
   read DNxHD
   Quicktimes. What is the regular procedure to get this to work?
   I have no problem watching them with different players. Google
   brought up a
   couple of threads, but the useful one ended with I got it to
   work :/
  
   thanks,
   Thomas
  
   ___
   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
 
   
   
   
   
 -
 ___
 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
   
  
  
  
  
  
  
   -
   ___
   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
  
  
  
   ___
   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
  


___
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] Linux read DNxHD Quicktimes

[Thomas Volkmann]

Hi,
my Nuke and HieroPlayer installations (Fedora20) are not able to read DNxHD
Quicktimes. What is the regular procedure to get this to work?
I have no problem watching them with different players. Google brought up a
couple of threads, but the useful one ended with I got it to work :/

thanks,
Thomas___
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] Linux read DNxHD Quicktimes

[Thomas Volkmann]

So what is the workaround?  I just tried using the system libraries, but that
gave me a segmentation fault :/


 Nathan Rusch nathan_ru...@hotmail.com hat am 28. März 2014 um 18:27
 geschrieben:
 
  Nuke’s ffmpegReader plugin has certain codecs blacklisted, some because of
 licensing issues and others for unknown reasons. DNxHD is definitely on that
 list in 7.0, and even though the plugin has changed in 8.0, there is still a
 codecBlacklist.h file included that I can only assume still contains DNxHD.
 
  -Nathan
 
 
  From: Thomas Volkmann mailto:li...@thomasvolkmann.com
  Sent: Friday, March 28, 2014 9:29 AM
  To: Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk
  Subject: Re: [Nuke-users] Linux read DNxHD Quicktimes
 
  Didn't know about that one, thanks.
  But unfortunately Nuke continues to give me unsupported codec :/
 
   Py Fave pyf...@gmail.com hat am 28. März 2014 um 17:09 geschrieben:
  
  
   add ffmpeg: in loader url ?
  
   ffmpeg:/home/user/myvideo.mov
  
  
  
  
   2014-03-28 15:18 GMT+01:00 Thomas Volkmann li...@thomasvolkmann.com:
Hi,
my Nuke and HieroPlayer installations (Fedora20) are not able to read
DNxHD
Quicktimes. What is the regular procedure to get this to work?
I have no problem watching them with different players. Google brought up
a
couple of threads, but the useful one ended with I got it to work :/
   
thanks,
Thomas
   
___
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] Linux read DNxHD Quicktimes

[Thomas Volkmann]

Yes, the common procedure when working in Nuke is to convert all the quicktimes
before. But I have the same problem in HieroPlayer and converting all the shots
for a whole movie is not a option I'm afraid :/

cheers,
Thomas


 Nathan Rusch nathan_ru...@hotmail.com hat am 28. März 2014 um 18:45
 geschrieben:
 
  The best solution is to not use MOVs in Nuke. There are numerous stability
 problems with various codecs, especially on Linux.
 
  -Nathan
 
 
  From: Thomas Volkmann mailto:li...@thomasvolkmann.com
  Sent: Friday, March 28, 2014 10:34 AM
  To: Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk
  Subject: Re: [Nuke-users] Linux read DNxHD Quicktimes
 
  So what is the workaround?  I just tried using the system libraries, but that
 gave me a segmentation fault :/
 
 
 Nathan Rusch nathan_ru...@hotmail.com hat am 28. März 2014 um 18:27
 geschrieben:
  
Nuke’s ffmpegReader plugin has certain codecs blacklisted, some because of
  licensing issues and others for unknown reasons. DNxHD is definitely on that
  list in 7.0, and even though the plugin has changed in 8.0, there is still a
  codecBlacklist.h file included that I can only assume still contains DNxHD.
  
-Nathan
  
  
From: Thomas Volkmann mailto:li...@thomasvolkmann.com
Sent: Friday, March 28, 2014 9:29 AM
To: Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk
Subject: Re: [Nuke-users] Linux read DNxHD Quicktimes
  
Didn't know about that one, thanks.
But unfortunately Nuke continues to give me unsupported codec :/
  
 Py Fave pyf...@gmail.com hat am 28. März 2014 um 17:09 geschrieben:


 add ffmpeg: in loader url ?

 ffmpeg:/home/user/myvideo.mov




 2014-03-28 15:18 GMT+01:00 Thomas Volkmann li...@thomasvolkmann.com:
  Hi,
  my Nuke and HieroPlayer installations (Fedora20) are not able to read
  DNxHD
  Quicktimes. What is the regular procedure to get this to work?
  I have no problem watching them with different players. Google brought
  up a
  couple of threads, but the useful one ended with I got it to work :/
 
  thanks,
  Thomas
 
  ___
  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
 

___
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] Render Manager of choice?

[Thomas Volkmann]

Have you taken a look at RoyalRender?

/Thomas

Howard Jones mrhowardjo...@yahoo.com hat am 30. November 2012 um 09:37
geschrieben:
 I moved onto deadline recently and have no regrets for small scale set ups. I
 used to use Qube somewhere and is great but expensive.

 Howard

 On 30 Nov 2012, at 02:44, Nathan Rusch nathan_ru...@hotmail.com wrote:

  We currently use Rush here, though with a Python render stack built on top
  of it, and we’ve been planning (read: trying to find the time) to move away
  from it for awhile. Frankly, I wouldn’t wish it on anyone, especially as a
  long-term solution. The user-facing tools are some of the least intuitive
  (and indeed, least usable) I’ve seen, and you pretty much have to implement
  any features you want/need yourself.
 
  Deadline 6 (currently in beta) uses a database for the repository storage
  instead of a directory tree like 5, meaning it should scale much better. The
  UIs are also being redesigned and are now written in PyQt using
  platform-native libraries, so the clunky Mono GUIs on Linux/OSX are no more.
  The monitor also updates automatically as well.
 
  I don’t have experience with Qube! myself, but I’ve heard good things, as
  well as that it’s not worth the (hefty) premium over other solutions.
 
  Apparently Tractor is still a product as well, and a reasonably priced one,
  but I haven’t heard a peep about updates or new versions.
 
 
  -Nathan
 
 
  -Original Message- From: Ned Wilson
  Sent: Thursday, November 29, 2012 2:24 PM
  To: Nuke user discussion
  Subject: [Nuke-users] Render Manager of choice?
 
  Hey all,
 
  I'm working on building out a small render farm for a brand new facility. As
  such, I have some ability to install a render manager of my choice.
 
  At this point, I've narrowed it down to either Deadline or Qube!. At risk of
  starting a religious war here, do people have a preference? Is there another
  product that I am entirely overlooking?
 
  -n
 
  ___
  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
___
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] nuke archiving scripts?

[Thomas Volkmann]

I tried this once, and it worked:
http://www.vfxtalk.com/threads/23935-Nuke-Archiver-Script

 Original-Nachricht 
 Datum: Thu, 15 Mar 2012 20:29:42 +0530
 Von: Khushnum kfchi...@tataelxsi.co.in
 An: nuke-users@support.thefoundry.co.uk
 Betreff: [Nuke-users] nuke archiving scripts?

 Hi,
 Can anybody help me with archiving my nuke scripts? I need to compile all
 the elements in one folder...where everything sits in one place, image
 sequences, movs, source files etc. 
 
 also could someone direct me to getting render licence for nuke6.3. I seem
 to be going round in circles on the foundry website.
 
 forgive my ignorance, I am quite new to this
 
 Thank you
 any help would be much appreciated. 
 Khush 
 
 
-- 
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!  

Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
___
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] Same operation on multiple inputs

[Thomas Volkmann]

Thanks Holger,

exactly what we've been looking for...


 Original-Nachricht 
 Datum: Mon, 21 Nov 2011 20:22:31 +0100
 Von: Holger Hummel|Celluloid VFX hol...@celluloid-vfx.com
 An: Nuke user discussion nuke-users@support.thefoundry.co.uk
 Betreff: Re: [Nuke-users] Same operation on multiple inputs

 
 i stumbled upon this a few days ago:
 
 http://www.creatogether.com/foreach-nk
 
 haven't tested it myself yet but looks like it's doing at least some of 
 the stuff you're looking for.
 
 cheers,
 Holger
 
 
 Thomas Volkmann wrote:
  Some interesting stuff so far, but not yet exactly what we are after
 (though it definitely is an improvement).
  Is there any documentation on that python-tab in the write node? I
 didn't find anything on this, but maybe I'm not searching properly, because I
 didn't find the former mentioned 'topnode'-expression either.
  If we could something like if write2 - use switch 2 to work that
 would be perfect!
 
  Thanks for your input!
 
 
 
   Original-Nachricht 

  Datum: Mon, 21 Nov 2011 12:49:33 +0100
  Von: michael vorberg pingkin...@googlemail.com
  An: Nuke user discussion nuke-users@support.thefoundry.co.uk
  Betreff: Re: [Nuke-users] Same operation on multiple inputs
  
 

  two things come into my mind:
a) you can build a temp script with the read node and all the things 
  you want to do. and the end put in a write node
  in the read node file knob write: [argv 0]
  and in the write node put an expression to build the name from the
 write 
  node or put in [argv 1]
  then start nuke from a commandline with: nuke tempscript.nk 
  path/to/read/images.ext path/to/write/images.exr (you can get rid
 of 
  the second argument if you build the write node filenames by
 expression)
 
  this will start nuke and put the first argument 
  (path/to/read/images.ext) into the read nodes file knob
 
  b) the switch method isnt that bad, i would make an expression on the 
  disable knob of the write node which makes it only active if the right 
  switchinput is selected.
  something like: switch1.which==3?0:1
 
  Am 20.11.2011 21:22, schrieb Thomas Volkmann:
  
  Hey,
  is it possible to setup some sort of batch-processing in Nuke? E.g. 
  having multiple Read nodes that need all the same treatment, and then 
  write them out to different places.
  First idea was to put the compositing tree into a group and clone that
  one...that was when I found out that you can't clone groups. Another 
  approach a co-worker came up with, was to connect all the Reads to a 
  Switch-node and have multiple Write nodes in the end, of which 
  everyone has a 'before render - change switch'-expression, but 
  somehow that didn't work.
  Probably I am just missing the obvious... I there a common workflow 
  for that?
 
  Thanks,
  Thomas
  ___
  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
  
 

 
 
 -- 
 Holger Hummel  -  hol...@celluloid-vfx.com
 
 Celluloid Visual Effects, Paul-Lincke-Ufer 39/40, 10999 Berlin
 phone +49 (0)30 / 54 735 220  -  m...@celluloid-vfx.com
 
 ___
 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

-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!   
Jetzt informieren: http://www.gmx.net/de/go/freephone
___
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] Same operation on multiple inputs

[Thomas Volkmann]

Some interesting stuff so far, but not yet exactly what we are after (though it 
definitely is an improvement).
Is there any documentation on that python-tab in the write node? I didn't find 
anything on this, but maybe I'm not searching properly, because I didn't find 
the former mentioned 'topnode'-expression either.
If we could something like if write2 - use switch 2 to work that would be 
perfect!

Thanks for your input!



 Original-Nachricht 
 Datum: Mon, 21 Nov 2011 12:49:33 +0100
 Von: michael vorberg pingkin...@googlemail.com
 An: Nuke user discussion nuke-users@support.thefoundry.co.uk
 Betreff: Re: [Nuke-users] Same operation on multiple inputs

 two things come into my mind:
   a) you can build a temp script with the read node and all the things 
 you want to do. and the end put in a write node
 in the read node file knob write: [argv 0]
 and in the write node put an expression to build the name from the write 
 node or put in [argv 1]
 then start nuke from a commandline with: nuke tempscript.nk 
 path/to/read/images.ext path/to/write/images.exr (you can get rid of 
 the second argument if you build the write node filenames by expression)
 
 this will start nuke and put the first argument 
 (path/to/read/images.ext) into the read nodes file knob
 
 b) the switch method isnt that bad, i would make an expression on the 
 disable knob of the write node which makes it only active if the right 
 switchinput is selected.
 something like: switch1.which==3?0:1
 
 Am 20.11.2011 21:22, schrieb Thomas Volkmann:
  Hey,
  is it possible to setup some sort of batch-processing in Nuke? E.g. 
  having multiple Read nodes that need all the same treatment, and then 
  write them out to different places.
  First idea was to put the compositing tree into a group and clone that 
  one...that was when I found out that you can't clone groups. Another 
  approach a co-worker came up with, was to connect all the Reads to a 
  Switch-node and have multiple Write nodes in the end, of which 
  everyone has a 'before render - change switch'-expression, but 
  somehow that didn't work.
  Probably I am just missing the obvious... I there a common workflow 
  for that?
 
  Thanks,
  Thomas
  ___
  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

-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!   
Jetzt informieren: http://www.gmx.net/de/go/freephone
___
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] Same operation on multiple inputs

[Thomas Volkmann]

Hey,
is it possible to setup some sort of batch-processing in Nuke? E.g. 
having multiple Read nodes that need all the same treatment, and then 
write them out to different places.
First idea was to put the compositing tree into a group and clone that 
one...that was when I found out that you can't clone groups. Another 
approach a co-worker came up with, was to connect all the Reads to a 
Switch-node and have multiple Write nodes in the end, of which everyone 
has a 'before render - change switch'-expression, but somehow that 
didn't work.
Probably I am just missing the obvious... I there a common workflow for 
that?


Thanks,
Thomas
___
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] Particles switching channels

[Thomas Volkmann]

Hey list,

I want my particle-system to change from channel a to b in frame 50. Therefore 
I take a particleExpression Node and write frame==50 down in the chans-field 
and set to to b.
The Particles change to channel b now, BUT not all of them in frame 50. It 
seems that frame is somehow relative to the frame where the particle was 
emitted.
Is that expected behaviour? 
In the end I want to freeze my simulation at a certain frame, is this the right 
approach to do that, or is there another way?
And as it is my first day playing with Nuke-particles, is there a way to debug 
stuff (e.g. to see which value is passed to the particles from that 
chans-field)?

Thanks,
Thomas

P.S.: there is a simple sample scene attached
-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de


particle_states.nk
Description: Binary data
___
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