NOTE: this is probably the last testing version before 2.0.0. Please test and report problems, application should be stable enough for everyday use. Any feedback is welcome!
Not sure what do you mean by 2 different packages on a channel.
If you mean two different ensemble configurations, then you do not need it with AbracaDABra as written by andimik. The application updates the ensemble configuration each time you tune the channel and on top of that it fully supports ensemble reconfigurations for audio services, that means runtime reconfigurations of the ensemble are no problem for audio services. You may only hear short dropout if you listen to the service that changes audio coding or subchannel capacity. On MP2 (DAB) it is typically even without audio dropouts.
Yes, this is by design. One channel means one ensemble. If it changes then the application updates service list otherwise it makes not so much sense in my opinion. If 12C is occupied by CRo then what would you do with SRG?
Could you please be more specific about the use case - what exactly you do and what you expect the app should do?
andimik is right.
I am sorry, implementing what you are asking for would mean redesign of service list handling and it would cause a lot of issues for "normal" users.
You can have more INI files each with service list that is valid for particular antenna configuration. Then you can run the application with specific INI file using --ini command line switch. I think this way you can achieve the behavior you want to have.
In theory yes, Qt6 should be supported, but I have no idea how to do it from Ventura. Does it mean that the Intel DMG I have released does not work? I have no possibility to test it, I have only MacOS Ventura running on Apple Silicon M1.
The current version only works with macOS Ventura. Even with macOS Monterey you get locked out. That was different with AbracaDABra version 1.2. This version still worked with older Macs. It's a pity that many users are not allowed to try out your new features. Apple's version policy is of course stupid and not environmentally friendly. Microsoft takes a similar approach and blocks many users from Windows 11. I would really appreciate backwards compatibility of your software.