[LAD] ZASFX is mean with my Qtractor XML session files

[Rui Nuno Capela]

On 07/08/2016 01:28 PM, Philip Yassin wrote:
> It has been like this for as long as I can remember: When I insert a
> ZASFX plugin instance in a Qtractor session, gone is the joy I have
> editing my session files, because all the ZADSFX entries are messed up:
> the "<" character is represented by its ASCII entity: "<" and it make
> even my Emacs choke: scrambles the formatting, the syntax highlight, the
> indentation, everything. The right chevron is OK.
>
> Looks like this:
>
> (...)
>    <plugins>
>     <plugin type="LV2">
>      <filename>http://zynaddsubfx.sourceforge.net</filename>
>      <index>0</index>
>      <label>ZynAddSubFX</label>
>      <preset></preset>
>      <direct-access-param>-1</direct-access-param>
>      <activated>1</activated>
>      <configs>
>       <config key="urn:distrho:state">
> <?xml version="1.0f" encoding="UTF-8"?>
> <!DOCTYPE ZynAddSubFX-data>
> <ZynAddSubFX-data version-major="2" version-minor="5"
> version-revision="4" ZynAddSubFX-author="Nasca Octavian Paul">
> <INFORMATION />
> <BASE_PARAMETERS>
> (...)
>
>
> I hate to be the "Sales dept guy in the tech open-space" but surely
> /this doesn't sound like something that would be that hard to fix/ (tm) ;p
>
> Oh, and it doesn't cause any other problem that I can think of, BTW. But
> still.
>
>
> Phil
>
> PS - ZynAddSubFx is, despite everything, the coolest synth I worked
> with, by far. I want to warmly thank everybody that made using it in
> Qtractor possible, guys, you are heroes of mine.
> PPS -Is there any plans to have (at least some of) its controls
> automatable? I asked this in a whisper because I want it so bad it's
> ridiculous :p
>

uh oh... maybe it's the distrho implementation lv2_state to blame? maybe 
a lv2::string is being reported (by disthro), and then qtractor's xml 
parser (qt xml/dom) just escapes the state as bland xml::cdata aka. POD 
(plain old data)?

otoh. zynaddsubfx is a dang complicated contraption... i doubt it will 
ever have any subset (yes, tiny subset) of parameters that may have any 
reasonable automatable capabilities, besides, of course, the nominal 
ones: read channel volume, panning, modulation, filter cutoff and reso, 
regular effect-sends, like chorus and reverb. and that is already plenty 
overwhelming to address from the plugin pov. (no matter it's vst or lv2 
we're talking). from a host's stand point, it gets what it gets, nothing 
else. yoshimi might have an edge over there, but still, you get what you 
get :)

cheers
-- 
rncbc aka. Rui Nuno Capela