Welcome to our community

Be a part of something great, join today!

  • 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 :)

Redline supporting Red Rocket

Colin Hubick

Well-known member
Joined
Mar 23, 2007
Messages
629
Reaction score
0
Points
16
Location
Canada
any news on Redline supporting RedRocket? Is this even something on the radar, or has it been abandoned?

thanks
Colin
 
A little bird told me it would happen and that there is beta-soft doing that.The bad news is that this is a second-hand bird, so it's as good as any rumor out there...

I know who I'd have PM'ed to get a confirmation, though...
 
What would be the biggest benefit of RedLine supporting RED Rocket™?

Apps like Clipfinder, Crimson and Monkey Extract having access to Rocket rendering without having to write their own encoding engine.
 
I think Clipfinder can already do it.

David

Not really.

Clipfinder has a hack which uses Rocketcine-X to do the rendering, but is only released to a small alpha testing group. It is not Hans' intention that this is the way it will work in the long term.
 
the sdk which supports rocket is available.... probably it will work with that..... ???
MIST software for example use it and you can do the hole roundtrip.... but its only windows based....

redline with rocket support would be cool anyway.... it will come for sure, but the to do list of deanan is very very long... big thx at this point.....
 
Rocket support is in the RED SDK, which Clipfinder and others are using to support R3D files to being with. New SDK with the new color science and FLUT support is said to be happening this week... So soon. We still have to wait / hope the developers get it incorporated. Incorporating Rocket support for the first time adds a lot of extra work.

As for ROCKET support in REDLINE. I wouldn't count on it. In fact, it was said just recently that REDCINE, RED ALERT / REDRUSHES (which uses REDLINE), are at their end. Moving forward all development is going into REDCINE-X. An update to Rocketcine-x has been mentioned last week, but it was also said that eventually it to will be rolled into Redcine-X.

Not sure what the benefits to Redline supporting the Rocket would be. Unless you had multiple systems with a Rocket and wanted to use render management software to drive Redline and really speed through transcodes. In that regard, it would make sense to have a Redline that supported the Rocket. But beyond that, I don't really see it.

Nothing stopping anyone with the SDK from creating their own version of Redline that supports the Rocket....
 
...In fact, it was said just recently that REDCINE, RED ALERT / REDRUSHES (which uses REDLINE), are at their end. Moving forward all development is going into REDCINE-X. An update to Rocketcine-x has been mentioned last week, but it was also said that eventually it to will be rolled into Redcine-X.

Said by whom??? Dropping RedLine would be very short sighted in my opinion. The very nature of processing Red footage is batch processing, and a lot of us are using RedLine to accomplish this. RedLine allows for very simple qmaster clusters to process footage very easily, anyone can do it. I have automated scripts that process dailies just by dropping R3Ds into the right directory, I don't want to have to navigate some GUI when I'm on a set and footage is coming fast and furious.

I can appreciate that Red wants to sell RedRocket cards, and that the more they sell the cheaper they'll get, but to eliminate the command line batch processing tool that is effective for so many of us would seem to be an attempt to drive us to that solution. RedLine is only limited by the number of CPUs you can set up in your cluster, whereas RedRocket does have a limit to its abilities as it sits in one computer.

Mac Pro plus RED Rocket™: $3000 + $4500 = $7500 (Reported 24 FPS)
Twin i7 Hackintosh: $3200 x 2 = $6400 (32 processing threads)

I sincerely hope it is not true...

Bob
 
Nothing stopping anyone with the SDK from creating their own version of Redline that supports the Rocket....

That is a very good point. If Red are not going to do it (anybody from Red care to confirm) any programmers out there feel like doing it?

Writing a 'proper' application with it's own rendering engine is a big deal, but batch scripting a command line utility is something anybody can have a go at!
 
Not sure what the benefits to Redline supporting the Rocket would be. Unless you had multiple systems with a Rocket and wanted to use render management software to drive Redline and really speed through transcodes. In that regard, it would make sense to have a Redline that supported the Rocket. But beyond that, I don't really see it.

Nothing stopping anyone with the SDK from creating their own version of Redline that supports the Rocket....

