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
Why would you use other technics to compensate for an audio quality loss you yourself committed? Surely just don’t reduce bit resolution in the first place?
Because the the original audio might be a 16bit file.
Are we discussing the same thing here? The discussion is about using normalization.
Well, is it forbidden to combine higher bit depth with normalization?
Uh? The point is why reduce bit resolution when at the normalization stage? My point is why would you do that? Please if you have a good reason let me know?
Moving or copying, previous version always copied (Duplicates)
That's what the OS (Files app) does for "moves" between file providers. I don't believe a file provider can alter that.
@j_liljedahl iPhone landscape view FTW!
@j_liljedahl The normalize feature should also include tPD (True Peak Detection) to avoid 'real' clipping when normalizing.
While I do like AudioShare I've more and more started to do most of the stuff with Auditor since it doesn't really care where the source files are when they need editing but It's not without it quirks (still prefer the 'fluidity' of TwistedWave).
I love audioshare, the only thing I would like is a forward button to be added under the waveform view so that I don't have to go back to the browser page to forward to another audiophile when I'm moving fast and just want to move to the next file but stay in edit mode. I guess a back button would be good too.
Not really, consider that you have high frequency content where a few samples are already at 0db, the one in the middle will go above 0db when played back or simply clipped if the samples on either side of the sample in the file are already maxed...
Here's a snap from twisted wave (Mac version).
Without tPD the high frequency sine-waves will get 'clipped'.
It's an audio editor and under it's regular normalize menu.
There are separate functions for compression and limiting for squashing the audio.
When I normalize with some other apps and then analyze the files there are plenty of clipped samples which to me is a nono...
(They will sound 'distorted' when played back with a bit of volume).
Oh well, thankfully there are other tools so we're not limited to one apps way of doing things
As I see it, the point with looking at a LUFS target is that it may help you in your mastering decisions. If you hit -2 you know you can back off a bit on your compression/limiting/saturation if you think it will sound better, without loosing perceived loudness when streamed on Spotify.
If you think it sounds right and good as it is, there's really no point in just lowering the volume. Spotify will do it for you, no need to do it yourself.
Also, there's a big difference between peak dB (as used by normalization) and LUFS. You can normalize to 0 dB and still get -14 LUFS, it depends on the material.
If you have samples at exactly 0 dBFS, and normalize with true-peak detection for 0 dB, then yes it would probably lower the volume.
And if you have a 32-bit float file, you could even have samples above 0 dB.
It displays poorly on an iPhone 11. It makes fading really difficult
I know. This is fixed in the current beta, which should be available soon (after Apple has processed it, it seems to be taking days this time!)
PS. Please report bugs to me by email, I made this thread only to invite users to test my coming beta version
You can go over 0db if you use a 32 bit float file which @j_liljedahl was referring to.
🙂
@j_liljedahl : Any risk when using the beta on an ancient iOS 10 device? I.e. if there are problems can I revert to the version currently on it?
A long time wish of mine too! Great to see AS receiving some love.
Can any beta testers confirm that existing Audioshare files are present and unaffected by installing the beta version?
Independent of anyone's experience, it is wise to back up your files before installing a beta.
My existing files were unaffected but it is important to keep your files backed up.