On Sat, 7 Jul 2012 09:39:04 +0200 (CEST) Julien Claassen <julien@xxxxxxxxxxx> wrote: > Hello Nils! > I do like the way, this is going. One question about the sidekick tool: Why > create the sfz-file in temp and not in the current directory? OK, it's > supposed to be a temporary file, but the other main expectation is, that > programs create files in the current working directory. Just wondering... > Otherwise it's great! > Warmly yours > Julien The are new features now which marks version 1.4. Instead of a temp file you cn create a regular sfz file with relative paths. Example: lisalosfzgenerator.py path/to/samples -o path/to/output.sfz The working directory is not a good idea here because the path you give for output.sfz (which can be the working directory of course. Just give the filename without any paths) is the root path for the sfz internally. Also new: If you use lisalosfzgenerator.py with a single wave or ogg file, instead of a sample directory, you get that sample mappend and transposed over the whole keyboard range. If you choose to load a single file the -k <number> parameter will be the root, the center of the sample mapping. Example to load a recorded piano middle C to the right keys: lisalosfzgenerator.py pianoC.wav -k 60 Example to load a Glockenspiel middle C (note off is ignored aka. percussive mode) lisalosfzgenerator.py pianoC.wav -pr -k 60 Of course all this in in the -h parameters. There is also a small convenience program called lisalo-quickload-samples which will start directly start Linuxsampler through Lisalo with your wave dir/file. lisalo-quickload-samples foo.wav -k and -p work here as well. Nils _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
