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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Wav file to MP3 converter app?

2»

Comments

  • The new Media Assistant app does mp3 (batch) conversion, and lots more.
    https://apps.apple.com/uz/app/media-assistant/id6466176223

  • @tja said:

    @rs2000 said:
    @tja It's been a while but I guess that you'll still find some information on the hydrogenaud.io forums.
    An older detailed result report can be found here:
    http://listening-test.coresv.net/results.htm

    Edit: A more recent blind test, comparing different AAC encoders:
    https://hydrogenaud.io/index.php?topic=120062.0

    Thanks, but those are what I posted above - they are not tests of AAC at any rate against a max. MP3 (defined as VBC and -V0 with lame, but maybe the FFMPEG is even better?)

    I don't expect MP3 to beat AAC at rates of 128kb/s or lower!
    But I suspect that a max. MP3 may be the same experienced quality as any AAC.
    At least for most ears.

    I am tempted to run my own test - here on the forum.

    Which AAC encoder is rated best?
    Maybe on all of iOS / iPadOS, Windows, Linux and macOS?
    Just in case you know ...

    I think that Apple's encoder is still amongst the best rated ones.
    I'm only using it on the Mac commandline but I'd expect the Windows version coming with iTunes to be the same.

  • edited November 2023
    The user and all related content has been deleted.
  • edited November 2023

    @tja This is my command line for encoding at 160k:

    afconvert "inputfile" -o "outputfile.m4a" -q 127 -b 160000 -s 2 -f m4af -d aac/

    afconvert sits in /usr/bin/.

  • The user and all related content has been deleted.
  • edited November 2023
    The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • @tja 160k was the best from my own listening tests, I couldn't spot a difference at this rate and since the encoded files are for my own use, that's OK.
    m4af is the file type. I had issues with compressed files that just didn't work in some apps and "m4af" fixed it for me.

  • @rs2000 said:
    @tja 160k was the best from my own listening tests, I couldn't spot a difference at this rate and since the encoded files are for my own use, that's OK.
    m4af is the file type. I had issues with compressed files that just didn't work in some apps and "m4af" fixed it for me.

    how did the file sizes compare?

  • @espiegel123 said:

    @rs2000 said:
    @tja 160k was the best from my own listening tests, I couldn't spot a difference at this rate and since the encoded files are for my own use, that's OK.
    m4af is the file type. I had issues with compressed files that just didn't work in some apps and "m4af" fixed it for me.

    how did the file sizes compare?

    They only depend on the chosen bit rate. The encoders generally match that setting very well.
    If you're using VBR (variable bit rate), it will depend on the quality setting and the audio you're compressing.
    At bit rates between 96k and 160k, AAC/m4a and Opus sounded best to me and I chose m4a because of the compatibility in most apps.

  • this is exactly what i needed, super fast 👍🏻

Sign In or Register to comment.