My main reason for wanting to see Redline support RED Rocket™™ is for the very reason of distributed processing using Qmaster (which kicked-ass for me). Prior to RED Rocket™™ we used Monkey Extract to conform our projects, and only render out the material used in the locked pic. If RedCine-X or RocketCine were able to conform, and only process out the material used in the locked pic, I would agree, no need for Redline anymore. But at the time of writing this, there is no indication that such features will be incorporated into RedCine-X or RocketCine. Further if Redline was able to work with RedRocket, you could in theory set up 3 or 4 Red Rocket machines, and have uber fast processes from multiple machines...

If someone knows something different I'm all ears.

best
Colin
 
Said by whom??? Dropping RedLine would be very short sighted in my opinion. The very nature of processing Red footage is batch processing, and a lot of us are using RedLine to accomplish this. RedLine allows for very simple qmaster clusters to process footage very easily, anyone can do it. I have automated scripts that process dailies just by dropping R3Ds into the right directory, I don't want to have to navigate some GUI when I'm on a set and footage is coming fast and furious.

Mac Pro plus RED Rocket™™™: $3000 + $4500 = $7500 (Reported 24 FPS)
Twin i7 Hackintosh: $3200 x 2 = $6400 (32 processing threads)

I sincerely hope it is not true...

Bob

I couldn't agree with you more. Add RED Rocket™ in this mix, and you have something quite good.

Sounds like Bob and I are on the same exact page. (high - five)
 
My main reason for wanting to see Redline support RED Rocket™™™ is for the very reason of distributed processing using Qmaster (which kicked-ass for me). Prior to RED Rocket™™™ we used Monkey Extract to conform our projects, and only render out the material used in the locked pic. If RedCine-X or RocketCine were able to conform, and only process out the material used in the locked pic, I would agree, no need for Redline anymore. But at the time of writing this, there is no indication that such features will be incorporated into RedCine-X or RocketCine. Further if Redline was able to work with RedRocket, you could in theory set up 3 or 4 RED Rocket™ machines, and have uber fast processes from multiple machines...

If someone knows something different I'm all ears.

best
Colin

We've said a couple times already that we will be adding hooks for third parties build their own conform into redcinex so you're not limited to anything we might do with one editor vs another.

REDline has undergone a six million dollar rewrite and is better, stronger, faster and rocket enabled. It's almost ready to go out to a bigger group of testers.
 
That's great news Deanan! can't wait for it.

We've said a couple times already that we will be adding hooks for third parties build their own conform into redcinex so you're not limited to anything we might do with one editor vs another.

REDline has undergone a six million dollar rewrite and is better, stronger, faster and rocket enabled. It's almost ready to go out to a bigger group of testers.
 
It's almost ready to go out to a bigger group of testers.

Great to Hear, I base my whole archiving on XML's I get out from REDLINE and a bit of scripting, also vice versa when it comes to XML (FCP, AVID) for batch rendering.....

Is my name in that group :-)

On another note, does this include some form of EXPORT from redcine-x say CSV, XML etc....

regards

Marcus
 
We've said a couple times already that we will be adding hooks for third parties build their own conform into redcinex so you're not limited to anything we might do with one editor vs another.

REDline has undergone a six million dollar rewrite and is better, stronger, faster and rocket enabled. It's almost ready to go out to a bigger group of testers.

I remember you telling me that Redline wouldn't be abandoned, thanks for confirming that it won't. Looking forward to trying it out!

best
Colin
 
REDline has undergone a six million dollar rewrite and is better, stronger, faster and rocket enabled. It's almost ready to go out to a bigger group of testers.

Will the new redline support M-X raw images ?
Will it works with REDcolor and F-LUT ?
Will .rsx files still usable, or how will it get grading infos from our first light ?

I'm trying to setup new offlining workflows based on redcine-X, but alone as a batch tool it doesn't seems to be robust enough yet and ready for any kind of automation...

Thanks much to all at RED for your hard work on every front

Mikael
 
Will the new redline support M-X raw images ?
Will it works with REDcolor and F-LUT ?
Will .rsx files still usable, or how will it get grading infos from our first light ?

I'm trying to setup new offlining workflows based on redcine-X, but alone as a batch tool it doesn't seems to be robust enough yet and ready for any kind of automation...

Thanks much to all at RED for your hard work on every front

Mikael

yes
yes
It'll support the new look format (rsx replacement)
 
Back
Top