Aye, doesn’t Flame use more drive-based processing to preview, etc? As oppossed to AE using mainly RAM after the CPU? Can’t remember the details, but Autodesk stuff processes/renders data in a totally different way to AE someone was telling me..?
As for workflow – I’m pretty sure you can ingest/output from data files (cineon/frame sequences/QT) on a Linux Flame, just as well as you could in AE. Products like Xstoner and some max-t systems can totally integrate autodesk systems with PCs/Macs for networking and sharing storage. I currently ingest either from Digi via Premiere and into AE, or directly form our Editobox via SDI. Output is the same.
Antother question – how much compression does digibeta REALLY introduce?…
..We still use an old linear digibeta suite for some sport progamming (no digitising time wasted) and that still uses a VTR>VTR editing environment through a series of external DVEs and mixers – which would bring into effect LOTS of generations of recordings from one digi tape to another and I can’t really see much difference between the rushes and the final edited master tape.
*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0