RELEASED: BETA REDAlert! (v3.4.2)

[Brent@RED]

RED ALERT! & REDline & REDrushes (v3.4.2)

New Features:

* TC Burn in for RL and RR
* Added Select RSX for setting look to RL and RR
* Added shutter and build output to RL metadata output
* Added DNxHD output (needs a the new codec from Avid or output is noise)

Bug Fixes:

* Misc fixes

Thanks, BC

[Luminance]

Hi Brent,
Seems the QT wrappers are still not working for certain clips. I'm trying to make proxies from an R3D file, and all I can come up with is the _H proxy, if I select Make All. The function works on certain clips from that batch, but not all of them.

Tried both the Source Folder and a Destination Folder.

Is there a backwards-compatibility issue with RedRushes?

Marc-André Ferguson

[MikeHedge]

is this mac only?

[Steve Freebairn]

is this mac only?
yes, it's mac only

[Gabriele Turchi]

May i ask you if in the feature will be a perfect match between the image corrected displayed in Red Alert and the Qt references created from that?

I mean , we know that there is a problem using the curves, but even without using the curves after some adjustment like exposure contrast WB etc...the QT references created are quite far from the image that i can see in Red Alert...

So,there is hope for that?

Thanks

G

[Deanan]

Hi Brent,
Seems the QT wrappers are still not working for certain clips. I'm trying to make proxies from an R3D file, and all I can come up with is the _H proxy, if I select Make All. The function works on certain clips from that batch, but not all of them.


Is it working for some but not for others?

[Mark L. Pederson]

4K 16x9 _M wrappers play fine in QT player - but will NOT render in compressor - _H works fine - used 3.0 and 3.1 Quicktime component -

Quicktime 7.5 - OSX 10.5.4 (doens't work on 10.4.11 either)

renders are all good RedRushes

[Luminance]

Is it working for some but not for others?
Right.
Most clips work no problem.
Some clips give me 3 or the 4 proxies, and then another clip only gives me _H.
Kind of odd.
Thanks!

[Deanan]

Right.
Most clips work no problem.
Some clips give me 3 or the 4 proxies, and then another clip only gives me _H.
Kind of odd.
Thanks!

Very strange. Rob and I are looking at it now and have some hints as to where the problem might be. It looks like it actually goes back quite few versions.

[Luminance]

Thanks guys!

[Jason Diamond]

waiting for the new AVID codec as well yes?

[Deanan]

The DNxHD output will work properly when the new one is released from Avid.

[Deanan]

Right.
Most clips work no problem.
Some clips give me 3 or the 4 proxies, and then another clip only gives me _H.
Kind of odd.
Thanks!

Fixed. New version v3.4.3 going up for download soon.

[Keith Nealy]

Deanan, if a PC version magically appeared you would go down in RED history as the savior of multitudes, a messiah of the masses, the one who could turn water into wine, (or at least R3D's into AVI's) and you would be revered for time immemorial.

What say you, oh prophet of REDness...? :whistling:

aloha,

Keith

[Gabriele Turchi]

Denan

What about the differences between the image displayed in Red Alert! and the image created as a Quicktime Ref?

Are you working on that or it's just not possible have the same image (i mean now is pretty close but the color and the exposure it's actually not the same...)

Thanks

G

[Brent@RED]

Fixed. New version v3.4.3 going up for download soon.

This new version is live on RED.com/support....

BC

[Deanan]

Denan

What about the differences between the image displayed in Red Alert! and the image created as a Quicktime Ref?

Are you working on that or it's just not possible have the same image (i mean now is pretty close but the color and the exposure it's actually not the same...)

Thanks

G

The problem you're seeing is the classic QT gamma problem.

[Luminance]

Works likes a charm! You guys never cease to amaze me.
Thanks!

[Dylan Reeve]

* Added DNxHD output (needs a the new codec from Avid or output is noise)


WOO!!!!!

Uh, how do we get the new codec from Avid?

[Gabriele Turchi]

The problem you're seeing is the classic QT gamma problem.

Well actually i am not talking about the gamma problem using the curves etc...i am talking about without touch the curves , the image is not the same , is close , but the color and in general i can't say that is the xact same

does anybody noticed that ?

And what about the gamma problem?News for the future realase?

Thanks

G

[Paolo Tinari]

WOO!!!!!

Uh, how do we get the new codec from Avid?

Search here but i'm not sure http://www.avid.com/onlineSupport/browseCodec.asp

[Dylan Reeve]

Nah, I believe it's the revised version MichaelP was talking about recently. I don't think it's publicly released yet.

[Tim Fassnacht]

you guys kick ass and take names.

Stoked.

[Kenn Michael]

Well actually i am not talking about the gamma problem using the curves etc...i am talking about without touch the curves , the image is not the same , is close , but the color and in general i can't say that is the xact same

does anybody noticed that ?

And what about the gamma problem?News for the future realase?

Thanks

G

Yep, that's still the QT gamma issue.

[Scott Mason]

