Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


godbout last won the day on May 17

godbout had the most liked content!

About godbout

  • Rank

Contact Methods

  • Twitter
  • Website URL

Profile Information

  • Location
    Macau/Hong Kong/South China/France
  • Interests
    Code. Design. Swimming. Climbing. Reading. Writing.

Recent Profile Visitors

953 profile views
  1. sorry just need to pass by to say that i cannot live without this Workflow. all my love to you taco man ❤️
  2. can you try with this version: https://github.com/godbout/alfred-airpodspro-connector/releases/tag/1.3.0 also i'm not sure why it's showing up with my own AirPods in your log lol. my AirPods mac address shouldn't be exported. check in the variables if you have a mac address. if yes remove it and try again.
  3. ok so there's an incompatibility with bluetoothconnector 2.0.0: https://github.com/mariuskiessling/alfred-airpods-connector/pull/3 will update the Workflow today.
  4. it seems it's trying to find my own AirPods Pro lol. ok gonna have a look, thanks!
  5. any info from the debug panel?
  6. good point, i didn't think of this. but i don't think it comes from this. i had the same issue with my Time workflow. i think it's just the script getting called multiple times, and the time to process the query and generate the item. but i might be wrong? see with the Time workflow below: if you type like a maniac (like i do, i type my stuff and return immediately) then the script misses what you typed during the last few milliseconds. now i use a PHP package that i made to build my Workflows because i kept forgetting how Alfred works 😂️, so that's totally possible that i'm missing something and my package (or the way I build the Workflows) could be improved. let me know if i'm missing something. any hint would be deeply appreciated!
  7. new version 1.1.0. i've tried several ways to show the current volume. the good thing with a Script Filter is that i can show the current volume as a subtext. the (very) bad thing is that it takes some milliseconds to register the typing. happened several times that i entered for example 65 and only 6 is registered, and sometimes nothing. in terms of UX it kinda sucks. so i decided to go through a notification. maybe altogether it takes about the same time, maybe even longer, but the whole thing feels more responsive. so, to my taste, more enjoyable. to get the notification with the current volume, just type `mv` (the new keyword) and enter. to choose your new Music.app volume, type `mv 65` or `mv up` or `mv down`.
  8. ok so after using it myself i found out that i would like to know the current level of the volume. currently you can get it through a notification but you need to update the workflow to allow for empty argument. it works but i'll add this as a subtext later.
  9. i had to dig into bash, unix, a couple of unix tools, and two books about scripting 😂️ but there's a new version. i understand the code better now, cleaned it, and added the Case battery level if available: https://github.com/godbout/alfred-airpodspro-battery have a look and let me know if you guys still have any issue with wrong data being printed out. thanks!
  10. i've made a Workflow to change the Music.app volume rather than the system one: maybe this topic can/should be moved to feature suggestions?
  11. change the volume of the Music.app from Alfred. useful if you're using AirPlay devices. GitHub: https://github.com/godbout/alfred-music-volume Packal: http://www.packal.org/workflow/alfred-music-volume enjoy 🌻️
  12. of course one hour after i had the idea that maybe Alfred was lowering the global volume instead and yes. i think it would be still nice to have the possibility to set the Music app volume to any % but well, not a bug.
  • Create New...