Summary: | Rosegarden doesn't sound when Qsampler is running | ||
---|---|---|---|
Product: | QSampler | Reporter: | Francisco <fmcamas> |
Component: | qsampler | Assignee: | Rui Nuno Capela <rncbc> |
Status: | CLOSED FIXED | ||
Severity: | normal | CC: | xbran |
Priority: | P2 | ||
Version: | 0.1.5 | ||
Hardware: | Other | ||
OS: | Linux | ||
Attachments: | lscp file |
Description
Francisco
2007-11-18 20:51:29 CET
Save your qsampler session into a .lscp file and attach it here. You must have at least one sampler channel loaded with one instrument (.gig) file, and properly directed to the MIDI input device and ALSA|ARTS|JACK? device. In case of JACK, make sure the output ports are connected to your auditory device (system, alsa_pcm); can either use the devices dialog to make this binding or, yours truly, qjackctl. Created attachment 19 [details]
lscp file
And this is the list of messages I get when I load the lscp file: 00:06:02.037 Client connecting... 00:06:02.039 Server is starting... 00:06:02.039 linuxsampler 00:06:02.042 Server was started with PID=6402. lscp_client_create: cmd: connect: Conexión rechazada (Spanish for rejected connection) LinuxSampler 0.5.0 Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck Copyright (C) 2005-2007 Christian Schoenebeck Detected features: MMX SSE SSE2 Creating Sampler...OK Registered sampler engines: 'GIG' Registered MIDI input drivers: ALSA Registered audio output drivers: ALSA,ARTS,JACK Loading instrument editor plugins...OK Registered instrument editors: Starting LSCP network server (0.0.0.0:8888)...OK 00:12:16.088 Client connecting... 00:12:16.089 Client receive timeout is set to 1000 msec. 00:12:16.090 Client connected. 00:12:16.097 New session: "Untitled1". LinuxSampler initialization completed. :-) LSCPServer: Client connection established on socket:4. LSCPServer: Client connection established on socket:5. Thread: WARNING, can't assign realtime scheduling to thread! Thread: WARNING, can't assign realtime scheduling to thread! Starting disk thread...OK Scheduling '/home/fmcamas/VSL_Samplers/01 VIOLIN-ENS_standard.gig' (Index=1) to be loaded in background (if not loaded yet). Loading gig file '/home/fmcamas/VSL_Samplers/01 VIOLIN-ENS_standard.gig'...OK Loading gig instrument ('/home/fmcamas/VSL_Samplers/01 VIOLIN-ENS_standard.gig',1)...Scheduling '/home/fmcamas/VSL_Samplers/01 VIOLIN-ENS_standard.gig' (Index=4) to be loaded in background (if not loaded yet). 00:12:24.161 Open session: "/home/fmcamas/Ubuntu Configuraci On your lscp file, this one looks suspicious: # Global volume level SET VOLUME 0 certainely you can't hear a thing with that volume level; try raising it above zero, with the provided volume slider on qsampler toolbar and check if the problem is solved just like that. I'll raised it but the changes in the volume level are not written in the lscp file. Even if the volume level is at the top I can't hear anything. (In reply to comment #4) > On your lscp file, this one looks suspicious: > > # Global volume level > SET VOLUME 0 > > certainely you can't hear a thing with that volume level; try raising it above > zero, with the provided volume slider on qsampler toolbar and check if the > problem is solved just like that. > > I think I know what the problem is. Because we had something like this before. I think it's caused by your localization setting. Try running qsampler (and LS if you launch them separately) with the english default localization. It's been a while, but I think it's: LANG="C" qsampler and let us know if the 0 volume phenomenon is gone that way. If it works that it would be of course a bug, but at least we know for what to look for. But please make sure you really use the latest CVS versions, so we don't have to search for bugs that are already fixed. It works! Volume is saved with a non-null value and I get sound from Rosegarden. Thank you very much! *** Bug 94 has been marked as a duplicate of this bug. *** Ok, this issue is finally fixed with the CVS version of liblscp (0.5.5.10). So starting from that liblscp version, qsampler should finally also behave correctly with different locale settings. |