REDrushes Suggestions (September 2009)

[Chris Hocking]

Hi Everyone,

Firstly let me just say that I'm already in love with REDCINE-X. I've only been using it for a few days now and it's already been invaluable. That said, I'm still a massive fan of REDrushes, and would imagine that a lot of people will be using REDrushes for a while to come...

So with that said, here are some suggestions that I would love to see implemented at some stage in the future. I'm sure some of these have already been discussed on other areas of the forum - so apologies if they have.

Here's my wish list:

1. The "Total" frame counts should be listed as soon as you add the clips. That way you can know approximately how big all the clips are from the get go.
2. At the bottom of the list, there should be a "totals" section. If it could tell you how many minutes of footage is in the queue, that would be extremely handy. Better yet, if it could give you a very rough estimate of how long it will take to render everything, that would be even better! Surely it could work out how long it takes to render the first 50 frames of one clip, and then do the maths for the rest?
3. If you stop a batch, it shouldn't reprocess any clips that were completed when you start it again. The stop button should basically just act like a pause button. As REDrushes is basically just an interface for REDline, I think pausing a clip and then resuming it might be impossible (in the current REDline form), so it you pause it, you might need to restart whatever clip you stopped on - but it shouldn't process any clips that have already been done.
4. You should be able to "shift select" multiple clips in a row or "command select" multiple individual clips to select more than one clip in the list for removal. So say you want to delete the first five clips from the list, you should just be able to click the first one, hold down shift on your keyboard and then select the fifth one and press delete to get rid of all four.
5. REDrushes should translate all file paths so that they are compatible with REDline. For example, at the moment if you add clips that have a directory with a funky character in it (i.e. "rolls 1 & 2", without quotes), REDrushes will freak out. REDrushes should be able to handle any and every "legal" MacOS directory structure.

If I think of anything else, I'll write it here... Feel free to add to the list!

Thanks!

Best Regards, Chris!

 

[Mikael Lubtchansky]

one word answer : clipfinder

one word answer : clipfinder

ever looked at clipfinder ?

http://www.daun.ch/software/

check it out, it has all those requested features plus many more... the only real thing missing from REDrushes (as of today but not for long) is a full .ale export, it works well right now but is not as detailed as in REDrushes.

 

[joe hedge]

Also the ability to select different files in the same batch as look source:camera and others as .RSX

 

[Chris Hocking]

I have tried Clipfinder, and it's great for some things, but I find REDrushes a lot more stable... As we're using Avid for most jobs, the lack of ALE support is also a major downer...

 

[Chris Hocking]

6. There is a strange bug when you save an ALE, but choice to overwrite an existing ALE file (as opposed to typing in a new file name). It seems to merge the content of the existing file with the new file. I'm not sure if this is deliberate, but either way, if the original file only has a couple of headers, it doesn't bring the new headers from the newly created file to the existing one. I'm presuming it's a bug - as it should just delete the old file and replace it with the new one.

7. It would be really cool if the "Reel ID" when set to "FCP 8 Character" would also apply to the ALE exports.

 

[Cail Young]

Hey Chris!

Have you tried Metafuze over there? I haven't looked at it recently but it may be better suited given you guys are an Avid shop.

As to Clipfinder's stability, we did 38 hours of rushes for Hawke with it... Couple of hiccups with corrupted source files, but the render process itself was fine.

 

[dino g]

if you shoot 4k 16 x9 at 24 frames then the files size can roughly tell you how many frames you need to render. x 100... so 4.3 gigs = 430 frames


so when you pull in a batch of files from a drive or card, make note of the total number of gigs. then add those same clips to redrushes, set everything up and hit start. now get out your iphone and start the stopwatch, each time 25 frames render hit the lap button, do that for about 5 or 6, 25 frame renders. then you will have the average time it takes to render 25 frames, day 11.5 secs per 25 frames. if you set redrushes to 2 clips and 8 cores then you multiply the 25 x 2 and then divide the 50 frames by 11.5 seconds and you get 4.34 frames per second. now take that 4.34 and use that as the denominator and the number of frames as the numerator. so in our example 430 frames divided by 4.34 = 99 seconds then divid by 60 and you'll get your minutes and seconds...

takes about 2 minutes to do this and you will have your answer...

having said that, i asked deanan for this feature a year ago.

dino