|
From: Mark K. <mar...@co...> - 2003-12-29 15:33:20
|
Hi, I know I can use '-n 2' to set the number of periods used by LS and Alsa, but I'm not clear how I set the buffer size in LS. I'd like to run LS with the same buffer sizes that I run GSt under Windows with when doing comparisons between them. Is there a command line option for this? Thanks, Mark |
|
From: Christian S. <chr...@ep...> - 2003-12-29 17:20:05
|
Es geschah am Montag, 29. Dezember 2003 16:33 als Mark Knecht schrieb:
> Hi,
> I know I can use '-n 2' to set the number of periods used by LS and
> Alsa, but I'm not clear how I set the buffer size in LS. I'd like to run
> LS with the same buffer sizes that I run GSt under Windows with when
> doing comparisons between them.
>
> Is there a command line option for this?
Yes, but there's no -n switch, actually these are the switches you want:
--numfragments sets the number of audio fragments
--fragmentsize sets the fragment size
and btw there are three new commandline switches:
--instrument index of the instrument in the instrument file if it
contains more than one (default: 0)
--volume sets global volume gain factor (a value > 1.0 means
amplification, a value < 1.0 means attenuation,
default: 0.25)
--inputclient connects to an Alsa sequencer input client on startup
(e.g. 64:0 to connect to a client with ID 64 and port 0)
'linuxsampler --help' for more.
CU
Christian
|
|
From: Mark K. <mar...@co...> - 2003-12-29 17:29:51
|
On Mon, 2003-12-29 at 09:15, Christian Schoenebeck wrote: > Es geschah am Montag, 29. Dezember 2003 16:33 als Mark Knecht schrieb: > > Hi, > > I know I can use '-n 2' to set the number of periods used by LS and > > Alsa, but I'm not clear how I set the buffer size in LS. I'd like to run > > LS with the same buffer sizes that I run GSt under Windows with when > > doing comparisons between them. > > > > Is there a command line option for this? > > Yes, but there's no -n switch, actually these are the switches you want: > > --numfragments sets the number of audio fragments > --fragmentsize sets the fragment size But LS does seem to recognize -n as the number of periods! mark@Wizard mark $ linuxsampler --gig /mnt/samples/Gigs/Pianos/Bardstown\ Audio/The\ Bosendorfer\ Imperial\ Grand\ Version\ 2.2.gig -n 2 Initializing audio output...Warning: your soundcard doesn't support chosen hardware parameters; trying to compensate support lack with plughw...OK Loading gig file...OK Caching initial samples...OK Starting disk thread...OK Starting MIDI in thread...WARNING, can't mlockall() memory!: Operation not permitted OK WARNING, can't mlockall() memory!: Operation not permitted sched_setscheduler: Operation not permitted Starting audio thread...OK LinuxSampler initialization completed. WARNING, can't mlockall() memory!: Operation not permitted) sched_setscheduler: Operation not permitted LinuxSampler stopped due to SIGINT0 (Max: 000, Unused: 100) Error snd_pcm_writei failed. : Interrupted system call Segmentation fault mark@Wizard mark $ linuxsampler --gig /mnt/samples/Gigs/Pianos/Bardstown\ Audio/The\ Bosendorfer\ Imperial\ Grand\ Version\ 2.2.gig -n 4 Initializing audio output...Warning: your soundcard doesn't support chosen hardware parameters; trying to compensate support lack with plughw...Error setting number of periods. : Invalid argument mark@Wizard mark $ > > and btw there are three new commandline switches: > > --instrument index of the instrument in the instrument file if it > contains more than one (default: 0) Great!! Is there any way yet to query a gig file for how many instruments it contains, and what their names are? None the less, it's great to have this capability. > --volume sets global volume gain factor (a value > 1.0 means > amplification, a value < 1.0 means attenuation, > default: 0.25) Cool. I'll try it out and see what I need to do to be approximately equal to GSt. > --inputclient connects to an Alsa sequencer input client on startup > (e.g. 64:0 to connect to a client with ID 64 and port 0) Thanks! Thanks! Thanks! Thanks! BTW - If I didn't say it, then thanks! > > 'linuxsampler --help' for more. > Will download and build now. Will try out in about 8 hours or so. Cheers, Mark |
|
From: Christian S. <chr...@ep...> - 2003-12-29 22:10:57
|
Es geschah am Montag, 29. Dezember 2003 18:29 als Mark Knecht schrieb: > But LS does seem to recognize -n as the number of periods! At the moment, yes, you can use the one character abbreviation for all available switches at the moment, but this only works as long as it's unique. > > and btw there are three new commandline switches: > > > > --instrument index of the instrument in the instrument file if it > > contains more than one (default: 0) > > Great!! Is there any way yet to query a gig file for how many > instruments it contains, and what their names are? None the less, it's > great to have this capability. Not in linuxsampler itself yet, but there are a couple of command line tools in the libgig CVS module: cvs -d:pserver:ano...@cv...:/home/schropp/linuxsampler co libgig (one line of course) To compile: make -f Makefile.cvs && ./configure && make then you can run for example: src/gigdump GIGFILE | less and see all samples, instruments and many, many other informations. It's quite much, so better pipe the output as shown through 'less' or redirect the output to a file. > > --inputclient connects to an Alsa sequencer input client on startup > > (e.g. 64:0 to connect to a client with ID 64 and port > > 0) > > Thanks! Thanks! Thanks! Thanks! > > BTW - If I didn't say it, then thanks! :) You're welcome. And btw I also already commited looping support. I just usually don't post every CVS change to the mailing list. CU Christian |
|
From: Mark K. <mar...@co...> - 2003-12-29 20:15:33
|
On Mon, 2003-12-29 at 09:15, Christian Schoenebeck wrote: > --numfragments sets the number of audio fragments tested - working > --fragmentsize sets the fragment size tested - not sure if it's working. It let's me set strange sizes like 512 bytes. Does LS do any checking of the value provided? > > and btw there are three new commandline switches: > > --instrument index of the instrument in the instrument file if it > contains more than one (default: 0) tested - working in the sense that LS does correctly understand when a value given is larger than the number of instruments available in the gig file. I have not listened to the actual sound to ensure that it's loading the right instrument. > --volume sets global volume gain factor (a value > 1.0 means > amplification, a value < 1.0 means attenuation, > default: 0.25) Not tested yet - will do this evening when I do the sounds. > --inputclient connects to an Alsa sequencer input client on startup > (e.g. 64:0 to connect to a client with ID 64 and port 0) Tested - kaconnect shows the connection after LS has loaded and the connection goes away when LS is killed. Good work! Thanks! Cheers, Mark |
|
From: Mark K. <mar...@co...> - 2003-12-29 20:58:08
|
On Mon, 2003-12-29 at 12:14, Mark Knecht wrote: > > --fragmentsize sets the fragment size > > tested - not sure if it's working. It let's me set strange sizes like > 512 bytes. Does LS do any checking of the value provided? > <hehe!!> Sorry - should have said 513 bytes! Oops! |