I understand the request, and if there is a growing demand, I will certainly improve the remote control for MambaNet. But now now, as I have a huge backlog of features/projects that have higher priority.
What’s really puzzling for me - this basic “one way” MambaNet support has been around for several years, since 2014, and I actually implemented it according to the requirements specified by D&R. So I was under the impression that it was “good enough”. And actually noone ever asked for an improved interface - in all these years! What happened so that several people are suddenly asking about it?
I guess mAirlist is now considered a serious playout system. Most axum/axite users are (considering the price range) professional (local) stations. They use other systems. Maybe just because of their integration, maybe because the sellers promote them. Like Aeron is (as far as I know) very frequently used with Axum.
Maybe the improved (custom) skins make it more interesting for ambitious radiostations to use mairlist in their studio. It looks more appealing.
Since the prices of the Axum/Axite dropped, its more affordable for Mairlist enthousiast to buy a digital D&R solution. Since mairlist is (under another name) the preffered player for d&r, people expect brilliant hardware/software integration. Although, I did.
For me it’s pretty painful that the Airlite that I used is far more capable in interacting with mAirlist than my pricey new Axite.
But I understand you have to prioritize.
Maybe the Airlite owners are a far larger part of your targeted clients.
If you want to take Mairlist to a higher (sales) level, I would suggest you to pick another default (dark) skin and make it more compatible with higher end mixers like the AXITE and AXUM.
The cooperation with D&R started with the Airence, and then the Airlite, back then, and of course we put a lot of work and effort to make these remote controls the most powerful and convenient in order to promote our products.
Noone ever talked about the Axum or MambaNet until there was this request to add basic support for it a while later; and actually also not after that.
My impression during all these years was that the (original) Axum was considered a niche (or even almost discontinued) product. We do have a lot of professional users with digital consoles, but most of the time that would mean DHD, Lawo, Axia or maybe Wheatstone. I can’t remember when I last saw an Axum in the wild. In other words, the Axum didn’t seem to be sold alot (anymore).
Now it seems that D&R offers this new “Axite” variant, with a modernized surfe, a Dante card and a lower price? Fair enough. And of course we will see how we can improve the remote control support.
But as I said, it takes time and effort, and we have tons of other new features on our to-do list (you mentioned a few), so I do understand and accept your request - but it will take some time.
I found out where to put the background scripting…
But the sensors are not visible in Axum/mambanet.
I guess they need to be created/addressed by mAirlist the same way the actuators are addressed.
Somewhere mairlist tells there are 64 actuators. At the same way mairlist should tell there are 64 sensors I guess.
I’m sure a d&r technical genius can tell you more.
But at this moment axum/mambanet isnt aware that a script van send sensor signals. So nothing can be set at the Axum side.
Got an error:
Runtime error “List index out of bounds (5198049)” in background script D:(…)\mambanet-stopplayers.mls, handling message: PLAYERCONTROL_STOP 7CD1F4A2735A1531 00 00000000 00000001 244,875 ?
Ok, invested some time to check this again. I originally implemented the sensors as parts of the existing actuator objects, e.g. combined actuator/sensor objects. Which is allowed according to the documentation, there is even an example for it
Anyway, I changed it now so that the sensors are separate objects. There should now be a total of 128 objects, 64 actutators and 64 sensors.
This is in the latest snapshot 4459, can you please have a look?
Disclaimer: I had to change the code quite a bit, hope I didn’t break anything regarding the (working) actuators, so be prepared to downgrade if there is an issue. As you know, I am unable to test it here.