So you loose all the programming inside the .gig? Not that I know the implication of that but there must be a ton of attack, release type stuff in there.dahnielson wrote: You need to extract the samples from the .gig file, e.g. you can use gigextract that ships with libgig to do that. Next you author a SFZ definition file in you favorite text editor (or write a script file to generate it) to use the extracted samples. Regions containing the start of a new note need the trigger= opcode set to "attack" (the default), legato samples without the attack bit need the trigger= opcode set to "legato", and if it's true legato we're implementing, need the sw_previous= opcode set to indicate what the previous note should have been to trigger the region.
I'm going to write more about it in the future when I have time to play around and help Grigor develop the SFZ engine.
I guess what I should do is extract one instrument and start to look around.
Your manual/write up would be much appreciated.
Thanks!