02-08-2019, 10:39 AM
Darryl,
Snapshot solves a few issues and/or makes the NDLR more user friendly device.
Assumption: I call "global setting" as “session" here
Here we go:
1. Snapshots helps with a compartmentation of a session
I have one session (song) with a few snapshots: Bridge, Chorus and Verse
2. Not enough slots: With the current capability saving 8 sessions, allows only 3 “songs”..with each having 2 parts or modulation settings.
3. Easier access
My approach involves two steps:
a) encoder push
b) black button push
so two actions required (Assuming you’re in the R mode for snapshots (arrow pointing sideways) which when you perform you will)
Current approach:
a) click Menu button
b) click the 8th encoder
c) pick a session (rotate #1 encoder)
d) shift + 5th encoder push to load session
4. Two snapshot types provides Variety; 2-3 choices of modulation setting over 2-3 choices of panel setting
This way I can have “nuances/timbres" of "modulation snapshots" for Bridge, Verse or Chorus “panel snapshots” thus allowing 9 combination
5. Utilizing another session slot with only 1/4-1/3 partial parameter changes ? ;
Having a slightly altered session to save to another session slot is a long discussion but since you’re also coding this (so you wear the "coding hat”
) I can use “a coder analogy" here.
Your suggestion to copy to another session is the same as when coder does copy and paste code. All good in short run but then,.... Your first version will not get the refresh/changes made to second session. Oh... so then we copy the new over to the old one, hmmm... see where is this going ? (BTW I have a lot of groove boxes where I can save sequences to another slot but I don’t do that. Just for this purpose: parts of my newer version (second session) are better and NEEDS to be MERGED with original (first session)
The snapshot only takes panel/modulation parameters which is 1/3 of all data in a session for panel OR modulation settings
Again if memory of NDLR is the issue you don’t have to give us 3+3. 2+2 is much better than 8 sessions
What do you think
Snapshot solves a few issues and/or makes the NDLR more user friendly device.
Assumption: I call "global setting" as “session" here
Here we go:
1. Snapshots helps with a compartmentation of a session
I have one session (song) with a few snapshots: Bridge, Chorus and Verse
2. Not enough slots: With the current capability saving 8 sessions, allows only 3 “songs”..with each having 2 parts or modulation settings.
3. Easier access
My approach involves two steps:
a) encoder push
b) black button push
so two actions required (Assuming you’re in the R mode for snapshots (arrow pointing sideways) which when you perform you will)
Current approach:
a) click Menu button
b) click the 8th encoder
c) pick a session (rotate #1 encoder)
d) shift + 5th encoder push to load session
4. Two snapshot types provides Variety; 2-3 choices of modulation setting over 2-3 choices of panel setting
This way I can have “nuances/timbres" of "modulation snapshots" for Bridge, Verse or Chorus “panel snapshots” thus allowing 9 combination
5. Utilizing another session slot with only 1/4-1/3 partial parameter changes ? ;
Having a slightly altered session to save to another session slot is a long discussion but since you’re also coding this (so you wear the "coding hat”


The snapshot only takes panel/modulation parameters which is 1/3 of all data in a session for panel OR modulation settings
Again if memory of NDLR is the issue you don’t have to give us 3+3. 2+2 is much better than 8 sessions

What do you think