Command Line tool...

[Jannard]

is included in the new RED Alert! posted today... in case you haven't noticed.

Jim

[Bing Bailey]

Sweet!

[Frank Weeks]

this is great news. Thanks again

[Deanan]

open terminal, enter REDline, and you'll get the help info to get started.

[Brook Willard]

Thanks, Deanan... I was searching all over for it.

[Brook Willard]

For those curious...


Last login: Wed Feb 6 20:01:16 on console
brook-willards-macbook-pro:~ brookwillard$ REDline
Input filename needed.
usage: REDline v1.4.7
-i <filename> : input file (required)
-o <filename> : output basename

Format Settings:
-w or --format <int> : output formats, DPX=0, Tiff=1, QT wrappers=10, QT transcode=11[default = DPX]
-R or --res <int> : Render resolution: full=1, half=2 [default = 1]
--stdout : Redirect to StdOut. Use -s to specify which frame. Only one frame output.

Frame Settings:
-s or --start <int> : start frame
-e or --end <int> : end frame
-S or --startTC <timecode> : start TC as "00:01:00:00"
-E or --endTC <timecode> : end TC "00:01:00:00"
--useEC : use EdgeCode instead of TimeOfDay/EXT TC
-V or --renum <int> : new start frame number or -1 for timecode as frame count from 00:00:00:00
i.e. 00:00:02:00 = frame 48 @ 24fps

Crop and Scale Settings:
--resizeX <int> : resize to X dimension [default = none]
--resizeY <int> : resize to Y dimension [default = none]
--fit <int> : fit src to dest using: 1=fitX, 2=fitY, 3=StretchXY [default = fitX]
--cropX <int> : crop demosaiced source before resize using origin X [default = no crop]
--cropY <int> : crop demosaiced source before resize using origin Y [default = no crop]
--cropW <int> : crop demosaiced source before resize using Width [default = no crop]
--cropH <int> : crop demosaiced source before resize using Height [default = no crop]
--filter <int> : filter using: [default = 6 (Mitchell)]
1=Bell (smoother)
2=Lanczos3 (sharper)
3=Quadratic (smoother)
4=Cubic-bspline (smoother)
5=CatmulRom (sharper)
6=Mitchell (smoother)
7=Gauss (smoother)

Metadata Settings:
--useMeta : Use look metadata in R3D as defaults (overridden for each value explicitly set)
--printMeta : Print out metadata settings, 1=normal, 2=csv

Quicktime Wrapper Settings:
--QTsize <int> : QT wrappers to output, 0=all, 1=M/Qtr, 2=H/Half, 3=P/Eighth [default = 0]
--QTdir <directory path> : output directory to dump QT wrappers in [default = same as source R3D]
--omitNA : Do not insert _NA into wrapper filename

Quicktime Transcode Settings:
--QTcodec <int> : QT codec to output [default = ProRes HQ]
0=ProResHQ
1=ProResSQ
2=H264
3=MJpegA
4=MJpegB
5=ComponentVideo
6=H263
7=RawCodec
8=Pixlet
9=DVCPROHD720P
10=JPEG
11=Animation/RLE

Color Space Settings:
-G or --gammaCurve <int> : gamma curve: lin=-1, custom=0, rec709=1, sRGB=2, REDlog=3,
PDLog985=4, PDLog685=5, PDLogCustom=6 [default = 3]
-v or --gammaCustom <float> : custom gamma value [default off]
-c or --colorSpace <int> : color space: rec709=3, camRGB2=9 [default = 9]
-d or --detail <int> : detail: leadingLady = 1, medium = 4, high = 8 [default = 8]
-D or --sharpen <int> : post sharpen low = 1, med = 50, high = 100 [default OFF]
--NR <int> : Noise reduction off=0, very mild = 1000, milder = 500, mild = 250 medium = 100, strong = 50, max = 10 [default OFF]
-n or --noMatrix : no Matrix [default ON]

