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
Thank you Lars :-)
Not knowing the features in the update i think this is too early to say.
Iminent - Words uttered by a marvel hero, recently immortalised in film, when he realised what powers he had.
Spring - The noise made when I get too enthusiastic with my LPK25
Iminent - Phrase uttered by marvel superhero, recently immortalised in fil, when he realised what superpowers he had.
Spring - Word describing the natural sound produced by over exhuberance on an LPK25
Dear all,
Please allow me to reflect on the previous questions regarding Cubasis 2.0.
As stated earlier, Cubasis 2.0 will be a free update for existing customers (same for 2.x related updates). Of course, possible IAP releases make an exception to this rule.
Hope that helps to clarify the situation.
Enjoy being creative
& a great weekend for all of you,
Lars
Ah-ha! he extrapolates wildly etc.....
Unfortunately infinitely does my head in.
As always I'm looking forward to updates to existing software.
Hopefully the next version of Cubasis will cure the issues with freezing iaa-tracks and add sample accurate editing to the recorded waveforms so we can edit away the latency that is added to the beginning of audio files when freezing tracks, the amount of silence is relative the the buffer-size used in Cubasis, smaller buffer = less empty space in the beginning of the frozen file...
Just try freezing a midi-track/iaa-instrument to audio-file with different buffer sizes.
Also a 'pre-record' buffer would be handy when recording an IAA-Generator driven from a Cubasis Midi-Track so that the beginning would not be 'cut-off'.
These are two of the issues that can drive one insane for less, not to mention the zooming...
Samu, have reported that on the Cubasis forum?
To my knowledge these are pretty knows issues regarding iaa-freezing, and the generic solution seems to be to set buffer-size to '256' or something similar.
The sample accurate editing has been requested long time ago, the 'zoom-level' is already there but even if the grid is off it defaults to some default grid-size making sample accurate editing impossible. It works in the Micro-Sampler so I see no reason not to enable it for AudioTracks too.
The iaa-generator recording is related to buffer size, to my knowledge there is no pre-roll recording of audio in Cubasis, meaning, the bigger the buffer, the more 'cut' there is in the beginning of the recording.
I'll do some more experimenting with the 'Output Latency' in the Midi Settings to see if I can push the notes forward so they will not be cut when recording the iaa-generator that is driven by a midi-track.
The pre-roll recording would also be handy for midi-recording to as it's way to often the first note is missed because it's played just before the recording starts.
A seemingly simple solution would be to set the buffer-size to 0 samples when freezing Internal Midi and IAA-Instrument tracks to avoid silence in the beginning of frozen tracks.
These findings are purely based on observation when using the app and probable causes.
I know @LFS reads these forums from time to time and probably picks up some valuable information too
@LFS Read what Samu wrote!!
Thanks
I've been playing around a bit more with midi-latency & audio buffers and there is definitely a co-relation.
As en example I'm driving iM1 using a midi-track and recording the output from iM1's iAA-Generator into Cubasis.
On an iPad Air 2 with a audio-buffer size set to 256 and midi-latency set to 0ms the beginning of the recorded drum-transient is 'cut off'.
To capture the audio-transient of the first drum hit midi-needs to be delayed between 5-6ms for 256 buffer, for 512 buffer around 5ms. With an audio buffer set to 128 the delay needs to be adjusted to around 8ms.
Some apps do respond faster then others, so it's understandable that a 'generic' solution feels a little utopian.
Have to revise this, appears that the wave-editor does in-deed allow editing down to sample-level with no snapping, bravo!
Next I'll do freezing of IAA-Instrments and see if adjusting midi-latency helps and how it affected by buffer size.
I feel a bit tech-geeky today...
I'm honestly 'clueless' here, maybe someone can shead a little light onto what's going on here?
iM1 is used as IAA-Instrument, midi-track is triggering 1/8th kick drum.
The audio-tracks are 'frozen' at various buffersizes 128, 256 & 512.
At least my brain tells me the frozen kicks should be 'spot on' with the midi-notes!?!
I'll leave it the the programmers to figure out what's going on, it is a little annoying though...
Good days investigating Samu! :-)