Re: [Linuxsampler-devel] trials

[Christian S. <sch...@so...>]

Es geschah am Mittwoch, 25. August 2004 22:03 als Robert Jonsson schrieb:
> Hi guys,
>
> Back yet from your respective vacations? :-)

Jo! :)

> Compilation worked very well, launching qsampler worked aswell, but I was
> unable to instantiate any channels from qsampler, everytime it complained
> about these things:
>
> 21:56:11.257 lscp_set_channel_audio_type: There is no audio output driver
> 'Jack'. (errno=0)
> 21:56:11.261 lscp_set_channel_midi_type: There is no midi input driver
> 'Alsa'. (errno=0)
> 21:56:11.265 lscp_set_channel_midi_port: There is no MIDI input port with
> index 0. (errno=0)
> 21:56:11.284 lscp_set_channel_midi_channel: There is no MIDI input port
> with index 0. (errno=0)
> 21:56:11.302 lscp_load_instrument: No audio output device on channel
> (errno=0)

Should already be fixed with latest CVS.

> The port names are not spelled uppercase which in later tests seems like it
> could be the problem. I rumaged around in the sources for a while but could
> not find where these come from...
>
> I had built linuxsampler from cvs and qsampler from the latest version
> which might account for this discrepancy?

Hope it works with latest CVS, so please try again.

> Anyway, having failed that I grabbed the specs and tried going from there.
> And got a bit further:
>
> CREATE AUDIO_OUTPUT_DEVICE JACK
> CREATE MIDI_INPUT_DEVICE ALSA
> ADD CHANNEL
> LOAD ENGINE GigEngine 0
> SET CHANNEL AUDIO_OUTPUT_DEVICE 0 0
> these worked, after this I was going to add a midi device also, but this I
> was unable to do.
> SET CHANNEL MIDI_INPUT_CHANNEL 0 0
> returned that the midi port didn't exist
> I tried some MIDI_PORT commands also to no avail.

That didn't work, because the default amount of ports was 0 by default.

	CREATE MIDI_INPUT_DEVICE ALSA PORTS=1

or 

	SET MIDI_INPUT_DEVICE_PARAMETER 0 PORTS=1

after your CREATE command would have done it. But I have changed the default 
amount of ports to 1 now, so don't worry about that.

> Also, a minor bug in the interpreter, even if you input a command correctly
> but give it the wrong arguments the interpreter still complains:
> Err:0:Unknown command.
>
> Which I really think should be changed to:
> Err:x:Bad parameter.
> or something similar.

Yes, known. Not fixed yet due to low priority.

> All for tonight, keep up the good work!

Keep up testing and reporting bugs! I'll try to fix it ASAP.

Thanks!

CU
Christian