Adobe and QT timecode

[Stacey Spears]

In the AVID section there is a lot of discussion around the fact that AVID currently does not support the timecode embedded in a QT file.

Does Adobe have this limitation?

[Kevin Halverson]

Premiere appears to handle this without a hitch.

[Graeme Nattress]

I brought a R3D wrapped as Quicktime into Premiere Pro on my mac, and it did display the same timecode that RedAlert! was displaying for that clip.

Graeme

[Stacey Spears]

Thank you, Graeme.

[Kevin Halverson]

Now, as soon as RedCine and the Windows codec gets released, we can test to see if the same is true on the Windows side. I suspect that it will be.

[Antoine Baumann]

fantastic Graeme, tell us more, how does it play back? at what resolution? What kind of hdd system do you have? Graphic card?

thanks a lot for the precious informations.

antoine.

[Graeme Nattress]

Didn't really test for playback speed - was more interested in the timecode. I'll get a final (for now) of the codec and see how it works later on though.

Graeme

[number6]

Seeing that Graeme is monitoring this thread, I have a hypothetical. I've just ordered (price was too good to wait for Nehalem or even PCIe 2.0) a dual-quad core (8 totoal) Xeon. Have also ordered OEM Windows Vista Ultimate 64 bit operating system.

Hope to have my first RED by late Spring '08 and plan to shoot a short with it. My question is, will REDCINE be compatible with my Adobe PP3 and AE3 workflow on Windows Vista by then?

[Kevin Halverson]

My question is, will REDCINE be compatible with my Adobe PP3 and AE3 workflow on Windows Vista by then?

No one can be certain, but the latest word is that RedCine on Windows has a planned release by the end of November.

Fingers crossed!

[number6]

No one can be certain, but the latest word is that RedCine on Windows has a planned release by the end of November.

Fingers crossed!

Am wondering if that will just be with Windows XP or if Vista will also work? Haven't heard much from them on the Vista front:construction: :ohmy:

Fingers crossed that there will be no double-cross

[MikeHedge]

well WinXP is gonna be gone by Dec 2008 as far as I know. so I hope when they say RedCine will be OSX and PC, I hope they mean Vista....

I'm sorta waiting to build a new system....

[Mike McCarthy]

well WinXP is gonna be gone by Dec 2008 as far as I know. so I hope when they say RedCine will be OSX and PC, I hope they mean Vista....

I'm sorta waiting to build a new system....

I wouldn't bet on "gone" in that time frame. XP still has many advantages over Vista, but support for Vista will increase, and support for XP will decrease, and eventually everyone will find it beneficial to make the jump, some waiting longer than others. I will be one of the later ones this time, and I have plans to be installing XP past Dec 2008, even if I have to stock up on extra licenses before they stop sales in June 2008. The performance disadvantages of Vista are too great right now for me to consider it for anything but experimentation.

On the otherhand, most people will be on Vista by then, so I expect RedCine will work on Vista in the not too distant future.

[Steve Freebairn]

Didn't really test for playback speed - was more interested in the timecode. I'll get a final (for now) of the codec and see how it works later on though.

Graeme

Any results on this Graeme?

[Graeme Nattress]

Been helping with some RedCine things, so haven't had a chance! Sorry.

Graeme

[indivfx]

I brought a R3D wrapped as Quicktime into Premiere Pro on my mac, and it did display the same timecode that RedAlert! was displaying for that clip.

Graeme

Graeme,

Sorry to steal the thread. But I have a Mac g5 PowerPC with Final cut studio 2 how can i import redfootage and start editing. Recently i'm thinking of buying a laptop the DELL XPS seems cheaper than MAC BOOK pro.

thank you

[Graeme Nattress]

You need an intel mac or a PC. Check out what GPU the Dell has though to make sure it runs with Redcine.

Graeme

[Rob Lohman]

For a Windows machine (like that DELL) you want to get a decent NVidia card. We also haven't yet fully certified REDCINE for Vista yet, so stick with XP SP2 32-bit if you want to be safe.

[galexander]

http://www.microsoft.com/windows/lifecycle/default.mspx

