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.
Comments
Thanks for the reply ccs2.
Still a bit confused about the Apple Camera Connection Kit/Adapter. The one that I see online is a 30 pin but I have an iPhone 7 with a Lightning connector. Is there a way to use the 30 pin version with the iPhone 7 or do I need this one perhaps? https://www.apple.com/shop/product/MD821AM/A/lightning-to-usb-camera-adapter
I can see from you linked post that there is quite a bit involved in your set up! It's going to take me awhile to parse through all the information in your post but perhaps I might start by weeding out the apps you mention that I won't need. For my purposes I'd just be using Quantum's MIDI OUT to control external MIDI synthesizers and Quantum's MIDI IN driven by an external MIDI controller to control Quantum's 16 faders (in velocity mode). I wouldn't be using any other iOS apps in which case I'm assuming I wouldn't need AUM, Audiobus or AUFX as they all deal with iOS audio, correct? That leaves the two MIDI routing apps MIDIFire and MIDIDesigner. But is there a reason to use both, or might I be able to use just one?
You’re better off getting this one, which allows you to charge the iPad at the same time.
https://www.apple.com/shop/product/MK0W2AM/A/lightning-to-usb-3-camera-adapter
What @wim said, @morbank.
(it has midi)
You should check out Audiobus3 at least
MidiDesigner Pro 2 is very sophisticated and versatile. You map your controller and it translates to the options in Quantum, one of which is to select individual sequences, and notes, etc.
(MidiFire has the advantage of creating a virtual midi port for re-routing back to the hardware.)
@morbank
Hi All , I was a betatester for the year before Quantum release , when I decided to go off grid for various reasons ...
anyways , as I believe it was in part my 01V96 (!) investigations that contributed to the control output coding & mention of 01Vs I felt obliged to re-appear from my lurking on reading this to clarify , so .. details follow :
yes ,as proof of concept it is possible to do as you suggest & more, but the Yamaha 01V range of mixers’ midi implementation is deceptive , disappointing & ultimately probably not worth it for the hassle & sacrifices necessary
Firstly , if referring to 01V first gen - notice it annoyingly only has 15 faders .
I had recently upgraded to 01V96 , so hoped to enjoy full 16 faders ..
however the BIG problem is that the much advertised 4 Midi control pages CANNOT respond the motorized Faders to Midi CC IN :
only the Audio Layer’s page faders respond !
So that means sacrificing audio channels for motorized midi control ,
on the 01V96 this was at least feasible as there are 2 audio layers , so by setting this up my 32 channel desk becomes a 16 channel desk , with the 2nd layer 17-32 stripped of any audio routings to exclusively control & respond to Quantum .
Then there is the issue of having to reprogram the Control Change Assign Table in the 01V Midi menu ; whilst Quantum has midi learn you will have to reprogram all the faders & buttons on the 01V that you want to control whilst also removing the default settings for the audio layers control ... or Quantum will play havoc with your mixer audio . It is possible & I did it ! but there are hundreds of parameters to navigate .
I was also disappointed to discover the 01V Control Table is Global , I had assumed it was per preset , so you cant just change back to the default or other settings for automated mixer use without having to perform midi sysex dumps / loads .
On the positive , you can also use the Select buttons for Mutes with illuminated feedback (but not the Solo buttons ! ) & the banks of User Assignable buttons can be used to navigate around Quantum , switching between Racks , parts , parameter lanes etc , & yes with Faders & illuminated buttons updating parameter feedback .
As proof of concept it worked pretty well* & was fun to use along with the headaches of setting up & learning how to use , although I am no longer giving half my studio mixer channels over to it so this info is from bleary mists of rusty memory .
So whilst I commend the hard work Tony put into this aspect of Quantum , it was the Yamaha midi implemenation that let down my hopes of using it this way , & I still hope to find another motorized controller to make better use of external control **.
(* some scaling issues on a couple of lanes IIRC)
(**especially as the on screen new Skip buttons make using Mutes more difficult now IMO )
@ ccs2, Ok I’ll take a look at AudioBus3. Do you disagree with wim’s Camera Kit/Adapter recommendation?
@ Wally (see below)...
Hi All , I was a betatester for the year before Quantum release , when I decided to go off grid for various reasons ...
anyways , as I believe it was in part my 01V96 (!) investigations that contributed to the control output coding & mention of 01Vs I felt obliged to re-appear from my lurking on reading this to clarify , so .. details follow :
Thanks for jumping back onto the grid to clarify!
yes ,as proof of concept it is possible to do as you suggest & more, but the Yamaha 01V range of mixers’ midi implementation is deceptive , disappointing & ultimately probably not worth it for the hassle & sacrifices necessary
Firstly , if referring to 01V first gen - notice it annoyingly only has 15 faders .
Yes, I did notice that. 15 is a very odd and inconvenient number!
I had recently upgraded to 01V96 , so hoped to enjoy full 16 faders ..
however the BIG problem is that the much advertised 4 Midi control pages CANNOT respond the motorized Faders to Midi CC IN :
only the Audio Layer’s page faders respond !
Ouch. That is unfortunate. This is exactly the kind of information I am looking for. Definitely something I’ll have to try to look into with any other potential 16 motorized fader controller candidates.
So that means sacrificing audio channels for motorized midi control ,
on the 01V96 this was at least feasible as there are 2 audio layers , so by setting this up my 32 channel desk becomes a 16 channel desk , with the 2nd layer 17-32 stripped of any audio routings to exclusively control & respond to Quantum .
Interesting. The 01V96 may be overkill for me as I wasn’t planning on using the audio mixing features in my set-up.
Then there is the issue of having to reprogram the Control Change Assign Table in the 01V Midi menu ; whilst Quantum has midi learn you will have to reprogram all the faders & buttons on the 01V that you want to control whilst also removing the default settings for the audio layers control ... or Quantum will play havoc with your mixer audio . It is possible & I did it ! but there are hundreds of parameters to navigate .
I only plan to use the 16 motorized faders on the controller so I guess I’d mostly be removing the default settings as you mention. Was this process complicated or just time consuming, or both?
I was also disappointed to discover the 01V Control Table is Global , I had assumed it was per preset , so you cant just change back to the default or other settings for automated mixer use without having to perform midi sysex dumps / loads .
Also unfortunate. However, as I mentioned I wouldn’t be using the mixer aspects so I wouldn’t need to switch back and forth.
On the positive , you can also use the Select buttons for Mutes with illuminated feedback (but not the Solo buttons ! ) & the banks of User Assignable buttons can be used to navigate around Quantum , switching between Racks , parts , parameter lanes etc , & yes with Faders & illuminated buttons updating parameter feedback .
Yes, Mutes, Rack Switching, Parts, (Solo would have been nice), etc. would be very cool. The only essential feature for me though is the 16 “total recall” style motorized faders.
As proof of concept it worked pretty well* & was fun to use along with the headaches of setting up & learning how to use , although I am no longer giving half my studio mixer channels over to it so this info is from bleary mists of rusty memory .
Very much appreciated, bleary or not!
So whilst I commend the hard work Tony put into this aspect of Quantum , it was the Yamaha midi implemenation that let down my hopes of using it this way , & I still hope to find another motorized controller to make better use of external control **.
(* some scaling issues on a couple of lanes IIRC)
(**especially as the on screen new Skip buttons make using Mutes more difficult now IMO )
You mentioned finding another controller, have you looked into any other suitable candidates? As mentioned, I would be happy with a pretty bare-bones set-up as my only real requirement is the ability to have the 16 motorized faders with updated parameter feedback. I wonder if the Behringer BCF2000 might be an option. Of course I’d need to chain two of them together which might complicate things. And judging by the BCR2000 I have the build quality probably isn’t very good. Does anyone here have any experience using Quantum with the BCF2000?
Cheers
Hi, @midiSequencer I'm still getting odd things when using Quantum => Audiobus midi => ApeMatrix. notes are getting through but with zero velocity. Not sure which app would be at fault here but not noticed this behaviour with another sequencer yet.
Having some problems with actions as well. After applying and playing they keep disappearing from the list, saving and loading snapshot doesn't help. The snapshot disappears too. Not sure if this has been changed but I don't remember actions behaving like this before.
alright, I see what's happening here. It's the first time I've tried applying actions in loading "versions" in the list which also have their own different actions list. Maybe we also need an "overwrite" for the versions because when you save a version it becomes a new one and it gets quite confusing if you want to sequence them.
edit: Yes I think the actions should auto-save for the version you are creating for. Unless you save a new version the actions will disappear when you load a different version number. I think this is a bit messy for workflow. Anyone else sequencing versions with actions?
Welcome @morbank
We (ios music peeps) often use "CCK" or "Camera Connection Kit" as a (now) generic phrase meaning "USB interface dongle thingie for iOS devices". Back in the proverbial day "Camera Connection Kit(CCK)" is what Apple called its USB adapter. They don't call it that anymore but they are the same thing. You definitely want the one @wim suggested if keeping your device charged while using it is important. If that doesn't matter (you know you're only going to use it out in the field or something), you could save a few bucks by getting a non-charging USB adapter. Whatever you do, accept that Apple surcharge—off-brand copies are known to cause more issues than the 10 bucks worth of 'savings' is actually worth.
Also, welcome-to-the-forum bits that might be helpful...
You can quote someone by clicking the Quote button at the bottom of a post or by manually adding a
>at the beginning of a line.> like thiswhich will render like this:
Also, if you want to mention someone (so that they get a notification) make sure there's no space between the @ symbol and the username.
@ morbankwon't work but @morbank will.Thanks for these details. I have a Roland VS-2480 that is doing nothing but taking up space. It has MIDI I/O and automated faders (and a dedicated 'MIDI Controller' mode). I've been meaning to give a Quantum setup a serious go but haven't carved out the time because it all felt a bit nebulous. Your breakdown, though largely 01V specific, is very helpful/informative.
@syrupcore
Thanks for the tips! I did try to use the quote tool but for some reason in iOS Firefox once I selected the text I wanted to quote I was unable to scroll back to the top to tap the quote tool
If you end up trying your Roland VS2480 with Quantum please report back with your findings. I think I’m going to try using a BCF2000. I’ll post back with any progress...
@Wally was indeed instrumental in bringing control output of controls in Quantum (as well as providing its name!) - scenes too so that all faders were sent, but without an 01v96 it was difficult for me to complete this - so indeed it may (and probably does) contain bugs. If anyone notices them I will fix them.
If you have midi flow monitor you could determine this in Audiobus(or just replace it with a synth). I don't have ApeMatrix myself. Is that where 0 velocity is occurring?
Yes I've been monitoring it with the midimonitor in apeMatrix.
edit: Hold on it is working, but some instruments aren't responding to it, but some do. Not sure why. If I send directly outside Audiobus it works as expected. Seems to be not making sound with AudioLayer AU for me even though it's triggering the zones.
If I use the midiflow adapter instead of apeMatrix in the midi output slot it's all working as expected. So not sure where this issue lies
so it might be apeMatrix? Basically if you see midi outside of a source then it usually isn't the source.
Let me know if you want me to test a particular setup though.
it's odd, yes it proabably is apeMatrix but this doesn't happen with any other sequencer, if I add another sequencer into the same Audiobus lane as Quantum the midi gets through great, but with Quantum it doesn't most of the time but sometimes it does, I should say it gets through but just doesn’t make every instrument sound. Yet it's working with AUM in the same combination. So if it's apeMatrix at fault it shouldn't work with other sequencers either in Audiobus.....
i could upload a video if it helps. I was having the same problem in the beta stages of apeMatrix with Quantum but nothing else was behaving in the same way so left it and it seems neither of the updates has changed anything.
I'm sure Alessandro would give you a code to test if you don't have apeMatrix, but well worth having btw especially for the type of evolving music you like making and a great host for Quantum instruments
It may be worth seeing if anyone else can get quantum to trigger AudioLayer properly in apeMatrix via AB3, here’s a basic setup to test, using a built in audiolayer instrument.
http://preset.audiob.us/0e7tvWfEoEB3meE
Just need to add some notes into quantum sequencer and press play.
If I add Zeeon into this setup it also doesn’t sound, but Sunriser works, very strange. Would like to see why this is happening
This is a problem that was also discovered during the Xequence Audiobus Beta. It has to do with the way either Audiobus, apeMatrix or both (still investigating) handle MIDI timestamps and only occurs with sequencers that (correctly) schedule MIDI packets in advance using timestamps. A fix is complex but being worked on by everyone involved
http://www.amssoftware.org/manual/QuantumManual.pdf
Not sure why you couldn't access it from the app it works for me?
Yes, I got in today. It was definitely not working for me yesterday. I have started to review the guide. Thx for your effort.
Trying to use my LaunchControl with Quantum to adjust the sliders in Quantum, but I just can't figure out how to do it. I've tried every option in LEARN. I can see CC changing when I fiddle with a knob on the LaunchControl, but nothing happens with the sliders in Quantum. Any suggestions on how to get this to work?
you need to enable midi in(button next to midi out on main page) and go into Devices/input and enable your LaunchControl
Thank you!! That did it. Cheers! :)
I don't have Ape matrix and have hardly used Midi in Audiobus, but this is really interesting info. I'm a layman thus the basic questions: are the use of advance timestamps in Xequence and Quantum specific / limited to the Apple Midi format? If so how are advance packets using timestamps "translated" and transmitted via DIN? As sysex?
Get's me wondering which HW midi sequencers actually send advance Midi packets. Certainly not the Octatrack. Older generation Akai's MPC 1000, 2.5K, MPC Live?
Command Stations (They transmit Midi Timecode)?
How about the flash newer gear such as the Pyramid?
My main step sequencer is the Octatrack. Sometimes I run into barriers due to CCs etc being sent after note on. In some cases there are workarounds, sometimes not. More insight would be much appreciated!
Just seen Seven System's message was from back in August! Anyways, I'm still curious.