On Wed, Sep 28, 2011 at 1:37 PM, Christian Schoenebeck
<schoeneb...@linuxsampler.org> wrote:
> But I definitely agree that adding those as extension would make sense!
> However
> since those are not really CCs and the numbers used here are somewhat not
> really standardized, I would probably use some textual replacement probably.
No, the CCs don't really make sense. Opcodes like:
xfin_lopolyaft
xfin_hipolyaft
xfout_lopolyaft
xfout_hipolyaft
xf_polyaftcurve
xfin_lochanaft
xfin_hichanaft
xfout_lochanaft
xfout_hichanaft
xf_chanaftcurve
... might make more sense, though they lead to the same problem that
lopolyaft and hipolyaft have, that being that the note information in
the aftertouch message isn't taken into account.
I do wonder how much software (aside from SFZ itself) uses the hackish
cc opcodes for channel pressure and polyphonic aftertouch. It may be
worth implementing for compatibility reasons.
If and when LinuxSampler does gain crossfading for channel pressure
and polyphonic aftertouch, I'll add whatever opcodes LinuxSampler uses
as an option to synthclone's SFZ plugin.
Thanks for the reply,
--
Devin Anderson
devin (at) charityfinders (dot) com
CharityFinders - http://www.charityfinders.com/
synthclone - http://synthclone.googlecode.com/
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
