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

Red Rushes

An iMac 24" can get you a long way with your RED, as long as the hard drive is not getting too full.

Emmanuel
 
Sorry do disappoint your conspiracy theories but there is no agreement that prevents us from doing anything at all. Development takes time and resources. REDalert started as our internal R&D app and was never intended to be released. It's architecture is not easy to grow into RC functionality without rewriting most of it. Doing so takes alot of time and then becomes
a trade off of providing featurs now or waiting a long time and rewriting.


Deanan,

Would it be hard to write a mini app that does what REDrushes does but extracts only the audio files.

It might be nice to have something that just extracts the audio from the R3D and places it into the folder the picture is rendered too. Then it could be really easy to open in FCP and sync the clips.

I like that kind of double system idea.

But maybe it would just be easier to build audio into RA in the future.

In terms of multi clips can RA run a script to say apply one of the presets onto a bunch of clips? Sort of like a photoshop script.

OPen>apply>save>close, etc.

Regardless. I like that RA is the little app that could. It's amazing how simple and easy it is but most of all I like that it is very stable.

Thanks for RedRushes, it's one I had been waiting for.

David
 
Sorry do disappoint your conspiracy theories but there is no agreement that prevents us from doing anything at all. Development takes time and resources. REDalert started as our internal R&D app and was never intended to be released. It's architecture is not easy to grow into RC functionality without rewriting most of it. Doing so takes alot of time and then becomes
a trade off of providing featurs now or waiting a long time and rewriting.

OK, understood!

So there's not really anything stopping RC from accepting EDL's, exporting colordata in the XMLs and let RedLine do the renders (as the post was refering to) That's great news! :)

Gunleik
 
Any plans to add any other transcode codecs such as DnX HD for us who prefer to use Avid?

Glad to see the multi-threading being used more efficiently and a proper debayering being done. I'm a skeptical red 'user', but I have to say, this one is pretty good.
 
Been working on that with Avid and we got it partially working last night and a fixed data rate.
 
I suppose m2v will be difficult, since Apple dropped the direct export in QT some time ago. But what about HD in H.264 and playing it from a PS3 to a decent projector? That's what I'd call dailies…
 
I just saw the "make avid compatible audio" option in the options menu, so I guess ou are going to add audio to a future release. GREAT!

David
 
How do you make the RSX file and how do you get REDrushes to look at that file?

does it apply the curves and exposure info you create in RED alert??

Sorry I do not have footage to test with it at the moment my camera is in customs and I am on location.

Thanks, Mark

I have asked this same question on another thread.

I too have tried to load RSX files, but they are all whited out. Only the R3D's are available to import.

The RSX files are from a previous version of RED ALERT (1.5.?) with Build 15 source files.

Dylan Macleod
Cinematographer
Toronto, Canada
www.dylanmacleod.com
 
You can only load the R3D files. If there's an RSX for that R3D file in the same directory, then it can optionally be used to provide a look setting.
 
You can only load the R3D files. If there's an RSX for that R3D file in the same directory, then it can optionally be used to provide a look setting.

By "optionally" do you mean by selecting "RSX:metadata if no RSX" in the "look source" pull down?

And by "file directory" do you mean the source folder that the R3D is in?

Thanks Deanan.

Dylan Macleod
Cinematographer
Toronto, Canada
www.dylanmacleod.com
 
A little update:

We just finished using Rushes to create some 720P editorial QuickTimes from one of our red mags from a recent shoot.

Rushes worked flawless, even on my MacBook pro: processing 146 shots with a variety of 3 and 4K frame sizes. It took about 3 hours for all the shots.
 
RSX vs. RLX

RSX vs. RLX

My hopes are dashed!

I was confusing RSX with RLX files.

I'd love to be able to use saved RLX files and be able to apply them as looks in REDRUSHES.

Wouldn't this be more useful than the RSX option?

What is the RSX anyway? Is it just an "autosave" of the last adjustment you made to a particular file in REDALERT?

Dylan Macleod
Cinematographer
Toronto, Canada
www.dylanmac;eod.com
 
I also have problems on a imac 24" (10.5.4, 4GB ram, FCP6.0.4, QT7.5)
RedRushes and the R3D automator action both render white frames when rendering to Prores. Using Redline directly in the terminal works as intended as does RedAlert. Very weird...

Both my MacBook and MacPro works as intended.
 
Try to render with the option "RSX+in/out…" in case you tried "RSX:…" (the second option). I get white frames as well, but the first one works, even without in/out points really set.
 
What is the RSX anyway? Is it just an "autosave" of the last adjustment you made to a particular file in REDALERT?

Yes.

Remember everything here is a work in progress. REDrushes was cranked out in a very short timespan and released so people could start using it asap. It's just the first version. If we waited we had time to add all the features we wanted then it'd be two months later before it got released and there would have been no opportunity for guys to use it a give feedback. Just saying...
 
Try to render with the option "RSX+in/out…" in case you tried "RSX:…" (the second option). I get white frames as well, but the first one works, even without in/out points really set.

Thanks for the samples. Looking at it now.
 
Back
Top