M4 with Sequoia?
Hey @Chad
Just a heads up that some of the Groups scripts in this package no longer work with M4/Sequoia (they move too fast). They likely need the waitFor callback routine.
I had to borrow your getCurrentlyInGroupTracksForModifyGroups()
function to add a check that tracks were correctly added to the Currently In Group list for the Add To Group script. This seemed to work for me.
// Add to the Group
sf.ui.proTools.windows.whoseTitle.is("Modify Groups").first.buttons.whoseTitle.is("Add").first.elementClick();
// Wait for the selected tracks to appear in the "Currently In Group" list
sf.waitFor({
callback: () => {
// Get the current list of tracks in the group
const currentGroupTracks = getCurrentlyInGroupTracksForModifyGroups();
// Extract the track names from the fetched group items
const currentGroupTrackNames = currentGroupTracks.map(track => track.name);
// Check that each selected track appears in the current group track names
return selectedTracks.every(selectedName => currentGroupTrackNames.includes(selectedName));
},
timeout: 2000, // adjust timeout (in milliseconds) as needed
}, "Failed waiting for the selected tracks to be added to the 'Currently In Group' window.");
// Now that the selected tracks are confirmed to be in the group...
sf.ui.proTools.windows.whoseTitle.is("Modify Groups").first.buttons.whoseTitle.is("OK").first.elementClick();
- Chad Wahlbrink @Chad2025-05-03 04:09:44.784Z
Thanks for this, @Forrester_Savell!
I noticed some other users also having issues, and finally tested this on macOS Sequoia. I updated the scripts to work better with macOS Sonoma and above. I believe it's the same issue with asynchronous pop-up menus that was discussed here:
- FForrester Savell @Forrester_Savell
Hey @Chad
I'm not exactly sure when the change occurred, might have been MacOS 15.4 but it broke my solution I posted above. I agree it's probably related to the GroupIDView popupmenu blocking things. As I haven't had the time to sink into coding that solution, I've found just a
sf.wait
seems to solve it for now. Same goes for all the other Sequoia woes, of which there are many!
I tried your latest v1.2.2 but that doesn't look like it has the fix yet?Chad Wahlbrink @Chad2025-05-06 16:40:28.398Z
Hi, @Forrester_Savell,
The fix I posted should be in version 1.2.4 of my package, which I published a few days ago.
Let me know if that works for you.
Also, I'd be curious to hear about your other issues with Sequoia. I have a Sequoia installation set up and haven't run into many problems unique to Sequoia. However, I am still primarily mixing in Pro Tools on an older macOS (still on Monterey on my main rig). If you wanted to hop on a quick Zoom call at some point and show me what you are running into on your system, I'd be happy to do that. Contact support@soundflow.org, and we can set that up whenever you have time.