Application ID's in Soundflow
Would it be good to have a universal, single place to define various different Applications and their ID's? I presume that sometimes an app ID changes when it updates (example Adobe Premiere is currently "com.adobe.PremierePro.14" but this is likely to change when Adobe updates it.
Since my various scripts reference this ID in different places, I'd have to update the scripts wherever the ID appears. If there was a way of updating it once in a master location, and then the ID is the correct current ID for wherever it's used in commands, surfaces or triggers, So for the user, they just need to reference adobePremiere and it would always be the correct ID, once they have updated it in that single place.
Is there a way to do this currently or is it a new feature request?
- Christian Scheuer @chrscheuer2021-03-20 10:47:24.152Z
SoundFlow is likely to add version agnostic app bundle references in future updates, when we increase general support for more apps.
Until that, I'd recommend that you look into SoundFlow modules, where you can re-use code between different scripts:
- AAndrew Sherman @Andrew_Sherman
That looks very useful, thanks
- In reply tochrscheuer⬆:AAndrew Sherman @Andrew_Sherman
Version agnostic references would be great. it might also be useful to have the same kind of functionality for the app path, in relation to launching it etc.
- In reply tochrscheuer⬆:AAndrew Sherman @Andrew_Sherman
Hi Christian, just checking if there is any further progress on global application IDs? I have updated my Adobe apps and they all have new IDs (eg com.Adobe.PremierePro.24), and some of my commands use keyboard triggers. Now I have to go and update all of my keyboard triggers (I don't think I can use modules in this case).
Christian Scheuer @chrscheuer2023-12-11 10:40:04.224Z
Hi Andrew,
Auch yea that sucks. We'll need to implement this on a per-application basis since they all use different versioning schemes wrt. bundle IDs (the best ones don't change their bundle IDs at all, obviously).
Besides Premiere, what other apps are you experiencing this with?- AAndrew Sherman @Andrew_Sherman
Hi Christian, I thought the Adobe ones all had name changes, but it turns out it's just Premiere, Bridge & Media Encoder, although even they don't have a consistent naming structure.
com.Adobe.PremierePro.24
com.adobe.ame.application.24
com.adobe.bridge14
com.adobe.AfterEffects
com.adobe.illustrator
com.adobe.Photoshop
com.adobe.lightroomCCcom.blackmagic-design.DaVinciResolve
com.ableton.live
net.whatsapp.WhatsApp
com.microsoft.VSCodePerhaps there could also be some kind of global application path for apps that get updated (eg I have an application launcher that needs the paths, which change when the app is updated). if we could update ID and path in one place, then it updates everywhere else, in commands etc.
eg path:
/Applications/Adobe Premiere Pro 2024/Adobe Premiere Pro 2024.appChristian Scheuer @chrscheuer2023-12-11 11:36:28.267Z
Thanks, Andrew. Are you using triggers with the AME and Bridge apps?
Wrt global app paths for launching stuff etc. that's not easy to build in a way that would work for all users, but you can easily use modules to accomplish this.
Christian Scheuer @chrscheuer2023-12-11 11:37:59.117Z
You can also make a script that looks for an app starting with "Adobe Premiere Pro " and locates the matching one, then launches it.
- AAndrew Sherman @Andrew_Sherman
Thanks for the suggestions, I'll look into it