Can you help me figure out how to make this device listen to incoming MIDI clock? It should be possible but the documentation is not very clear on how to do it. I am using the MIDI out of my Digitakt. Thank you!
I don't have the Digitakt but the MIDI clock is a standard signal so it should work the same. Does the SIG blue LED blink at all? If not, it might be a problem with connection or cable polarity.
@@gechologic Thank you for the quick answer, I appreciate it. The SIG LED is not lit or even blinking but I am able to pass midi notes from the Digitakt to the Loopsynth. However, my goal is to get the infinite looper to sync to the midi clock coming from the Digitakt. I can see in the settings leaflet a configuration for MIDI sync mode (first RST, then SET, then B3, then B3 again?) but for the life of my I cannot figure out how to activate this setting, even after hours of looking at the documentation and fiddling about. With all due respect, the user interface is not really intuitive or user friendly. It would not be such a big deal if the documentation is clear but that's not the case for this particular setting. I was really excited to get the Loopsynth to work with the Digitakt but it seems to be a huge challenge so I am now considering selling it unfortunately...
The website specifically mentions Electron gear as an example of a different world / logic / approach / workflow, that is deliberately left outside of the scope of compatibility for this project: "If, on the other hand, you already use larger gear for example from Electron, Ableton, Novation or Teenage Engineering's OP-1 or OP-Z, and you are not a collector, then my product probably does not have anything interesting to offer you. I don't know much about that group of synths and I am not planning to get any of them in order to figure out how to make my devices seamlessly compatible with them." Sorry if you missed that bit (unless your unit is 2nd hand). The red texts in the checkout screen are there for a reason, but I understand if it's too much of a fine print to read. However, implementing sync in the infinite looper would be quite easy, I just never thought about it - so thank you for the idea. The looper doesn't currently use the global tempo setting, like the other channels do which play chords and melodies but I guess it might work by adjusting the loop length to be an integer multiple of a bar length, or a certain amount of quarter notes, which might even create interesting polyrhythms / shifting beats, something like that.
@@gechologic I bought the Loopsynth second-hand but thanks a lot for the explanations, I'm starting to understand it better! Well if the MIDI clock won't sync directly from Digitakt, I could always try some kind of MIDI to CV sync converter. However, I now understand that the tempo sync is not implemented for the infinite looper loop length anyway - that's too bad (for whatever reason I assumed it was)! The Digitakt has no built in-mic so I was hoping to use the Loopsynth to easily bring some organic textures and DIY percs to otherwise dry sounding beats and, indeed, it would be awesome to experiment with the different rhythms/bar lengths! In my mind, that would fit into my workflow like a glove and I really like the way the Loopsynth sounds! Any chance the tempo sync will be implemented for the loop length at some point?
@@bonistik Thank you for explaining what you are trying to achieve. I think it is possible. This device typically does not use the external clock information, because usually there is nothing to trigger by each clock pulse (as it would be in a more traditional sound engine, which advances the sequencer or play head by each clock pulse, and triggers playback of notes and samples). And although changing the loop / delay line length is possible (with some minor side effects), I cannot imagine how it would be possible to make it to react to the clock information instantly, the closest thing I could figure out was to count pulses for a while, derive BPM from it, and then adjust timing accordingly at specific intervals. There is channel 222 (SD recording slicer) which uses the logic of cutting the sample playback / switching from one slice to another, once a certain amount of MIDI clock pulses is received. I'm going to reuse that same logic to reset play heads in the infinite looper. It will probably not be perfect as there will be side effects of shortening the loop (cutting some sound off) or lengthening it (which adds a bit of silence to the end of the buffer) but maybe the result will be interesting. There was not any update to the firmware in 2 years as I was busy with other things, also ran out of ideas a bit (at least those that fit into the available RAM and CPU power :) but have been working on it slowly, adding new sound engines and effects, there will be at least 2-3 new in the next update. Also, more direct controls for certain channels, e.g. possibility to control every single parameter in Clouds without need to use external controller or edit the patches file manually, as was suggested by users. So with your idea there will be enough new things to justify releasing an update. One was recently made for Loopstyler, so the Loopsynth deserves to be next :)
Great rhythm and great sound.
Great jam!
Just incredible :)
just wow
Need to update for this. You promised this Sync thing in the manual if i Remember....
Can you help me figure out how to make this device listen to incoming MIDI clock? It should be possible but the documentation is not very clear on how to do it. I am using the MIDI out of my Digitakt. Thank you!
I don't have the Digitakt but the MIDI clock is a standard signal so it should work the same. Does the SIG blue LED blink at all? If not, it might be a problem with connection or cable polarity.
@@gechologic Thank you for the quick answer, I appreciate it. The SIG LED is not lit or even blinking but I am able to pass midi notes from the Digitakt to the Loopsynth. However, my goal is to get the infinite looper to sync to the midi clock coming from the Digitakt. I can see in the settings leaflet a configuration for MIDI sync mode (first RST, then SET, then B3, then B3 again?) but for the life of my I cannot figure out how to activate this setting, even after hours of looking at the documentation and fiddling about. With all due respect, the user interface is not really intuitive or user friendly. It would not be such a big deal if the documentation is clear but that's not the case for this particular setting.
I was really excited to get the Loopsynth to work with the Digitakt but it seems to be a huge challenge so I am now considering selling it unfortunately...
The website specifically mentions Electron gear as an example of a different world / logic / approach / workflow, that is deliberately left outside of the scope of compatibility for this project: "If, on the other hand, you already use larger gear for example from Electron, Ableton, Novation or Teenage Engineering's OP-1 or OP-Z, and you are not a collector, then my product probably does not have anything interesting to offer you. I don't know much about that group of synths and I am not planning to get any of them in order to figure out how to make my devices seamlessly compatible with them." Sorry if you missed that bit (unless your unit is 2nd hand). The red texts in the checkout screen are there for a reason, but I understand if it's too much of a fine print to read. However, implementing sync in the infinite looper would be quite easy, I just never thought about it - so thank you for the idea. The looper doesn't currently use the global tempo setting, like the other channels do which play chords and melodies but I guess it might work by adjusting the loop length to be an integer multiple of a bar length, or a certain amount of quarter notes, which might even create interesting polyrhythms / shifting beats, something like that.
@@gechologic I bought the Loopsynth second-hand but thanks a lot for the explanations, I'm starting to understand it better! Well if the MIDI clock won't sync directly from Digitakt, I could always try some kind of MIDI to CV sync converter. However, I now understand that the tempo sync is not implemented for the infinite looper loop length anyway - that's too bad (for whatever reason I assumed it was)!
The Digitakt has no built in-mic so I was hoping to use the Loopsynth to easily bring some organic textures and DIY percs to otherwise dry sounding beats and, indeed, it would be awesome to experiment with the different rhythms/bar lengths! In my mind, that would fit into my workflow like a glove and I really like the way the Loopsynth sounds! Any chance the tempo sync will be implemented for the loop length at some point?
@@bonistik Thank you for explaining what you are trying to achieve. I think it is possible.
This device typically does not use the external clock information, because usually there is nothing to trigger by each clock pulse (as it would be in a more traditional sound engine, which advances the sequencer or play head by each clock pulse, and triggers playback of notes and samples). And although changing the loop / delay line length is possible (with some minor side effects), I cannot imagine how it would be possible to make it to react to the clock information instantly, the closest thing I could figure out was to count pulses for a while, derive BPM from it, and then adjust timing accordingly at specific intervals.
There is channel 222 (SD recording slicer) which uses the logic of cutting the sample playback / switching from one slice to another, once a certain amount of MIDI clock pulses is received. I'm going to reuse that same logic to reset play heads in the infinite looper. It will probably not be perfect as there will be side effects of shortening the loop (cutting some sound off) or lengthening it (which adds a bit of silence to the end of the buffer) but maybe the result will be interesting.
There was not any update to the firmware in 2 years as I was busy with other things, also ran out of ideas a bit (at least those that fit into the available RAM and CPU power :) but have been working on it slowly, adding new sound engines and effects, there will be at least 2-3 new in the next update. Also, more direct controls for certain channels, e.g. possibility to control every single parameter in Clouds without need to use external controller or edit the patches file manually, as was suggested by users.
So with your idea there will be enough new things to justify releasing an update. One was recently made for Loopstyler, so the Loopsynth deserves to be next :)
those patch cords
Candycords!
what is this magic?