Saez

@Saez the CLI approach that @vitor shared works great. Also if you you need lots of control of your audio I/O you might consider a third party approach like Rogue Amoeba's Soundsource. They just added shortcuts support and you can't easily build some custom workflows around those shortcuts.
 
It is something else to consider if you need to really tweak.
 
 

There are probably quite a few sound device selector script filters out there, but the ones I've come across are mostly written in applescript. I rewrote my own in C++ Swift and it runs much faster, so I'm sharing it here in case anyone's interested. 
 
Features
Directly uses system APIs to list and select sound devices, which makes it very fast and reliable No dependencies - no additional installs required Optionally add devices to a blocklist to hide them from results Optionally disable device selected notifications  
Installation note
On initial run, you'll see a pop-up window that says something like:
"sound_filter" / "sound_selector" cannot be opened because the developer cannot be verified. This is a macOS security feature that blocks execution of non-codesigned binaries You're seeing it because this workflow uses pre-compiled binaries rather than interpreted code (e.g. Python) I can't codesign those binaries because I'd need an Apple developer account and that costs money The security risk is that you have to trust that I'm not doing malicious stuff with the binaries (I'm not) (This workflow is open-source and you can compile the binaries yourself, in which case all this is moot, but that's very inconvenient) You have to bypass this security feature to use this workflow. To do so, follow the instructions here.  
Changelog
v2.1.0
Fixed: Icon visibility in light mode (icons automatically change with appearance settings) New: Prettier notifications no longer require terminal-notifier v2.0.0
New: `switchaudio-osx` no longer required New: Significantly faster loading speeds New: Icons now indicate whether a device is selected New: Makes use of Alfred 5 user configuration panel to simplify setup v1.1.1
Fixed: Cannot parse switchaudio-osx JSON in some cases  v1.1.0
Added: User-configurable device blocklist (see feature request) Fixed: Issue with user-set path for switchaudio-osx v1.0.2
Minor performance optimisations v1.0.1
Added: In most cases, users no longer need to specify the path of switchaudio-osx (see relevant comment) Fixed: Missing icon images in terminal-notifier notification  
Download | Source
 
Screenshots
 

 

 

Now I got it. I will check if it's solve my wishes. Thank you so much @vitor

I understand the solution you’re pursuing. But like I said you’re making something which is a workaround, GUI automation which is likely to break on Ventura. Wouldn’t you rather a more robust solution which has a better chance of surviving through (at least) the next update?
 
Furthermore, the command-line tool I linked you to seems to do exactly what you want, is maintained, relatively popular, and should allow you to switch sources with literally one line of code. So why pursue the long winded slow solution which is likely to break instead of switching to the quick robust solution which is likely to continue working?

If you don’t have a working solution yet, don’t get married to a specific language. In particular, you’re using GUI automation to control System Preferences, meaning the approach is likely to break once you update to macOS Ventura because the app is being revamped.

There are Workflows to switch input sources as well as command-line tools which you can use and will likely continue to work with the update. The latter should be easier to work with too, since you’re likely to be able to switch to the specific sources you want with a single line in your Workflow.

Welcome to the forum.

Switching to Android wouldn’t do anything because I was talking about macOS, not iOS. But even if I were talking about iOS, switching to Android would still not do anything because as far as I’m aware it doesn’t have ubiquitous automations capabilities and no AppleScript. So essentially in response to “I’m unhappy about this thing in this platform” your suggestion was “switch to another platform which also doesn’t have the thing you want”.

I don’t want to switch to Android. I don’t like it. I don’t like everything about iOS either, but as a whole it fits my needs considerably better. But I don’t have any interest in flamewars; everyone should use what they prefer.

More importantly, though, I was wrong. Apple did not kill AppleScript when they introduced Shortcuts. They haven’t extended it either, but Shortcuts has direct support for AppleScript which proves they at least acknowledge it. And they do not require a developer account to share automations and there’s no indication they will.

It needs to be a built-in feature. Just like another tab in the Alfred preferences where you can purchase or download some new workflows. It doesn't have to be too sophisticated for now. I believe integration with Packal API will be enough. It just has to be really naive and simple for users to find new workflows and that's it. That's my thoughts.

Alfred has excellent documentation. For your daily sites Workflow, you’d connect a List Filter Input to an Open URL Action. To open apps should be similar, depending on exactly what you need.

Really useful! Thank you very much!

I see the usefulness in muting your microphone from a Hotkey, as it’s a way that should work universally across apps.
 
I’d be wary of calling it a way to take control of one’s privacy, though. Just like the Workflow can unmute the microphone programmatically, so can anyone else, which means muting it doesn’t offer any protection against those who are shady.

Intriguing! Solving a need I didn't know I had, will check it out, thanks for sharing!

Well, it is doing what you asked but I don’t know if what you asked for is correct. I adapted Dean’s code above which is expecting a name, not a URL. Does Music support playing a playlist from a URL? I don’t know; I never touched Apple Music (neither the service nor the app).

So you need to figure out what input Music needs to play the playlist, which you can do by reading the dictionary or searching online. My code showed you how to pass the argument to your code but you need to figure out what the correct argument is.

Alfred Workflow - Apple Music Playlist
This workflow was based on the information provided by MacStories in this post
Tired to check the page everytime I wanted to hear something new and also tired to find something new in a mess of Apple Music App, I imported manually each link and image to here.
So, just type "amusic" to see a list or "amusic+type" to select a specific list and choose inside it, for example "amusicplaces".
After choose, tap enter and the music app on your mac will be opened at the playlist choosen, just play and enjoy.
 
Feel free to edit and reshare.
Check it here https://github.com/gustavosaez/Alfred-Workflow-Apple-Music-Playlist

Alfred Workflow - Apple Music Playlist
This workflow was based on the information provided by MacStories in this post
Tired to check the page everytime I wanted to hear something new and also tired to find something new in a mess of Apple Music App, I imported manually each link and image to here.
So, just type "amusic" to see a list or "amusic+type" to select a specific list and choose inside it, for example "amusicplaces".
After choose, tap enter and the music app on your mac will be opened at the playlist choosen, just play and enjoy.
 
Feel free to edit and reshare.
Check it here https://github.com/gustavosaez/Alfred-Workflow-Apple-Music-Playlist

check this out: http://superuser.com/questions/172970/hotkey-to-mute-mic-on-mac-os-x
 
Make a new alfred workflow: Templates/Essentials/Keyword to script
 
For the keyword, make it what you want and set arguments to "No Argument"
 
double click on the script box and select usr/bin/osascript for the language
 
copy and paste the code on the page mentioned by 'tkneis' into the script area, save.
 
Now, This will toggle whatever your input is ... so, in system prefs, make sure your boom mic is set as input ... and the script will toggle it between mute and 100% each time you run it.

@Saez This is possible by changing the fallback searches here:
https://www.alfredapp.com/help/features/default-results/fallback-searches/
 
Cheers,
Vero