Hi Nathan, Yep, that's me :-) I would drop the Deadline dev. team a note and sound out our concerns. They will bend over backwards if you need a certain feature or configuration. They also turn stuff around at a scary, fast speed! IronPython/.Net is built in to Deadline, but you can ALSO add the entire CPython modules into Deadline. Yes, there have been times when an IronPython module doesn't quite hit the spot, but this doesn't matter when I can access everything in CPython, making it very compatible with legacy pipelines and a dream to work with :-) On Mono, if they are any issues, they will be either fixed ASAP by the support team or they will be dependent on a newer Mono build coming out. So any software which is reliant on a certain issue/bug in Mono will also be affected by this same issue. Worth bearing in mind, when you deep dive into the background technologies on all these network render management software solutions. >From a pipeline / integration point of view, I'm doing the exact opposite to what you mentioned in your reply! I'm integrating it everywhere and for me, I'm finding it to be an enjoyable and easy experience, but as always, YMMV. If I was you, I would ask for access to the Deadline beta version. I think you will be surprised :-) Mike
On 7 July 2011 07:44, Nathan Rusch <[email protected]> wrote: > Hey Mike, I recognize you from the Deadline boards. :D > > There’s nothing inherently “wrong” with either .NET or IronPython. However, > having to build and maintain an entire framework just to run a render slave > is, it must be said, better to avoid if possible. Also, in the past I’ve run > into issues getting CPython modules into Deadline’s IronPython environment, > and given how deeply hooked into our pipe Rush currently is, I can’t see a > transition to Deadline being a fun process. > > I am aware that Deadline is supported on all three platforms. However, I’m > curious if it gets quirky on Mono. > > At this point, I’m most concerned with large-farm scalability and deep > integration, and from my previous experience with Deadline, it may not be > the Swiss Army knife we need on the integration side. From an end-user and > surface interaction perspective, it’s a dream come true; from a pipeline > TD’s, I’m afraid not so much. That said, I won’t write it off without at > least trying it on Linux. > > Thanks for the response, > > -Nathan > > > *From:* Mike Owen <[email protected]> > *Sent:* Wednesday, July 06, 2011 11:17 PM > *To:* Nuke Python discussion <[email protected]> > *Cc:* Nuke-Users <[email protected]> > *Subject:* Re: [Nuke-python] OT: Render Manager Survey > > Hi Nathan, > Can you explain what is wrong with having both .Net and also IronPython > available in Deadline? You can also add CPython to Deadline by simply adding > its library in the global repository options for your entire pipeline. > You do know Deadline runs on all 3 platforms, via Mono and is fully > supported across all 3 platforms? > Some exciting and somewhat major developments are taking place in Deadline > v5.x...I would listen out for Siggraph if I was you :-) > Mike > > On 7 July 2011 07:05, Nathan Rusch <[email protected]> wrote: > >> Hey everyone, >> >> Hope this isn’t considered inappropriate list spam, but I’m in search some >> outside opinions. >> >> We’re considering switching farm management packages (currently on Rush), >> and I’m trying to get a feel for what (commercially available) solutions >> other shops are currently using and if anyone has any opinions on any of >> them. I realize these lists may not be the place to get a lot of that kind >> of information, but I figure it’s worth a shot. >> >> The packages I’ve been researching thus far are Qube!, Smedge, Tractor, >> RenderPal, and DrQueue. I’m pretty experienced with Deadline, but at this >> point it’s seeming a less viable option due to its .NET/IronPython roots >> (we’re primarily Linux). If anyone is using or knows of any other major >> players, I’d love to hear about them as well. >> >> Thanks, >> >> -Nathan >> >> >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> > > ------------------------------ > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
