cocamon

Does anybody here have a functioning approach for syncing data between a multislider and a buffer~ inside of gen~? 

The syncing case I'm struggling with at the moment occurs when I try to resize the sequence length to a value that is greater than the current value. With the naive approach of multislider always writing to buffer that means that its impossible to preserve data from longer patterns (for example returning to a gate pattern with length 16 after one of length 8).

On the other hand if I avoid resizing the buffer and dump its data into the multislider each time I increase the sequence length, I run into the issue of narrowing down exactly that case to avoid creating a feedback loop where its unclear which of the two objects has the correct state

So, has anyone found a workaround to avoid maintaining both a buffer~and a multislider to make editable sequences in gen~? Or can anyone think of an elegant algorithm to determine when the multislider should write to the buffer and when the buffer should write to the multislider ?

Hi folks,

Does anybody here have a functioning approach for syncing data between a multislider and a buffer~ inside of gen~?     

The syncing case I'm struggling with at the moment occurs when I try to resize the sequence length to a value that is greater than the current value. With the naive approach of multislider always writing to buffer that means that its impossible to preserve data from longer patterns (for example returning to a gate pattern with length 16 after one of length 8).
 
On the other hand if I avoid resizing the buffer and dump its data into the multislider each time I increase the sequence length, I run into the issue of narrowing down exactly that case to avoid creating a feedback loop where its unclear which of the two objects has the correct state

So, has anyone found a workaround to avoid maintaining both a buffer~and a multislider  to make editable sequences in gen~?  Or can anyone think of an elegant algorithm to determine when the multislider should write to the buffer and when the buffer should write to the multislider ?




Hi folks,

Does anybody here have a functioning approach for syncing data between a multislider and a buffer~ inside of gen~?     

The ... 

gen-buffer-and-multislider-sequencer

sounds like a problem that could be solved by instituting some sort of 

 paradigm(preferably, the 'model' would be in the event realm(not buffer))... perhaps then, you could define your multislider as 'controller', and buffer as 'view' or vice versa...

one way to do this is simply to instantiate a separate data-space for the model(could be anything, even a dict or coll, to store the multislider-like data), then update both the multislider and buffer, only as needed, using data from that space. hard to describe(without seeing your patch), but hope it helps to make a little more sense.

On the other hand if I avoid resizing the buffer and dump its data into  the multislider each time I increase the sequence length, I run into the  issue of narrowing down exactly that case to avoid creating a feedback  loop where its unclear which of the two objects has the correct state

sounds like a problem that could be solved by instituting some sort of Model-View-Controller paradigm(preferably, the 'model' would be in the event realm(not buffer))... perhaps then, you could define your multislider as 'controller', and buffer as 'view' or vice versa...
one way to do this is simply to instantiate a separate data-space for the model(could be anything, even a dict or coll, to store the multislider-like data), then update both the multislider and buffer, only as needed, using data from that space. hard to describe(without seeing your patch), but hope it helps to make a little more sense.

I don't know if this helps for your use-case, but quite often in these situations instead of a multislider I use a waveform~ with the UI mode set to "draw" -- it offers a very similar interface, but you are directly modifying the buffer~ data itself.

You can set the draw mode to clip. You can also zoom the waveform~ view to show only a sub-region of the buffer~. It is pretty powerful.

I don't know if this helps for your use-case, but quite often in these situations instead of a multislider I use a waveform~ with the UI mode set to "draw" -- it offers a very similar interface, but you are directly modifying the buffer~ data itself.
You can set the draw mode to clip. You can also zoom the waveform~ view to show only a sub-region of the buffer~. It is pretty powerful. 

waveform also offers you a rangeslider functionality in addition. i´ve used this for years before switching to lcd.

it will require a buffer of the right length, but it doe not reqire DSP ON to output mouse movement.

waveform also offers you a rangeslider functionality in addition. i´ve used this for years before switching to lcd.

it will require a buffer of the right length, but it doe not reqire DSP ON to output mouse movement.


thank you to everyone for their replies. Graham, your suggestion is pretty much exactly what I'm looking for.

Gen~ buffer~ and multislider sequencer