Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Command Line tool...

Status
Not open for further replies.
Jeff Kilgroe said:
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.
Click to expand...

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.
 
darkkelt said:
Glad you liked my homeland. wish I was shooting there now. beautiful rainy dublin grey sky. its a ripe place for a noir thriller :)
Click to expand...

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
 
sbaechler said:
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.
Click to expand...

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.
 
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?
 
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.
 
wow, i never thought i have to ressurect my school knowledge of basic, pascal, logo and cpm to shoot 4k footage ;-)
 
martinnoweck said:
wow, i never thought i have to ressurect my school knowledge of basic, pascal, logo and cpm to shoot 4k footage ;-)
Click to expand...

you only need to know how to use a shell. much easier than basic.
 
J Clark said:
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.
Click to expand...

My name is Thor Wixom, and I approve this message.
 
jbeale said:
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.
Click to expand...

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/
 
conflict said:
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/
Click to expand...

How much does it cost?
 
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.
 
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:
 
i found something here after spending sometime in searching and reading

nwfilmclub said:
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?
Click to expand...
:usd: if there is more detailes i would appreciate it .thanks
 
I can't wait for the Linux version - I want to try out DrQueue (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...
 
Status
Not open for further replies.
Back
Top