Vista - like a big bloated upgrade for XP, i would not recommend this to anyone under any cirumstances until Vista SP2.

XP x64-really good and fast, but codec support and getting 32-bit hardware drivers working is a spotty. if you buy XP x64 buy from a manufacturer and get an extended warrantee/support, at least the stock drivers will work "most" of the time.

Svr 2k3-is the "best" M$ OS IMHO. stable, patches that work, but not cheap.

Windows XP Professional EOL January 31, 2009
Windows XP Tablet PC Edition EOL January 31, 2009
Windows XP Professional x64 EOL January 31, 2009
Windows XP Home Edition EOL January 31, 2009
Windows XP Media Center Edition2 EOL January 31, 2009
Windows 2000 Server EOL 7/13/2010

M$ will also support the last SP for 2 years for WinDoZe.

[Rob Lohman]

I just can't take any of your advice seriously when you're saying "M$" or "WinDoZe"..... I thought that sort of thing had passed by now?

I'm extremely happy with my Vista Media Center for example. They used to say the same thing about XP when it came out, that it was bloated and slow. New stuff always needs to find its sweet spot. Give it time.

[galexander]

I just can't take any of your advice seriously when you're saying "M$" or "WinDoZe"..... I thought that sort of thing had passed by now?

I'm extremely happy with my Vista Media Center for example. They used to say the same thing about XP when it came out, that it was bloated and slow. New stuff always needs to find its sweet spot. Give it time.

Frankly, i don't care what advice you take seriously or not. I have no emotional stake in your reply.

In the context of this thread, if you think Vista Media Center is an OS applicable for a 4k processing workflow. I suggest you have no clue about OSes at all.

XP WAS bloated when it came out, the company i was with then wasn't about to waste time until SP2.

You have not addressed anythng meaningful in your reply. You quote an entirely laughable OS for a 4k workflow and just wrote personal attacks and biases, so perhaps YOU NEeD tO FiND A MOrE meAniNGFul ExistEncE if YOUR cOnceRN iS Of My TyPing STYlE. If you can't keep to the thread, maybe you should not be posting. IMHO.

[Mark L. Pederson]

lets play nice and not make it personal.

[Deanan]

You quote an entirely laughable OS for a 4k

Rob was not suggesting mediacenter for a workflow if you reread his post.

[Rob Lohman]

In the context of this thread, if you think Vista Media Center is an OS applicable for a 4k processing workflow. I suggest you have no clue about OSes at all.

I wasn't suggesting that at all. However, you do know Media Center is basically just an application & service on top of the base Operating System, right?

So what you are saying is Vista isn't applicable? Do you not want us to support it (in the near future)?

Out of curiosity, what is your profession?

[galexander]

I wasn't suggesting that at all. However, you do know Media Center is basically just an application & service on top of the base Operating System, right?

So what you are saying is Vista isn't applicable? Do you not want us to support it (in the near future)?

Out of curiosity, what is your profession?

kernel scheduling, time slicing, and memory fragmentation in ANY version of winDoze in an unholy nightmare. media center is another bloated gui layer sucking down more system resources just to make things look pretty for the average consumer who wants to use a remote control and a wireless keyboard to play dvd's.

the lower, cheap, flavors of vista wouldn't be applicable at all, you have to throw a ton of graphical computing horsepower at 4k frames. so if you reccommend those crappy versions of vista, you are basically forcing anyone who wants to use 4k to dramatically increase the cost in hardware unnecessarily. you couldn't pay to use vista in its current state.

xp has been basically stable since sp2, when xp x64 gets another year of driver 'upgrades' and sp3, that would be the preferable system. anyone who uses an OS in a production environment, locks the OS down tight, no upgrades, no tweaks unless something fails. once the system is running, you don't screw with it.

my previous and current, paid occupations, SGI/BSD/Solaris/Linux kernel hacker, radar design and tracking, developed hardware/software of real-time multi- and hyperspectral CCD sensors. currently i design and build phased arrays and write brutually fast number crunching code in f77 and matlab. the current GPUs are excellent for FDTD, they are massive amount of parallel pies. so i'm here because i'm starting now to make independent films and interested in the Red solution but i'm not convinced the work flow is ready for prime time. i would rather just have specs of the data port and i'll write my own driver and aquisition routines being forced into quicktime solution is not to my liking.

