This is very true. Roland, in particular seem to be notorious for doing very little in the way of updates to existing product lines. They clearly maintain the culture of their hardware manufacturing roots.Yes Powder wrote: ↑Thu Oct 10, 2019 12:23 pmThat sucks, but this isn't new behavior for Roland- or the industry in general.
This is exactly why you should never trust hardware that has a software element to it.
And if you ever must get a piece of gear that relies on software running on another device, plan on never upgrading that device again.
This is the main reason that favour hardware. It doesn't arbitraily stop working. I can switch on my Korg Prophecy and it works as well as it did in 1995.
There are some products that I am using, including AIRA Modular, that are hybrid but as a general rule, I avoid them.
Open sourcing of code is not always possible, for many reasons. Commercial reasons have been hinted at, but there are also licensing issues. When Sony originally killed AIBO, people wanted them to open the codebase. I met one of the developers who said that this wasn't possible because of licensed components that they had used.
Re-compiling aged code is problematic and most musicians won't do it, but somebody might if it becomes annoying enough for them.
The OP may be able to get the Aira Modular editor working by buying an old Android tablet to dedicate to it. You can also sample the messages that come out of the headphone jack to store known patches. You can play them back from with any sample player.
In the case of the AIRA modular editor, I don't think that commercial considerations would be holding back release of the software. I doubt that the editor contains DSP secrets, it just sends re-configuration information. It wouldn't surprise me if it does this over MIDI, as the device implements USB MIDI Control channels (but it's not class compliant, so it still remains dependent upon the drivers).