I’m using Reaper on a Mac and have just started working with Auto Align Post 2 for dialogue sync, but I sometimes get this error (see attached screenshot). I’m using Vordio as a converter from .aaf to .rpp and sometimes I’ve been using AATranslator .aaf to .rpp or .omf to .rpp, but this error seems to not go away. So I’m wondering if I’m doing everything correctly or there’s some funny stuff happening with the filenames etc.?
ARA is working on the audio file level. meaning the ARA adjustment/change is linked to the underlying audio source range.
For example, let’s say we have 1min (60seconds) long audio file with a clip on timeline starting at 4th second and using the audio file from [30s-40s], so you end up having a 10 seconds clip on timeline at 00:00:04:00 that ends at 00:00:14:00. so when playhead arrives to 00:00:04:00 it starts playin the 30est second within the audio file.
Now let’s say we duplicate that clip, so we now have another clip with the same length (and signal) that starts at timeline 00:00:14:00.
So if AAP will “modify” the audio within [30:40] on the first clip, the second clip will also be affected. since they’re overlapping the same underlying audio.
The warning suggests the above clips on the track are using same underlying audio.
As always, if you need extra help or have additional insights. feel free to contact us through support to dive deeper.
Thanks for the fast reply! Alright, I understand the error, but it seems quite logical that a clip on a movie edit is used 2 or more times during the whole timeline starting and ending on different timecodes. If the editor makes an AAF export (on davinci resolve for example) does it give each clip an original filename or does it reference the full raw file? Looking at the structure of an AAF I would suppose it’s made up of smaller clips, that each has a specific filename, but I’m not sure.
So I guess my questions would then be:
Is this problem common?
Is it DAW related or ARA related or AAF related or Vordio related that it has such a warning?
Is there a solution in any of these cases where it can be done without glueing/rendering all the items separately?
Is it DAW related or ARA related or AAF related or Vordio related that it has such a warning?
The limitation of applying the “modification” on the audio file is by the ARA design.
Is there a solution in any of these cases where it can be done without glueing/rendering all the items separately?
I’m afraid you’ll need to render something at some point wheter it is while exporting the project to AAF, converting it to REAPER or rendering the item/clip of AAP and then following to align the next one.
But with current ARA, we can only work on the audio file level.
If you have Davinci btw, you can try and apply the AAP step on Davinci before exporting.
Alright, so do you know if this problem is in the encoding of the AAF? I’m just thinking if there’s something I could tell the picture editor to do before the files reach me, so that while making the AAF, the files are split into smaller clips, that are original? As far as I can see there’s many small clips in the AAF Audio Files folder that comes with the .aaf file, so it should be done already, no? I’m asking because I genuinely don’t know how each software makes the AAF file, because I know that there are differences between Adobe Premiere AAFs and Avid Media Composer AAFs and Davinci AAFs, but how do they differ I don’t understand. Davinci so far is the best in keeping the metadata and everything in order (or at least it looks the same as the picture editors project), but yeah, I want to know how I can do this automatically, or as you say “render something at some point…”. I would really prefer for it to be done before the aaf reaches me, but if nothing else I’ll try the rendering in Reaper.
Hi @edvardsbroders ,
Sorry for this one slippin on me.
I’d suggest moving this discussing to be with via our support email so we’ll be able to inspect actual content (if possible) .
It might also be helpful contacting Vordio to figure out how it works on their end since they convert it to a Reaper project.
Ideally, if you have a very small project (with less than 10 items as an example) that can reproduce this issue, it’ll be much easier to try and figure out what’s going on.