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
@Yendor: I don't think you can delete the currently-loaded file. I had to load another file and then delete the first (IYSWIM) to make it work OK.
Well, I'm giving up on MidiBand for the timebeing
I've been unable to make it do anything useful with bs-16i and what small successes I did have seemed somewhat random and not really within my control.
I'm happy to accept that it works flawlessly under iOSv8.3 but I'm not ready to leave the relative stability of v7.1.2 yet and MidiBand is evidently not happy under v7.1.2, so...
Hopefully a fix is coming soon.
Hi KING777 - I have not seen any on-screen keyboard yet convenient enough for a serious musician - that's why I thought that an external MIDI keyboard should always be required. Also I did not want to do badly something other apps already do quite well. Bismark bs-16i has a great sound engine and MidiBand plays nicely with it while in the background. The same goes for on-screen keyboards: find an app capable of sending keyboard events on Channel 1, and you've got yourself a screen keyboard.
:-) Cheers!
I think you've (maybe) over estimated your customers here. There a lot who use nothing else but on-screen keyboards and there are so many keyboards that work. Even the worst is better than none. Especially for mobility. Having to use another app is too much work to set up each time.
Also when you say serious musician, there are Grammy winners who have never played a single keyboard note. (Use piano roll etc..)
Have a think about it. For me I doubt I would use this app as is. It's good for what it does, but it could be simpler.
I actually only have "Soundfont Pro' not Bismark. SFP sounds hang in the background when I stop MidiBand, I feel that is a SFP issue. But I would not buy another app to play another app. In this case buying Bismark for MB, unless I couldn't do without the app.
My opinion will count for a lot of potential customers. I wish MidiBand had those things, I know exactly what it (MB) is capable of doing. Customers using a midi keyboard (regularly) will be well happy with your app!
(One) of the reasons I moved my music studio over to the iPad is because of the on-screen keyboards. I wish you the best with it. :-)
I will keep an eye out for updates in case you see the obviousness of what I'm saying and add a keyboard.
Cheers again! :-)
If anyone is interested, in lieu of an external keyboard ,Soundprism Pro appears to work nicely with Midiband, no crashes yet, for me at least. However, I am still having issues getting Chordpolypad to work with Midiband (still getting a lot of feedback)
+1
I got CPP to work with MB but I had to turn off all Midi in on CPP because MB was sending MID out which caused CPP to constantly trigger pads by itself
Yeah you were getting the classic midi feedback.
Gonna try BS16s keyboard. Didn't think of that option. I guess channel 1 is set as default to melody or lead.
Yeah, the track sliders in MidiBand are definitely broken under iOS 7. You cannot move them by hand, and when you move them indirectly by the master volume slider, they go into the opposite direction and not for a full scale. No such problems whatsoever on iOS 8. Why does Apple need to change the basic API with each release? The sliders have existed in iOS forever...
Anyhow, I can see it, so I can fix it. This will be my first priority and will be fixed in a day or two. After this, it's all in the hands of Apple reviewers.
MidiBand initially allowed users to select outputs, but I took the feature out. My concern was that I will get reports of not being able to get sound out of the MidiBand just because the desired output was turned off. The multicast to all known outputs and accepting events from all known inputs seemed like a safer option. Looks like I need to put the feature back in )
Yeah that's awesome! Please put them back. If anything, maybe by default leaving it as is and in an "Advanced Midi Settings" page out the ability like you said. The guys here are really advanced users and catering to both noobs and advance users is greatly appreciated.
FYI: I think currently there's a midi issue with BS16 as it recently got an update. I haven't personally had time to test it but will later.
Great work KSH!
On top of each track there is a button that, for most tracks, says "Melody & Chord". This value determines how incoming events on a channel corresponding to that track are interpreted. The possible values are:
Melody & Chord: Already familiar split-point between chord notes and melody notes
Melody: no split point, no chord, all incoming events are interpreted as melody notes
Chord: the opposite, all incoming notes are used to build a chord
Section Change: special mode where incoming notes are interpreted as instructions to switch to a new section - C switches to first section, C# - to second section, D - to third section, and so on.
Finally,
Style means that there are style notes on that track, and it should not be used to also accept midi events.
To summarize, you could connect three physical MIDI keyboards and:
Set Track1 to Chord, set first MIDI keyboard to send events on Channel1, and use Keyboard 1 for left-hand chord play.
Set Track2 to Melody, set second MIDI keyboard to send events on Channel2, and use Keyboard 2 for right-hand melody play - no split point needed.
Set Track3 to Section Change, set third MIDI keyboard to send events on Channel3, and use Keyboard 3 for changing sections as you play, even and especially with MidiBand in the background.
This is all assuming that the style contains no notes on Tracks 1-3, which is likely, as MidiBand tries to move all notes to higher tracks.
I just tested MidiBand with the latest Bismark release dated June 6. The infamous HonkyTonk plays fine, although the sound of instruments does seem to have changed a bit to my ear.
Yeah, just tried it too and they did something with the Soundfont. It sounded so much better. Almost if not better than Roland SC.
I did have an issue were BS16 froze after I went to it to see how it was working while MidiBAND was playing. I could see all the channels in BS16 receiving midi data as they were all blinking. Checked all 16 channels. All my mixer settings were working as well. But once I went back to midiband then BS16 froze. So it is a little more sensitive reg midi than before. Still I liked what I heard. Again, I was using the default soundfont for BS16.
It's nice to see the developer and user(s) working so well together
Hi guys - MidiBand 3.1 and MidiXpress 1.1 fixing volume slider issues on iOS 7 are both in Apple's review. Please be patient.
Hey @Ksh, take a look at the ’myBand' app if you haven't already done so. In-built sounds also keyboard. Yes you have to purchase IAP's but the principal of the thing.
I've had this app on my pad for a while never used it (maybe all the IAP's put me off, can't remember) but is insta-play.
You may need to reconsider your customers? When we have options we are more likely to use them (meaning on-screen keyboard on or off etc).
As you can tell I would like to use your app, with my own produced midi files.
No man is an island
Added they haven't updated for coming up to a year so not much competition from them and no import as far as I can tell. You have the field..
Cool. Thank you.
KING777
Try the Navichord app or the free Yamaha synth and pad app. They work great with Midiband. I have the Yamaha app using the pads sending chord midi data and keyboard data on separate midi channels and I realized that Midiband actually tracks the chords so much better as they're digital being sent internally instead of one using the midi controller keyboard.
I just need to figure out what midi notes trigger the variation changes, like Main A-D and fills etc. That way I can program those on the pads and send both chord and variation data at the same time.
Thank you KSH for the update.
I got some nice working styles I'll share later for those interested.
@musikman4christ can you give any idea on your setup for Yamaha Synth and Pad app to make it work for Midiband? I tried to get both apps working together working but am not having any luck.
:-) cheers man!
I got the Navichord yesday, so I'll give it a go tomorrow Sunday and see how smooth things are!
First off, until the update gets approved thru Apple, if your setup is IOS below 8, the latest Midiband will not work as designed.
I'm using IOS8.2 so all the features work. There are still a few things but it could be more user error than anything.
I got the Yamaha app to work in the Pads section. You have to go into settings and enable virtual midi. Once you do that, go back to the pad section and hit edit on the pad, then it will show you what chords are there already, also there is a little option that lets you set the midi channel for each note. Check that one to the right to enable it. Once you do that, you'll see a list of channels 1-16. So for the left side of the pad I selected the notes I wanted the pad to play and set those to midi Chan 1.
Then for the right side of the pad I selected a note like F2 or something and that one I selected midi channel 2. So I hit play on midiband and went back to the app and I hit the pad and midiband recognized the chord according the notes I had programmed. And when ivhit the right side of the pad, a fill in was activated.
To me this works but I guess I'm being a bit lazy to program all the chords, that's why I'm gonna get Navichord.
I still need to figure out how to start and stop Midiband thru a midicommand. That way I can do it remotely thru the Yamaha app or Navichord.
A lot of this is trial and error. But it is fun trying to figure all this stuff out. I was playing the Pads in Cubasis and I really liked the premade chords that were there. But you can't change variations tho.
But Cubasis chords were definitely recognized by MidiBand.
Some PSR9000 styles I found work really great with Midiband and Roland Sound Canvas.
Only reason I want to use an app chord progression generator is cause Midinand detects the chord so much better that way instead of a midi controller as you have to press hardware keys instead of software.
Either way, been having so much fun with Midiband. It really makes a difference to find good and well programmed styles otherwise you get howling dogs, and piano drums all over the place. :-)
I have taken some screen shots of my setup in Yamaha Synth and Pad app. Also, in Midiband. Roland Sound Canvas pretty much is left default.
In Midiband make sure the second midi track is set to "Section Change" as shown on the screen shot. Hope this helps. It pretty hard to explain all this but one has to really keep trying. But it's always good to ask cause thats why were all here to help each other out.
here is another one
midiband
last one...