I am suspecting something like that too.On 07-08, 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.Well, Zyn isn't doing that, so it's somewhere between Qtractor and Qt that this weird escaping is happening.
Woah, wait. What? But... Am I missing something, I can't see any of said params in the "properties" window, maybe it's another Qtractor idiosyncratic limitations (I learned to love them) :pPPS -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 :pThe majority of Zyn parameters can be bound via MIDI learn and there's a good number of parameters which update running notes (added within the past version or two) on changes to either the GUI controls or bound MIDI CCs.
Well, I'm using the one in the KXStudio repos, I guess it's up to date... WaitIf there's a particular parameter which doesn't automate well with the current zyn-git, I'd encourage you to make a note of it on the feature tracker.
The only parameters which have major technical limitations with automation are parameters within the oscillator view, the resonance graph, and anything which requires the apply button in Pad Synth. --Mark
_______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
-- Philip "xaccrocheur" Yassin http://manyrecords.com http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur