Pause requires 'doubleclick' the first time

[kasbah]

Just to update on this. I have implemented "CC Off" and "CC On" binding types that are the equivalent of the "Note On" and "Note Off" but for CC messages. If Jesse is OK with it these should be in the next release.

[Ansible]

Just to update on this. I have implemented "CC Off" and "CC On" binding types that are the equivalent of the "Note On" and "Note Off" but for CC messages. If Jesse is OK with it these should be in the next release.

Cool! So then I could make a 'cc on' binding and a 'cc off' binding for pause, so that either one would trigger pause. Thx for implementing that!

[kasbah]

So then I could make a 'cc on' binding and a 'cc off' binding for pause, so that either one would trigger pause.

I guess it would make more sense if you could do it with one binding. It should really work that way already. I will look further into it.
By the way when I test this case, if I don't select the "SUS" options it seems to do an UNDO_ALL instead of unpausing. Have you experienced this?

[Ansible]

sorry for the late reply! No I haven't seen the 'undo all', but I haven't used SL in a week or two. I'm not a very advanced user, I'm not sure how I would recognize it if there was an undo_all event. But if I do see that I'll post here.

[kasbah]

I'm not sure how I would recognize it if there was an undo_all event.

The whole loop disappears and returns to the "Off" state.

[kasbah]

Another update. This was actually an issue with the way the GUI handled the binding. If you want a quick fix you can edit your .slb file and change the CC binding that looks something like this:

Code: Select all

0 cc 21  note pause 0  0 1  norm 0 127


to

Code: Select all

0 cc 21  hit pause 0  0 1  norm 0 127


If you change the binding though and save it then your change may be overwritten.

If you feel so inclined you could compile my development version where the fix is permanent (although the binding file will still need to be changed): https://github.com/kasbah/sooperlooper