QT Proxy Camera Organization Request

[Rick Darge]

I posted this in another thread but thought I would create its own thread here.

I just did DIT / compression work on a 3-day short. A lot of data, 800GB worth. Over 300 individual folders/clips.

I would love it if there was an option to send all R3D files & your choice of P, M, H or F QT Proxies in a single folder. That way when I hook up my Red-raid to the Mac, I can easily highlight, drag & drop the QT files into compressor.

Right now I have to open all the folders by highlighting and clicking the Right-Arrow, then scrolling down and highlighting all QT files.

Maybe this could be a script one could create for OSX. I would pay for it.

 

[I Bloom]

I posted this in another thread but thought I would create its own thread here.

I just did DIT / compression work on a 3-day short. A lot of data, 800GB worth. Over 300 individual folders/clips.

I would love it if there was an option to send all R3D files & your choice of P, M, H or F QT Proxies in a single folder. That way when I hook up my Red-raid to the Mac, I can easily highlight, drag & drop the QT files into compressor.

Right now I have to open all the folders by highlighting and clicking the Right-Arrow, then scrolling down and highlighting all QT files.

Maybe this could be a script one could create for OSX. I would pay for it.

Already built into my new software.
I

 

[Dylan Reeve]

Pretty easy to do with REDline too - I will post a script tomorrow if you like.

 

[Rick Darge]

I figured it was easy. I love this community.

Ian, when is the new Redtrip coming out? Dylan, that was be a lifesaver..

R

 

[Dylan Reeve]

I've used this (I've tidied it up a little and haven't retested it, so I could have broken it, let me know if it doesn't work). I put it in my home directory under a folder called scripts.

This originally germinated from a script that Deanan posted, I think.

Go into directory where RED files are (it will search the current directory and all subdirectories) and run it:

~/scripts/make-ref.sh 1 /Volumes/Media RAID/REDfiles

That creates _M res files in REDfiles on my Media RAID drive.

The first option is the size, as per REDline: 0=all, 1=M/Qtr, 2=H/Half, 3=P/Eighth

The second option is the target directory.

make-ref.sh

#!/bin/tcsh

if ($# < 2) then
        echo Usage: $0 [proxy_type] [target_directory]
        exit 1
endif

echo "Building file list..."
find . -name "*_001.R3D" -print > /tmp/filelist.$$

echo "Making QT Reference Files..."
foreach i (`cat /tmp/filelist.$$`)
        echo Processing $i
        REDline -i $i -w 10 --useMeta --QTdir $2 --QTsize $1
end
rm /tmp/filelist.$$

 

[Dylan Reeve]

While we're at it...

This one makes a CSV of all the meta data from the RED files...

~/scripts/makemeta.sh /Volumes/Dump\ Drive/REDfiles ~/redmeta.csv

It pays to specify an absolute path in this one, as that is the path that will be used in the filename in the CSV file.

makemeta.sh

#!/bin/tcsh
if ($# < 2) then
        echo Usage: $0 [search_directory] [output CSV]
        exit 1
endif

echo "Filename,ReelID,Camera,Reel,Clip,FrameWidth,FrameHeight,FPS,TotalFrames,TCStart,EdgecodeStart,TCEnd,EdgecodeEnd,Kalvin,Tint,Exposure,Saturation,Contrast,Brightness,GainRed,GainGreen,GainBlue,BlackX,BlackY,ToeX,ToeY,MidX,MidY,KneeX,KneeY,WhiteX,WhiteY" > $2

echo "Building file list..."
find $1 -name "*_001.R3D" -print > /tmp/filelist.$$

echo "Reading metadata..."
foreach i (`cat /tmp/filelist.$$`)
        echo Reading $i
        REDline -i $i --printMeta 2 >>& $2
end
rm /tmp/filelist.$$

 

[Deanan]

This originally germinated from a script that Deanan posted, I think.

Tcsh and find are dead giveaways for someone to lazy to learn bash or do it in python/perl

 

[Deanan]

I think you might also want to add --useMeta in there if you want the QT refs to use the metadata set on the camera.

 

[Rick Darge]

This is all a little too foreign for me. Thank you for offering this solution, but can you point me in the direction of a good 'how to script' document for the laymen?

 

[Dylan Reeve]

Tcsh and find are dead giveaways for someone to lazy to learn bash or do it in python/perl

I usually use bash, but I found some trouble with some aspect of it...
I've not really perl'd in about 10 years...
And Python has never been my language - I fear whitespace sensitive languages...

 

[I Bloom]

Not to one up anybody. But this is a little bit of a different approach:

Richard,
Open this zip file, then drag the parent directory of all of your footage into this droplet.

http://www.reduser.net/forum/uploaded/582_1203920758.zip
If you are on windows, you need to run the python script from the command line. And god help you.

If it works, the folder called "References" will then contain lots of goodness.

I was thrown by python at first. But learned to love it back in my Blender days.

IBloom

 

[Dylan Reeve]

One up me will you!?!?

Good stuff, more user friendly I guess.

 

[I Bloom]

One up me will you!?!?

Good stuff, more user friendly I guess.

Not better...different.:innocent:

 

[Rick Darge]

IAN

YOU SIR, ARE A RED-GOD

Thank you so much, this will make my life a lot easier

 

[I Bloom]

IAN

YOU SIR, ARE A RED-GOD

Thank you so much, this will make my life a lot easier

Plenty of extra time on your hands now to go write an article on http://www.RedHax.net :devil:

 

[Rick Darge]

http://www.redhax.net/wiki/Footage_Conversion

 

[Kenn Michael]

Great script Ian, thanks!

So now (just getting into RedTrip for the first time) I have all my proxies in one folder, but when I use Compressor to convert the _H proxies into ProRes, using 'Source' as a destination puts the ProRes files in the _H.mov Reference folder instead of in the same folder with the .R3D files.

So now, if I cut with these Proxies that aren't in the same folder as the .R3D files, RedTrip won't be able to parse correctly to RedCine...

Is there another slick script to put these proxies in the right place? I was trying to think of a cool Automator script to do it, but I came up blank.

 

[I Bloom]

Great script Ian, thanks!

So now (just getting into RedTrip for the first time) I have all my proxies in one folder, but when I use Compressor to convert the _H proxies into ProRes, using 'Source' as a destination puts the ProRes files in the _H.mov Reference folder instead of in the same folder with the .R3D files.

So now, if I cut with these Proxies that aren't in the same folder as the .R3D files, RedTrip won't be able to parse correctly to RedCine...

Is there another slick script to put these proxies in the right place? I was trying to think of a cool Automator script to do it, but I came up blank.

Um... but... Richard said... fine Kenn. You're right we have a problem. (Stupid Compressor.) In fact, there is a solution, but you'll have to be patient.

http://www.redhax.net/wiki/Footage_Conversion

Welcome to Olympus. There's a chair here for you by the fire.

IBloom

 

[Kenn Michael]

Welcome to Olympus. There's a chair here for you by the fire.
IBloom

Cozy!

Appreciating all the great work you're doing to streamline the workflow. Thanks much and can't wait for the new mystery software.

 

[Dan]

That's a great little script Ian, big thanks from this side of the pond!