SooperLooper feet setup

Hardware
61

I saw that bit you also spoke at the end of allocating other functions to switches or pads. .

62

You mean this comment? SooperLooper feet setup - #55 by Baggypants

Then it would be 10 buttons
Rec, overdub, mute toggle 1-4, channel select 1-4.

1 Like
63

But you can’t do that at the moment. Mute toggle only works on the selected clip.

Clip selection would need to send the same CC with different value.

[Edit] You could cascade commands, e.g. select clip and then mute but how to toggle???

64

7 buttons then :wink:

65

How did you do it in the ui with the per-channel mutes?

66

How to toggle indeed…

67

The “widget” drives Sooperlooper directly with OSC messages but the presentation to Zyncontrollers is not parallel and that is currently the only way to map MIDI bindings.

68

so I made a quick edit, assigning commands to the 4 buttons.
The settings were:
hostname = ‘zynthian.local’
port = 9951
Do you have it set up the same way? I’m assuming your hardware will have some kind of liblo library. Liblo-python connects by target = liblo.Address(hostname, port)
In speak of PedallinoMini https://github.com/alf45tar/PedalinoMini/blob/master/images/webui-options2.png
set this:

Remote host/ip: zynthian
port: 9951

On zynthian I set up a channel with superlooper and sent these commands

/sl/0/hit mute
/sl/0/hit record
/sl/0/hit reverse
/sl/0/hit pause

It worked without any problems.
Again for PedallinoMini https://github.com/alf45tar/PedalinoMini/blob/master/images/webui-actions.png
I would try:

value: record
osc address:  /sl/0/hit

Here I see a weak point in the configuration and I would contact the people behind the project if they could better describe the OSC communication.
If I look at you pick up signal,

21:34:03.015 | RECEIVE | ENDPOINT([::ffff:192.168.0.13]:57296) ADDRESS(/sl/0/hit s:undo) INT32(0)

so I think it should be

21:34:03.015 | RECEIVE | ENDPOINT([::ffff:192.168.0.13]:57296) ADDRESS(/sl/0/hit) STR(undo)

Conclusions:

  • ping is not necessary for one-way communication
  • somewhere you have an error in the controller settings
  • since I don’t have a PedallinoMini, I can’t give you more advice.
2 Likes
69

I think your conclusions are good, that my message is not formated the right way.
And Zynthian CUIA osc is working only because… There is no space nor special characters.

On a side note : the documentation of SooperLooper is quit bad and not soooo helpful :no_mouth:

Edit: I use 255.255.255.255 to be able to snif the messages, and pedalino does not allow to put values other than 0to127… I does not look to value in case of osc messages

70

Need advise, a step by step instruction of triggering MIDI learn for Mute.
I have no problem of using MIDI learn for other functions except Mute.
For MIDI learn I quickly press top right button, after that I use touch screen or rotate a knob, and do the same on a MIDI keyboard, but not the mute in the sooperlooper.

71

Stable or oram-bookworm?

72

Stable

73

It seems to work here. Enter MIDI learn mode, select mute, send CC - MIDI mapping is done. Be aware that mute operates on the currently selected loop. There can be up to 6 loops (channels).

[Edit] It looks like the stable release has mute CC binding inverted, i.e. sending CC with value 0 enables mute and sending with value > 63 disables mute. This is resolved in Oram.

74

Nice to see that the sooperlooper story still goes on. It was getting a bit quiet on the other thread.

I got my hands on a UNO 2 chip for my fcb1010. Now I can program every button to my own taste.
button 1 - select loop 1 - toggle between rec/overdub/play
button 2 - select loop 1 - mute
button 3 - select loop 2 - toggle between rec/overdub/play
button 4 - select loop 2 - mute
etc.

This way you can operate it like a boss rc300.

2 Likes
75

I’m still trying to figure out how to erase a track. I assigned midi CC 21 to undo/redo and send: value 0 to it. But that only erases the last recording.

I’d rather clear the whole thing and start from scratch. Is there a way to do that?

76

Nearly one year after : Hurray ! I’ve made my FCB1010-PedalinoMini working, and can use SooperLooper with it !
But now i’m wondering how to “sync” everything ? I’ve touched the “Global Sync 1” and “2” pages without noticing any change.
What does “sync to Internal / Midiclock / Jack/Host / None Loop x” means then ?

And how to resync a track after a pause ?

Ps : I still think about a dedicated pedal, let me use SooperLooper and I’ll do my best to have a great thing.

77

This decides what some actions (like record) will be triggered by. A common workflow is for the first loop to be the leader and subsequent loops to follow it, e.g. will start to record when the first loop restarts to play at start of loop. This is the default for the first preset which has sync to = Loop 1.

None would give completly asynchronous behaviour with operations like record starting immediately they are requested by the user.

Jack/Host will synchronise with the internal clock. This can be useful if you want Sooperlooper to synchronise with the sequencer, MIDI player or other processes driven from the internal clock. Note that this requires the internal clock transport to be running which only happens when the sequencer or MIDI player is playing. (This is something we plan to visit in the next major release after Oram.)

MIDI Clock will sync with an external MIDI clock. I’m not sure how well this works as Sooperlooper requires MIDI clock input for this and we may block that. (I don’t remember.)

Internal means the internal clock generated by Sooperlooper. I am not sure this is of much use in our implementation, but haven’t investigated too far.

To start a track in sync with the sync source, e.g. when Loop 1 restarts, click the trigger button in the UI or operate the trigger parameter.

2 Likes
78

Oooh I have some that wrong.

Very precious informations here ! That explain a lot, there is a precise workflow !

I will try the “trigger” thing with the pause button too. And go re-read the SooperLooper manual too.

Note that as we can only have one SooperLooper instance, I’ve set it to the master channel, and then I’ve put my drum (sequenced) channel in direct output, so it does not goes thru SooperLooper. It’s great to discover workflows, I hope this tip will give you fun moments

1 Like
79

You can add SL as post fader effect To any existing chain.

80

Another way could be to create a group to which you send the chains you want to include in the looper. Add an audio chain with sooperlooper in it, disable audio input and route each other required chain to the group chain instead of main output.

There are many ways to achieve similar results, each with benefits and limitations. I am glad you are using the chain output routing - this is why we added it.

1 Like