Welcome to our community

Be a part of something great, join today!

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

RELEASED: BETA REDAlert! (v3.4.8)

Brent Carter

Brent Carter

REDUSER.NET
Joined
Aug 22, 2007
Messages
4,992
Reaction score
5
Points
0
Location
Irvine CA
Available on www.red.com/support

RED ALERT! & REDline & REDrushes V3.4.8 READ ME

Changes:
* Added Debayer Half (Normal). The old Half is now renamed to Half (High) to RR&RL
* Added Eighth Res Debayer to RR&RL
* ALE export now writes wrapper extension in name field

Bug Fixes:
* Fixed bug with "no extension for QT wrappers".
* Fixed problem with burnin stopping renders early.
* Fixed bug on really long files at 59.94

Thanks, BC
 
Is the install fixed? Are the files going where they are supposed to?

Nick.
 
Brent - you mentioned the next build would include audio, and I assumed you meant the one released today. Do you mean the next major build will include audio?
 
This build was bug fixes. Audio is being worked on for the next major one.
 
Hey, Guys. Thanks for cranking out these updates. It makes me feel good that some of these less-than-perfect things will be taken care of and not in the usual "big-company, wait 2 years way." :-) I have to say RED Rushes is fast becoming the app I love just due to the ease at which you can bring media in, batch output it overnight and start editing with it in HD the next day without any additional color correction other than in FCP. For much of our work (and probably many other peoples'), that is a great workflow and closer to what we're used to in the non-film world.

One thing of interest...I did some tests for speed and file size on a 9 second clip. I found that with all settings exactly the same except for the Debayer Quality, the "Full Res" clips are actually smaller file size than the "Half Res." This a bug? Didn't make sense to me. Here are the final sizes for the clip I tested, when exporting as a ProRes (HQ), Scale to 1920x1080 fit width, no BITC file using an Intel Macbook Pro:

-Full Res: 181.4 MB
-Half (High): 189.5 MB
-Half (Normal): 184.8 MB
-Qtr: 174.5 MB
-1/8th: 183.1 MB

You can see where the 1/8th is more than the 1/4, too. Odd...

The one take away from my VERY brief test is: These different settings don't change file size all that much, so I will probably use "Half (High)" when going directly to an HD file to edit/finish for corporate type or broadcast, non-spot type work.

HOWEVER, the speed at which these work is MUCH different. If we need just DVD's for viewing, I will absolutely use 1/8th Res. It looked good still and was MUCH faster than the others. For instance...

9 sec clip @ Half Res (High): 3min 35sec
9 sec clip @ 1/8th Res: 54 sec

9 sec clip @ 1/8th Res w/ NO SCALING, 512 x 256 pixels, W/ BITC: 20 sec.
9 sec clip @ 1/8th Res w/ NO SCALING, 512 x 256 pixels: 16 sec



Granted these are on a Macbook, but it should give an idea to people of the difference between settings. For me, it looks like footage that we want to start editing on, we'll do Half Res (High). For footage we want to send to clients with timecode, we'll do 1/8th Res w/ No Scaling w/ BITC and let Compressor upscale the file for DVD's or just send the quicktimes...

Still would love:
-Umm..audio. :-)
-Addition of preset "looks"
-Preview window (if even the first frame only)
-Ability to drag and drop clips
-Warning if a clip does not export all the way for some reason. (love you can open and play a partial clip...but dangerous as you think it finished.)

Thanks again. Great work!

Kevin
 
I had the duration of that clip wrong...it was not 12 seconds for the tests I did, but 9 seconds. I edited it.

Thanks.

Kevin
 
There is time associated with starting each process so a better test would be to use a longer clip as a test.

Also, since REDline is not fully utilizing all cores currently and RR is running multiple threads, you may want to test with a bunch of clips and measure total running time / total rendering time.

Regarding file sizes... because you're adding the effects of the scale to the processes, which why 1/8th is probably bigger than 1/4th.
 
I imported 10 clips in REDrushes: Debayer set to full, Scale set to fit height and set a new output folder and hit start.

REDrushes appears to be rendering. All clips finish with 100% in progress, but there are only two .mov files in the output folder. They are each 4k and when clicked report : "This is not a movie file". I reinstalled REDrushes and tried a few more clips, the .app looks like it is working, but no files are created in the output folder.

REDrushes v. 3.48 (1)
3.2GHz Quad-Core Xeon
16GB Ram
OS 10.5.4
 
Do you have any funky characters in the output path?
email me the output of export script if you can. d e a n a n - a t - r e d
 
Deanan,

I Emailed my Export script and shortly after I think I figured out the problem. The output disk ran out of space. My last render filled the drive.

It was confusing because REDrushes doesn't report an error. It looks like it is rendering and shows 100% complete, but when you check the output folder there are either no files or corrupted files that can't be opened.

My initial tests to a clean drive are all working fine. Maybe some form of disk check before rendering would be helpful.


Side Note: A cool Mac program for graphically looking at where files are on a disk is Disk Inventory X. Check it out.
 
I know you have a lot on your plate and I'm very grateful for free bonus applications like RedRushes, so this is obviously not a high priority, but I'd love to see 'iPhone' added to the list of export presets in RedRushes. With rushes in .mp4 format, you can use wi-fi and personal web sharing to allow anybody on the set with an iPhone/iPod Touch to view timecoded rushes.
 
Spaces, parentheses, dashes, and apostropes are fine for red rushes and rendering inside redalert. For REDline, you have to escape those and many other non alphanumeric characters.

It's always good practice to only use alphanumeric and underscore for spaces if you intend to do command line work. It'll make your life much easier.
 
RedRushes is an amazing tool, deanan! And it keeps getting better and better. Some stability issues , though. It keeps crashing at around 3 hours of rendering. Did this twice in a row. I have not been able to sustain rendertimes of over 3 hours.
Also, could there be a setting for how many simultanious renders. Right now it seems to be set to 6, but I've noticed serious reduction in rendetimes when only selecting 3 at a time, but then I have to be present the whole time and start batches.
Thanks again for this app!
 
Which version did this happen on?

RR is using REDline to run each clip as a separate process so rendering is largely independent of RR. I've done tests with running hundreds of clips for days and haven't had problems. That leads me to believe that you might have a particular clip that's causing a problem.

I'd suggest as a test, exporting a script and running that script in the command line.
 
I had RedRushes crash on me yesterday after only a few minutes. I had six clips in it, and it crashed immediately after the first two got to 100%. Those two had completed properly, but the other four were corrupt.

Any extra info/crash log that would be helpful to you?
 
Try running the clip in REDline via the terminal and see capture the output on the third clip.
 
You must log in or register to reply here.
Back
Top