On Monday 03 March 2014 08:16:29 Sergey wrote:
> OK, modified it to handle c-style includes. Try to apply the attached diff.
I just applied the patch in modified form. I had a) a concern that
currentDirectory was not handled correctly (since that member variable is also
read in push_opcode()) an
Hi!
OK, modified it to handle c-style includes. Try to apply the attached diff.
---
Sincerely yours,
Sergey
On 03/02/2014 11:41 PM, Andreas Persson wrote:
Even though it isn't listed on their custom opcodes page, Aria seems to
have an include statement, as one of the instrument in the Free So
Christian Schoenebeck wrote On 2014-02-28 15:44:
> On Friday 28 February 2014 13:09:39 Sergey wrote:
>> I've searched available SFZ specs and there is no official include
>> operator. So yes, it is my suggestion.
>
> In general I think that extension makes sense, so I am not opposed to apply
> it
On Friday 28 February 2014 13:09:39 Sergey wrote:
> I've searched available SFZ specs and there is no official include
> operator. So yes, it is my suggestion.
In general I think that extension makes sense, so I am not opposed to apply it
to the sampler. I just wonder whether a special prefix sha
On Friday 28 February 2014 08:46:45 Sergey wrote:
> With a patch, everything is simplified to the following:
> === master.sfz ===
> .include key-up-layer.sfz
> .include key-down-layer.sfz
> .include pedal-up-down.sfz
> .include release-layer.sfz
> === end of master.sfz==
Is that ".include" stateme
Hi!
I've just implemented a trivial SFZ parser patch to allow composite SFZ
files. The rationale behind it is that after converting musical
instrument from KONTAKT format I often have multiple SFZ files (main
instrument, pedal up-down sounds, release sounds, etc). Loading each SFZ
in a dedicat