[Stacey Spears]

All of the UI in Vista can be turned off, so you don't need to throw of ton of anything at it. MCE can also be fully disabled. By default, none of its services are running under Vista. The first time you launch it, it will enable the PVR service. Again, easy to shut down.

It bugs me to see people recommend XP 64-bit. I would avoid it and wait for Vista driver support to catch up as XP 64-bit driver support is never gonna get there. Server 2003 is a bit better in that regard, but most vendors (e.g. nVidia) are focused 99% on Vista. Be that good or bad.

Rob, which compiler are you using for REDCINE on Windows? I am just curious how much trouble it is to offer a 64-bit version. I suppose if you have a bunch of hand written MMX/SSEn code, its a problem.


Red solution but i'm not convinced the work flow is ready for prime time.

I would say it is currently in its infancy. I imagine a year from now, things will be a lot better.


So what you are saying is Vista isn't applicable? Do you not want us to support it (in the near future)?

Given my new HW, Vista is really my only option, so I hope you support it sooner rather than later. (e.g. by this summer)

[Steven Caesare]

kernel scheduling, time slicing, and memory fragmentation in ANY version of winDoze in an unholy nightmare. media center is another bloated gui layer sucking down more system resources just to make things look pretty for the average consumer who wants to use a remote control and a wireless keyboard to play dvd's.

the lower, cheap, flavors of vista wouldn't be applicable at all, you have to throw a ton of graphical computing horsepower at 4k frames. so if you reccommend those crappy versions of vista, you are basically forcing anyone who wants to use 4k to dramatically increase the cost in hardware unnecessarily. you couldn't pay to use vista in its current state.

xp has been basically stable since sp2, when xp x64 gets another year of driver 'upgrades' and sp3, that would be the preferable system. anyone who uses an OS in a production environment, locks the OS down tight, no upgrades, no tweaks unless something fails. once the system is running, you don't screw with it.

my previous and current, paid occupations, SGI/BSD/Solaris/Linux kernel hacker, radar design and tracking, developed hardware/software of real-time multi- and hyperspectral CCD sensors. currently i design and build phased arrays and write brutually fast number crunching code in f77 and matlab. the current GPUs are excellent for FDTD, they are massive amount of parallel pies. so i'm here because i'm starting now to make independent films and interested in the Red solution but i'm not convinced the work flow is ready for prime time. i would rather just have specs of the data port and i'll write my own driver and aquisition routines being forced into quicktime solution is not to my liking.

Let's discuss thread scheduling (which encompasses your somewhat ambiguous term of "time slicing") and "memory frgmentation" in the NT/XP/Vista kernels.

We can start on what you think "memory frgmentation" in virtual memory model with flat address space means. Feel free to include discusssions of on demand paging in a VMM environment and/or kernel non-paged pools if you so desire.

Proceed.

[Gavin Greenwalt]

Speaking as a 3 year veteran XPx64 user I would wave people towards Vista x64. That seems to be where all the development focus for drivers and software is going.

Windows XP x64 was a nice stop gap (and I assume development platform) but it's been mostly neglected by the third parties. (even windows desktop search can't search network drives on XP x64) I'm considering upgrading for that alone.

galexander I would direct you towards the fine folks at Autodesk and ask them how they tolerate using windows for their flagship 4k grading application. http://images.autodesk.com/adsk/files/lustre_2008_brochure_high_resolution_for_print.pdf

[Steve Freebairn]

Vista Support Is A Must! I Use Both Os's And There Are Advantages To Both, But Ignoring One Won't Help.

[galexander]

Speaking as a 3 year veteran XPx64 user I would wave people towards Vista x64. That seems to be where all the development focus for drivers and software is going.

Windows XP x64 was a nice stop gap (and I assume development platform) but it's been mostly neglected by the third parties. (even windows desktop search can't search network drives on XP x64) I'm considering upgrading for that alone.

