On 11/03/2014 08:28 PM, Ted Felix wrote: > Ah! I hadn't thought of that. That does sound like a better first > step. A new "all-numbers" mode.
It would have a lot of applications. The issue doesn't come up often, but every time it does, there has never been a satisfactory answer. > It might be activated by a special tag in the "all-numbers.rgd" file. The all-numbers.rgd and raw-numbers.rgd files aren't actually complete, and don't really work properly. It would be a lot cleaner to go with a solution that rendered these files obsolete. It could be as simple as filling in a number whenever a slot is empty. In the current scheme, the great strength and the great weakness of Rosegarden is that to be able to transmit "artifact n" to a synth, some string for n has to be defined in the studio. No string, n isn't even presented as an option. That lets you make neat work of cleaning things up where there would be a lot of big gaps between few useful things, but it requires you to fill in strings in advance for anything that might potentially be useful. When I tried to do that hack back in the day, I couldn't work with the resulting XML file with 128 * 128 + 128 entries in it, which is why there's something incomplete about one or the other or both of those files. (Details forgotten, sorry.) It was just too big. I could almost certainly overcome those limitations today, several processor generations and gobs of RAM later, but it still strikes me as grotesquely inefficient having to define almost 17,000 things that are mostly useless. Long and short: If we had a mode to show and allow access to everything, whether it's filled in with a string or not, I think we could solve the problem at runtime pretty inexpensively. I'm not quite sure what implications this would have for saving and loading files, and particularly what compatibility issues it might present. It's always seemed like the sensible way to go to me, but I hit some road block trying to implement it once upon a time. Deal with that, then it makes a lot more sense for a device definition to be highly specific the way you propose. Load the DX7 device, everything not actually available on the DX7 is inaccessible, and if you want to gain access to that stuff, change the device to something else. > This could then evolve to offer new modes that remove the checkboxes, > disable bank selects, etc... The original Bank/Program combo/checkbox > presentation would still be available for those who really want it. A > "Classic" mode, perhaps. I'm thinking everything should default to the legacy mode until someone otherwise specifies by editing the .rgd file to use one of the newer modes. If one of these new device level flummies is checked, hide the legacy controls, otherwise carry on as always... Talk is cheap though, and once again I'm just talking without actually digging in and looking at anything specific. -- D. Michael McIntyre ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
