Re: [Nuke-users] OT: FFMpeg Blackmagic

2013-01-29 Thread namyrb
It doesn't look like it. They have an update on the official site that says they'd like to get more raw formats to work (including bm yuv 10-bit), but thats that was in 2011 and it looks to be the last mention of it. On Mon, Jan 28, 2013 at 11:45 PM, Ron Ganbar ron...@gmail.com wrote: Hi all,

Re: [Nuke-users] OT: FFMpeg Blackmagic

2013-01-29 Thread Ron Ganbar
Thanks man, in that case, does anyone have an idea how to create a post process in Deadline to take a tiff sequence output and make it into a Blackmagic quicktime? Ron Ganbar email: ron...@gmail.com tel: +44 (0)7968 007 309 [UK] +972 (0)54 255 9765 [Israel] url:

Re: [Nuke-users] OT: FFMpeg Blackmagic

2013-01-29 Thread Jimmy Christensen
AFAIK v210 = Blackmagic 10-bit YUV Best Regards Jimmy Christensen Developer Ghost A/S On 29/01/13 08:45, Ron Ganbar wrote: Hi all, does anybody know if ffmpeg can be used to generate blackmagic codec quicktimes on Windows? Thanks, Ron Ganbar email: ron...@gmail.com mailto:ron...@gmail.com

[Nuke-users] Tiff metadata / tags

2013-01-29 Thread John RA Benson
Hey out there - Does anyone know of a way to embed certain tiff tags into a (tiff) render? A ModifyMetaData node doesn't seem to do it unless there is a magic key I don't know of. We are rendering tiffs and having some odd render issues. I'm hoping by adding TIFFTAG_HOSTCOMPUTER

Re: [Nuke-users] OT: FFMpeg Blackmagic

2013-01-29 Thread Holger Hummel|Celluloid VFX
i remember something like Jimmy's statement from past experience, too. iirc, a v210 QT file would always show the blackmagic codec in QT player's info window if the blackmagic coded was installed and output fine over a BM card. on systems where the codec/card is not installed it would show

Re: [Nuke-users] OT: FFMpeg Blackmagic

2013-01-29 Thread Jimmy Christensen
I think V210 is also the basis of the Quicktime 10-bit which is installed by FCP. Best Regards Jimmy Christensen Developer Ghost A/S On 29/01/13 12:02, Holger Hummel|Celluloid VFX wrote: i remember something like Jimmy's statement from past experience, too. iirc, a v210 QT file would always

Re: [Nuke-users] OT: FFMpeg Blackmagic

2013-01-29 Thread Ron Ganbar
Thanks Holger. I might try to contribute to the cause. I'll see what they're after exactly. Ron Ganbar email: ron...@gmail.com tel: +44 (0)7968 007 309 [UK] +972 (0)54 255 9765 [Israel] url: http://ronganbar.wordpress.com/ On 29 January 2013 13:02, Holger Hummel|Celluloid VFX

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread Nathan Rusch
I don't think Nuke will currently let you write arbitrary TIFF metadata, but a simple solution (if you've got the time to run test renders) would just be to do a Text node burn-in with [info hostname] as a text expression. -Nathan -Original Message- From: John RA Benson Sent:

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread John RA Benson
ha - yes, but that kind of ruins the render ;) the issue pops up as we saturate the farm (of course) and I think sys would have me fired if I did it myself anytime in the next 3 months! Cheers JRAB On 01/29/2013 06:15 PM, Nathan Rusch wrote: I don't think Nuke will currently let you write

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread Nathan Rusch
Yup, like I said, it's only a good option if you've got the time (and CPU power) to burn. What kinds of render issues are you running into exactly? -Nathan -Original Message- From: John RA Benson Sent: Tuesday, January 29, 2013 9:24 AM To: nuke-users@support.thefoundry.co.uk

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread Julik Tarkhanov
into the alpha. Or pad the render with a strip of pixels for that burnin. On 29 jan. 2013, at 18:17, Nathan Rusch nathan_ru...@hotmail.com wrote: would just be to do a Text node burn-in with [info hostname] as a text expression. ___ Nuke-users

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread chris
hmm, or if you can spare a single pixel somewhere, you could just burn in the hostname as color (or alpha) value... like in the bottom right corner, each render machine gets a slightly different shade of black (ie render1 is 0.1, render2 is 0.2 etc) then if you have corrupt renders

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread John RA Benson
We had this issue on a project awhile ago (using Nuke5.1), where systems were going into swap. Say, you have 3 jobs on an 8 proc machine, using 4, 2, and 2 procs of memory. One job is a real mem pig, using all the system memory, so the other 2 jobs waited. Really, all 3 jobs wait because the

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread Nico Dufort
While I am enjoying the microdots-spy approach to tag an image with secret render host information, am I missing something or you could just check your render logs? Or... you don't have logs? =P On Tue, Jan 29, 2013 at 10:50 AM, chris ze.m...@gmx.net wrote: or extending on that idea...

Re: [Nuke-users] Tiff metadata / tags

2013-01-29 Thread Nathan Rusch
Hmm. I don't mean to skirt the central issue too widely, but in my experience, rendering simultaneous Nuke jobs on a single machine that are doing anything more complex than converting files (or something equally simple) results in high enough instances of instability and performance