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.
Mimix volume pot muting channels-help!
So, I could be doing something wrong but I have 5 faders on my controller assigned to control the level knobs of the first 5 ports of Mimix(each loaded with a different sound app coming from AB). For some reason, when I slide the fader to the third port to adjust the volume of that app, at a certain point it mutes all of the channels. Any assistance would help.
Comments
Should have mentioned that I'm using an M Audio Code 61 controller.
could you post a screen snap showing MIDI Learn mode?
Here's what I have dwarman.
Is your controller new? Have you a midi logger? Try t find what messages you are sending.
You've got some duplication on some of your cc values...
The problem is, as @Cassetteur stated, that You have some controls that has the same CC value set. If You set the CC of a knob and a button to the same value and set the knob behavior to let's say GM, that will mean if You move the fader on the controller lower than halfway it will turn that button off, and if You move it past halfway it will turn the button on. When the button behavior is set to toggle, each slight movement will toggle the button also.
So please make sure no two controls have the same CC value set in MiMiX to avoid this problem. Yo can change the individual CC values in MIDI learn mode by selecting the button or knob and pressing the red + and - buttons next to it.
yeah, port 3 level and port 6 solo are the same. why were they changed from the clear default sequence in the first place btw?
Thank you guys for the help. The controller is new and I have the manual so I will check it out. I now see that some parameters are set to the same number. I have no idea how they were changed from default. I am new to midi mapping, so I was relying on midi learn. I would select a knob on Mimix then move one of my sliders and it would automatically map it. Also, when I try to change the cc value, it will change, but then it goes back to its original value when I move that fader... Not sure why?
To fix the learnt value You must exit MIDI learn mode by tapping on the setup screen in the right top corner. You will see all knobs and buttons will show the normal red outline. While an knob ur button is selected, all other conrols will show a pale red outline and the selected control will change to the CC is sees every time You touch something on Your controller. There is a manual for MiMiX here: http://ttrgames.hu/mimix/mimix_manual.pdf - i hope it clears things a bit if You didn't read it already.
Read some parts of it, but must admit not all. Thanks a lot! this definitely makes sense, I will get back at it.
Probably you used and mapped to the same CC to two different parameters.
Because since you don't have a controller with a double sided MIDI data transfer which will be updated seamlessly with the controlled device[you move a fader on your controller and it will assign a new value to the assigned parameter, then you adjust the same parameter with something else(mouse, a different controller, etc), your device will update your controller and mirror-move your fader] but due to the fact that controllers are meant to control rather than being controlled it happens that as soon as you move your fader, which position wasn't updated from your device, it will send a message coherently with its position.
A little example[MIDI common messages range from 0-127, which are also the keys in a grand piano]:
You adjust your fader to set the sustain of your synth to 100%[MIDI value 127]
Then you find it sounds better with a setting of 50%[MIDI value 64]so you adjust it from it's interface, leaving your controller on its own.
Later you decide your synth, while playing in the background, will kill it if only sustain is at 40% but in that very moment you are very busy at playing the best guitar riff ever so during a short pause you move your fader, which was untouched since you set it at 127, and BANG! Your lovely plucked bass sound now is a evil speaker blower sound.
What happened when you moved the fader is that little son-of-a-fader, in the moment you moved it, sent a message to the sustain starting from where it was, aka MIDI value 127. Knowing that MIDI is a digital signal you'll also know that your sustain will move according to the signal to which is linked, which in that very moment is saying 126, not 64-1.
This is most of the times with some continuous rotary knobs which are effectively sending a incremental signal.
Now that's what the "Knob Pickup" feature supposed to address. When turned on, the knob will only move if the MIDI controller sends a value that is close to the value the knob is currently set.
Ah! Didn't see that knob pickup feature, think I'll implement that to play it safe. Sorry for all of the newbie questions, but here's one more
Do I need to set the parameters to specific cc numbers if I'm trying to control let's say all Mimix levels from my midi controller? Or am I fine with the default numbers provided I don't repeat any?
(I have all of my apps on different midi channels and I am switching between them from the controller, but I just want a level control for each one so that I can keep the volumes for each app balanced for live playing).
There are two ways to set this up. One is to set Your controller to the CC values of the default MiMiX settings, the other is to teach MiMiX to the CCs already set on Your controller. Most of the time the former is the harder since a lot of controllers have either fixed setup or can be modified via external programs. So the latter way is the preferred one since it's pretty straightforward - choose level knob on port1, move fader 1, choose lever knob on port2, move fader 2 etc. When finished, check other knobs and buttons You don't want to control and change the conflicting CCs so there is no overlap. Also, there are 4 MIDI setup presets in MiMiX so it is possible to set up 4 different controllers if needed.
Good to know. I'll keep it in mind when I'll get mimix.
Once you are switching channels you can also double cc numbers. CC are also channel exclusive.
But anyway here is a generic midi chart which could help you sorting out which CC could be better then others, which will probably be mapped(sparing you some work at mapping everything all the time).
And read the F manuals, they're always filled with useful infos and hints&tips&tricks. When provided, in the appendixes, there is a midi chart listing which parameter are already linked(you won't always be able to remap knobs and stuff). And consider that channel 10 is usually intended for drums(iElectribe can't switch from that for example).
About reading manuals(not quick start guides): loved the synthesis cookbook at the end of Waldorf's manuals. I'm always happy to study some kind of theory besides proper instructions.