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

The killer RedRushes feature I want ...

Transcoded quicktimes

Since FCP is doing the transcoding, they write the quicktimes differently than the manual way we do it. There are a bunch of different libraries and methods to write quicktims ( a royal headache ) and no proper documentation and lots of undocumented stuff. We'll see if we can find out what they're doing in FCP to match it.
 
Since FCP is doing the transcoding, they write the quicktimes differently than the manual way we do it. There are a bunch of different libraries and methods to write quicktims ( a royal headache ) and no proper documentation and lots of undocumented stuff. We'll see if we can find out what they're doing in FCP to match it.

Thanks Deanan,

I'll have a crack at it once I get the updated Red SDK.

Ziggx
 
I like where this thread is going...

Here are a few suggestions I posted in another thread 1 month ago :

- Support for drag and drop. Drag a folder or a shot into Redrushes instead of having to go through the "open" process.
Same for RedAlert, just drag your R3D (or the folder containing it) into RA and it opens the shot.

- Make the "delete" key have the same action as clicking the "Remove clip" button. Allow for multiple selections.

- When you double click on a shot in RedRushes, could it open this shot automatically in RA ?
And if you hold down the CTRL key while double clicking, it would open the QT proxy (set a preference to determine which proxy size it opens)

- Display some of the metadata in the tabs near the file names. Like resolution (4K / 3K / 2K), Aspect Ratio (16/9 / 2:1 / ANA), if an RSX file has been created for this shot (Yes / No), Length, I/O points, Framerate,...

- A load / save function to quickly set your own render presets (for example a high quality option with HD output, an offline option, etc...)

- Also a Save option for the current project / batch list, if you need to stop and restart later, or in case the app crashes (Autosave would be usefull too then. Maybe save the project automatically each time a shot has been rendered).

Thanks,
Nils.
 
- Support for drag and drop. Drag a folder or a shot into Redrushes instead of having to go through the "open" process.

- ... Allow for multiple selections.

These two functions should be a basic feature of any program.

I was really surprised when I discovered Redrushes would neither open a clip that was double-clicked in the GUI nor accept a dropped file.

I know it's beta so I'm sure it will follow common GUI conventions soon.
 
I like where this thread is going...

Here are a few suggestions I posted in another thread 1 month ago :

- Support for drag and drop. Drag a folder or a shot into Redrushes instead of having to go through the "open" process.
Same for RedAlert, just drag your R3D (or the folder containing it) into RA and it opens the shot.

- Make the "delete" key have the same action as clicking the "Remove clip" button. Allow for multiple selections.

- When you double click on a shot in RedRushes, could it open this shot automatically in RA ?
And if you hold down the CTRL key while double clicking, it would open the QT proxy (set a preference to determine which proxy size it opens)

- Display some of the metadata in the tabs near the file names. Like resolution (4K / 3K / 2K), Aspect Ratio (16/9 / 2:1 / ANA), if an RSX file has been created for this shot (Yes / No), Length, I/O points, Framerate,...

- A load / save function to quickly set your own render presets (for example a high quality option with HD output, an offline option, etc...)

- Also a Save option for the current project / batch list, if you need to stop and restart later, or in case the app crashes (Autosave would be usefull too then. Maybe save the project automatically each time a shot has been rendered).

Thanks,
Nils.

Like so ?
Next week.

Cheers
Hans
 
There's an interface quirk, I've been meaning to ask about in RedRushes. If I want to reset a clip I have to physically click on that clip in the queue before clicking on the reset button. Why is that? If I arrow up or down to highlight it, it won't let me reset, I have to physically click on it.
 
Back
Top