Actually, on SDC web site it says 15.25, but in fact, when you click on Mac version it gives you 15.24 - this one should work. If not - just find me on Telegram testers and I will send you the version I am running (it is 15.24)

With graphics - OK. Well, iMac should run much much lower... Not sure why it is like that.

On Pro - just get Thunder (or USB) to Ether adapter - we all running on adapters with Macbooks.

Hi Pavel

Found 15.24 and works a treat with EESDR 3. You've been very helpful, saved me a lot of head scratching today.
Now I have confirmed SDC working with the alpha and the alpha working on the iMac I guess the way forward is to take the plunge.
Before I do that I will check V2 on my old backup of OSX running on this machine. What makes my suspicious is I have an app called
Snagit which also makes the fans run. What did we do with all our time before computers?
Take care Pavel and thank you

73 de Rob GØHFN

Happy it went well, mate.

Regarding versions - hard to say. Too many options.

ESDR2 was developed on order version ov the Qt framework - with different set of audio/video drivers loading). When trying to run it on latest OS - I would expect backward compatibility, but...

ESDR3 - build on latest Qt framework, all modern OS bells and whistles supported. So it has more chances to run on latest OS more reliably.

That above might be one of the dozen reasons. Or may be something else.

Brilliant. The latest version of ESDR3 seem to run fine (no fans) without update the firmware. Sometimes the audio glitches but all good as a test!
Enjoy the rest of your day Pavel and thanks again

Hi Pavel

Just thought you would be interested to know. I used a backup copy of macOS Monterey on this machine, earlier version 12.4. Esdr2 worked fine without sucking up resources. So I updated the image to macOS 12.6 and it still works fine. So there is something wrong with the current version loaded into the internal drive on this machine.
I am quite pleased we found the issue but I suspect it will mean an OS reload to fix it. Anyway, should someone else have a similar issue, you have the info.

Thank you so much

73 de Rob GØHFN

Hmm... interesting...

By any chance, did you have earlier any software, which might be using common ESDR2-3 command port range (UDP 50000-50001)? From known SW it includes Anydesk, IC-9700 comms software (there might be some other which we yet to discover).

What I have in mind - potentially even deleted, conflicting SW might leave traces in .plist and other settings, which were cleared by backup restore.
There definitely has to be an explanation of that behaviour, freeBSD structure is quite transparent (apart from what Apple did to it )

Also - settings!!! - that might be an issue. I do not recall exactly the version, but in ESDR2 I had to remove old settings directory and .plist while moving from one update to another (update 7 to 8???, do not remember).

Settings location /Users/[username]/Library/Preferences/Expert\ Electronics and /Users/[username]/Library/Preferences/eesdr.com.plist
Usually in Mac it is good practice to have screenshots of all settings in app and delete those two above while moving from one major version to another.
What I mean, if you were using ESDR2 (say) update 3 and then jump to update 11 - there is high risk some setting might be in conflict

Hi Pavel

The good news is a fresh copy of Monterey has fixed the issue completely. So delighted.( I had removed all the plists I could find before going drastic)
I can't think of any software that may have messed the ports up. The backup SSD actually had more on it. One thing that crossed my mind is I had
ELAD software loaded (deleted). The Sunsdr, replaced the ELAD, so who knows? Maybe? . So its just reloading all the apps now.

Good outcome

Thank you for all the suggestions

73 de Rob GØHFN

Well, complete OS reinstall, perhaps, most radical way, but often does the job.

BTW, you do not need to delete all plists you found. In particular case of ESDR, this file contens recorded app windows resolutions and coordinates for the Launcher and Main window, plus main directory path (see attached screenshot). (BTW, not sure if the path is in use).
The reason for deleting it is because in some cases (example: when resolution elements has been changed during development of new ESDR version) the old version dimension sizes may become incompatile with new version -> this may lead to App crach. To ensure crash not happen on this reason - we just deleting plist and it is re-created automatically on App windows new launch.

ELAD - not sure, never used it. Unless there is documentation explaining what ports it is using and whether it records them into startup scripts, we may only guesstimate. However, there is no mystery - what we are after is to ensure that no other SW, except ESDR, uses UDP range 50000-50004

And regardinng Firmware - do not be confused, you can certainly, upgrade-downgrade it with no issues, It is absutely mandatory to use corresponding FW when using one or another version od ESDR. However, there are couple tricks - for example discussed plist, which need to be deleted prior switching ESDR version. The reason - because it is same filename for V2 and V3 and, say, V2 may not be happy launching while using V3 plist.

Hi Pavel

There is only so much time I can spend searching for the problem. In this case, faced with a certain fix it was easier to cut my losses and reinstall.
All working now. Many thanks for the info on plists. I doubt very much if I will use V3 until it enters beta as I unfamiliar with the ESDR and
need to confirm what is normal vs alpha/beta behaviour.

Many thanks

73 de Rob GØHFN
Devon England

I thought SDC was for Windows only. Os there a MAC os version? I’m

CW Skimmer is Windows only, SDC is also MacOS.
73 de Rob GØHFN