I have noticed the same thing in the quicktime player, but it looks fine in FCP, regarding the gamma shift. (no shift in FCP but big shift in quicktime, makes no sense to me ;)

p.s. this version of redrush seems to work great for me. I like the new interface and options. I will test more throughout the week but am very pleased now.

All I need is audio and I won't have to perform the extra step with my terminal script that combines the video with audio.

whoo hoo great job red. On another note all this build 16 footage kicks ass. It looks so good every time I watch a clip I am amazed, and my clients are in awe.

mahalo
scott

[Kyle Mallory]

Deanan, last I knew quicktime proxies would lose audiowhen regenerating them from RedAlert. Is this still true?

Kyle

[Trevor Meier]

Assuming still no audio support in Redrushes? (don't have access to footage to test at the moment)

[Kevin Wild]

Trevor, in another post they said audio pass-through will be in on the next build, not this one.

I love that timecode has been added and that you can add the "look" that you had from your camera. Can't wait to test this tomorrow.

Kevin

[Deanan]

Deanan, last I knew quicktime proxies would lose audiowhen regenerating them from RedAlert. Is this still true?

Kyle

Audio from the remade proxies has been in for a while.
Audio going into the transcoded QTs will be in the next build.

[Scott Mason]

Audio going into the transcoded QTs will be in the next build.

whoo muther f*#*kin hooooo That is the best news ever!!!!! Redrushes seems to be working flawless. I will test it on an entire reel tomorrow in the office, but at home it is flawless. Any word on the 2gb file limit when rendering over the network?

[Dylan Reeve]

I've rendered to network drives without any such limits? I think.

[Trevor Meier]

QT renders over AFP stall at 2GB...

[JoshBertrand]

I'm rendering to Pro-Res and I get files that start at the first frame again during the render and are thus not rendering all of the frames. For instance one shot is 22 minutes when viewed through the QT proxy, but my render is only 9 minutes which includes a restart at frame one 4.5 minutes in to the clip. I have another clip that restarts at 1:04 then freezes on a frame for 9 seconds toward the end. Most of the clips in the batch (from the same shoot) repeat, though a few are fine.

The render seemed to go smoothly, reporting 100% on everything. What can I do to troubleshoot? I'm on 10.5.4 with QT 7.5. Red Rushes 3.43.

[Deanan]

Email me the output of export script (file menu). Also, are you rendering locally or over the network?

[Bastiaan Houtkooper]

Same here, rendering with RR 3.42 and 3.45 gives 100% finsihed renders but when you look at the final clips they restart after 1.3-2 minutes.

Input 4K 16:9 R28 B16- output QT H264 rescaled 1280x720. Selected RSX file, no burn in, no crop.

Did the same in ProRes with the same (bad) results.

Looking at the activity monitor it reports 3 threads going over 100% on my quadcore MacPro. This seems not OK,

[Deanan]

RR 3.45 shouldn't have the clip restart problem but in any case, 3.46 is better overall. PM with your email and I'll send it to you. 3.46 should be out shortly.

For a quadcore, it does run three threads at over 100%. That's how it uses all four cores.

[Scott Mason]

Deanan-

I know I am asking for too much, but will redrushes ever be able to take an xml and pull just those r3d files into it, or remove the files that are not in the xml. This would rock my online workflow.

Just gotta ask. I know I can do this with crimson and redcine, but redline is so much easier to use and is rock solid (I imagine redrushes is using redline to render)

p.s. being able to save the last look created in redalert would make for applying it to the next clip I load much easier. I know I can make a preset, but I just want a temporary copy and paste.

mahalo for all your hard work, I can see the light at the end of the tunnel for all this post workflow and we all appreciate it.

scott

[Deanan]

Thanks Scott. REDrushes is using redline to render.

I'm expecting that once people start digging into the SDK we'll start seeing all sorts of solutions for conforming from edl or xml. At that point we'll need
to evaluate if we need to provide those options or not.

[Nicholas Shields]

I normally use RedCine, but thought I'd give RedRushes a go but I've encountered problems. In attempting to render out, my progress indicator goes to "error" almost immediately. I'm taking 2K 16:9 24fps R3D files and attempting to convert them into ProRes HQ 720. I'm attempting to use a single RSX file from the first clip in the batch on all other clips. The RSX file is in the first clip's folder. I'm attempting to output to a completely different directory. Any help would be greatly appreciated.

Nick.

[Jonas Nyström]

I normally use RedCine, but thought I'd give RedRushes a go but I've encountered problems. In attempting to render out, my progress indicator goes to "error" almost immediately. I'm taking 2K 16:9 24fps R3D files and attempting to convert them into ProRes HQ 720. I'm attempting to use a single RSX file from the first clip in the batch on all other clips. The RSX file is in the first clip's folder. I'm attempting to output to a completely different directory. Any help would be greatly appreciated.

Nick.

Exactly the same problem here! Error all the way! Booth B15 and B16.

Cant get Log and Transfer to work with B16 either.

Any ideas anyone?

[Seth Larney]

Hey guys,

Same error here.. I've tried every checkbox and codec, plus DPX/TIFF output instead of QT..

Latest QT codec and RedAlert .. on new Mac Pro

Same software versions work fine on my Macbook Pro.

Weird..

[Seth Larney]

Oh yeah, OSX 10.5.3 as well

[Jonas Nyström]

Oh yeah, OSX 10.5.3 as well

And B16 v3.2.5!?!

[Seth Larney]

Yup.. B16 v3.2.5

Rendering out of Redcine on a 8-Core, 16GB RAM Mac Pro to 1080P Prores instead right now .. 1.5 hours wants to take 42 hours to transcode..

Aiiiiirrggg.. .I love you so dearly RED but I'm crying on the inside

[Seth Larney]

One more note ..

Redline doesn't work for me when I try 'render in command line' from RedAlert!.

I get an error like "error: resolution must be 1 or 2" .. or something similar (not at the machine right now). I'm assuming this is casing the problem with RedRushes?

[Seth Larney]

If only PRORES wasn't mac only, I'd be able to use our SCRATCH to render out the rushes. Instead I spent 8 hours trying to work around this issue this evening only to end up wishing that I'd started that 42hour Redcine render 8 hours ago..

drat.. oh well :wink:

[M Most]

Yup..

Rendering out of Redcine on a 8-Core, 16GB RAM Mac Pro to 1080P Prores instead right now .. 1.5 hours wants to take 42 hours to transcode..

Aiiiiirrggg.. .I love you so dearly RED but I'm crying on the inside

Sounds like you're using Full debayer and also not setting the display to Full High. Three questions:
1. Am I correct?
2. Assuming I might be, do you **really** feel you need Full debayer for 1080 output?
3. If you have the display at anything other than full and you're using Full debayer, change the screen display to Full. You should find a dramatic increase in render speed. Note: This also holds true for Standard (set to Half High) and draft (set to Quarter high). For the fastest good results on what you seem to be doing, try Standard debayer and Half High display. On an 8 proc Mac, this should reduce the render time to less than 4:1 for pre-B16 footage, higher for B16, provided your storage (both for the source and render directories) is fast (i.e., fast local array or fast SAN). For even faster results, try rendering to DPX rather than QT files if you can handle DPXs through post. Rendering to DPX with pre-B16 footage using the same settings I mentioned above should get render speeds of a little over 2:1. At least that's what I've found...

[Seth Larney]

Sounds like you're using Full debayer and also not setting the display to Full High. Three questions:
1. Am I correct?
2. Assuming I might be, do you **really** feel you need Full debayer for 1080 output?
3. If you have the display at anything other than full and you're using Full debayer, change the screen display to Full. You should find a dramatic increase in render speed. Note: This also holds true for Standard (set to Half High) and draft (set to Quarter high). For the fastest good results on what you seem to be doing, try Standard debayer and Half High display. On an 8 proc Mac, this should reduce the render time to less than 4:1 for pre-B16 footage, higher for B16, provided your storage (both for the source and render directories) is fast (i.e., fast local array or fast SAN). For even faster results, try rendering to DPX rather than QT files if you can handle DPXs through post. Rendering to DPX with pre-B16 footage using the same settings I mentioned above should get render speeds of a little over 2:1. At least that's what I've found...

Hey Mike,

Thanks for the input mate :)