galexander I would direct you towards the fine folks at Autodesk and ask them how they tolerate using windows for their flagship 4k grading application. http://images.autodesk.com/adsk/files/lustre_2008_brochure_high_resolution_for_print.pdf

ha ha, i don't know how anyone tolerates windoze, but it is the 2000lb gorilla which has a lot of application written for it. my preference is for QNX but you'll be on your doing lots of development work instead of using the application.

XP x64, agree, the driver support just isn't there, but in all of the flavors of Vista i played around with x32, "Ultra" (laughable), it took hours just to strip all of the bloat crap off and get the power user feel again with have to hack through the registry to turn something off, something else one.

i'd suggest if you want good stable system that support large ram, killer networking, streaming, get Server 2k3.

[galexander]

Let's discuss thread scheduling (which encompasses your somewhat ambiguous term of "time slicing") and "memory frgmentation" in the NT/XP/Vista kernels.

We can start on what you think "memory frgmentation" in virtual memory model with flat address space means. Feel free to include discusssions of on demand paging in a VMM environment and/or kernel non-paged pools if you so desire.

Proceed.

hmm, what's ambiguous about time slicing? fairly common term. cpus spend certain amount of cycles performing operations, to get anything close to an RTOS, as a programmer to you need to have a fairly deterministic kernel. deterministic=when you can expect a result back from the kernel processing within XX ns. the variability of expectation from the windows clock/timer resolution without real-time extensions or an atomic 'watchdog', is a veritable infinity.

memory fragmentation, when the address space is non-contiguous therefore limiting the amount of processing you can do any one chuck of memory at any time. even linux has a much better malloc. try it run IDL, Matlab, your fav app and try to process a big monster file, under doze if you get more than a 1.5 Gb useable i'd be highly surprised, as windoze splatters the memory space like a garden hose with many leaks. unless the CPU supports vector processing like Altivec and can do a lot of inlining, your processing is slowing to a crawl.

[Jay A. Kelley]

Frankly, i don't care what advice you take seriously or not. I have no emotional stake in your reply.

In the context of this thread, if you think Vista Media Center is an OS applicable for a 4k processing workflow. I suggest you have no clue about OSes at all.

XP WAS bloated when it came out, the company i was with then wasn't about to waste time until SP2.

You have not addressed anythng meaningful in your reply. You quote an entirely laughable OS for a 4k workflow and just wrote personal attacks and biases, so perhaps YOU NEeD tO FiND A MOrE meAniNGFul ExistEncE if YOUR cOnceRN iS Of My TyPing STYlE. If you can't keep to the thread, maybe you should not be posting. IMHO.

Chaos,

As one of your bigger fans, let me say this: No matter how right you are, if you piss people off, you will be ignored, and then gone.

You're a very smart guy, which is not that remarkable. But if you can be a smart guy, AND nice, then you will truely impress everyone.

Rob, Graeme, and the guys are a fine bunch of people, give them the benefit of the doubt and for God's sake.. Be NICE!

Getting into any type of fight on the internet is nothing short of a joke, we're all hiding behind little computers, how tough can we be?! :)

I love having you on here, but please, be nice.

Jay

[Mark L. Pederson]

Chaos,

As one of your bigger fans, let me say this: No matter how right you are, if you piss people off, you will be ignored, and then gone.

You're a very smart guy, which is not that remarkable. But if you can be a smart guy, AND nice, then you will truely impress everyone.

Rob, Graeme, and the guys are a fine bunch of people, give them the benefit of the doubt and for God's sake.. Be NICE!

Getting into any type of fight on the internet is nothing short of a joke, we're all hiding behind little computers, how tough can we be?! :)

I love having you on here, but please, be nice.

Jay

Nice post Jay.

I'd hate see Chaos go -and I also agree, he should take it down a notch.

A little respect goes a long way in the world of RED.

It's great to state opinions and share expertise - that's what a forum is for.

It is not a contest.

[galexander]

Nice post Jay.

I'd hate see Chaos go -and I also agree, he should take it down a notch.

