Hi, I was parsing xml cubase track exported because I want to do in multiple tracks almost the same actions throw script, but I see the state of plugins is saved in hexadecimals, there’s a way to read it getting values of parameters or maybe converting it in base64 readible in juce setStateInformation?
I totally misinterpreted your problem (I thought you own the plugin’s code).
The state of the plugin seems written in binary format. I am afraid that only FabFilter engineers know how to decode it
I tried to write this (searching hardcode my micro on graph to test) to set state of the plugin (with this code with setStateInformation nothing happens), but it seems strange what memoryBlock.toString() prints…
I don’t know if with this procedure I’m on the right track to get what I need, 'cause I’m afraid cubase adds something of its own to this hexadecimal string…
There’s no requirement that the hosts have to store the plugin binary state data in some particular way. (It just needs to somehow end up exactly the same as the plugin originally provided it.) The hosts may add their own things and they may compress and/or encrypt the data. The chances are pretty low you will be able to get the plugin state data from another host and reuse it elsewhere.
just a thing that I don’t understand: I’d like to have from juce::MemoryBlock a binary string that represent the state of plugin (so 0 and 1 digits), how can I get it? also toBase64Encoding doesn’t encode only the state of plugin (and add dots, it’s not a real base64…).
I observed what steinberg store on Hexadecimal string that represents the state of plugin and it doesn’t seem it’s so cripted… so my idea is transform steinberg hexadecimal to binary, get on my app the binary of the same plugin and compare them, I expect to have in the middle the same piece of digits and then reconvert this piece of digits in something readible from setStateInformation
I only want to import state of plugins I use in cubase in the same plugins loaded in my host to have the same presets without saving and loading them each time (I’m speaking of thousand plugins…)
Not yet used reaper … but it would be very useful to be able to read this content from daws like cubase or reaper to recreate the state of the plugins in a proprietary daw and also vice versa to load work done on an xml into these daws (on the other hand, for example, cubase already provides a xml in which all track parameters are in the clear, it’s a pity you can’t take advantage of this also for the plugin binary)…