Liveslice - track clear

[shamann]

Any chance that when a user hits the clear track button, it could actually clear the track instead of leaving a bunch of empty slices on each beat? Is there a reason that I'm missing for the function as it currently is?

Also wondering, if I've used the auto-slicing with sensitivity set to max, is there any way to add a slice marker without losing the current slice config? If my max is at 36 and I bump it up manually to 37, all the slices readjust to equal spaces, rather than stay around the peaks and valleys. I guess it might be hard to work around this, but maybe some way of selecting a slice and then splitting it (i.e. add a marker inside a slice)?

[Juanjo]

From the manual:

- About clearing a track in the Arranger:
"To clear the contents of all events press the clear button. To completely remove all events, press clear with the right mouse button."

- About adding a marker in the Slicer:
"New slices can be added with CTRL+LMB." (LMB is Left Mouse Button)

[shamann]

Excellent! Thanks.

You know, since I was on the original beta team, I kind of forget that there's a manual. Shame on me.

Still I wonder, what's the benefit of the default clear function, are there times a user would want all those empty slices in there?

[shamann]

Damn, that does the trick exactly. Wish I'd known sooner. Must make a mental note to look at the manual once in a while for new stuff.

[Juanjo]

Still I wonder, what's the benefit of the default clear function, are there times a user would want all those empty slices in there?

From the manual:

"Empty events can be handy when randomizing or sequencing midi. You can use the the events control to a number of evenly spaced events to a track. Empty events can also be useful for doing unusual time signatures. You can do 11/16 by setting beats to 4 and events to 11, and then just add slices to the empty events."

[ohm]

Still I wonder, what's the benefit of the default clear function, are there times a user would want all those empty slices in there?

You have me wondering too the intention was that empty slices are handy when randomizing, and they were neccesery before the snap was implemented... I will reverse the LBM / RMB functionality so that LBM does a full "clear" and RMB leaves empty events behind

[shamann]

I will reverse the LBM / RMB functionality so that LBM does a full "clear" and RMB leaves empty events behind

[ohm]

forgot to implement this in 1.43 - will be in 1.44.