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

What to do while waiting for RedCines release

I had the chance to sit with the latest beta build on Thursday (9-27). Is the release version going to be any different in terms of the UI? Any other updates that can be shared?

No major UI changes are planned for the moment. Quality and making sure things are stable and work as they should is our main goal at the moment, closely followed by performance enhancements and new features / tools.
 
I actually thought that the UI was absolutely fine in the version that I saw. Other than aesthetic changes that might be desired, the UI was intuitive and quick to manage. Will the new features include abilities to handle audio extraction (tied to edge code)? I am really looking forward to working with the application, for a beta, it looked pretty mature to me. Great work!

Any ETA estimates?
 
What is the latest on RED Cine?

What is the latest on RED Cine?

Is there any new information about RED CINE?
 
What do you want to know? Work is progressing on it...
 
Hi Rob,

My only real questions are:

What are the audio extraction capabilities in terms of supported file formats and how
is related to time code (edge)

&

ETA

Thanks,

Kevin
 
so do i assume that out of 100 camera's delivered all are Mac'ers or ended up going to Mac's ???
seems there's got to be some PC'ers in there ??

anything working for a PC without going thru a Mac ??
 
donatello: redcine will be out very soon

kevin: the camera is not recording audio yet, so no post tools do either. I'm not sure about your timecode question. Can you elaborate?
 
anything working for a PC without going thru a Mac ??

The rumors I heard were that it was all PC and not too much Mac as of a couple weeks ago... so I wouldn't worry about RedCine on a PC. Maybe Rob will clarify if both OSX and XP will release at the same time.
 
donatello: redcine will be out very soon

Sweet- can we get a sticky on this board when it's out? Sometimes the Red emails get lost...

-Noah
 
Red Cine one month away

Red Cine one month away

Red Cine is said to be a month away now...
 
kevin: the camera is not recording audio yet, so no post tools do either. I'm not sure about your timecode question. Can you elaborate?

Hi Rob,

Sorry that I didn't respond until today, somehow I missed your follow up question and didn't notice it until now.

I understand that the in camera audio is not enabled, but I was assuming that there was a parallel development for the post tools side, but perhaps my questions are premature. On the chance that they are not, let me elaborate a bit.

Are the audio files standalone or interleaved within the .r3d files?
If standalone, what data structure is used?
If embedded within the .r3d files, what extraction tools will be provided?
If embedded, how is volume spanning accomplished?
Will meta data include entries for audio and if so, what information will archived?

And for the big question...

any new ETA for RedCine?

Thanks!

Kevin
 
1) interleaved inside the R3D files

2) tools are to be decided, but it makes sense to support writing out to the common audio formats including BWF

3) can you elaborate on volume spanning?

4) yes to audio metadata, but at the moment it's things like number of channels, bit depth, khz, gain setting etc. Are you thinking of some specific metadata?
 
It might be useful to have audio metadata which let you label each channel, so you could identify which channel was used for which mic in a complex multi mic setup.
 
1) interleaved inside the R3D files

2) tools are to be decided, but it makes sense to support writing out to the common audio formats including BWF

3) can you elaborate on volume spanning?

4) yes to audio metadata, but at the moment it's things like number of channels, bit depth, khz, gain setting etc. Are you thinking of some specific metadata?

Thanks for the follow up Rob.

Let me expand upon several of these.

Audio formats. I would suggest that the best approach is the simplest and that would be .wav and/or .aif. These are simply headers appended to the raw PCM data and they adequately describe the audio content with an extremely small amount of overhead (44 or 54 bytes in the minimum expression). Between these two data types, beyond the header the only difference is the byte order for each sample block.

Volume Spanning. Since you have confirmed that the data is interleaved inside of the .r3d files, then the fact that a take could exceed a single file's capacity and 'span' across several files will have to be addressed with the tools that Red provides.

Metadata. The list you have is a great starting point.

Another point, one that really bugs me is the use of "kHz" when describing audio sample rates. A better term is kS/s or 'kilo samples/second'. Describing the sample rate as a frequency, though nearly universal across many consumer products, is not ideal.

I have a large number of additional questions, but will save them until we can see what has already been addressed when audio gets enabled and the tools are released.

Kevin
 
I hate to bump my own thread, but...

BUMP.

Hey Rob, any update on RedCine's release?
 
yes, it's just been released
 
Back
Top