Atom Feed
RSS Feed
Buy Mike Recommended
edit systems & gear
from Silverado Systems
Buy Books, Software, & More
at HD for Indies Amazon Store
Buy New Movies from
HD for Indies Amazon Store
Or, you can also support
HD4NDs by contributing
to the tip jar...
Help Support HD for Indies
RSS Feed
Buy Mike Recommended
edit systems & gear
from Silverado Systems
Buy Books, Software, & More
at HD for Indies Amazon Store
Buy New Movies from
HD for Indies Amazon Store
Or, you can also support
HD4NDs by contributing
to the tip jar...
Help Support HD for Indies
Advertisements
Great HD Links
- HD For Indies Home Page
- HD For Indies FAQ
- HD 24
- Cinematography
- Bare Feats
- 24p Entertainment
- Light Illusion (was Digital Praxis)
- OneRiver Codec Resource
- CamcorderInfo.com
- LumiereHD
- HighDef.org Info
- Understanding RAID
- Video Systems (Reviews)
- DV Film (DV=>Film)
- SonyHDVInfo.com
- Plus 8 Digital (vendor)
- Digital Cinema Society
- Texas High Def (local F900 guy)
- Creative Cow (news & forums)
- Philadelphia FCP User Group
- Los Angeles FCP User Group
- Cinema Tech
- FresHDV
- DV Info's forums
- HVX User
- Pro App Tips
- Bluesky Media - Instruction
- RedUser.net
- fxguide
- little frog in high def
- VideoMaker Learning Section
- Stu Maschwitz's ProLost
Archives
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- November 2008
- December 2008
- January 2009
- March 2009
High Definition Video for Independent Filmmakers
A How To Guide for Digital Filmmakers
Welcome all! This is my blog to share my latest research,
thoughts, etc. on utilizing HD for independent filmmaking.
YES, I am available for consulting
Contact me at mike@hdforindies.com
All content copyright 2004-2007 Mike Curtis.
Sunday, November 12, 2006
Red workflow tidbit: "How fast is REDCINE?" Graeme answers
How fast is REDCINE? - DVXuser.com -- The online community for filmmaking
For those not keeping track, Redcine is the software that will read the Red One's proprietary codec and convert it to...anything you have installed on your system, as well as DPX/Cineon/JP2K/TIFF/etc. sequences. The question of speed has been raised - another RAW processing camera was said to take 8 seconds per frame at one point in its development, and folks were concerned about.
Graeme Nattress, Voodoo High Priest of Red's software/codec effort answers. Graeme's statements in italics, my comments interspersed in plaintext:
1) you can play your REDCODE files in real time - at what resolution depends on your processor specs.
(sounds to me like you can play the files and it'll do a realtime extraction of lower resolutions - so your slower machine may play high res files only at 1K, for instance)
2) colour transforms are GPU based, and hence very fast indeed. I'd expect realtime performance for a lot of configurations, but again, more details as we get nearer release.
(...so think of it like Aperture for video processing- it is GPU based, it demosaics RAW imagery, then it kicks out in a variety of file formats and sizes. Except instead of just stills (or still seqences), it can write to QT/AVI formats as well)
3) full quality demosaic of the full 4k will be a touch slower. It's got to be as we're using a complex / nice demosaic. However, hardware is getting rapidly faster and we'll be looking into how to best optimize the demosaic algorithm.
Presuming you've got a hoss system...which is why I'm waiting for 8 processor Intel Macs before buying a new desktop)
More details, such as questions about Avid & FCP specific workflows (I chime in on the latter) are in the thread, and it's growing quickly.
Graeme wrote in to add:
I should add, that 1) and 2) and 3) above go together, so that you shouldn't expect to see 4k being demosaiced and colour corrected and played back in real time.
RE: 2) GPU is not used for demosaicing. CPU is. It's hard to get the complexity of demosaic we need running on a GPU.
RE: 3) As posted earlier, current time for just the demosaic of 4.9k raw frame is 1.7 seconds (single core of quad G5, totally un-optimized development code). That's todays "touch slower" we hope to get that time down, but until we've got into the optimisation, I don't know how far down it will go. (People were worried when they'd heard that Dalsa was taking 8 or 4 seconds per frame.)
I don't want people to think either of two things:
a) it will be dog slow
b) it will be realtime everything
As we all know, in the real world, 4 processors doesn't make code 4 times as fast, as there overheads and other things at work.
The above is of today. Things can and will change.
-Graeme
-mike
For those not keeping track, Redcine is the software that will read the Red One's proprietary codec and convert it to...anything you have installed on your system, as well as DPX/Cineon/JP2K/TIFF/etc. sequences. The question of speed has been raised - another RAW processing camera was said to take 8 seconds per frame at one point in its development, and folks were concerned about.
Graeme Nattress, Voodoo High Priest of Red's software/codec effort answers. Graeme's statements in italics, my comments interspersed in plaintext:
1) you can play your REDCODE files in real time - at what resolution depends on your processor specs.
(sounds to me like you can play the files and it'll do a realtime extraction of lower resolutions - so your slower machine may play high res files only at 1K, for instance)
2) colour transforms are GPU based, and hence very fast indeed. I'd expect realtime performance for a lot of configurations, but again, more details as we get nearer release.
(...so think of it like Aperture for video processing- it is GPU based, it demosaics RAW imagery, then it kicks out in a variety of file formats and sizes. Except instead of just stills (or still seqences), it can write to QT/AVI formats as well)
3) full quality demosaic of the full 4k will be a touch slower. It's got to be as we're using a complex / nice demosaic. However, hardware is getting rapidly faster and we'll be looking into how to best optimize the demosaic algorithm.
Presuming you've got a hoss system...which is why I'm waiting for 8 processor Intel Macs before buying a new desktop)
More details, such as questions about Avid & FCP specific workflows (I chime in on the latter) are in the thread, and it's growing quickly.
Graeme wrote in to add:
I should add, that 1) and 2) and 3) above go together, so that you shouldn't expect to see 4k being demosaiced and colour corrected and played back in real time.
RE: 2) GPU is not used for demosaicing. CPU is. It's hard to get the complexity of demosaic we need running on a GPU.
RE: 3) As posted earlier, current time for just the demosaic of 4.9k raw frame is 1.7 seconds (single core of quad G5, totally un-optimized development code). That's todays "touch slower" we hope to get that time down, but until we've got into the optimisation, I don't know how far down it will go. (People were worried when they'd heard that Dalsa was taking 8 or 4 seconds per frame.)
I don't want people to think either of two things:
a) it will be dog slow
b) it will be realtime everything
As we all know, in the real world, 4 processors doesn't make code 4 times as fast, as there overheads and other things at work.
The above is of today. Things can and will change.
-Graeme
-mike
Comments:
I should add, that 1) and 2) and 3) above go together, so that you shouldn't expect to see 4k being demosaiced and colour corrected and played back in real time.
RE: 2) GPU is not used for demosaicing. CPU is. It's hard to get the complexity of demosaic we need running on a GPU.
RE: 3) As posted earlier, current time for just the demosaic of 4.9k raw frame is 1.7 seconds. That's todays "touch slower" we hope to get that time down, but until we've got into the optimisation, I don't know how far down it will go.
I don't want people to think either of two things:
a) it will be dog slow
b) it will be realtime everything
As wel all know, in the real world, 4 processors doesn't make code 4 times as fast, as there overheads and other things at work.
The above is of today. Thing can and will change.
RE: 2) GPU is not used for demosaicing. CPU is. It's hard to get the complexity of demosaic we need running on a GPU.
RE: 3) As posted earlier, current time for just the demosaic of 4.9k raw frame is 1.7 seconds. That's todays "touch slower" we hope to get that time down, but until we've got into the optimisation, I don't know how far down it will go.
I don't want people to think either of two things:
a) it will be dog slow
b) it will be realtime everything
As wel all know, in the real world, 4 processors doesn't make code 4 times as fast, as there overheads and other things at work.
The above is of today. Thing can and will change.
Anonymous & Anonymouse -
After careful consideration, I pulled your comments, not because you don't like Barry & Jarred, but the vitriol with which you attack...and the anonymity with which you do so.
If you use your real (full) name, and tone down the language to that which would be suitable for a civil face to face conversation, you are welcome to repost.
But I'm not cool with scathing anonymous attack posts on my blog...about my friends.
Again, criticize civilly and don't hide behind anonymity and you are welcome to make constructive criticism here.
-mike
After careful consideration, I pulled your comments, not because you don't like Barry & Jarred, but the vitriol with which you attack...and the anonymity with which you do so.
If you use your real (full) name, and tone down the language to that which would be suitable for a civil face to face conversation, you are welcome to repost.
But I'm not cool with scathing anonymous attack posts on my blog...about my friends.
Again, criticize civilly and don't hide behind anonymity and you are welcome to make constructive criticism here.
-mike
You have only done exactly what I expected you to do.
Do you consider Jim Jannard a friend Mike?
Just asking...
Do you consider Jim Jannard a friend Mike?
Just asking...
1.7 seconds is still a bit slow when you realize that an hour of shot footage will take 40 hours to render.
Even making that almost twice as fast at 1 second per frame will make for 24 hour renders to convert one hour of shot footage.
Of course machines will get faster, so I'm sure by next year with 8-core machines, the numbers will come down even further, but I still think at the end of the day, you're probably going to be looking at 10-12 hours for one hour of shot footage being converted.
Even making that almost twice as fast at 1 second per frame will make for 24 hour renders to convert one hour of shot footage.
Of course machines will get faster, so I'm sure by next year with 8-core machines, the numbers will come down even further, but I still think at the end of the day, you're probably going to be looking at 10-12 hours for one hour of shot footage being converted.
Demosaic is important though. You can't rush it by using a simple algorithm or you get nasty zipper artifacts, or any noise in the image will get turned into a strange parquet floor artifact. There's no point shooting 4k if you're going to ruin it in post. And of course, if you need to see 4k more rapidly, you can see it in 1k or 2k, or, rapidly demosaic the 4k.
And of course, 1.7 seconds is slow, unoptimized development code that is being used currently for what you see at IBC etc. Released code will be a lot smarter.
But after all, you need to know we're looking at quality here. If you're shooting 4k, it's vital you've got good quality.
And of course, 1.7 seconds is slow, unoptimized development code that is being used currently for what you see at IBC etc. Released code will be a lot smarter.
But after all, you need to know we're looking at quality here. If you're shooting 4k, it's vital you've got good quality.
You know Grame and Mike I think you should start reading the cml list if you are not. I saw no bashing of RED at all but when Jarred came on, I mean read his posts, he insulted once, then insulted again ,and then goes on DVX user to tell the fans that they don't like us at cml. He's stirring his troops up. Its obvious. Now Jim Jannard has come on CML to defend Jarred. I'm seeing a real persecution complex from both of them. I have read cml for years andnever saw the idiotic attitude Jarred showed. He insulted and insulted again. He said he was joking. What? Using the old standby excuse.Its ridiculous or a PR move of some kind. This never happened with any other camera. What conclusion can you make then. And I didn't read the post but anyone bashing Barry Green is a fool. He IS DVXuser not Jarred. If Barry leaves that forum is its all over for DVxuser. Without him its nothing but fanboyom.
Post a Comment
Links to this post:

