referenced AAF for multichannel .wav-files to ProTools

I think we had this tick box selected and they were working on ProTools (not sure which version as this was a while back).

(screenshot attached)

That is strange. Were they working across machines or drives that could possibly cause a permissions issue when trying to find the WAV files? Glad it hear it works on your end.

Thanks,

Daniel

Hi

Okay, so not sure why I had issues before, but it seems that if I do a workflow test on my own machine with Resolve / Fairlight as my DAW, it works.

I used to get so many audio engineers complaining that it didn't work!

Let me continue some more intensive testing using the same settings.

Regards

Wilhelm

Hi Wilhelm,

How exactly is it not working? Are you getting an error message or is it not linking to the original files?
The Reference works by linking to the WAV files file path so the machine running Pro Tools can't see the file path then the audio will not appear in Pro Tools.

Thanks,

Daniel

Good day

I have also not had any success with the "Reference WAV files in place" setting on the main interface (screenshot attached). We have tested it with multiple versions of ProTools, Logic and Nuendo. And none of them worked.

Is there a setting we have missed? We are forced to always use the embedded option. Which works fine with most Final Mix Engineers after some clean up in the fcpxml on my side, but they lose timecode information, since new data is written when embedding and it "resets" the timecode.

Could you please talk me through the settings or do a workflow test with me perhaps?

Regards

Wilhelm Conradie

Dear James,

I don't know how PT is working in this regard, but from my side: no path at all, so that the sounddesign-studio just can "relink" to their copies of Multichannel WAVs.

Hi F

So if I understand what you want is to put an alias path in the AAF for the referenced in place media, i.e. not the path it can currently be seen by Project, the alias path will point to the media from the machine running PT.

Regs.

James

Unfortunatelly I can't provide you with a PT version. It's just a general question. Original path is utopian. The sounddesigners usually have there own Server- and Path-Systems. I also asked a colleague about his experiences and, like with me, all tests eventually failed, maybe they could relink, but the channel names scrambled or other weird stuff happend.
I understand that AAF is a unconsistent format to deal with - so, hats off if you could crack that!
On that note: there's no way to go around AAF and write a PT-project directly, is it?

Hi F,

Yes it should provided they have access to the original path the media was located on, and what version of PT you sent it to. If you can find out the PT version, I will see if we can check it.

Yours Sincerely

James

so, if i check "Reference WAV files in place" and send it over to another studio it should work? All the times I tried it it failed. To be fair: the last time I tried it was 2 years ago.

Hi F

I think this is just a configuration on your side, you can always set the AAF to be created with a link to the WAV's including multichannel, there were some issues with anything other than PT and PT version 10 opening / importing them. So I guess the question is what version of PT are you sending to.

Yours Sincerely

James

Good day to everybody!
This is the feature I miss the most since years: To send a referenced AAF (for multichannel .wavs) to our sound-designers. It would make our workflows so much easier and faster. For example, at the moment we are sending 6x40min episodes with dialogue and fx to a sound-departement in another country. Each file is more than 20 GB. If something goes wrong we lose literally days of conforming, uploading, downloading, reimporting. I would pay for such a feature easily the amount I spent for the pro-upgrade.
The files would be small enough to send via email...
And, as far as I know, ProTools is capable of opening multi-wav without breaking apart and reconforming to mono-wavs.
I would appreciate to know if there are any stakes on the ProTools-side that prevent you to invent such a feature.
All the best.
F