Thank you, Matt.
We sneaked in this feature into Auto-Align Post 2 
Check out the /tmp %TEMP% directories on macOS and Windows respectively@yair’s answer below for the correct file location.
Let us know if you have any questions.
Cheers,
Nir
1 Like
You’re rockstars! We’ll check it out.
Matt
Oh wow. I’m definitely jumping on this too to make a SoundFlow script for this.
1 Like
On Mac, is it:
/tmp/
When I select run AAP2 in visualize or render, nothing appears in that director/folder…
(I meant “boot volume”/tmp/)
The correct path on macOS should be ~/Library/Caches/AutoAlignPost/AapAlignResult.txt where ~ is your user home folder.
Also: It’s only enabled when the mode is STATIC+POLARITY.
1 Like
Fantastic! Thanks Yair!
2 Likes
Phenomenal thanks Yair! It’s a tiny thing but this will hopefully save so many assistant editors so much time.
1 Like
Thanks @Nir and @yair for adding this! Just updated my KM macro to take advantage of this feature. Will need to update the demo video as well. I
2 Likes
Working well in Sound Flow!
3 Likes
I’m not sure this is possible with the custom UI that AAP2 uses, but is it possible to have the buttons be exposed to accessibility so they can be programmatically set/controlled? (I’m out of my depth here in terms of what that means on your end so I understand if it’s a massive headache)
Thanks!
1 Like
Hi @dustinharris ,
You’ve actually stumbled another sneaked feature 
AAP2 is our first accessible product.
As we’re still getting more valuable feedback from accessibility users. it’s not mentioned as a whole feature just yet.
If there’s something missing, let us know.
2 Likes
maybe it’s a function of HOW SoundFlow wants to access the custom UI elements?
They don’t seem to appear visible to SoundFlow. When I log the children of the AudioSuite window, I can see all of the usual AAX plugin options, but I can’t seem to see any of the custom UI elements. (All that said, I have no idea how to make elements visible to Sound Flow):
{
"title": "Audio Suite: Auto-Align Post",
"description": null,
"role": "AXWindow",
"fullRole": "AXWindow:AXFloatingWindow",
"children": [
{
"title": "PluginView",
"description": null,
"role": "AXGroup",
"fullRole": "AXGroup",
"children": [
{
"title": "dummy",
"description": null,
"role": "AXSlider",
"fullRole": "AXSlider"
},
{
"title": "Master Bypass",
"description": null,
"role": "AXSlider",
"fullRole": "AXSlider"
}
]
},
{
"title": null,
"description": null,
"role": "AXStaticText",
"fullRole": "AXStaticText"
},
{
"title": null,
"description": null,
"role": "AXStaticText",
"fullRole": "AXStaticText"
},
{
"title": "input mode",
"description": "",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Settings Menu",
"description": "",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Plug-In Selector\nPackage: AAX AudioSuite",
"description": "Plug-In Selector\nPackage: AAX AudioSuite",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Use Processed Output In Playlist",
"description": "Use Processed Output In Playlist",
"role": "AXButton",
"fullRole": "AXButton:AXToggle"
},
{
"title": "Selection Reference",
"description": "Selection Reference",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Target button",
"description": "Target button",
"role": "AXButton",
"fullRole": "AXButton:AXToggle"
},
{
"title": "Key Input",
"description": "",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Processing Output Mode",
"description": "Processing Output Mode",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Processing Input Mode",
"description": "Processing Input Mode",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "Preset",
"description": "",
"role": "AXPopUpButton",
"fullRole": "AXPopUpButton"
},
{
"title": "COMPARE",
"description": "",
"role": "AXButton",
"fullRole": "AXButton:AXToggle"
},
{
"title": "Previous setting",
"description": "",
"role": "AXButton",
"fullRole": "AXButton"
},
{
"title": "Next setting",
"description": "",
"role": "AXButton",
"fullRole": "AXButton"
},
{
"title": "Plug-In Settings select",
"description": "",
"role": "AXButton",
"fullRole": "AXButton"
},
{
"title": "Analyze",
"description": "",
"role": "AXButton",
"fullRole": "AXButton"
},
{
"title": "AudioSuite Handles have been disabled due to Processing settings.",
"description": "AudioSuite Handles have been disabled due to Processing settings.",
"role": "AXButton",
"fullRole": "AXButton:AXToggle"
},
{
"title": "Render",
"description": "",
"role": "AXButton",
"fullRole": "AXButton"
},
{
"title": "Processing Handle Length in Seconds",
"description": null,
"role": "AXTextField",
"fullRole": "AXTextField"
},
{
"title": null,
"description": null,
"role": "AXButton",
"fullRole": "AXButton:AXCloseButton"
},
{
"title": null,
"description": null,
"role": "AXButton",
"fullRole": "AXButton:AXMinimizeButton"
},
{
"title": null,
"description": null,
"role": "AXStaticText",
"fullRole": "AXStaticText"
}
]
}
@dustinharris the sound flow script looks great.
I don’t have my iLok at home, but I’ll check tomorrow. I thought I saw a way to get the text box that says the offset. I’ll check again for the other buttons. It might be a child of one of those objects you listed.
1 Like
I’m actually reading the offset from the tmp file location Yair gave us, which should be a bit more robust as I can store the current date right before I hit ‘visualize’, which should refresh the offset written to the file, and as long as the file last-written date is newer than the stored date I know the correct offset has been used
Hey Dustin,
I’ve further investigated this. while we ‘expose’ the UI. it looks like Pro Tools always put a big area of it’s own PluginView which for conventional plug-ins, exposes the parameters.
I’ll update as we have something fresh about this.
A possible workaround @yair suggested until we resolve this is adding a pro tools preset with STATIC to be used by the script.
1 Like
Hi Tal! Thanks for the update. A plug-in preset is a really elegant solution!
1 Like
Hi @tal just a heads up, I’ve experimented with saving plugin presets, and it appears that the Time and Phase settings actually aren’t saved as part of the plugin preset (or maybe just the UI isn’t being updated when the saved preset is loaded?) PT 2021.10.0 on Mac OS 11.6.1 and 12.0.1.
Hi @dustinharris ,
Thank you so much for all your great feedback and efforts.
Myself and @Oran from our QA are squashing those issues for the upcoming maintenance release.
Will update as soon as we have more details.
Tal.
1 Like
I just wanted to chime in and say that this feature, combined with the extended delay time in the 2.0.3 public beta, has been extremely useful.
I work as an assistant sound editor at a post audio house called Signature Post. One of my first tasks when I started working at Signature was to put together a workflow for syncing the dialog assemblies we give to our DX editors, without the use of SyncroArts’ Titan and its Fix Sync function. Titan is something that many assistants still use and rely on, but the program is no longer supported, isn’t for sale, and cannot run on newer operating systems, so many of us have been looking for an alternative.
being able to access the offset value data was the exact feature we needed. With some help from our lead engineer I put together a macro in Keyboard Maestro that selects a clip, presses visualize, opens the .txt file, copies the offset value to the clipboard, strips the extraneous characters from the text, pastes the remaining numbers into Pro Tools nudge value field, then nudges the waveform using the “nudge within clip boundaries” key command to shift the production mic channels into sync with the AAF, in a single keystroke. in action it looks very similar to the script @dustinharris posted above.
Is there any chance a function similar to the macro I described could be incorporated into the plug directly, in a future version of AAP2? Being able to quickly sync the production mic channels without rendering any new audio is essential and if AAP2 could do that “out of the box” without relying on any additional programs (ie soundflow, keyboard maestro) it’d be a big help to a lot of other assistants I know. I do know there are a few other companies currently trying to create an adequate replacement for Titan’s FixSync, but just by making the offset value data available you guys are already miles ahead.
Anyway, that’s it, just wanted to put that out there, thank you for thinking to add this feature, it’s truly a lifesaver.
Best,
Nick Papalia
Assistant Sound Editor
3 Likes