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 dedicated channel sometimes break things (release layer not playing most notable). So there was a need to assemble layers back into one long SFZ.
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== The patch is really trivial - most of the File(...) constructor body moved out to separate method parseFile(...) which is called recursively on encounter of ".include" if the beginning of a file line. Do you think it is useful to have this functionality in a trunk of linuxsampler, or I'd better keep that as a local patch ? --- Sincerely yours, Sergey ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