Color Settings:
-I or --iso <int> : ISO [default = 320, range = 100 to 2000]
-k or --kelvin <int> : kelvin [default = 5600, range = 1700 to 50000]
-t or --tint <float> : tint [default = 0.0, range = -100 to 100]
-x or --exposure <float> : exposure [default = 0.0, range = -12 to 12]
-T or --saturation <float> : saturation [default = 1.0, range = 0.0 to 2.0]
-C or --contrast <float> : contrast [default = 0.0, range = -1.0 to 1.0]
-B or --brightness <float> : brightness [default = 0.0, range = -10 to 50]
-r or --redGain <float> : red gain [default = 1.0, range = 0.0 to 4.0]
-g or --greenGain <float> : green gain [default = 1.0, range = 0.0 to 4.0]
-b or --blueGain <float> : blue gain [default = 1.0, range = 0.0 to 4.0]
-X or --drx <float> : DRX: Dynamic Range Extender [default = .5, range = 0.0 to 1.0]

Print Density Settings:
--pdBlack <int> : Black point [default = 95, range = 0-511]
--pdWhite <int> : 90White point [default = 685, range = 512-1023]
--pdGamma <float> : Gamma [default = .6, range = 0.0 to 2.2]

Curve Settings:
--black <float> : black level [default = 0 , range = 0 - 100]
--white <float> : white level [default = 100 , range = 0 - 100]
--blackX <float> : curve black point X value [default = 0 , range = 0 - 100]
--blackY <float> : curve black point Y value [default = 0 , range = 0 - 100]
--toeX <float> : curve toe point X value [default = 25 , range = 0 - 100]
--toeY <float> : curve toe point Y value [default = 25 , range = 0 - 100]
--midX <float> : curve mid point X value [default = 50 , range = 0 - 100]
--midY <float> : curve mid point Y value [default = 50 , range = 0 - 100]
--kneeX <float> : curve knee point X value [default = 75 , range = 0 - 100]
--kneeY <float> : curve knee point Y value [default = 75 , range = 0 - 100]
--whiteX <float> : curve white point X value [default = 100 , range = 0 - 100]
--whiteY <float> : curve white point Y value [default = 100 , range = 0 - 100]

brook-willards-macbook-pro:~ brookwillard$

[Jay A. Kelley]

Because this is in REDAlert, am I to assume we PC people must wait?

:(

Please tell me I'm wrong

Jay

[Jannard]

Because this is in REDAlert, am I to assume we PC people must wait?

:(

Please tell me I'm wrong

Jay

Working on it... really!

Jim

[Brook Willard]

But for now, we Mac users get to post snarky ads (http://pulsar.esm.psu.edu/Faculty/Gray/graphics/movies/crowd.mov).



Kidding, Jay. :)

[Jay A. Kelley]

Yes it's true.. I am the bastard child of the RED community.

:)

Jay

[Deanan]

Yes it's true.. I am the bastard child of the RED community.

:)

Jay

It'll be available on Win fairly soon.

[David Birdy]

Yes it's true.. I am the bastard child of the RED community.

:)

Jay

I like both MAC and PC's. I use a computer like a tool, selecting the best tool for the job is important. As My RED Ones are not at my door I'm still on the fence...But for onset dailies a MAC seems to be the way to go right now?

Can anyone with a camera comment ?

Dave

[Jeff Kilgroe]

Linux too, right? My Linux render nodes want to party.

..or not. I can boot those systems to windows too, depending on the job.

[Greg M]

I like both MAC and PC's. I use a computer like a tool, selecting the best tool for the job is important. As My RED Ones are not at my door I'm still on the fence...But for onset dailies a MAC seems to be the way to go right now?

Can anyone with a camera comment ?

Dave


MacBook Pro should be considered an essential part of your field package.

[Jay A. Kelley]

I think MAC are your best bet for onset delivery.

We've been working out workflow for the last couple of days, and a topic that's come up a bit has been if we want to roll playback into our package. It makes sense to do so.. This will also keep the directors stickly little fingers off the master footage drives.

We're looking at Adobe On Location for the capture of playback. and a Xena card for taking the feed.

This brings up an important question I need answered:

Do the HD-SDI ports have audio embedded? If yes, is it active yet? If not, is it coming in the next couple months?

Jay

[Brook Willard]

What is this MAC you guys speak of? :wink:






Alright, I'm done.

[Deanan]

linux too. probably not long after win.
basically, we're trying to get both out asap.

[Steve Freebairn]

linux too. probably not long after win.
basically, we're trying to get both out asap.

