I think that this might work if worked out properly. Many codecs take
advantage of all your processing power, so if you wanted to work while an
export/transcode was going on, then they'd have to limit the amount of
processing power being used. Otherwise, the editing experience would slow
down tremendously. You also have to consider IO/Storage. You'd have to
limit the transfer rate in order to split performance equally. Try working
in MC while Sorenson is transcoding in the background over 1Gbit Ethernet
on an Isis. It's very slow. This is also very evident in Nuke while
rendering/caching.
Maybe I'm wrong. Maybe Adobe already does this successfully.
On Tue, Jun 26, 2012 at 1:47 PM, Benjamin Hershleder <Ben@contactben.com>wrote:
>
>
>
> I have to imagine that type of goodness is in the dev. pipeline.
>
> B
>
>
> Benjamin Hershleder
> http://ContactBen.com
> http://Hershleder.com
>
> Wear It In Post!
> Fun T-shirts, mousepads, mugs & more
> for Post Production Professionals
> http://www.WearItInPost.com
>
> On Jun 26, 2012, at 1:44 PM, Pete Opotowsky wrote:
>
> > Render, Import, Export, Capture - Now that we're 64bit, can we use some
> > of those cycles to do some of these operations behind the scenes? Please?
> >
> > --
> > Pete O
> > POP Pictures
> > Orlando
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Search the official Complete Avid-L archives at:
> http://archives.bengrosser.com/avid/
> Yahoo! Groups Links
>
>
>
>
[Non-text portions of this message have been removed]
No comments:
Post a Comment