To answer your questions :

1) Actually I am already set to Full and High as this is what I have found as well, but I can see why you might think this is the case.. thanks for the heads up!
2) I do feel like I need full debayer as I find that the noise size (what little there is) is dramatically reduced with a full debayer, even when downconverting to 1080. I'm from the "anything less than the absolute best isn't good enough' school (unfortunately for me sometimes) :whistling:
3) Thanks mate, this is what I have found as well.. right now I am set to Full Debayer and Full view. Funnily, this is not usually the case, but if I try to set 'Standard' Debayer and 'Half' View, then my render time INcreases to 49hours. Weird, but doesn't really matter for me now as I'm pretty set on a full debayer.

I must add, that after the render settled a little, it went down to 36hours, so that's a "little" better.

:ninja:

I think what I really need is for RedRushes to work.. oh well, the gods don't want me to have efficient multithreaded happiness today.

[Nicholas Shields]

Just a reminder for Deanan to take a look at the question posed a few posts ago.

Thanks,

Nick.

[Jonas Nyström]

Seth

Strange, RedRushes work on my PB as well. And not on my 8-core Power Mac.

[Jonas Nyström]

I normally use RedCine, but thought I'd give RedRushes a go but I've encountered problems. In attempting to render out, my progress indicator goes to "error" almost immediately. I'm taking 2K 16:9 24fps R3D files and attempting to convert them into ProRes HQ 720. I'm attempting to use a single RSX file from the first clip in the batch on all other clips. The RSX file is in the first clip's folder. I'm attempting to output to a completely different directory. Any help would be greatly appreciated.

Nick.

Shouldn't you use the R3D files?

[James Brundige]

This fixes the linked clip bug, quite necessary. Thanks.

Installing this upgrade puts several action files on the desktop Do they need to stay there?