[Nuke-users] Windows 10
Anyone have trouble with Windows 10 and then resolve it? I tried Nuke 9 on a bunch of Windows 10 machines and they exhibited no problems. Now I'm trying it on my Workstation and it just crashes on startup, even safe mode. Compatibility mode didn't work. Admin privileges didn't work. Re-installing didn't work. Nuke 9.0v7 didn't work. I tried adding diagnostic "Hello World" to getenv.tcl and menu.py (which I think is the next item to load). No luck on either account. C:\Program Files\Nuke9.0v4>Nuke9.0.exe --safe -V 2 Nuke 9.0v4, 64 bit, built Jan 30 2015. Copyright (c) 2015 The Foundry Visionmongers Ltd. All Rights Reserved. Loading C:/Program Files/Nuke9.0v4/plugins/_pathsetup.py Loading C:/Program Files/Nuke9.0v4/plugins/init.tcl Loading C:/Program Files/Nuke9.0v4/plugins/init.py Loading C:/Program Files/Nuke9.0v4/plugins/setenv.tcl Loading C:/Program Files/Nuke9.0v4/plugins/formats.tcl Loading C:/Program Files/Nuke9.0v4/plugins/getenv.tcl C:\Program Files\Nuke9.0v4> ___ 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] Network performance and Nuke
So I've been trying to improve our GigE performance rendering Nuke comps with NAS footage and I was noticing that my network performance never peaked above 100mbps. Thinking there was surely something wrong with my connection to our network I did some physical and software testing to ensure the link was GigE and not 100Mbps between my system and the file server. After confirming I was in fact running a full GigE connection I tested the throughput with some benchmarking and found that NAS Disk -> My System could deliver ~450mbps sustained performance. So clearly it's not the network or the file system's disk. Any ideas on what's going on? Do I need to increase frame size or something simple to make network rendering feasible? I would like to see my CPU usage go above 10-20% when rendering off the network.I have to say the fact that it saturates up to 100mbps really makes me suspicious it's a bug/glitch somewhere. Any insight would be welcome. Gavin Greenwalt Straightface Studios ___ 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] ShotGun / RV player and Nuke
the
script instead of the pop-up window. Or you could use the Pop-Up window.
The deadline submission script shouldn't care where it gets those 3 pieces
of information from. Similarly it would be trivial to pull the username and
prepopulate the field from a scene node.
Now going back to the username for a second. There was some discussion
before of linking the Shotgun Username with the Deadline username. Not
terribly fond of that since I have a different Deadline username from
Shotgun username. System Username seems like the most reliable and
consistent system. But again there is no reason Thinkbox should have to
worry about that. If Deadline pulled the username from a Shotgun Software
defined standardized "Settings" node (or root.knob in the script settings
node ('S') then different studios would just need to write little startup
scripts which auto-filled the shotgun node with the current user. Maybe
when you open a script you already have a script which automatically checks
the script out. It can at the same time also find and fill out a
ShotgunSettingsNode.knob('sgUsername').setKnob(studio.getCurrentSgUser())
(forgive my made up Nuke Python I can't do off the top of my head).
Deadline doesn't have to worry about that. If it finds a node with a hidden
knob called something like "ShotgunSettingsNode" it just knows it needs to
pull the sgUsername field. Easy peezy!
Similarly if eventually Shotgun provided a more universal Shotgun Entity
Browser which just returns the aforementioned 4 important pieces of
information (or more, 4 is the minimum I believe, certainly not the
maximum) then Deadline could just call that with maybe a launch flag
specifying what it's requesting and Shotgun could continue to update the
Universal Entity Browser without Thinkbox having to continually update
their browser. Deadline would upgrade automatically as the Shotgun SDK
upgrades.
http://i111.photobucket.com/albums/n134/im_thatoneguy/Shotgun_Mini-Project_Browser.gif
http://i111.photobucket.com/albums/n134/im_thatoneguy/Shotgun_Mini-Entity_Browser.gif
- Gavin
On Wed, Dec 14, 2011 at 10:14 AM, Gavin Greenwalt
wrote:
> I wrote a read node which would find the latest elements for a shot.
>
> http://www.vfxtalk.com/threads/21217-Shotgun-Read-Node-(SG-Integration)
>
> But it was written in '09 and hasn't been updated since so you probably
> will need to tweak the SG API calls.
>
> - Gavin Greenwalt
> Straightface Studios
>
>
> On Wed, Dec 14, 2011 at 8:52 AM, Gerard Keating wrote:
>
>> Hi,
>> Have you seen shotgundropper
>> http://www.nukepedia.com/python-scripts/nodegraph/shotgundropper/ ?
>> We use a custom version of this and it works great.
>> Regards,
>> Gerard.
>> ___
>> 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] ShotGun / RV player and Nuke
I wrote a read node which would find the latest elements for a shot. http://www.vfxtalk.com/threads/21217-Shotgun-Read-Node-(SG-Integration) But it was written in '09 and hasn't been updated since so you probably will need to tweak the SG API calls. - Gavin Greenwalt Straightface Studios On Wed, Dec 14, 2011 at 8:52 AM, Gerard Keating wrote: > Hi, > Have you seen shotgundropper > http://www.nukepedia.com/python-scripts/nodegraph/shotgundropper/ ? > We use a custom version of this and it works great. > Regards, > Gerard. > ___ > 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] Gamma and Alpha
Thanks, that's what I thought. The white trick was actually what I had decided to try on the next job. It'll get 90% of the way there so I figure that's the best one can hope for. It's definitely better than assuming black and experiencing all of the saturation and luminance shifts as you point out Andy. Just accepting them is out the question but in this scenario it's going to flame to comp over a pretty much white background anyway with maybe a light vignette. I wanted to make sure I wasn't going crazy. :D I guess I *could* ask the flame artist to comp the footage in linear space but I always get really nervous when I send off footage and can't review it before it goes on air to make sure they are handling it correctly, I would much prefer something which has the least possibility of being botched somehow. - Gavin On Tue, Nov 15, 2011 at 12:28 AM, Ivan Busquets wrote: > Hi Gavin, > > As you said yourself, the equation cannot be solved UNLESS you know both > variables on one of the sides. > In other words, you'd need to have the BG image in order to prep a FG > image so it can be comped in sRGB space and match the results of a linear > comp. > > So is there no way to output a PSD or PNG or TIFF which will look the same >> as my composite in Nuke over a white background? > > > If you need to get the same results on a white background, you could prep > your FG element such that: > > X = ( (FG * alpha + (1 - alpha)) ^ 2.2 - (1 - alpha) / alpha ) ^ > (1/2.2) > > Where X is the FG image you'd want to export to be comped on a white BG. > But of course, this will only give you a match when comping the FG over a > WHITE BG. If the BG changes, then you'd need to prep a different FG to go > with it. > > Hope that helps. > > Cheers, > Ivan > > > > On Mon, Nov 14, 2011 at 12:13 PM, Gavin Greenwalt > wrote: > >> How are Nuke users handling workflows in which they need to deliver >> images with alpha that will be composited in sRGB space not linear space? >> >> Essentially we have a situation where you would need to find equations >> for u and v such that (xy + z(1-y))^(1-2.2) = (uv + z^(1-2.2)(1-v)). >> >> My initial impression is that it's impossible since the simplified >> version of this conundrum would be (x+y)^2 = (u+v) which I believe is >> mathematically impossible to solve... right? So is there no way to output >> a PSD or PNG or TIFF which will look the same as my composite in Nuke over >> a white background? >> >> Thanks, >> Gavin >> >> ___ >> 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] Re: Re: Re: SSD and red footage
I wouldn't think that SSD performance has any baring on r3d performance. I think you're CPU bound. Most NUKE footage is only about 45MBs @ 24p. I don't think any computer without a red-rocket can decode that fast. On Sun, Nov 13, 2011 at 4:23 AM, Adrian Baltowski wrote: > A little OT but remember, that in case of native r3d files in Nuke there > is a massive difference between operating systems. On the same hardware > (without rocket card) r3d decoding in Nuke is few times faster on Linux > than on OSX. Also Widows is slower than Linux with this format. There isn't > such a significant difference in case of any other format supported by > Nuke. If you really wants to work natively with r3d files in Nuke, Linux is > your only choice. > > Best > Adrian > > > > > > > > W dniu 2011-11-12 20:01:15 użytkownik Rob > napisał: > > Hi Remco, > > > > Inside Nuke I dont get a great deal of speed from the read nodes. Its > > like 2-2.63fps while caching up a 4k plate and High decode through an > > r3d and I get 16fps from a 2k dpx. Also launching applications and > > working in general feels very fast but can slowdown overtime and with > > larger scripts. > > > > Rob > > >> Hi Rob, > > >> > > >> i'm currently working with 5K (4K) red footage as well. No ssd.. And i > > >> wonder what the average framerate you get on playback with that ssd > disks. > > >> > > >> just curious > > >> > > >> Remco > > >> > > >> > > >> > > >> > > ___ > > 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] Gamma and Alpha
How are Nuke users handling workflows in which they need to deliver images with alpha that will be composited in sRGB space not linear space? Essentially we have a situation where you would need to find equations for u and v such that (xy + z(1-y))^(1-2.2) = (uv + z^(1-2.2)(1-v)). My initial impression is that it's impossible since the simplified version of this conundrum would be (x+y)^2 = (u+v) which I believe is mathematically impossible to solve... right? So is there no way to output a PSD or PNG or TIFF which will look the same as my composite in Nuke over a white background? Thanks, Gavin ___ 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] Invitation to connect on LinkedIn
LinkedIn Gavin Greenwalt requested to add you as a connection on LinkedIn: -- Paolo, I'd like to add you to my professional network on LinkedIn. - Gavin Accept invitation from Gavin Greenwalt http://www.linkedin.com/e/dosa9x-gqxzvzzm-1c/j-McRiaRYPJN6hyq0b1DBCPi16VxtjyCNFBe4hZjeY_12EH3hpR9/blk/I180916547_9/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_elYTd3kScjAMe359bQBvimBngD11bPAVdjwNd30SdPcLrCBxbOYWrSlI/EML_comm_afe/ View invitation from Gavin Greenwalt http://www.linkedin.com/e/dosa9x-gqxzvzzm-1c/j-McRiaRYPJN6hyq0b1DBCPi16VxtjyCNFBe4hZjeY_12EH3hpR9/blk/I180916547_9/0VnPsQdjoNej0UckALqnpPbOYWrSlI/svi/ -- DID YOU KNOW you can conduct a more credible and powerful reference check using LinkedIn? Enter the company name and years of employment or the prospective employee to find their colleagues that are also in your network. This provides you with a more balanced set of feedback to evaluate that new hire. http://www.linkedin.com/e/dosa9x-gqxzvzzm-1c/rsr/inv-27/ -- (c) 2011, LinkedIn Corporation___ 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] DiskCache node
I tried using it but resorted to just using read/write nodes which seemed more reliable and consistent. Except there is a bug in using a write node as a read node. It'll crop the bounding box when in read mode [reported] so be careful. -Gavin On Tue, Mar 1, 2011 at 8:29 AM, Michael Garrett wrote: > Is anyone actually using the DiskCache node? Is it working for you? > Are the hash tags still really sensitive? From memory, say if you > move some nodes around in the DAG upstream of the DiskCache node, it > would have to recalculate. I'll give this a try again asap but wanted > to ask others too. > > Thanks, > Michael > ___ > Nuke-users mailing list > Nuke-users@support.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://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
