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
Interesting view into the development process and how it is wrought with internal struggle. IMO a product should not be released to the public at the level this app seems to be at. (known load bug & stuck notes)
Very nice to hear @Mana giving us his take on the situation though.
@Mana .. Thanks for all the replies. I work as a project manager in software and understand all of those comments and constraints!
@mana Thank you for your reply. Welcome to the forum.
Interesting situation, arturia's service has been lacking for a long time and it's no secret. I am not a businessman, So I can't speak to the issues of refusing to release a product with a bug like that. It seems that any bug in a synth that affects playability would be a major bug even if it only happens once in a while. I use my iPad on stage at every gig and can't take a chance on using any synth that might go wrong in that way during set. I think that's the same reason that many players who are around in the early days of using synths don't take their vintage synths on stage anymore because they're too unreliable.
Anyway I appreciate your reply and please remain on the forum as it really helps.
Despite some problems: it sounds fantastic! I have absolutely no regret buying this one. I think it can match up with all the other big names, soundwise (isem, tera, nave etc.)
About the low-tone hanging notes bug
@mana said:
Now that it's released, please don't stop trying. - I hope that doesn't read as mean. I see a lot of apps being released with bugs and I'm thinking it must be maybe even more frustrating for you developers who worked on it for months than it is for us who waited for it for months.
@mana said:
The bug happens for me only with polyphonic presets. I can kill the low tones with turning the unison knob slightly up and back all the way down left. This way I don't loose any changes that I might have done to the preset like moving the stick for example. But I don't really consider any of these two ways a valid solution - the hanging low tones can come back to life soon after.
Jay, appreciate you being here and appreciate your candor. Good luck with it all.
I think maybe we're all a bit spoiled by talking with app developers who have 1-3 apps. If there are bugs, they can pretty easily float to the top of the list of priorities. Arturia and Retronyms have lots and lots of competing priorities. With a fixed number of hours in a day, some stuff just can't make the cut.
Also, this is a sort of peculiar relationship for software development - at least from the outside. One company making the engine and another company porting it to iOS. For users, it's all a bit muddy. Further muddied by the fact that Retronyms also puts out 100% created apps. Similar to iMini and iSem (and...) users are often left wondering who to contact with questions, suggestions or problems. I often wonder what the support deal is.
Or with the question of the stuck note bug in the desktop version of Arturia's Prophet V, is it Retronyms' job to fix it on iOS? Is the contract 'port this code to iOS/objective-c'? I imagine if I was a PM at Retronyms, I'd say no! But then again, the relationship is muddy from the outside.
@syrupcore said:
Well,the answer is already there...
@mana said:
ah yeah, I took 'take the fix' as ambiguous (take on the work, maybe) but it's exactly what you're saying.
I appreciate the friendly response! It makes me very encouraged to fix things and get stuff done.
@syrupcore said:
Sorry for the ambiguity, I meant that it's on Arturia to fix that bug (at least currently), and that if they do make the fix, we'll of course put it into iProphet.
To be honest, I don't know the contract specifics on such a detail, but this is the stance we're holding on that particular bug. It wouldn't hurt to email Arturia about that bug.
@firejan82 said:
That is a helpful report, thank you. I know I said it's on Arturia to fix the bug, but regardless, we want to record every bug and every useful report. And that goes for any bugs and feature requests on our products.
EDIT: Missed this post in particular
@mrufino1 said:
I totally understand (I do some production as a hobby, and it's a goal of mine to perform live as a regular gig), and it sucks for developers when there's no choice but to release, even with bugs (major ones too).
Mana, you know, from heaven. Thanks.
@mana I've been very verbal with my frustrations with Retronyms. However, your posts are the most honest sounding and least condescending of any I've ever read on any site from any Retronyms representative. It is a breath of fresh air. Please continue and please encourage all of your team to do the same! :-)
@Audiojunkie said:
Agreed 100%.
@mana said:
I will do that, even though I don't have Iprophet. If I may ask, the stuck notes that were ( maybe still are) a problem in imini, was that a similar situation? I have mini v classic (the one they gave away) on my Mac and haven't noticed an issue, but I have not used it nearly as much as imini. ISEM does not seem to have any if the same issues, but I am not a programmer at all and don't want to speculate on why that may be.
I can't say enough how much your participation here means @mana, thank you for being open and honest.
@Audiojunkie said:
I appreciate it and I will. In all likelihood any other representative you've heard from I probably know (we're all in one office), and they probably meant well but came across otherwise. Sorry about that. I've never gotten a feeling of bad intent from anyone here, so I hope you don't carry the sentiment to heart.
@mrufino1 said:
I worked on the tail end of iMini so it's a bit fuzzy, but I think that bug in particular is to do with our keyboard (i.e. the piano keys). The low rumbling is still present in both, but it's totally possible that our keyboard is making it happen more often than it should. iSEM wasn't made by us, and I haven't played with it much so I can't comment on it. And thank you! I like figuring out what's wrong with things and then fixing it.
I'll be gone until Tuesday so you won't see me post until then but I'll get back to the thread. Hopefully you guys can still enjoy using it (at the core it's still a pretty beastly synth!) despite some of the intrusive bugs and the like.
With imini the stuck notes only happen (ed) with an external midi keyboard, not the on screen keyboard. I'll have to test it again to see if that's been fixed but I could reliably make it happen (not the type of reliability I need! Ha!)
I'm aware iSEM was done by someone else, so I was referring there to the fact that both companies implemented arturia's code into ios. As I said, arturia was totally non responsive to any questions about imini. That being said, I am very much wanting a microbrute...too bad I don't actually need one for my gigs, my setup works fine...
I guess I've managed how to get iProphet to work with Audiobus and Cubasis on iOS7.1.2.
To receive MIDI from Cubasis, iProphet must be opened first, then Cubasis.
To record audio, an app must be in the Effects Slot. Tested on iPad Air.
First thanks to Jay, got a mail from Eric confirming its on the bug list.
@FRibeiro, for me no problem with midi or recording. And nothing in the effect slot. Opend Cubasis first. Air with 7.12
How are people finding this performance wise?
I ask as I have just put together a patch, four detuned saw waves, some lfo modulation on the cutoff, unison knob at 12 o' clock, nothing special. Add some delay, chorus and overdrive from within the synth.
Connect to Cubasis via IAA as an instrument and program a simple bassline over a single bar.
Add iMPC pro as an IAA generator and trigger a kick drum sample via virtual midi from within Cubasis.
No fx added from within Cubasis.
With HW latency at 256 in Cubasis the CPU overloads and the audio breaks up after looping 2 bars.
Change to 512 and CPU levels out and sits around 20%. Mini Retina, Cubasis 1.8.2, ios7.1.2
It seems to be pretty intensive, I would have expected to get it running with at least one other app at 256 without too much trouble.
^ Keep in mind that with unison activated it's playing 8 voices (depending on iPad model) x 4 oscs = 32 oscs at the same time.
Test to see what happens if you set unison to zero.
I can't use it at 256 buffers in AB on ipad2, but fine at 512.
Standalone, no issues.
@mana said:
Removal seems logical and perhaps change the name of the "All Voices" knob to "Pan Voices" or something like that.
That would make a lot of people happy. Assuming both Velocity and Pressure will be controllable from onscreen keyboard and external midi input.
I love its sound and UI, that's why I'm so eager to get the few bugs/problems solved :-)
@mana I agree with the other posters that your willingness to engage with the community in an open way here is very welcome. I've enjoyed using the synth and I would hope that Arturia would be willing to cleanup the bugs.
@R_2 said:
With unison at zero it's ok. I was expecting unison to up the CPU, was just curious if this was what others were getting with a similar set up.
I ask because I find IAA with Cubasis and the higher end synths maxes things pretty quick, but I normally get a couple running in parallel before freezing is necessary.
That aside, I think this is a nice synth with plenty of scope to create a range of useful sounds.
My only other negative observation is the overdrive. If I push it too far it makes my headphones sound like they have blown, rather than create a warm saturation or distortion. My phones are fine so I just need to push it less than I would have preferred.
Also echoing other comments, nice to have @mana responding on this thread. It is great to get this sort of open dialogue with the developer and is one of the real strengths of this forum.
A small comment of the accelerometers in the mod matrix: accels are a fine thing to use when your iThing is being used as an in-hand instrument doing only that one thing, but useless when it is either being used as a sound module from a standard external controller or as a part of the ensemble in a DAW, where accelerometer cannot be automated and is likely not even usable. However, if the mod matrix reverts to conventional inputs, those are a) automatable and b) if one wants accelerometer behavior, one can always use one of the MIDI surface designers like TB Midi Stuff or Lemur to convert accelerometer to MIDI.
Really digging the iProphet ...
Does anyone know how to assign/map the joystick to a MIDI controller? My Triton Taktile has a nice X/Y pad in the center, but there's no option for MIDI Learn or MIDI implementation chart for the iProphet A/B/C/D mixer joystick.
The tactile is one awesome looking beast of a controller not to mention the Triton sound engine. How is it working for you over all?
@Tritonman2
Pros: Nice selection of built in ROM sounds, X/Y touchpad is multifunction, expression & sustain pedals, decent screen, pads are comfortable & responsive, chord mode for pads, most all controls are re-assignable. Has low-power iPad native mode (with FW update) - great for MIDI/Gadget on the go.
Cons: Only powered by USB, no MIDI IN jack*, audio out is 1/8" headphone jack
I have my transport controls assigned to Loopy HD, which is what I use most for recording tracks and ideas.
Using the USB MIDI, you get both in & out. I prefer running MIDI out from the Taktile jack to MIDI in on my Alesis IO Dock, so I can use the Alesis too. Doing USB MIDI into my Akai EIE does not work, as the Akai doesn't provide the USB power, but that's for another topic
Has anybody lost all of their saved presets? This is the third time, the second time i 'bout cried because i had some really awesome ones. It was right after i updated isem. Today it was after i updated thumbjam. I saw the i prophet app icon go dim and it said "cleaning" and i have never seen that before. Anyone have any ideas on what gives?
@Synco that sucks... Didn't happen to me yet. The "cleaning" icon I've seen with Animoog in the past, all the IAP timbres were gone but could easily be restored.
Was iProphet running in the background while you updated thumbjam?
The app 'cleaning' process should only wipe unimportant cache data, obviously NOT user presets.
Perhaps Jay @mana could look at this > Are the user presets at the right location/map?
@Cubilas said:
Sadly:not possible.Funny sidenote:it made me really want to play AND record something with a stick or similar so i gave Alchemy another try...and bought the"Pro"Version along with all soundbanks.Couldn't care less about only blending some boring Osc volumes now
@lost presets:i'm sure it was mentioned that this can happen if you use Ram cleaner like Cmemory.Was this the case here?
Iprophet was not open. I saw a few other apps say "cleaning" about the same time.