Logic Pro renamed their app. I can't get SF to switch to my Logic Pro deck
System Information
SoundFlow 5.4.2
OS: darwin 22.3.0
ProductName: macOS
ProductVersion: 13.2.1
BuildVersion: 22D68
Steps to Reproduce
- Set Application "Activate" Trigger for "Logic" or "Logic Pro X" to raise a Deck.
- Open or Activate Logic Pro.
- Deck won't activate, probably because the current Logic Pro application is named "Logic Pro"... not "Logic" or "Logic Pro X"
Expected Result
Using an Activation Trigger for Logic should raise the Deck when Logic is activated.
Actual Result
Deck won't activate.
Workaround
No... I tried Window Activations, UI Clicks, etc, but they all start with requiring the Application to be activated, but it can't see it due to the name issue.
Other Notes
Links
User UID: CaeT2w1eKrgpwAxLJ6hF9iiU1nK2
Feedback Key: sffeedback:CaeT2w1eKrgpwAxLJ6hF9iiU1nK2:-NXLzusaJTRTPw4QTU3t
- Christian Scheuer @chrscheuer2023-06-07 20:07:37.497Z
Hi Brian,
Which version of Logic is this that you installed/upgraded to?
- In reply toBrian_Steckler⬆:Brian Steckler @Brian_Steckler
Logic 10.7.7 with Ventura 13.2.1
Christian Scheuer @chrscheuer2023-06-07 22:07:55.308Z
Thanks! @Kitch can I get you to do a bundle ID check on that, if you can install it? One guess is that the bundle ID has changed.
Christian Scheuer @chrscheuer2023-06-07 22:08:27.616Z
Currently, SF expects
'com.apple.logic10'
Kitch Membery @Kitch2023-06-07 22:09:22.049Z
I'll check it out shortly :-)
- In reply tochrscheuer⬆:
Kitch Membery @Kitch2023-06-07 22:14:11.261Z
The bundle ID looks the same
com.apple.logic10
. I'm on Logic Pro version 10.7.7 OS Ventura 13.3.1.
- In reply toBrian_Steckler⬆:Christian Scheuer @chrscheuer2023-06-08 11:44:00.889Z
@Brian_Steckler, can you share a screenshot of the Application Trigger you've set up? From looking at your logs, only the Application Trigger for Finder seems to be executing.
- In reply toBrian_Steckler⬆:Brian Steckler @Brian_Steckler
Here's the 2 Triggers that should bring up the this deck, but don't.
Christian Scheuer @chrscheuer2023-06-08 21:02:21.549Z
Thanks. Does this deck show up properly if you click the "Show Deck" button?
Brian Steckler @Brian_Steckler
Sorry… missed your question.
Yes, I can raise the deck with a button on the Stream Deck or the show deck button in the editor.
But there’s currently no way to get a window trigger to raise it that I can figure out. It makes for clunky workflow when I have to leave Logic for a second, which brings up my Finder deck or whatever and then back to Logic and the deck won’t follow.
Christian Scheuer @chrscheuer2023-06-23 15:17:47.257Z
@Kitch can you help make a debugging script for Brian that logs the frontmost app's bundle ID, so he can focus Logic and run the script so we can see if for some reason his bundle ID is incorrect/different?
Kitch Membery @Kitch2023-06-23 18:05:14.196Z
@chrscheuer I'm able to recreate the Application Trigger issue on my system here.
Something I noticed... It seems Logic Pro has two options under "When these apps" in the Application Trigger popup.
Unfortunately, neither of them seems to work for window triggers, and there is nothing showing in the SoundFlow logs when I switch to logic.
On my system, the Bundle ID for the frontmost app when logic is focused is
com.apple.logic10
Here is an element debug with attributes when logic is focused in case that offers any other insight.
23.06.2023 10:56:43.31 <info> [Backend]: >> Command: Frontmost App Bundle ID [user:ck0h82cwn000daz10hbpeyuoy:clj8tkh9u0000qc10nlsjeixz] 23.06.2023 10:56:43.33 <info> [Backend]: { "AXChildren": { "class": "__NSArrayM", "isSettable": false }, "AXChildrenInNavigationOrder": { "class": "__NSArrayM", "isSettable": null }, "AXEnhancedUserInterface": { "class": "__NSCFBoolean", "isSettable": true, "value": false }, "AXExtrasMenuBar": { "error": "kAXErrorNoValue" }, "AXFocusedUIElement": { "error": "kAXErrorNoValue" }, "AXFocusedWindow": { "type": "Element" }, "AXFrame": { "error": "kAXErrorAttributeUnsupported" }, "AXFrontmost": { "class": "__NSCFBoolean", "isSettable": true, "value": true }, "AXFunctionRowTopLevelElements": { "class": "__NSArray0", "isSettable": null }, "AXHidden": { "class": "__NSCFBoolean", "isSettable": true, "value": false }, "AXMainWindow": { "type": "Element" }, "AXMenuBar": { "type": "Element" }, "AXPosition": { "error": "kAXErrorAttributeUnsupported" }, "AXPreferredLanguage": { "class": "NSTaggedPointerString", "isSettable": null, "value": "en" }, "AXRole": { "class": "__NSCFConstantString", "isSettable": false }, "AXRoleDescription": { "class": "NSTaggedPointerString", "isSettable": false, "value": "application" }, "AXSize": { "error": "kAXErrorAttributeUnsupported" }, "AXTitle": { "class": "NSTaggedPointerString", "isSettable": false, "value": "SoundFlow" }, "AXWindows": { "class": "__NSArrayM", "isSettable": false } } 23.06.2023 10:56:43.33 <info> [Backend]: { "title": "SoundFlow", "description": null, "role": "AXApplication", "fullRole": "AXApplication", "children": [ { "title": "SoundFlow", "description": null, "role": "AXWindow", "fullRole": "AXWindow:AXStandardWindow" }, { "title": null, "description": null, "role": "AXMenuBar", "fullRole": "AXMenuBar" } ] } << Command: Frontmost App Bundle ID [user:ck0h82cwn000daz10hbpeyuoy:clj8tkh9u0000qc10nlsjeixz]
Christian Scheuer @chrscheuer2023-06-23 23:20:53.711Z
Thanks! So this is only a problem for Window triggers? Application triggers work correctly?
Kitch Membery @Kitch2023-06-23 23:22:10.908Z
Sorry @chrscheuer, I meant Application trigger, not Window trigger.
- In reply tochrscheuer⬆:
Kitch Membery @Kitch2023-06-23 23:28:01.505Z
Just tested Windows triggers and it seems to have the same issues... So both Application and Window Triggers are not working with Logic Pro.
Brian Steckler @Brian_Steckler
Hi, sorry guys, i was out of the studio most of the day.
But, this is the exact issue I've found... neither of those Logic options work.
Kitch Membery @Kitch2023-06-24 00:50:53.461Z
Hi Brian, can I get you to follow the steps laid out in my previous post to make sure we're seeing the same issue?
Thanks in advance.
Brian Steckler @Brian_Steckler
Yeah, working on that right now.
Brian Steckler @Brian_Steckler
Here's what I get:
|com.apple.logic10|
Kitch Membery @Kitch2023-06-24 01:09:16.315Z
Much appreciated Brian,
We'll get back to you once we've found where the issue is. Thanks for your patience on this.
Out of interest how are you switching your apps? A temporary workaround could be to have a keyboard shortcut assigned to a macro that... 1. Activates Logic and 2. Displays your logic deck on your specified device.
Example.
Or in script form something like this.
const logicDeckId = 'Add your logic Deck ID here'; const targetStreamDeckSerialNumber = 'Add your Stream Deck Serial number here'; sf.ui.app('com.apple.logic10').appActivateMainWindow(); sf.decks.get(logicDeckId).open({ device: sf.devices.streamDeck.getDeviceBySerialNumber(targetStreamDeckSerialNumber), });
Brian Steckler @Brian_Steckler
At the moment, I've got 2 buttons my my Stream Deck... one to launch Logic, and then one to bring up the main deck for Logic.
I'm not sure your Macro will work for the same reason... Activate App's Main Window won't work... I think. I'll try it.
Kitch Membery @Kitch2023-06-24 01:15:26.984Z
Fortunately the
appActivateMainWindow();
method is not affected by the issue so it should work :-)Brian Steckler @Brian_Steckler
Yep, you're right... works great.
That's helpful until we get it working like all my other apps. Thanks.
Kitch Membery @Kitch2023-06-24 01:18:13.790Z
Awesome! We'll keep you posted.
- In reply toBrian_Steckler⬆:
Kitch Membery @Kitch2023-06-23 17:29:51.926Z
Hi @Brian_Steckler,
Here is a debug script that will copy the Bundle ID of the Frontmost App.
const bundleId = sf.ui.frontmostApp.activeBundleID; log(bundleId); sf.clipboard.setText({text:`|${bundleId}|`});
Please create a new script and paste the above code into it, then assign a Keyboard Trigger to the script.
Once you've done that manually switch over to Logic Pro and run the script using the keyboard shortcut.
This will copy the Logic Pro's App Bundle ID to your clipboard for you to paste into a reply message on this thread.
Thanks in advance. :-)
- In reply toBrian_Steckler⬆:Brian Steckler @Brian_Steckler
You can't tell from the Screenshot, but in the "When these apps" window, one is "Logic" the other is "Logic Pro X".
- In reply toBrian_Steckler⬆:Brian Steckler @Brian_Steckler
Any progress on this issue? Any workarounds you can think of?
One way around it would be if the Window Trigger didn't need the full text name of the window but could see included text. For example, in Logic, the Main window name is always the "[session's file name] - Tracks" and the Piano roll window (another one I'd like to have SF follow_ is "[session's file name] - Piano Roll". So, if the Window Trigger could see just "Tracks" and "Piano Roll" it'd work for me I think.
Christian Scheuer @chrscheuer2023-06-23 10:23:55.187Z
Hi Brian. I was waiting for your reply on this post:
Logic Pro renamed their app. I can't get SF to switch to my Logic Pro deck #post-11Brian Steckler @Brian_Steckler
Oops, didn’t see your question above…
- MIn reply toBrian_Steckler⬆:Matt Norriss @Matt_Norriss
Following, as I'm running into the same issue. Running a Mac Studio on 13.4.1 with clean installs of Soundflow and Logic 10.7.9. Been getting around it just by clicking "show deck" from my LPX deck in the Soundflow editor
Other application triggers work fine, eg. Pages, Preview, RX, TextEdit, Finder
TIA!
~Matt
Brian Steckler @Brian_Steckler
Yep, that's the issue. Sure would be nice to get this working right.
Christian Scheuer @chrscheuer2023-07-25 18:37:24.538Z
Are you both seeing
com.apple.logic10
logged when running this script and Logic being the frontmost app?const bundleId = sf.ui.frontmostApp.activeBundleID; log(bundleId);
Brian Steckler @Brian_Steckler
Yes, that's what I get.
- SIn reply toBrian_Steckler⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-885
- In reply toBrian_Steckler⬆:Brian Steckler @Brian_Steckler
Any progress on this? Tired of the extra buttons to switch to Logic every time I bring something else to the front.
- MMatt Norriss @Matt_Norriss
@chrscheuer @Kitch Any progress? Thanks for your insights so far, I saw it's now tracked internally as SF-885
~M
Kitch Membery @Kitch2023-08-30 21:35:43.862Z
Hi @Matt_Norriss,
We've made no progress on this yet but it is on our to-do list. We'll keep you updated.
Thanks for your patience.
Christian Scheuer @chrscheuer2023-08-31 11:17:08.402Z
Thanks all. I've been able to reproduce this on my end, but haven't found a fix yet.
- MMatt Norriss @Matt_Norriss
Appreciated, both! Fingers crossed it’s able to be fixed at some stage 🤞🏻
Christian Scheuer @chrscheuer2023-09-22 05:52:00.781Z
Confirming this will be fixed in SF 5.5.0 :)
- MMatt Norriss @Matt_Norriss
YAY THANK YOU!
- In reply tochrscheuer⬆:
Brian Steckler @Brian_Steckler
Yes! This will really change my day to day. Do you have an ETA on 5.5?
Christian Scheuer @chrscheuer2023-09-25 17:57:15.938Z
Not yet, still beta testing some bugs and shuffling around some priorities, but it's mostly feature complete by now. Ping me in a few weeks if we haven't released by then.
- MMatt Norriss @Matt_Norriss
Hey Christian, any updates on the release of 5.5.0? :)
- In reply tochrscheuer⬆:
Brian Steckler @Brian_Steckler
HI Christian! Pinging you more that a few weeks later... got a 5.5 about ready?
Kitch Membery @Kitch2023-12-03 01:13:13.550Z2023-12-03 13:31:32.236Z
Hi @Brian_Steckler and @Matt_Norriss,
Thanks for reaching out.
Yes, 5.5.1 is available. You can install the latest stable version of SoundFlow from the following link my.soundflow.org/install :-)
- SIn reply toBrian_Steckler⬆:SoundFlow Bot @soundflowbot
The linked internal issue SF-885 has been marked as Done