vitor

Sorry for the delayed response.
This sounds like your Mac has problems executing the Swift script.

Have you installed the Workflow from the Gallery (https://alfred.app/workflows/tobiasmende/audio-switcher/) or from the forum?

I thought the requirements are pre-installed in the modern Mac versions, but maybe some requirement is missing. This might be solved by running `xcode-select --install` on the command line.

This is vey much untested (I have neither Pro Tools nor a keyboard with numpad), but what I was suggesting was something like:
 
const systemEvents = Application("System Events") const keycodeNumpadMap = { "0": 82, "1": 83, "2": 84, "3": 85, "4": 86, "5": 87, "6": 88, "7": 89, "8": 91, "9": 92, ".": 65 } function run(argv) { argv[0].split("").forEach(character => { systemEvents.keyCode(keycodeNumpadMap[character]) }) systemEvents.keyCode(76) }  
This is using /usr/bin/osascript (JavaScript).

Should also be worth considering joining both workflows together for the next version, so people only have to install one. Or (I just thought of this while writing the previous sentence) even having a Script Filter that both shows the battery and allows for connecting and disconnecting (you shouldn’t be able to know battery levels anyway when AirPods are disconnected, I’d guess).

If you have an alternative icon, that would be helpful to further differentiate from the other AirPods workflow too. It surprised me a bit when I downloaded the Connector yesterday, as the icon in the notification was different from the one in the workflow.

Thanks and apologies - I’m new here and didn’t know that there was such a thing.

good point. and very fair. thanks for the info.
 
 
well that was making sense for me to bundle it in the Workflow when it was only available from me and through GitHub, so that users had nothing to think about. but with the Gallery uniforming the Workflows installs, maybe users will get used to those notice about having to install the dependencies or that some dependencies are already bundled. so that changes things a bit and i'll have to rethink what's the best now. will depend on what i plan for the future, but my first feel is that the Gallery is the first place to go for Workflows, so that will influence my choice quite strongly. thank you! those notices are super welcomed.
 
 
ha excellent, thank you again! haven't touched those Workflows for a while and moved quickly onto other things. so great new knowledge. will digest, and most probably end up updating the Workflow. thank you again Vitor!

Not exactly, as the workflow already used Python 3, only the path changed so everyone’s on the same version. That break sometimes happens after a macOS update.

@vitor looks like it was fixed in the latest version of Orion RC. Sorry for the trouble!

Not exactly, as the workflow already used Python 3, only the path changed so everyone’s on the same version. That break sometimes happens after a macOS update.

just wanted to say that Alfred is amazing! super quality build, precisely customizable, and my absolute daily driver for everything. amazing app, thank you!

@Tee Elem See how to use the debugger.

Also @rdjfraser, make sure you’re using the fork by @giovanni and not the original by Dean. Same for the other thread.
 
Use the versions in the Gallery for both.

That is insane.  That was it!!!
 
I really like the TV and Movies workflow.  It's extremely useful.  I had no idea it had a bug.  I followed the steps in the linked thread and BOOM, it's fixed.
 
Thanks Vitor!
 
Brian.

The workaround I've settled on for this is to make macOS treat the non-retina display as retina, by forcing the Scale to be 2x (rather than 1x).
 
There are pros and cons to this approach, but it solves many visual problems so I'd say "it works for me". YMMV
 
https://blog.gingerbeardman.com/2024/01/25/running-modern-macos-on-non-retina-displays/

Add an Arg and Vars Utility with one file path per line in the argument. Connect it to a Split Arg Utility splitting on newlines to arguments (not variables). Connect that to the Automation Task.

Thursday, February 1, 2024 11:57 AM
 
Thanks for the reply folks.  

Stephen_C  I used your suggestion after I figured out that I had to have the YouTube URL on my computer, i.e. link on desktop.  I could not just open Safari then YouTube and copy or drag the link over to Alfred. In the end I figured it out, thanks a lot.
 
Vitor  I will have to investigate your tip and read up on Automation Task. Thanks also for taking time to reply to my request.
 
This is a great forum to solicit assistance.

To open a new window specifically, there’s an Automation Task for that.

Indeed there is. Right click the Script Filters and in the context menu, near the top, you can disable “Treat Input as Universal Action”.

i see. clearly the Workflow and/or 1Password are not the culprit yeah. it's my own setup that's doing something weird. as stated in my response to Vero, it may be possible that it's 1Password not connecting to their own services when i'm on a VPN. 
 
 
true, thanks. i would tend to avoid old software that are not maintained anymore tho. the path 1Password has chosen is the path they have chosen. that's fine. honestly if it was still making my day to day life better i wouldn't mind. the issue i'm currently having is not only related to the integration with Alfred, but to 1P itself that, for me, is making worse and worse UX decisions (requires more clicks to login etc.). anyways, thanks for taking the time. glad the Workflow and the integration usually do work well for thousands of users!

The challenge here is that this workflow has thousands of users but no other reports of this issue. Because you’re a power user (a programmer, even), it both means you know what you’re doing and we can discard the simpler stuff, but it also increases the possibility that something seemingly totally unrelated and external is causing the issue.

It is very much worth noting that 1Password 7 continues to work as well as it ever did, even on Apple Silicon (does not require Rosetta), and as such the deprecated 1Password 7 bookmarks feature in Alfred’s preferences should too.

For reference, it doesn’t have to be JavaScript. While JSON did start from JavaScript, every major language nowadays handles it. At the end of the day it’s just text with a specific structure, you can even write it by hand.
 
 
In the dte Script Filter, delete the last line and add instead:
 
cat <<EOF { "items": [{ "title": "$(get_day_of_week "$input")" }] } EOF  
For more information, see Script Filter JSON Format or the Getting Started example workflows (press + on the bottom left, in the workflow list).

The fuzzier the search, the bigger the performance implication. Have you considered a workflow with a Universal Action (keyword “mail”) connected to an Action in Alfred set to Jump to Mail to…?

For reference, it doesn’t have to be JavaScript. While JSON did start from JavaScript, every major language nowadays handles it. At the end of the day it’s just text with a specific structure, you can even write it by hand.
 
 
In the dte Script Filter, delete the last line and add instead:
 
cat <<EOF { "items": [{ "title": "$(get_day_of_week "$input")" }] } EOF  
For more information, see Script Filter JSON Format or the Getting Started example workflows (press + on the bottom left, in the workflow list).

Yes. You shouldn’t need those anymore. Reminder, as @Vero pointed out above, to not let an uninstaller clean Alfred’s files as they will likely delete what’s needed for Alfred 5 too.
 
Glad you’re sorted, have a nice weekend!

HA! Well now I'm embarrassed. Sure enough, it was a workflow I made that used the "Launch Apps/Files" and I’d put the path to the Alfred preferences in Alfred 4.
 
Apologies all around. Thank you @Vero and @vitor!
 
As a PS..should I remove Alfred 3 and 4 just in principle?

Go to the Gallery and type "learning” into the search box. Download a few of the resulting workflows and look through them. You can learn quite a lot from the way in which those workflows are constructed.
 
Stephen