01-14-2021, 05:24 PM
(01-14-2021, 11:07 AM)Jesse Johannesen Wrote: Good question, to give a little insight into save slot data, for every feature that is an on off choice it takes 1 bit, plus 1 bit for each save slot (x8) for each feature that has multiple choices you need enough bits to accommodate those (if pad range has 32 possible settings for instance you would need 5 bits) and 8 times that number for the saves (40 bits total for our pad range demo) The NDLR saves basically every setting for the save slots, so as you can see it adds up.
While the idea sounds enticing, it would require a major redesign of the software architecture which isn't something I can see likely at this point. Not to say it won't ever happen, just that I wouldn't plan around it. I'll log it as a feature request though and run it past Steve next time we get together.
Sorry Jesse, I didn't realise that was the internal structure for the data.
You have obviously jammed it all into a really small space.
Looks like the NDLR is as it stands, which is a great device.
Royce