On 30 Dez., 20:50, wrote:
> On Dec 31, 3:46 am, ¤R¼..-¦°€•*¦*b€rt°• <~¤..-¦-•¦-y¤€-•~¤¤¦*@le•
>
> €s.com> wrote:
> > On Tue, 30 Dec 2008 03:23:25 -0800 (PST), wildt®ax
> > schreef:
>
> > Maybe he can ask the DP, if he could deliver in Quicktime HD, instead
> > of 35 MM.
>
> > R
>
> Maybe we should ask post if they want an Avid or FCP sequence with all
> audio sync up and with whatever codec they prefer. lol
>
> Alan
Indeed. The main cost and time burner in audio-post today is the
conforming process. The work generated by films cut with mono-guide-
tracks or sound from telecine downmixes. The work can be a breeze if
all is done correctl from shoot to audio-post but can also be
extremely tedious and expensive only because one tiny aspect wasn´t
set correctly or a recordist forgot to flip one single switch.
I have no idea how MXF/AAF could improve anything since even with iXML
being supported by all of the machines it is still the human error
rate that generates or saves the cost in post.
MXF is just a different container for a BWAV file and in essence
contains that same data that the iXML meta-data does so in terms of
meta-info there wouldn´t be any difference other than the fact that
only 2 out of a universe of audio software could read an MXF file.
So I don´t really see why on earth MXF would become "the next big
thing". Even between NLEs and DAW using AAF/MXF as exchange format
still is very cumbersome and with some systems either not possible or
doesn´t work correctly or data is missing.
frank.
>> Stay informed about: Any Field Recorder that supports MXF or AAF in the file cr..