MMP wrote:I am having a difficult time imagining the workflow that this would enhance. Can you describe it in more detail?
thanks!
OK
Vision editor sends me an xml of of their Premier Pro job after achieving picture lock.
I translate the xml with AA Translator to create a SAWStudio edl.
Open the edl in SAW and audio editor (me) has to path the audio.
The vision editor often sends 6 or 8 tracks of audio which usually gets cut down to 3 or 4 tracks (stereo tracks is why).
I won't have all the audio in the vision editor's job. They will have used camera (scratch) audio from multiple cameras;
as well as the pro audio recordings that I likely have provided.
That original sequence may well need to be shown to the director/ producers, etc.
I might well need that camera audio for reference to find the corresponding pro audio if said audio has been recorded.
I might also need to supply the vision editor with timecodes related to their edit and possibly include filenames which would be tied to the empty regions;
or I might request missing camera audio if corresponding pro audio was not recorded and does not exist.
The SAWStudio File view will also have info including the vision editor's file locations, which could be helpful.
There are many reasons to retain such information :-)
Throwing that info away on a project that has taken several years to complete seems like a waste to me as importing an xml into SAW Studio is not possible afaiaa.
[quote="MMP"]I am having a difficult time imagining the workflow that this would enhance. Can you describe it in more detail?
thanks![/QUOTE]
OK
Vision editor sends me an xml of of their Premier Pro job after achieving picture lock.
I translate the xml with AA Translator to create a SAWStudio edl.
Open the edl in SAW and audio editor (me) has to path the audio.
The vision editor often sends 6 or 8 tracks of audio which usually gets cut down to 3 or 4 tracks (stereo tracks is why).
I won't have all the audio in the vision editor's job. They will have used camera (scratch) audio from multiple cameras;
as well as the pro audio recordings that I likely have provided.
That original sequence may well need to be shown to the director/ producers, etc.
I might well need that camera audio for reference to find the corresponding pro audio if said audio has been recorded.
I might also need to supply the vision editor with timecodes related to their edit and possibly include filenames which would be tied to the empty regions;
or I might request missing camera audio if corresponding pro audio was not recorded and does not exist.
The SAWStudio File view will also have info including the vision editor's file locations, which could be helpful.
There are many reasons to retain such information :-)
Throwing that info away on a project that has taken several years to complete seems like a waste to me as importing an xml into SAW Studio is not possible afaiaa.