Having some confusion with PGM

[Digital_Larry]

OK I think I am narrowing down the issue. I will start with some recommendations about the information presented here.

The #1 How to get started document from September 2020 is obsolete so it should be unpinned.

How to #1 add PluginGuiMagic to a new plugin

PluginGuiMagic consists of the module foleys_gui_magic. You get it from github. To use it, you need to either clone the repository or download preferably the latest release. CAVEAT: The Projucer will only accept the module if it has the name foleys_gui_magic. The download function adds a suffix, either the tag name or sometimes the branch name. You need to reverse that and rename the folder back to foleys_gui_magic. [Add-module] Now you add the module via Projucer to the project, or if you …

It should have an entry at the top indicating that it is out of date and a link to the correct doc (which should be pinned). I haven’t got as far as #2 or #3 pinned doc so I don’t know if those need an update also.

New way to use PGM in plugins

Since Version 1.3.0 there is an easier way to use PluginGuiMagic in a JUCE based plugin. What stays the same is to add the foleys_gui_magic to the project. Instead of inheriting juce::AudioProcessor inherit foleys::MagicProcessor You don’t need to add a magicState. It is alreadt added in the new base class You don’t need to use AudioProcessorValueTree, but you can. You need to remove the hasEditor and createEditor from your processor class, so the editor is created from the base class You sho…

I am pretty sure the problem gets down to this section.

FaustPlugInAudioProcessor::FaustPlugInAudioProcessor()
: foleys::MagicProcessor (getBusesProperties()), fParameterUI(this)	
#endif
{
    bool midi_sync = false;
    int nvoices = 0;
    
    mydsp* tmp_dsp = new mydsp();
    MidiMeta::analyse(tmp_dsp, midi_sync, nvoices);
    delete tmp_dsp;
	
#ifdef PLUGIN_MAGIC
    auto defaultGUI = magicState.createDefaultGUITree();
    magicState.setGuiValueTree(defaultGUI);
#endif

I’m just loading the defaultGUI.

If I try to use this approach:

magicState.setGuiValueTree (BinaryData::magic_xml, BinaryData::magic_xmlSize);

I get something wrong with BinaryData.

If I try to build, this happens:

I’ll look at how this is handled in the example which I got running.

This declaration is found in my project and the SignalGenerator project.

namespace BinaryData {
using namespace BinaryDataFallbacks;
}

When I look for declarations of this in SignalGenerator, I get:

When I try to find the declaration in my own project, I get:

(nothing)