thank you for all the effort and the great work you put in Zynthian. It is a lot of fun to use and a very versatile tool.
I hope you can help me with the following problem. I would like to use the Nektar Pacer to control the SooperLooper but if I want to assign a button to the switches on the Nektar Pacer they don’t get recognised. I checked in Admin/MIDI Input Devices that the Nektar Pacer is recognised. But instead of using the specific switches they just play notes instead of getting assigned to the right function. I saw that someone in the forum was able to set up the Nektar Pacer to control SooperLooper. But I couldn’t find a description how he did it.
Welcome to zynthianland! I’m happy to know you are enjoying the device.
Regarding your question, currently, zynthian controllers/switches can’t be learned to MIDI notes.
You should reconfigure the nektar buttons to trigger CC events instead of notes. Then you would be able to learn your buttons to the sooperlooper switches.
thank you for your reply. That’s exactly what I want. If I use the Nektar Pacer in Bitwig Studio it is not playing notes so the configuration must somehow be changed inside the Zynthian. But how to do that? How can I configure it that the buttons trigger CC events? It shoud be that way by default.
I had a setup with SooperLooper and Nektar Pacer that worked ok. But since then i hav had other things on my mind and i cannot be of specific help right now. But i haave this feeling (i got when i mooved the Pacer from one place to another) that i will soon get into it again. Maybe the week after the one starting tomorrow, as then kids are back in school, wife back at work, me free from work, and i have some time for myself.
I remember, my Pacer delivered CC to Zynthian/SooperLooper and i did some rather complicated setup in the Pacer editor (web based as i remember) to be able to scroll through the five loops, start, stop, rec and overdub them on so forth
Thank you very much. I appreciate it. I was hoping the Nektar Pacer is plug and play like my Launchkey Mini or at least easy to map. It would be great to use it for the SooperLooper. That would be a winning team.
The Pacer is very configurable which means plug and play is not simple because the Pacer may be configured for a wide range of behaviours. You want to configure the Pacer to send one CC per switch. A different CC number for each switch. Zynthian can be configured for momentary or toggle switches. You will have to decide which makes most sense but I suspect it will be momentary. (This probably means you can’t use the Pacer’s LED indicators.)
“Plug & play” behaviour does not depend of the device, but the specific driver included for your DAW that makes the magic. We have zynthian drivers for some devices but Nektar is not in the list currently. Perhaps some day manufacturers will include zynthian drivers for their devices Until then, we depend on someone from the community having the device, the skills and the motivation to create the drivers.
When no driver is available, the only way is using MIDI learning and for this to work, you need to reconfigure your Nektar to send MIDI CC instead notes.
I’m available whenever i start fiddling with mine again, but rusty (as mentioned)
I think it is worth it to put in a little effort to how to program your Nektar. It’s a versatile pedal, and i know that when i get around connecting mine again i will surely find other uses for it that just SooperLooper.
I encounter a new challenge. Any switch triggers the action only as long as I push it down. So for record or pause I have to hold it the whole time and it switches off immediately when I lift the food from the switch. Is there a way to change the settings so a one time push is triggering the action until a new action is done?
thank you. Now it is working. I’m very happy that I can use it now Is there a possibility to assign a switch to the “add loop” function? Since it is a non-physical touchscreen button I can’t use the encoder to assign it. Is there a workaround?
Yes, there is a assignable button called “loop count”. But if I assign a switch it doesn’t work. It seems it needs a round robin like encoder for assigning but not a switch. But no worry I’ll see if I figure it out.
As i recall, it is possible to load a user preset to SooperLooper, and that can have 5 (max number) loops already, and then you just use how many you need. I’m quite sure i was quite pleased with that way..
Indeed, you could just add all 6 tracks to start with and save as a preset to act as a template. In fact, I wonder why we even bother with variable quantity of tracks. Should we just have all 6 all the time?
Until then, we depend on someone from the community having the device, the skills and the motivation to create the drivers.