That and the QT codec for PC would be awesome (so that proxies will play back in Quicktime on PC)

[Deanan]

That and the QT codec for PC would be awesome (so that proxies will play back in Quicktime on PC)

All this is related to the same core code so yes for QT on PC probably around the same time.

[David Birdy]

All this is related to the same core code so yes for QT on PC probably around the same time.


Maybe Jim can break out the cloning tool for Graeme just this once...
Think of how easy the chores around the house would be...:usd:

[Rob Lohman]

Cloning tool for Rob....

[David Birdy]

Cloning tool for Rob....


Yes,

By all means cloning for Rob!

I just returned from Dublin Ireland Rob...Great country, great people, great name for your camera.. the only thing missing was my RED One..so I shot RAW stills.

Dave

[Gavin Greenwalt]

In the immortal words of Darth Vader:

Yipee!

[laguun]

Working on it... really!

Jim
excellent news. you made a bunch of people happy in berlin today!

with cli and QT on windows, the -main- missing gaps in the workflow for longform and fullfeature work here are closing.

We have 2 fullfeatures coming up in the next quarter which will be shot mostly with red, both with shooting ratios >10:1, both with parallel datawrangling, rough editing, VFX work while shooting. The rushes/daily/avid/discreet pipeline with the cli is -so- much easier to handle than with redcine.

thank you very much!

one question:
does the redline cli needs gpu or is it cpu only?
we have to plan ~32 cpus for the redrenderfarm here and it would be a nice cost (and energy) saver to use onboard grahics instead of nvidia boards in the blades.

[Stephen Gentle]

Cool - can you pass this some kind of XML configuration file for colour stuff? So you could load your footage up in RC, add your curve, white balance, cropping there, and then export a file to pass to the farm?

[Mark L. Pederson]

Cool - can you pass this some kind of XML configuration file for colour stuff? So you could load your footage up in RC, add your curve, white balance, cropping there, and then export a file to pass to the farm?

Color "look" file (or 1D LUT) spec has not been released yet - I am counting the days ...

[Simon Blackledge]

So who's working on the batch render gui ontop of this ? :)

[Paul Hazlett]

Because this is in REDAlert, am I to assume we PC people must wait?

:(

Please tell me I'm wrong

Jay




You know Jay,

Each year thousands of Macbook pros and Mac Pros enter this world
lonely and unloved....won't you care just little for one of these poor innocent macs? for just pennnies a day you too can join the community and adopt a Mac.

Thank you,

Steve Jobs

[Mark L. Pederson]

So who's working on the batch render gui ontop of this ? :)

most likely a BUNCH of folks at this very moment:w00t:

[Simon Blackledge]

Muhahaaa.. ;)

[Bing Bailey]

Yes,

By all means cloning for Rob!

I just returned from Dublin Ireland Rob...Great country, great people, great name for your camera.. the only thing missing was my RED One..so I shot RAW stills.

Dave

Glad you liked my homeland. wish I was shooting there now. beautiful rainy dublin grey sky. its a ripe place for a noir thriller :)

[Kyle Mallory]

Yes it's true.. I am the bastard child of the RED community.

:)

Jay

You ain't got 'nothing on me... I'm still waiting for Linux tools. At least you have Beta software, whether it works or not. You people look at my like I'm smoking something... Roswell, JFK, WMD's in Iraq, and Linux RED tools...

Now, shut the hell up and quit your bitching! :umm:

[Deanan]

one question:
does the redline cli needs gpu or is it cpu only?
we have to plan ~32 cpus for the redrenderfarm here and it would be a nice cost (and energy) saver to use onboard grahics instead of nvidia boards in the blades.

It's cpu only and will probably be that way for some time. GPU implementations are hugely inconsistent even between versions which makes supporting them really really hard.

[Deanan]

Cool - can you pass this some kind of XML configuration file for colour stuff? So you could load your footage up in RC, add your curve, white balance, cropping there, and then export a file to pass to the farm?

That's coming soon.

[J Clark]

Yes it's true.. I am the bastard child of the RED community.

:)

Jay


Jay, that makes us twins. We have 13 quad core XP PRO systems with 4gb RAM and ATI cards and we can't do anything with our Red footage yet... Our fingers are crossed and getting numb, but Kevin and Brent have kept us up to date and we're excited.

