I guess it depends on the content of a message.DSD team never get back, so, that is what happens. But that is their choice. I am sure they listen. But with lots of silly questions from begginers (I bet), they wouldn't have the time to answer back.
They surely replied to my email where I offered GUI development to them, they thought it was a good idea. They also said that TETRA support was something they intended to add in the future.
That might be my next step but it would require support from their side. For now it looks like I can get away with the keystrokes they already support and AutoIt function that sends keystrokes to a window.It would be cool to have a GUI that talks via TCP to FMP24 and DSD+ though.
SDR# uses way more resources than FMP24/DSD+ combination. It's perfectly usable on a normal laptop, but not so usable on a tablet, especially a small and weaker one. The goal of this project is to produce something comparable to handheld radio scanner so I'm using a cheap Windows tablet as a computer running DSD+.Tip: There is a plugin for SDR# that works with DSD (via virtual cable)...
I've tried using it with SDRuno (software working with SDRplay radio receiver) and DSD+ and it kind of worked, but the UI wasn't very usable on a small touchscreen and CPU usage was a bit high. IMO it's also an overkill to use a full blown SDR software to just perform a function of a radio scanner.
It is fine for some people, just not for most people. Most people don't want to learn to use software unless they really really need to.User interface is fine as it is. It is friendly enough a dummy like me can get it going![]()
To use FMP24 easily one has to remember the command line switches AND all the keyboard shortcuts. Is it possible to learn them all? Yes. Should everyone do that? Not sure, probably no.
In the modern world GUI is the most popular way to interact with computers (including mobile phones, tablets, etc) and there are good reasons for it.