Why not a REDcode PCI board ?

[moodyko]

I am a post guy and the owner of a post and VFX house building a complete RED pipeline,
We are even buying the (now I should say "a") Red camera and for our own VFX shoots.

From a post pov I am frightened by 5,6,9....28 K and redcode 225.
A 100k $ scratch suite is barely able to deal realistically with 2K 36, transfer to Symphony is a pain, indie directors will come with hours of 5K rushes...and no budget.

Transfer and renders times will be hell, should we have different rates for 2K,4K and...x K ? or limit the acceptable rushes to 2K and occasionally to 4K ?

So my question:

Is it possible (technically) that the guys from RED can manufacture a PCI (or whatever other slot) card that can handle by hardware all the encoding decoding work for a realtime playback for whatever Redcode and resolution.
Any disk array able to handle a single stream uncompressed HD is supposed to be able to keep up with the 225, Right ?
Then editing, grading and compositing software will only have to deal with the card.

May be it was discussed b4, I did a search but couldn't find anything.

 

[Emery Wells]

Well, REDRAY has the hardware to do this. They need to create a beefier REDRAY that can handle the higher data rates and make it a PCI card. This would be fantastic. Even if it was a $10k card, id happily pay that for rock solid full res REDCODE playback. However, with new workflows from Adobe and such, I think they are trying to move away from the idea of having to transcode everything first and moving towards realtime dynaimc decoding. Thats what the SDK is for.

 

[moodyko]

10K Redcode Card will still be cheaper than a REDBOXX 2 in a year.

I still have an ABVB avid Media composer alive and making money.... well the SGI O2 I bought the same year....... I don't even remember where It is stored.

omf never opened, AAF never happened, FBX was Autodesked... we know that any supposedly "universal High-end" format involving the nosy guys will never live, RED seem to become more open about Redcode spreading. I don't mind R3d 225 as a day-to-day format even for digitizing from SD and HD decks or importing 16 bit 3D renders for conforming.