A little respect goes a long way in the world of RED.

It's great to state opinions and share expertise - that's what a forum is for.

It is not a contest.

This is great, if i get banned from so be it. I'm not going to change, I love life, love being out on the edge, life is to explore these great adventures. If this adventures end, another great one will begin. :) I will have enjoyed greatly the posts and being able to help people just because I could but I'm not going to hold on to anything or anyone. It is the schadenfreude.

Banning me only shows reflections of the economics and ego who control this site. I'm not controlable ;-) I don't ask for nor would I accept any money, compensation, or acknowledgment. It is enough just to say "thanks" or "good on ya mate" and maybe next time you will help out the next person. I have to no ego to massage, coffers to fill. I truly enjoy what I do and how I live, every moment of every day, anything less would be a life not worth lived IMHO. I live full-on, sort of a force of nature, enjoy while you can.... because you can. :)

If there is talk of banning, I'll end this account now, if anyone has any more real problems, head over to the Doom9 forum, post something in the heading like

Chaos:: Redcine codec bombing out again or QT still doesn't work.

http://forum.doom9.org

[Steven Caesare]

It's ambiguous in the context you used it as something to which you said it was a nightmare, and specified it separately from "kernel scheduling". What do you believe is at issue with the NT scheduler? NT (nor most general purpose OS's) was never claimed to have deterministic characteristics so why are you bringing that up here?

Unfortunately you seem to be a bit confused about memory fragmentation in a Virtual Mapped Memory (VMM) OS. Address space allocated to the user-space process is ALWAYS flat address space (ignoring AWE extensions for the moment). CPU hardware translation is used to map virtual pages to physical addresses. This memory access has the SAME performance cost regardless of where the physical page resides. The cost to retrieve an NT page frame from the in-memory database and translate it is identical for the hardware, regardless if the physical pages are adjacent or not.

Performance penalties are of course incurred if the pages must be retrieved from the backing file (aka page file) on disc, but this penalty is a separate from your claimed "memory fragmentation", which doesn't exists as an issue.

How much memory is "usable" (as per your example), is purely a function of the combined memory footprint of processes running, and what you are attempting to do within your OS. It is such a separate issue from VMM behavior I have no idea why you bring it up. Unless these apps require physical memory to be contiguous (as opposed to "available"), in which case the app is likely broken.

I won't touch vector processing... you are already mixing up too many concepts.


hmm, what's ambiguous about time slicing? fairly common term. cpus spend certain amount of cycles performing operations, to get anything close to an RTOS, as a programmer to you need to have a fairly deterministic kernel. deterministic=when you can expect a result back from the kernel processing within XX ns. the variability of expectation from the windows clock/timer resolution without real-time extensions or an atomic 'watchdog', is a veritable infinity.

memory fragmentation, when the address space is non-contiguous therefore limiting the amount of processing you can do any one chuck of memory at any time. even linux has a much better malloc. try it run IDL, Matlab, your fav app and try to process a big monster file, under doze if you get more than a 1.5 Gb useable i'd be highly surprised, as windoze splatters the memory space like a garden hose with many leaks. unless the CPU supports vector processing like Altivec and can do a lot of inlining, your processing is slowing to a crawl.

[Mark L. Pederson]

I think this thread is .... Adobe and QT timecode ..?

[galexander]

It's ambiguous in the context you used it as something to which you said it was a nightmare, and specified it separately from "kernel scheduling". What do you believe is at issue with the NT scheduler? NT (nor most general purpose OS's) was never claimed to have deterministic characteristics so why are you bringing that up here?

Unfortunately you seem to be a bit confused about memory fragmentation in a Virtual Mapped Memory (VMM) OS. Address space allocated to the user-space process is ALWAYS flat address space (ignoring AWE extensions for the moment). CPU hardware translation is used to map virtual pages to physical addresses. This memory access has the SAME performance cost regardless of where the physical page resides. The cost to retrieve an NT page frame from the in-memory database and translate it is identical for the hardware, regardless if the physical pages are adjacent or not.

