You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be a basic question. I'm pretty new to aaf files in general and am having trouble understanding this part.
We're building an aaf file server-side, from WAV files. We then let the user download a zip that includes the aaf, and corresponding wav files. The problem is, once the user downloads it, the link is wrong. For example, a SourceMob has a locator object, with a urlstring pointing to the absolute path of the wav file on the server. Is there a way to set that locator to a path, relative to the aaf file? (Ex. ./source-wav-1.wav) Or is there another solution to this problem that I'm missing?
Logic Pro seems to handle it best, prompting the user to select the location of files it can't find. Pro Tools just gives an error.
The text was updated successfully, but these errors were encountered:
The AAF Edit Protocol says relative paths are supported. If pro tools supports them is another story. I'm not entirely sure the syntax, the spec says to follow RFC 2396. Unfortunately I don't have access to pro tools to test.
This may be a basic question. I'm pretty new to aaf files in general and am having trouble understanding this part.
We're building an aaf file server-side, from WAV files. We then let the user download a zip that includes the aaf, and corresponding wav files. The problem is, once the user downloads it, the link is wrong. For example, a SourceMob has a locator object, with a urlstring pointing to the absolute path of the wav file on the server. Is there a way to set that locator to a path, relative to the aaf file? (Ex.
./source-wav-1.wav
) Or is there another solution to this problem that I'm missing?Logic Pro seems to handle it best, prompting the user to select the location of files it can't find. Pro Tools just gives an error.
The text was updated successfully, but these errors were encountered: