Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


smirky last won the day on November 18 2016

smirky had the most liked content!

Contact Methods

  • Twitter

Profile Information

  • Location
    Portland, OR

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

smirky's Achievements


Member (4/5)



  1. Generally yes, although it's not a great solution for a released tool (assuming you're just an amateur coder like me). My understanding is that there are ways to do this via GUI Scripting, but that's an unreliable way to program things for use by other people. It's susceptible to breaking suddenly and very difficult to keep updated for anyone outside of the person who creates it. Any time Apple makes even the slightest change to their UI, the steps are broken. It's also difficult to maintain across multiple versions of OSes because I think you'd need to have every major OS version available on a testing machine to ensure that you cover everyone's needs. My old workflow for syncing devices via iTunes got killed off because of this - Apple moved that function to Finder and now it's not scriptable other than via GUI scripting. If you wanted to build something that was specific to your local machine, I think that Automator might get you there. I haven't used it in a long time, but that's where I would start.
  2. As suspected, this is an issue with how the Mac OS restricts interactions between iTunes/Music, Airplay devices, and the keyboard buttons. I found a Github project that appears designed to address this exact issue but I've not had a chance to test it out. Hopefully this will help you! https://github.com/alberti42/Volume-Control From the project's ReadMe:
  3. Thanks, I'll do a little more research but it sounds like you're describing a limitation within Airplay, Music, and Mac OS not something related to the workflow itself. Happy to try and fix something related to the workflow if that turns out to be the issue. I'll follow up when I find more info on the topic.
  4. Hi esceef, thanks for this info. I may have to do some research on this use case and possibly ask for your help in troubleshooting since I don't have a HomePod to test with. Can you confirm that when you select HomePod using only the Airplay button in iTunes (attached image) and not changing the system Sound option, you're able to change the volume using just the keyboard? I have a feeling there's an issue with how the iTunes Airplay setting interacts with the system Sound setting that might be outside of the current functionality of this workflow to handle without a huge re-write. I'll cross that bridge if I come to it.
  5. Thanks again, Vitor, really appreciate the input. I've created a new thread here:
  6. Submitting this workflow for possible submission. Let me know if you have any questions. If anyone can offer a Retina screenshot, I would greatly appreciate it! I am the author of this workflow. A link to the discussion is here. Hosted on Github here. How to use: The default method is "toggle". This will toggle the state for only the selected device. The typical use for this would be if you have more than one device that you like to have turned ON at the same time (i.e., listening in the main room and a second room). If you prefer to use only one device at a time, change the default method in the variable window to "select". This will toggle ON the selected device and toggle OFF all the others. The typical use for this would be if you prefer to listen on only one device at a time (i.e., listening through computer speakers or headphones). Two modifier actions are provided: You can choose to use the non-default method at any time by actioning on the device while pressing the 'option' key. This will cause Alfred to run whichever method is not the default. Holding 'control' will allow you to action a device without closing the Alfred window. This works well if you're often toggling more than one device at a time. The 'esc' key will need to be hit when you're done.
  7. I've thought about that and tend to land on not changing the name, although I'm 100% open to anyone's thoughts on best practices and improved clarity. My main reason for not changing it is because "Music" could be potentially confusing in regards to the workflow's scope. Unfortunately, "Music" might imply that the workflow can affect any music software that you're running instead of specifically "Apple Music". By that same logic, a better name might be "Apple Music Airplay Toggle" or similar. That had previously seemed too lengthy of a name for such a simple workflow, but now I'm starting to warm to it. I'll make the requested update, possibly with the new name, and post to the other thread shortly. Thanks again!
  8. Thanks Vitor, that would be cool. I don't have a retina display available so I generally avoided the idea of submitting my workflows. If someone was able to share a screenshot or two, I could add them to the ReadMe and make the update in #1 above all in one shot. Should I create a new thread in the other subforum for ease of tracking this? I'm happy to do that as well.
  9. Just posted an update to this workflow that gives you a keyword option in the workflow configuration page. This update should get pushed to your device via OneUpdater or you can grab it direct from Github. Let me know if you run into any issues! https://github.com/dotson/iTunes-Airplay-Toggle
  10. Hi Matthew! The simplest way for now would be to add your keyword to the first Script Filter action, see the two screenshots below. A better long term solution would be for me to add the keyword trigger and allow the user to customize it in the settings so that it stays after future updates. I might be able to work on that this weekend. Until then, the solution in the screenshots should do what you need just fine. Let me know if you have any questions!
  11. Well that’s super weird, sorry about that! Does the workflow work as expected but also triggers Parallels or does it not work at all plus Parallels opens up unexpectedly? Can you post the output from Alfred’s debug window after you run the workflow? What’s your Mac OS and Parallels version? I’ll see if I can mirror those and replicate this locally to sort it out.
  12. Just pushed an update based on your request. Give it a shot and let me know if it works for you. You'll just need to change the default behavior from "toggle" to "select" in the variables section, per the About This Workflow page in Alfred. Please let me know if you have any issues or other ideas on improvements! https://github.com/dotson/iTunes-Airplay-Toggle
  13. Thanks for the update, glad to hear that it's working for you! That feature should be fairly simple to implement and there are a couple ways to go about doing it. One is to allow a key option such that using it would toggle all choices rather than the one specifically chosen (i.e., action using shift-enter to make this one active and the others inactive). This would allow both the existing function and additional function to exist all at once. Another would be to let the user set which is the default type of action (i.e., set the variable in the preferences). I think it'd be possible to do both at once, so you could tell Alfred which choice is your preferred default ('individual toggle' or 'switch to') and then have the other option be chosen with the special key combo. I'm going to play around a bit and see if I can make that work.
  14. Hi, yes! I still maintain this workflow as regularly as possible via the github page linked below. The current version works with Catalina but you can grab an older version if you haven't upgraded yet. Let me know if you're having any trouble with the current version and I'll help fix anything needed. https://github.com/dotson/iTunes-Airplay-Toggle
  15. Just pushed an update to Packal and Github that hopefully fixes the above preference issues.
  • Create New...