Create a JUCE module to wrap and support WavPack.

[jrlanglois]

The aim is to lower the barrier for WavPack's adoption in an already popular environment using an existing system called a JUCE module.

JUCE is a popular C++ framework, specialising in VST/VST3/AudioUnit/RTAS/AAX plugin development and hosting.

Most apps built with JUCE use the audio playback features that come with it, including various codecs like WAV, AIFF, FLAC, and so on... to create samplers, audio players, and that sort of thing.

I have a working JUCE module already so I'm just looking for your thoughts on providing official support from within your repository.

Cheers!

[dbry]

Very cool! What would support from within my repository look like? Would it just be another "example" plugin like the winamp plugin? Why would it belong in the WavPack repo as opposed to the JUCE repo?

[jrlanglois]

What would support from within my repository look like?

If you mean support in terms of process: this should be about the same as it is now where people submit PR fixes or submit issues.

Would it just be another "example" plugin like the winamp plugin?

It would be a couple .h and .cpp files specific to manage a unity build that JUCE understands, called a JUCE module. Users would just configure their JUCE project to point to this repository's module, and JUCE's Projucer (the provided project management application) will add the files for compiling and linking to the user's project. This is the standard approach to JUCE-based development, so it would fit right in!

Why would it belong in the WavPack repo as opposed to the JUCE repo?

This is a tough question that I'm not sure how to answer. From my observation, it looks like there's a lack of interest in supporting it directly from within JUCE itself.

For example, take the issue I created and the PR that a fellow JUCEr created:

• Feature Request: Support encoding/decoding WavPack juce-framework/JUCE#271
• WavPack decoding support juce-framework/JUCE#168