Performance penalties are of course incurred if the pages must be retrieved from the backing file (aka page file) on disc, but this penalty is a separate from your claimed "memory fragmentation", which doesn't exists as an issue.

How much memory is "usable" (as per your example), is purely a function of the combined memory footprint of processes running, and what you are attempting to do within your OS. It is such a separate issue from VMM behavior I have no idea why you bring it up. Unless these apps require physical memory to be contiguous (as opposed to "available"), in which case the app is likely broken.

I won't touch vector processing... you are already mixing up too many concepts.


sorry but the only truly flat address space is with an OS like QNX, maybe you are confused. all applications in a real flat memory space can 'see' the memory of everything else, so each process can be killed and restarted without interrupting the kernel. the windows address space is not 'flat' at all. hence the confusion about what you were asking and why i didn't it serious and just some games you are playing.

i don't think you have any idea of what the timer resolution of the NT kernel is and how it affects the 'real' world to be honest.

when you need to debug a kernel or user mode driver because something bombed and your crappy hardware driver or program leaks are spraying the memory space everyone, try and track that one down with you VMM talk.
then tell me how your VMM is going to get your system up and running when the base commander with a full bird is looking at you and wondering what is delaying the range exercise.

if you have an 'real' issue or current problem, i'm happy to help you try and sort out but this seems like just a mental pissing contest and i have no interest whatsoever to be honest.

i knew that you were asking loaded questions, i choose not to participate. i can, will, and have gone mono-et-mono with PhD eggheads from MIT LL, don't think you BS me. my concepts are from practical experience of real-time debugging of kernels/user modes drivers and hacking them to get them to run, not some abstract book. :)

[Steve Freebairn]

Yeah, you guys are smarter than a lot of us, but like Offhollywood was hinting at, we'd love a QT solution for Adobe. I'm sure there are issues with the way windows does things, but I'm sure Rob and the rest of the Red team will figure it out. There are lots of us that want you to figure it out. Even if a company only uses Macs, there are going to be times where someone else needs it to feed into their Avid or for it to be loaded in Premiere.

[Steven Caesare]

Yeah, you guys are smarter than a lot of us, but like Offhollywood was hinting at, we'd love a QT solution for Adobe. I'm sure there are issues with the way windows does things, but I'm sure Rob and the rest of the Red team will figure it out. There are lots of us that want you to figure it out. Even if a company only uses Macs, there are going to be times where someone else needs it to feed into their Avid or for it to be loaded in Premiere.

Indeed. And galaxender's comments innaccurate comments regarding NT have no bearing on that. So back to the subject at hand.

[Mark L. Pederson]

let's play nice here - last warning - no intellectual pissing contests ... please!

[A. Bastaki]

I brought a R3D wrapped as Quicktime into Premiere Pro on my mac, and it did display the same timecode that RedAlert! was displaying for that clip.

Graeme

Graeme... does that mean i could wrap my redcode raw footage as a quicktime file... not lose the 10-bit quality?

