02-01-2019, 09:20 AM
I know Darryl said that the NDLR chip has some limitations with memory when I asked to save more than 8 “System" setups
I’m not sure if “teensy” is on a separate board inside of the NDLR. If yes then we could just pop-in a more powerful teensy board.
If teensy is on the main PCB then I would pay (kickstarter) for “upgrade” to better CPU with more memory. SO we can get less latency when using as MIDI THRU and get more setup slots. And I would call them session slots.
Also the setup slots could be alphanumeric (yes I know more bytes per slot) so I can have them as SONGS or sessions.
How about having "floating storage boundaries" for the biggest memory consumers: rhythmic pattern, melody pattern, setup slots
For example I hardly use melodic patterns, But I do a lot of rhythmic patters so I could use more memory for rhythms and setup slots)
Thanks!
I’m not sure if “teensy” is on a separate board inside of the NDLR. If yes then we could just pop-in a more powerful teensy board.
If teensy is on the main PCB then I would pay (kickstarter) for “upgrade” to better CPU with more memory. SO we can get less latency when using as MIDI THRU and get more setup slots. And I would call them session slots.
Also the setup slots could be alphanumeric (yes I know more bytes per slot) so I can have them as SONGS or sessions.
How about having "floating storage boundaries" for the biggest memory consumers: rhythmic pattern, melody pattern, setup slots
For example I hardly use melodic patterns, But I do a lot of rhythmic patters so I could use more memory for rhythms and setup slots)
Thanks!