Add APVTS parameter integration

[ImJimmi]

Add a real-time-thread-safe way of connecting a JIVE GUI Item to a parameter in an audio processor and/or the APVTS.

This will likely work by passing the APVTS to the jive::Interpreter, and a "apvts-id" property specified on the widgets to specify which parameter from the APVTS they should connect to. This would also use the parameter to decide things like the range of a slider, the choices in a dropdown, etc.

[forestbond]

Hi @ImJimmi. I'm not sure this is really the right place to mention it but I tried integrating JIVE into a simple plugin project today and failed miserably. I have seen the View way of handling parameter attachments but in practice I found it difficult to understand and make good use of. I take it from this ticket that this is an area still needing some development? It would be very instructive if there was a functioning example plugin that uses JIVE with parameter attachments. I don't think the trivial example in the docs will compile.

EDIT: The trivial example does compile, I'm not sure why I was running into problems with makeView. In any case there are some usability challenges with more than one attachment (how to search for the correct GuiItem?) and a working full example would be helpful.

EDIT2: Ok actually the example does not compile. I get an error stemming from the makeView call:

error: no matching conversion for functional-style cast from 'juce::AudioProcessorValueTreeState' to 'tuple<typename __unwrap_ref_decay<AudioProcessorValueTreeState &>::type>' (aka 'tuplejuce::AudioProcessorValueTreeState')

I found I can get it to compile if I make the EditorView constructor take a pointer instead of a pass-by-reference juce::AudioProcessorValueTreeState.

[ImJimmi]

Hi @ImJimmi. I'm not sure this is really the right place to mention it but I tried integrating JIVE into a simple plugin project today and failed miserably. I have seen the View way of handling parameter attachments but in practice I found it difficult to understand and make good use of. I take it from this ticket that this is an area still needing some development? It would be very instructive if there was a functioning example plugin that uses JIVE with parameter attachments. I don't think the trivial example in the docs will compile.

EDIT: The trivial example does compile, I'm not sure why I was running into problems with makeView. In any case there are some usability challenges with more than one attachment (how to search for the correct GuiItem?) and a working full example would be helpful.

EDIT2: Ok actually the example does not compile. I get an error stemming from the makeView call:

error: no matching conversion for functional-style cast from 'juce::AudioProcessorValueTreeState' to 'tuple<typename __unwrap_ref_decay<AudioProcessorValueTreeState &>::type>' (aka 'tuplejuce::AudioProcessorValueTreeState')

I found I can get it to compile if I make the EditorView constructor take a pointer instead of a pass-by-reference juce::AudioProcessorValueTreeState.

Ahh thanks for reporting - I hadn't thought to check the examples in the docs. I'll go through them and update where needed.

[ImJimmi]

@forestbond v1.3 adds support for parameter attachments as well as a new gain plugin example that utilises this feature. The outdated example in the docs was also removed, thanks again for reporting!