if that is true... how did you do it?
________
Suzuki Fronte History (http://www.suzuki-tech.com/wiki/Suzuki_Fronte)

[A. Bastaki]

oh and btw... im using redcine on windows 64-bit.. i cant seem to export dpx files.
________
VOLCANO CLASSIC REVIEW (http://vaporizer.org/reviews/volcano)

[Graeme Nattress]

Quicktime supports up to 32bit float for some applications. If you ask Quicktime for 8bit, that's what you get, or 16bit, that's what you get or 32float, you get it. If the codec data supports that bit depth, you get an increase in quality.

Graeme

[Dave Neathery]

For what it's worth, I tried the following things last weekend:
I built a new computer (PC) using an Intel extreme 2 motherboard, Q6600 quad core, Nvidia GeForce 8800 GTX (768MB) (over clocked), 2 GB RAM, 2TB raid 0 array, and a 500 GB ide drive for boot drive.
I installed XP pro (32 bit). I discovered that Redcine worked correctly as far as I could tell. (It didn't on the previous 8 computers I tried.) Render speeds varied based on output format selected. (Always used minimum display setting). (Fastest was about 1 frame per second.)
I did not load any additional software except Quicktime and Redcine.
I then loaded XP pro 64 bit version, (still with 2 Gig ram installed).
Not surprisingly, Redcine render times decreased somewhat.
Outputting tiff files ran at about 7 seconds per frame.
I added an additional 2 Gog of ram. No change in performance.
Then I installed Premier Pro cs3, and Cineform's 4K evaluation version.
I could not create a Quicktime file with the Cineform settings. I conculded that maybe Cineform does not work with 64 bit version.
I removed the extra 2 Gig of memory and reinstalled Xp pro 32 bit. (Reformatting the boot drive and starting over.)
I found that Cineform then worked, and created a Quicktime file that I could play, but the render time was still about 7 fps. Even though I had never actually used the evaluation copy of PP CS3 and had reformatted the disk, (not quick format either), it would not let me run the program, so I did not get to test whether or not editing would work. I have the full set of CS2 programs on another machine (dual zeon with 320 ultra SCSI), but I did not load Cineform there because I wanted to test green screen performance, and their new feature is only available in CS3 and also only on the PC version.

I purchased my 2 reds for doing a series that will have 24 1 hour segments. Each session will have about 2 hours of raw footage.
Even if Cineform works wonderfully, I does me very little good as I would have to wait weeks before being able to even start post production. So I will just have to wait for the codec for Adobe so that I can begin as soon as the files are downloaded to the machine.
Since the entire series will be chroma keyed, I cannot use an apple even if I were willing to.
I am not complaining, I just hope some of the information here will be useful.

Just so that there is no misunderstanding, I do not have either of my cameras yet, I got the footage from someone who did. I don't want to start a rumor that they have shipped higher numbers than they have.
Even though, I won't be able to do anything with it, (for a while), I'm looking forward to getting my Red One and the day when the codec is released so that I can start.

[A. Bastaki]

so how do you like wrap it. is it like export from redcine .mov? and what codec would i use to keep the 10-bit-ness of the footage and the file size down to redcode @ 27mb/s

can quicktime wrap redcode codec? is redcine or redalert able to do that? because if that's there... and the conversion times arent that big... the image quality intact.. then.. i mean that's like a loophole.. we can work around that in premiere or avid...

the next question would be... would after effects be able to read the .mov file and be able to save the same file with the same compression afterwards with the same quality integrity (aside from color correction grain and all the other stuff).

we can still atleast do a proxy for the editing... it aint a big deal. plus redcine is smokin' fast when it comes to downconverting stuff to hd on my machine.
________
Mazda Axela Picture (http://www.ford-wiki.com/wiki/Mazda_Axela)

[Antoine Baumann]

I purchased my 2 reds for doing a series that will have 24 1 hour segments. Each session will have about 2 hours of raw footage.
Even if Cineform works wonderfully, I does me very little good as I would have to wait weeks before being able to even start post production.

Do some tests, and find out how long would 48 hours of REDCODE RAW takes to be render out to CINEFORM. Consider that "standard" quality demosaic might be enough and test different shots, as my tests shows difference in rendering time from shots to shots with the same settings in REDCINE.
Also consider you can start rendering as soon as the files are on your pc, meaning on set.


antoine.

[Dave Neathery]

Do some tests, and find out how long would 48 hours of REDCODE RAW takes to be render out to CINEFORM. Consider that "standard" quality demosaic might be enough and test different shots, as my tests shows difference in rendering time from shots to shots with the same settings in REDCINE.
Also consider you can start rendering as soon as the files are on your pc, meaning on set.


antoine.

I did test the speed of Redcine with a number of different files. But I never dropped to "standard" quality. Based on the rates I've gotten so far each recording session will be followed by 160 hours of rendering in Redcine before editing can begin. (You have to have the files from both cameras before you can start editing.)
I am hoping that they will come up with a workflow for PC Adobe like they did for FCP so that editing can start as soon as file copying finishes.
(I will be working strictly from Red drives, I didn't even include the CF option in my order. Having to stop every 4 minutes or so would be untenable.)

Dave