Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
App to throttle CC messages?
Hey all,
I'm using my TR8s to sequence and CC control Tekno, it's mostly working great. But....
If turn a knob or slider on the TR8s too fast then Tekno chokes/stutters, I'm presuming it's too much MIDI data.
So, does any one know of an app that can Throttle CC data, but still let it some of it though?
Streambyter? Moziac?
Thanks!
Andrew.
Comments
https://apps.apple.com/us/app/cality/id1448694455
Cality is one of my favorites for “throttling” if I understand the usecase you’re looking for. There’s a bundle on all their apps right now, and they’re all pretty fantastic/“worth”
Thanks for the suggestion. Ah, I do have that app (picked it up for free by completing there bundle)
I just tried it and probability in Cality only works for mid Notes, but not CC sadly
Im not sure cality can throttle CC midi data. It plays with midi notes in an unconventional way, but if memory serves it doesn’t have any midi monitoring or midi cc filtering capabilities.
I’m guessing Mozaic would fit, if someone has developed a script. On the Loopy Pro Wiki, see top of forum page, and go to the Mozaic page someone took the time to categorize every mozaic script. You can check to see if they have something for filtering the midi cc data. There’s also several hardware specific Mozaic patches. However first you might need to do some troubleshooting to discover the root of the issue.
If I understand you correctly… you believe your hardware controller is sending too much midi data to Teckno when you move your hardware knob or slider too quick?
It could be, it could be several things, maybe something the midi controller is sending, or it could be the app it was just released could be a minor glitch, etc... not sure, but several possibilities.
My first suggestion would be to plug in a free Au midi monitor, place it in the midi fx chain. Inside a host, set up, Controller into AU midi monitor, into Tekno. That way you can see exactly what is going on midi wise when you turn the knob. That should at least give you an idea of where the issue is stemming from, or what to focus on, before considering another option.
Hi. "Too much MIDI data" is unlikely unless you have a very old iPad. MIDI controllers only sample knob positions periodically, sending the position at the sample time. So the app won't see every value as you turn the knob rapidly. You can check this with a MIDI monitor. It's more likely that the Tekno app doesn't handle large changes in parameter values very well, so the solution may just be "don't do this". An app like Streambyter could rate-limit value changes but that would be a band-aid solution, not a fix.
Can you show us the CC data with timestamps while turning a knob/slider using the Protokol MIDI monitor (small font please, to see enough messages)?
https://patchstorage.com/datareducer/
Hmm. Nothing at that link.
The link works for me.
Basically the 4/4 bass drum should stay on the beat, but when CC is received the notes are late. Note Tekno sequencer is turned off. If I sequence from Tekno then there is no problem when lots of. CC. Here is a video of the issue:
https://drive.google.com/file/d/1NqBfURgj2UgDz95odxxW0VHyphkwnSIN/view?usp=drivesdk
Seems not to be a public link
Oops, ok try link now
To get a sense of the data density, I suggest using Streambyter since it logs each message and includes a timestamp
Here is video with streambyter:
https://drive.google.com/file/d/1O6VWtyKbokazXzO2COBv_NBGiobeD12m/view?usp=drivesdk
[EDIT] I just tried the same set up with Brambos Noir and it behaves exactly the same as Tekno does, i.e. notes are out of time, so I think we can rule out that the issue is with Tekno.
That's highly abnormal behavior. It almost has to be from some other cause or people would be blowing up the forum with reports of that problem with Noir.
What happens if you filter out Sys Real-time, Sys. Common, and Sys. Exclusive in AUM's channel settings?
[edit] NVM. I watched the video again and see that the problem seems to be unrelated to that.
What is sending the midi?
The OP says TR8S.
Sorry, missed that. My eyes are dilated and reading is a chore right now. 😂
It would be interesting to know if this is seen with some other external source. It sounds a lot more like a problem getting the MIDI to the iPad with good timing than it not being processed properly once it arrives.
Thanks for all your thoughts and responses.
@wim ill give data reducer moziac script a shot this weekend.
FYI I’m using Bluetooth WIDI master to send from TR8s to iPad. I’m going to try Wired MIDI and USB cable to see if WIDI is the issue, I dont think it is though.
Also, it looks like TR8s CC midi is high resolution so 16384 as opposed to just 128.
iPad is A16 chip I think, circa 2021.
I’ll hopefully report back once I’ve had time this weekend.
I do.
I believe the TR8S MIDI CCs are conventional 7-bit, according to this document.
So, issue solved…I have a WIDI thru6, which was inadvertently connected to my iPad as well as the WIDI Master. Once I discovered and disconnected WIDI Thru6 and just used WIDI Master, all is working as expected 👍🏻💪
You were right @wim , defo Bluetooth. But I feel like a bit of a muppet for not noticing double Bluetooth sooner 😂
I'm glad you got it worked out. I wouldn't have thought about double routing either. It's bad enough when there are cables to follow without all that stuff zipping around through the air. 😎
💡Ahhh ... so that's probably why the midi values appeared to be 14-bit as well eh? 💡