> Does the track assignment also not work when mono files are named file_1.wav file_2.wav etc?
Files are named that way by the recorder, and whereas every version I have ever imported BWAV's in (probably v10 Meridien) respected the track number as assigned, only 7.0.4 and 8.3.1 did not respect this and makes them all A1. Tried different files from different productions, could always reproduce. Escalated it to Avid, got reproduced and fixed in the most recent updates.
>
> (But i never worked with perf slip, no clue how to go about it, and since digital sound 'perfs' are 1 sample i think it's a bit of an archaic way of looking at things these days....)
Archaic or not, it is the only way I can sync sound up with subframe accuracy.
> What do you mean by 'per channel content descriptor' ?
I mean things like "Boom" or "TX Pete".
> A Poly BWF has one track, thus one BEXT entry.
Yes, but if you use the "Group multichannel BWAV" option, MC only appends the metadata for X_1.wav.
The best workaround with Cantar recorded sound has proven to be:
- import files as monophonic
- import the Cantar-generated ALE
- relink clips from ALE import with existing media
That way, one gets mediafiles that have proper per-channel metadata while being able to work with single multichannel clips in MC.
> However, this entry can contain a TRK entry for each channel.
> (eg, sTrk1=Lav sTrk2=Boom etc.)
> That shows up in Avid (and probably gets lost after subclipping.)
And more importantly, Pro Tools has no clue about any of that metadata, and just looks at the mediafile.
> If the iXML is a problem, it's not that hard to extract the XML and re-format it as an ALE.
No the problem is that you cannot link that resulting ALE (that Cantar already makes) to a clip that is A1, A1, A1, A1 when the clip contains A1, A2, A3, A4.
Avid supports iXML via AMA-linking audio, but again, that forbids Perf Slip, so end of story. Hopefully they either enable Perf Slip on AMA'd sources, or enable iXML metadata via traditional import.
But still, if I bring in a single track that someone for some reason has designated as A4, why on earth would MC not respect that? And more importantly, it has always done it correctly, and then it stopped doing it correctly.
But Avid knows, agreed and have fixed the issue. Just not in 8.3.1. Which leaves me to wonder which version I should help my buddy install. I'm really leaning to 7.0.4.4.
> And you said Cantar brings a tool like that. What's wrong with that then?
> (I'm on 8.3 win, but mostly deal with BWF for developing, hardly any actual work, let alone complicated workflows...)
This is not even that complicated a workflow. It is a somewhat convoluted workaround to get everyday production sound BWF through editorial and eventually into PT.
Don't get me started on how they could have fixed all of that 12-13 years ago.
J
Posted by: "Job ter Burg (L2B)" <Job_L2@terburg.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (11) |
No comments:
Post a Comment