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
The app is actually a 'midi bus', so it doesn't seem that unreasonable.
I get the similarity, but that comes with the territory when you use generic names for your apps.
Imitation is, after all, the sincerest form of flattery.
@dwarman said:
Uhm... no, it's not.
Pop!
There's always two sides. We've only heard one here. I would rather not hear either, or deprecating comments. Not what I come here for.
Actually, we haven't heard either side, or anything to suggest there ARE sides...
http://discchord.com/blog/2013/12/12/midibus-released.html
I enjoy both apps and use both. I agree with those who suggest people who are buying apps should be left out of the conflicts between developers. Ultimately, I think people will tend to buy what works for them and the extent to which developers are able to co-operate for the benefit of their customers is ideal for us. This doesn't always happen but adding fuel to the fire tends to undermine your efforts. A good product and customer service speaks for itself.
@Sebastian said:
(on the discchord link, Nic said)
So that's Nic's side of the story. It appears to verify Sebastian's comment that that's all there is to the story behind the name.
I think Nic's original intentions were probably not to be malicious, but I agree with @syrupcore (and others) that this isn't an appropriate name. Audiobus is used as one word. If it was "Audio Bus" then calling Nic's thing "MIDI Bus" wouldn't be that bad, but when something is one word and it's not a dictionary word then that changes its position wrt branding, trademark etc. The URL of course seals the deal wrt it being a copycat.
E.g. I'd be really disappointed if someone released a piano app called pianism. No idea if it's legal or not, but it'd definitely be really uncool. Even more so if that app didn't adhere to the spirit of what my app tries to do with guitar, because it would directly damage my brand. Or if someone made a guitar app called StrumJam, that'd clearly be trying to ride on ThumbJam's name. I believe this is why Sebastian is publicly mentioning (in a few different places) that MIDIBus has nothing to do with them, because creating that distance is important to 'damage control' the impact on the Audiobus brand. To be clear, I'm not saying that Nic is trying to damage the Audiobus brand - I think he just didn't think of it that way.
Funny - searching for 'StrumJam' on the App Store gives me DrumJam as a result - who'da thunk...
Edit: I take back my comment on one word vs two - it's bad either way. Branding is branding.
Why does this seem so pointless to me? Two different products serving IOS musicians. Nothing illegal about the name. I'm trying to understand the point. Is it that, no other IOS music app can add bus to the end of its name? In all likelihood, I will probably use both of these apps, unless someone comes up with one app that does both, audio and midi. So, my biggest concern at this point, is how to incorporate both into my workflow. Seems like there are bigger and better battles to wage. Sebastian made his point that they were not affiliated. What else is there to say.
I have to agree with mgmg4871 on this. As in the example of Coca Cola and Pepsi Cola, the suffix is descriptive and shouldn't be subject to copyright. Pianism, to me, is a different matter. Drawing the line can be difficult though, but since AB doesn't incorporate MIDI, and MB doesn't incorporate audio, I can't see where anyone should be bent over this. I can understand that Sebastian would want to make sure people understand there's no affiliation, but aside from that, I can't see this as anything underhanded on MB's part....at least, I hope that isn't the case, since I must applaud any dev trying to tackle the iOS MIDI mess.
Hmm, StrumJam sounds like a good idea, thanks Rhism!
@Rhism: I'm still waiting for, "ORGANISM"!!!!! I hope you already bought that name...
@sonosaurus Lol so you didn't put strumjam in the drumjam keywords? Looks like Apple is detecting misspellings.
@NoiseHorse Lol I know!
BTW Jesse do you lurk on all threads around here?
I hadn't even tagged you!
Nobody got worried about this - https://itunes.apple.com/gb/app/cumbus/id471137858?mt=8
(Oh, and EEEWWWW!)...
It's clear the chap is a marketing wannabe and deliberately trying to ride on the success of the 'bus. I'm in the camp that thinks it could be malicious, but I agree with the others that deliberating it is pointless (oops!!)
However, further down in the discchord entry is this quote from Audeonic:
"In any case, I'm pleased to say the library was released today and Alex Mathieu of Glitchbreaks fame grabbed it almost immediately and added full blown well behaved MIDI to his new app in 3 minutes flat during his lunch break - no joke. See @distraub on twitter."
Whatever you think about his nomenclature, that certainly looks promising.
Lol. @PaulB.
Glitchbreaks and a reliable midi clock! Can't wait!! Love that app
@PaulB said:
I hope this didn't take too long for you to discover this app. Theoretically the developer of this app can come on the Audiobus but the app hasn't been updated in a couple of years.
I created this loop by using MidiBus clock to sync the following apps on Audiobus: SquareSynth, Thesys, Robotic Drums, and WOW. I also used AUFX:Dub, but it was at the end of the Audiobus chain and wasn't synced to midi clock. You can change the BPM from MidiBus and even do time signatures and it will automatically calculate the appropriate BPM it sends via midi clock.
@Paulinko - thanks for posting that. I have been holding off on it so far but it seems like it can be useful. I know it's only a couple of quid on the UK store, but I'm quite mean.
Anyone else notice this thread's most recent time never seems to change. Is it stuck in a time vortex?
The time was fine until that EEEWWWW post! @PaulB's app has gummed up the time vortex!!!
Let's be honest Midibus or Midi buss or whatever was the next logical thing in terms of a name for an app that comprehensively connected apps via Midi; just like what AB did for connecting audio apps for iOS musicians. Buss mixing apps. Sebastian has clarified this app is not in any way affiliated to AB so that settles it for me. I don't buy apps because of their names. Their functionalities are what I'm attracted to.
Amen.
Name controversy aside... Midibus just helped me to sync Cassini w Loopy HD.
The two apps weren't syncing, so I loaded up Midibus and selected it in Loopy's clock input. Left Cassini on omni Midi in, and activated both in Midibus(clicked start button, too).
Works...both, syncing both at 120 BPM, currently. No AB used so far on this one...
Here's a video I put together showing how to setup and control some apps with MidiBus in Audiobus.
I've also communicated with the developer about adding an audio engine to the app so it can run within Audiobus to take advantage of those controls rather than having to jump in and out similar to the way you can mute Thumbjam or SoundPrism Pro and use them exclusively as midi controllers. He said he would look into doing this but isn't familiar with the audio side of iOS. Hopefully he'll be able to add this functionality to MidiBus.
Thanks for that. Would like to take a look but says video is private.
Might it be worth creating a separate discussion for your video (and loop demo) since this thread seems to be staying in the past and your efforts could be buried.
Great to hear that Nic will look into making it Audiobus aware. If only he would do the same with MIDI Bridge.
Fixed the video access, you should be able to see it now. If Nic can figure out how to make MidiBus work in Audiobus, he can do the same with MidiBridge.
I wonder why this thread's date isn't updating when people post to it? Nice work on the video, @Paulinko.