One for the VV3 product manager:
I saw a post a while back on the rationale behind keeping the new DV codec internal to VV3 and have a couple of observations: 1) the new DV codec is superior to other codecs we've checked out; 2) the footage we work with comes in DVCAM and goes out to a DVCAM master, usually; 3) almost all the footage we work with goes through After Effects and is composited with Lightwave/Aura/Photoshop/Illustrator material. Only the final sections are assembled in a NLE.
In order for us to get the benefits of the new DV codec, we'd have to render everything out of After Effects as TGA sequences, read them into VV3, then render to DV.
It would greatly enhance our workflow to be able to render to the DV codec directly from After Effects, then assemble the clips in VV3. Since TGA sequences run about 30mb/sec and we've already got TGA sequences coming from Lightwave and Aura, the added disk usage hit would be considerable.
Wouldn't there be a way to tie the codec to only work on a machine that had VV3 installed? Move it from internal to VV3 to internal to the machine VV3 is installed on? It would greatly improve VV3's interoperability with other programs, at least in our case, without letting anyone get a "free ride".
Thanks.
I saw a post a while back on the rationale behind keeping the new DV codec internal to VV3 and have a couple of observations: 1) the new DV codec is superior to other codecs we've checked out; 2) the footage we work with comes in DVCAM and goes out to a DVCAM master, usually; 3) almost all the footage we work with goes through After Effects and is composited with Lightwave/Aura/Photoshop/Illustrator material. Only the final sections are assembled in a NLE.
In order for us to get the benefits of the new DV codec, we'd have to render everything out of After Effects as TGA sequences, read them into VV3, then render to DV.
It would greatly enhance our workflow to be able to render to the DV codec directly from After Effects, then assemble the clips in VV3. Since TGA sequences run about 30mb/sec and we've already got TGA sequences coming from Lightwave and Aura, the added disk usage hit would be considerable.
Wouldn't there be a way to tie the codec to only work on a machine that had VV3 installed? Move it from internal to VV3 to internal to the machine VV3 is installed on? It would greatly improve VV3's interoperability with other programs, at least in our case, without letting anyone get a "free ride".
Thanks.