To those who continually suggest we invest in Mac, please understand that we(and many others) are deeply invested in our XP PRO render and working environments and when you urge that we just use a Mac, you're not taking into account the additional software and codec costs, infrastructure, IT, training and all of the higher expenses associated with changing platforms to work with Red footage. The multi-platform scenario is the best solution and we greatly appreciate Reds efforts, being an equal opportunity deployer as they are.

[Miguel "Macgregor" De Olaso]

Maybe this might sound stupid, but what is the advantage of using command line tool?

[Steve Freebairn]

All this is related to the same core code so yes for QT on PC probably around the same time.

I don't know how much harder it is, but will the QT component be for XP and Vista? Do they use the same codecs or will it be XP only. I'm really hoping for XP and Vista.

[Cory Schulthies]

Yeah vista 64 bit is what i will be running soon. It works great with Adobe CS3 and I will finally be able to use more then 4 gigs of ram.

[jbeale]

Maybe this might sound stupid, but what is the advantage of using command line tool?

Not to seem unhelpful, but if you are asking a question like that, it is probably not your tool of choice.

For people who are doing automated processing, usually distributed over several machines, command-line tools are the only way to go. For example, distributed work on many systems being run from some script, you have to control the tool via command-line parameters, config files, or similar. The interface requirements are quite different from an interactive session run by one person with screen, keyboard & mouse.

[Jeff Kilgroe]

Is REDline multi-threaded? How well does it scale across multiple CPUs? Any comments on RAM usage from anyone yet?

Just wondering if it is more efficient to assign an instance of REDline to each CPU core, or if it will scale well on its own.

[sbaechler]

Is REDline multi-threaded? How well does it scale across multiple CPUs? Any comments on RAM usage from anyone yet?

Just wondering if it is more efficient to assign an instance of REDline to each CPU core, or if it will scale well on its own.

I was just encoding a Quicktime Proxy into another format with Quicktime Pro and it was using both cores. So even the Quicktime codec is multithread.

[MikeHedge]

exciting... I hope Redcine for Vista gets released.

mike

[David Birdy]

Glad you liked my homeland. wish I was shooting there now. beautiful rainy dublin grey sky. its a ripe place for a noir thriller :)

I have some great still shots of country side.
I would like to recreate the Easter rebellion at the GPO on my RED One....Sunday Bloody Sunday as the sound track.

Possibly the Manchester jail break from the police wagon...Hundreds of great stories from coast to coast just waiting to be told with the RED One!

Dave

[Dj Joofa]

I was just encoding a Quicktime Proxy into another format with Quicktime Pro and it was using both cores. So even the Quicktime codec is multithread.

Quicktime on Windows is serialized as opposed to Macs which is multithreaded. Now I am not sure if Quicktime Media Layer (QTML) on Windows will block threads from accessing the same QT component from the same process; definitely block from more than two processes -- that being the case if another Windows application is also using the same QT component.

[Alexander Nikishin]

Sorry if this question is off but i'm un-familiar with cmd line tools......

So if i'm reading a few of these posts right, it seems that you can basically daisy chain multiple macs together to create somewhat of a render farm for redcine tasks?

[Cüneyt Kaya]

read this...

http://en.wikipedia.org/wiki/Command_line_interface

and this

http://www.igeek.com/articles/OS/CommandLines.txt

asfaik this means you can create plugins but without GUI...if someone has created a useful plug in, then he can create a GUI, hence a little program with userface.

this is what i understood.

[Deanan]

You can specify how many threads you want to use. If you're on a 8 core and you want to keep working, just set it to 4 or whatever.

[martinnoweck]

wow, i never thought i have to ressurect my school knowledge of basic, pascal, logo and cpm to shoot 4k footage ;-)

[Chris Swinbanks]

wow, i never thought i have to ressurect my school knowledge of basic, pascal, logo and cpm to shoot 4k footage ;-)They taught that in school....??? now I'm feeling too old for this.... :sad:

[Ariana]

wow, i never thought i have to ressurect my school knowledge of basic, pascal, logo and cpm to shoot 4k footage ;-)

you only need to know how to use a shell. much easier than basic.

[martinnoweck]

They taught that in school....??? now I'm feeling too old for this.... :sad:

