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.
Problem with audio recording in Cubasis2
Is it a bug? When I try to record audio material in a track and set the track to loop, the recording stops before the loop ends and jumps back to the beginning. It only happens when recording audio, doesn't happen with internal or AU instruments. Tried on Air1 and Mini4 with same results :-( Never had that problem before the update. Can anybody reproduce that? Any ideas?
Comments
I can reproduce this issue using both internal mic and external audio-device(s) on my iPad AIr 2, iOS10.0.2.
What is going on here Lars(@LFS) and the Cubasis Team?
No problems here recording audio and setting track to loop using internal iPad Pro mic and speakers. Everything works fine on iPad Pro 9.7 running iOS 10.0.2.
Addition...
If I use the 'Punch-In & Punch-Out' and do not use the loop function the length of the recorded audio-event between the locators is correct so this is definitely a bug!
(Another 'Punch-In&Punch-Out' related bug is that the settings are not remembered between takes).
I don't know how careful and picky the beta-testers and quality-assurance team are but this is definitely a 'slip' that should have been caught during beta prior to release...
@Samu while I am not a beta tester for Cubasis, I have have done a lot of beta testing on desktop and iOS in my life and the reality is that even when issues and bugs get caught in beta they are not always fixed. A common reaction to bugs is for users to blame the beta testers, but usually it's down to a lack of time or resources in engineering. That's been my experience anyway.
(Edit) it should also be noted that complex software is never released bug-free. If the devs waited until all the bugs were fixed software would never get released. All complex apps will have bugs, the key is to try and fix the critical ones.
I know. I've done (and still do) my fair share of testing on both iOS and OS X and some other platforms too.
What bugs me is when some pretty obvious things are left 'unfixed'. Sure it could be due to time restrictions and other business oriented decisions but sooner or later they will come back and haunt the 'project'.
What I've learned that if I report an 'issue' with constructive feedback and potential causes for it's appearance there is a higher possibility of it getting fixed. That is why I try to 'figure out as good as I possibly can' why a certain bug appears prior to writing a feedback report to the developers. (I also try to make sure one way or another that I'm not the only one experiencing the issue).
I will try to 'hold my horses' regarding Cubasis 2 for now and let the team do their work as I'm pretty sure they are aware of a thing or two that I've not yet even bumped into
(Why else would they have a 'back-log' of things to do?).
Even with all the less than positive 'things' mentioned about Cubasis 2 it's still very fun app to use and I've learned to 'work around' many of the issues and I know sooner or later they will be sorted out.
I must be the only one who doesn't have this issue or is the issue only with earlier iPads before the iPad Pro.
Happens on my Air1 10.0.2 also.