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.

AudioKit, Soundpipe & the LGPL

A few days ago I noticed that the repo for Soundpipe, a DSP library used extensively by AudioKit, had vanished from GitHub.

After a little digging, I found an exchange on the CSound forum claiming Soundpipe was incorrectly using the MIT license [1], and an email to the developer asking that it be changed to the LGPL or similar [2].

[1] [Csnd-dev] How can the Soundpipe library use the MIT license?
[2] [Csnd-dev] Email about the licensing of Csound code in Soundpipe

Does this have implications for apps distributed via the App Store?

Comments

  • LGPL v2 is compatible with AppStore but v3 may not be. Which version is there?

  • ANAL: I think this leads to all AudioKit-based Apps having to share the source code for
    forking. In many cases the offending party tries to replace the LGPL'ed code they infringe on. Not sure there are many lawyers working everyone of these disputes. The EFF would typically weigh in with legal services to protect LGPL abuses.

    It could be our loss and will certainly come as a big surprise to developers that are caught in the lurch by trusting someone else's license as being accurate for the sources involved like the AudioKit Devs did.

  • @Poppadocrock said:
    Wow.

    Yeah. This type of issue is a developer's nightmare if they want to charge and make a few
    bucks. If they give the app away it's less of an issue. Developer's love the MIT license because they can allow others to sell derivative works with some protection.

    Maybe this type of mistake has been resolved but I doubt it. It's a nasty business where
    almost everyone looses when a license is mis-labeled and people rely on it as being accurate.

    There's this crazy situation where Sun open'ed up Java and Google created Android
    that also run's Java code. Then Oracle bought Sun's assets and sued Google for Java
    patent infringements and the court found Google at fault. Billions were involved
    and I think the court got it wrong. But Google has deep pockets.

    AudioKit is intended to allow developer's to have open code to build with and sell
    apps. Sad situation for all concerned but LGPL has to be defended to have any
    legal standing when it really matters.

    I expect the AudioKit dev's will replace the offending code. If anyone is looking for deep pockets here it would be Apple's headache so "stay tuned"...

  • Yay.
    More to fret over.
    2020 rules, bruh!
    😔

  • @McD said:
    ANAL: I think this leads to all AudioKit-based Apps having to share the source code for
    forking. In many cases the offending party tries to replace the LGPL'ed code they infringe on. Not sure there are many lawyers working everyone of these disputes. The EFF would typically weigh in with legal services to protect LGPL abuses.

    It could be our loss and will certainly come as a big surprise to developers that are caught in the lurch by trusting someone else's license as being accurate for the sources involved like the AudioKit Devs did.

    Came here for the content, stayed for the ANAL

  • “Stayed for the anal.” You don’t really hear that a lot.

Sign In or Register to comment.