1985 ...

[Ariana]

now that's old. :)

[Thor Wixom]

Jay, that makes us twins. We have 13 quad core XP PRO systems with 4gb RAM and ATI cards and we can't do anything with our Red footage yet... Our fingers are crossed and getting numb, but Kevin and Brent have kept us up to date and we're excited.

To those who continually suggest we invest in Mac, please understand that we(and many others) are deeply invested in our XP PRO render and working environments and when you urge that we just use a Mac, you're not taking into account the additional software and codec costs, infrastructure, IT, training and all of the higher expenses associated with changing platforms to work with Red footage. The multi-platform scenario is the best solution and we greatly appreciate Reds efforts, being an equal opportunity deployer as they are.

My name is Thor Wixom, and I approve this message.

[Zach Gray]

Not to seem unhelpful, but if you are asking a question like that, it is probably not your tool of choice.

For people who are doing automated processing, usually distributed over several machines, command-line tools are the only way to go. For example, distributed work on many systems being run from some script, you have to control the tool via command-line parameters, config files, or similar. The interface requirements are quite different from an interactive session run by one person with screen, keyboard & mouse.

We use Qube! for our Maya/AE/Lightwave rendering. It's a bit daunting to set up, but when it's running, an extremely powerful tool for managing distributed rendering tasks. It's very open, and you can write very tightly integrated job types for any software. You can also point it a a command line tool like RedLine. Given a RedLine processing job, Qube! could easily distribute and manage it across multiple worker cpu's.

It's also cross plaform, win, osx, linux.

LINK: http://www.pipelinefx.com/

[I Bloom]

We use Qube! for our Maya/AE/Lightwave rendering. It's a bit daunting to set up, but when it's running, an extremely powerful tool for managing distributed rendering tasks. It's very open, and you can write very tightly integrated job types for any software. You can also point it a a command line tool like RedLine. Given a RedLine processing job, Qube! could easily distribute and manage it across multiple worker cpu's.

It's also cross plaform, win, osx, linux.

LINK: http://www.pipelinefx.com/

How much does it cost?

[sbaechler]

Thank you RED for listening to your user's whishes. (I cannot say customer because I haven't ordered a camera.) But I'll be working with RED a lot.
I am stunned that you pulled this off so quickly.
This CLI just made the camera much more attractive for episodic TV and feature films that have a tight delivery schedule.

I'm looking forward to the day when you can online a RED project as easily as a digi beta project now.

[sbaechler]

Jay, that makes us twins. We have 13 quad core XP PRO systems with 4gb RAM and ATI cards and we can't do anything with our Red footage yet... Our fingers are crossed and getting numb, but Kevin and Brent have kept us up to date and we're excited.


You don't need a Mac to run OSX. Redalert, the QT plugin and FCP theoretically run very well on OSx86. ;-)


According to those forums:
http://forum.insanelymac.com
http://www.hackint0sh.org/forum/indexpage.php

[BASSAM MSSALATIE]

CLI something is very important
for deadline working enviorements as i understand .but i think we need somethin to simplify things (user manuel , tutorail.examples) to figure out
what is recommended workflow for it

1 - how it will serve our needs as much as possible

2- how to use it correctly

3- how to fix it (or fix its components)


cause guy's we are here not all of us ROB LOHMAN , or Graeme Nattress
we are users for some new
brilliant technology . it is right this Tech uses sometimes known methods as
CLI which is not all of use familiar with it at all

so PLEASE some Beiggeners Guidelines for us please :ohmy: :huh:

[BASSAM MSSALATIE]

i found something here after spending sometime in searching and reading


REDLine is so cool. I was playing with it last night. Looks like you could set up quick and dirty batch processing of your r3d files. Divide the work among several computers. I wonder how long before you would saturate your shared storage if multiple nodes processed to the same shared storage for simplicity... hmmmm. This get's me thinking... Has any script kitty out there already done this?
:usd: if there is more detailes i would appreciate it .thanks

[Stephen Gentle]

I can't wait for the Linux version - I want to try out DrQueue (http://drqueue.org/) (free and open source, runs on Mac OS, Windows, Linux, BSD, IRIX etc.) and see if I can get it to work with REDline.

From what I have read though, just getting DrQueue set up can be challenging enough...