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.

Manuals

2»

Comments

  • I guess I'm in the 'beggars can't be choosers' camp. I'm happy if there is a manual or user guide in any format, and grateful when they're well done.

    We could build a database of URLs and PDFs pretty quickly, if others would pitch in.

  • I don't care for HTML manuals because there are times when I don't have internet access or can't use it (data limits). So for me something I can use offline is important. The nice thing about PDF is that I can preload it into my iBooks application and have it readily available. I suppose I could do the same with a webpage -- however some people think it is nice and efficient to put their chapters on separate pages (I'm looking at you MIDI Designer Pro!)... which is useless for offline usage.

    I dislike the assumption that the Internet will always be there for a fresh copy of a manual.

  • @fprintf said:
    I don't care for HTML manuals because there are times when I don't have internet access or can't use it (data limits). So for me something I can use offline is important.

    Ah, but that is the whole point of the modern progressive web apps – they take an offline-first approach.

  • edited February 2018
    The user and all related content has been deleted.
  • @Max23 said:
    this got 1.300 clicks until now, seems like there is quite an interest in pdf manuals.

    Not sure if you noticed this thread was started in March 2013. There were over 900 hits when it was bumped.

  • The user and all related content has been deleted.
  • @u0421793 said:

    @Max23 said:

    @SevenSystems said:

    @u0421793 said:
    Not pdf! Stop! They are dangerous. My job is to write documentation and the last thing I want is people taking a pdf and keeping it around, while meanwhile I’ve updated the docs or manuals several times as the product changes.

    Hehe. Well, we maintain both an online and a downloadable PDF version. Having the manual online as HTML is probably the best overall approach, I agree.


    I don't read manuals. but pdfs are great, they are searchable and you don't need a network connection.

    Promise us all in the doc. eng. (Document Engineering) profession that as soon as they’ve made an update to their documentation you’ll set fire to your current pdf and get/make a fresh one. Otherwise how can the truth be represented?

    I totally understand the hoofla about saving a pdf being a risk that I might not have the current documentation, but...
    1. It doesn't negate my point that it's hard to leave an app to read a manual, then return to fumble with finding where you left off.
    2. I'm an old IBM software guy... I can't tell you the hours I spent updating paper manuals. If there are others out there who shared that experience, you'll know what I mean. Yes, it's important to have updated manuals.
    3. To all you "documenters" out there, I have seen great documentation that has been modified and made unusable in the process.
    4. On this very forum when I was looking for answers about iWavestation, there were several veterans here who proposed looking at the doc for the Wavestation hardware device. They were well aware that helpful information can come from ANYWHERE, including old copies of pdfs.

    If I look in my PDF manual and get no joy, I can still go to the source of the updated help, right? But I'd rather have a quick and easy documentation source FIRST, and accuracy second. Hey, I won't complain if your documentation doesn't have what I'm looking for, but I WILL complain if the in-app or html documentation seriously interrupts the workflow.

    Thanks for everyone's comments. It's nice to feel needed. [grin]

Sign In or Register to comment.