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

Mac Pro Workflow

Yes, that's right. Native apps like REDCINE can read the data files direct, but for convenience, the camera makes a Quicktime reference file so that any app can read the data as 1k, 2k or 4k. Works great.

Graeme

That presumably also helps get round the 2GB file size limit
 
There is sort of that in there at the moment, and we're in the process of refining it further.

Nice.

That presumably also helps get round the 2GB file size limit

One of the Apple guys was saying on Digital Production Buzz that FCP6 is also going to have a "Log & Transfer" mode (the tapeless equivalent of "Log & Capture"). When importing footage that way, FCP could presumably concatenate files. I don't know if it will, but that would be the ideal case. Having a QuickTime wrapper that hides from apps the fact that footage is spread across multiple files is nice, but actually not having the footage spread across multiple files is even better.

I'd assume Redcine would be able to concatenate while ingesting as well.
 
Actually FCP 5 has this as well, but it's only for P2 imports.
It will automatically append files spanning across multiple cards.

I believe the new "Log & Transfer" or RAD window is pretty much identical to the P2 import window, but it now imports more filetypes and gives the ability to transcode as well..
 
Got a screenshot of it in FCP 6:
import.jpg
 
Yup, the 1k quicktime movie is a couple of k in size, and just points to the 4k data file and tells quicktime to decode it as 1k rather than 4k.

Graeme

Graeme, so would one be able to successfully use REDCINE out in the field with a MacBook Pro?
 
I use REDCINE on a macbook pro and it works great.

Graeme
 
Yes, that's right. Native apps like REDCINE can read the data files direct, but for convenience, the camera makes a Quicktime reference file so that any app can read the data as 1k, 2k or 4k. Works great.

Graeme

I think I already know the answer to this, but since you're here...

I assume Scratch is what you would consider a "native" app, and also reads the Red data files directly, a la Redcine - bypassing the Quicktime approach. Is that correct? Either now or in the future ;-) ?
 
Native apps like REDCINE can read the data files direct, but for convenience, the camera makes a Quicktime reference file so that any app can read the data as 1k, 2k or 4k. Works great.

Graeme

I heard that the native files have the file extension .jim!
Is that correct? Nice touch, in any case. :biggrin:
 
No, native files are not .jim. That was just a little joke between friends.....

Yup, REDCINE handles the files natively.

I'd hope Apple don't change the name of Color to Colour in other countries or I'll have to write a seperate installer.....

Graeme
 
hi everyone
its mac pro intel dualcore enough for editing 4K ? and disk storage space?
 
LDJ films check out the first page of this thread

LDJ films check out the first page of this thread

lddj films, check out the first page of this thread...



I cut 'Crossing the Line' on a dual dual-core Mac Pro with FCP5, using native 4K redcode files in 1k proxy mode. It never dropped a frame.

Also my Assistant Editor was working with the native 4k files in FCP on a MacBook Pro (Core 2 Duo). That too worked fine.

cheers

-Jabez Olssen
 
Hey Graeme -

So, you got 1T of 4K Redcode RAW media on your raid - you cut inside FCP using the 1K extraction QT's in realtime - what happens when you hit MEDIA MANAGE ...?
 
Back
Top