Loopback 2.4.x, and xdax and wsjtx NOOP in Sonoma and Sequoia...how to fix this ?????

K3SF

HI all

i run xdax and acat and loopback ans wsjtx on allmy macs whihc include minis ( intel and M1) and macbook air (M1)…i run Mostly Sonoma Macos onthe mini and now have run Sequoia on macbook air…

I am unable to get xdax and loopback and wsjt to work properly in transmit in sequoia . Al indicator show i need to give xdax mic privileges. But there is no way to make that happen. and i have not hear back from Mario who develop xdax.

So sequoia is xdax/loopback killer.

Now in Sonoma , i update from 2.3.x to 2.4.x loopback..once again xdax/loopback and wsjtx do not work in transmit…. i revert back to loopback 2.3.x and all works well again…

so now i am convince maybe loopback 2.4.x is the culprit after all and not xdax.

rougue ameba has not been able to resolve this issue either…after many (4) beta versions i have tested for them…

so if there are any Mac user that have loopback v2.4.x and xdax and wsjtx working in Sonoma please let me know what you did to make it work in transmit.

Even more important is there are any Sequoia mac users, that run xdax/xcat/wsjt and loopback…what is the secret sauce you used to make it all work

any info would be greatly appreciated

Paul K3SF

Mike WA7IJV

Hi Paul,

W/r to Sonoma…

As you may recall, I “work around” the xDAX TX issue by running xDAX inside a Terminal window. Still works on my M2 mini running Sonoma 14.7.1 with Loopback 2.4.

Earlier, wasn’t sure if the workaround required Terminal to be in the Microphone list.

Now convinced Terminal must be in list for xDAX-via-Terminal to work.

To get Terminal into the mic list (if not in yours), I think one needs to do something that gets MacOS to ask if Terminal should be added.

I’d try running an app in Terminal known to MacOS to use the mic (such as fldigi or wsjtx). But, not xDAX, as MacOS doesn't know it needs access.

I believe this could be tried without upgrading back to Loopback 2.4 (if you are presently at 2.3):

1) Launch Terminal

2) Run fldigi or wsjtx via Terminal’s “New Command…” to see if MacOS will prompt you for Terminal mic access. For example: /Applications/fldigi.app/Contents/MacOS/fldigi (or wsjtx)

If successful, MacOS should display dialog asking about Terminal mic access (perhaps also listing the app running in Terminal). If it looks right, allow.

If Terminal is now in mic list and "on", try running xDAX using Terminal’s “New Command…”: /Applications/xDAX.app/Contents/MacOS/xDAX

W/r to Sequoia…

Only minor success on Sequoia 15.1. Requires Loopback 2.4. Using Intel T2 mini.

Sometimes can launch apps (except xDAX) from Dock. Other times, can only launch apps via Terminal (SmartSDR, fldigi, etc.).

Typically, things run fine for some tens of minutes. Then, SmartSDR and xDAX freeze. Usually can be restarted, but will later freeze, again.

Mike WA7IJV

K3SF

hi Mike….

I tried your work around…didnt work out for me…

guess i'll wait and see what new from next version of sequoia

One good thing i found out is that macssdr works fine in sequoia even its dax function which i have been able to get loopback to work with properly…

i will continue to use my macbookair M1 as test bed

but

operational mac mini's will stay on Sonoma till i get the Macbook air working the way i like with Sequoia

and

i wont be in any kind of rush to get new M4 Mac Minis either ;-)

thanks again

Paul K3SF