linuxsampler-devel — This list is for discussing LinuxSampler development issues and ideas

[Linuxsampler-devel] Skin complete

[ThoR <th...@ho...>]

hehe, i finished it moments ago, its located at
www.hocore.com.ar/imgz/skin1.jpg

should anyone wants to skin the QT with it, drop me a line and i will =
make all the parts to skin the different objects. the central square =
look lame to me, but i had no more ideas for it (think i should get rid =
of it, but the empty space looks even worse)
well if anyone has some new ideas drop a comment (im kind of in between =
projects right now so i get very boored at work, plus helping a really =
coooool project is a nice thing)

just an idea. is it possible to add a master mixer unit (like reason) =
don=B4t know about the dificulty on that one, or the priorities in the =
project, but that would be really coool :P

Jorge

[Linuxsampler-devel] Design ideas

[ThoR <th...@ho...>]

mmm, i know i sent this mail an hour ago, but i didnt received it back, =
so i probably sent it elsewhere lol

well, i was thinking yesterday night on the qsampler skin and did a =
rough block diagram to distribute the space, it can be seen at
http://www.hocore.com.ar/imgz/draft.bmp

i need some feedback from rui specially, the thing is that a don't know =
qt and want to know where it can get (example, i like the turning knobs, =
but to do a skinned one its no easy task in the languajes i know).
also would like some ideas on what to put on the skin.

regards

Jorge

[Linuxsampler-devel] design ideas

[<th...@ho...>]

Well i'veen thinking what to make 4 the qt skin, so i did a draft (mspaint) in 
some sort of block diagram of what to put in there, here i would like especially 
rui's feedback on what can and can´t be made (like the knobs for example, i 
know i would like some reason like turning knobs, but the rotating effect its 
not easy to make), height,width of each module,etc.
the LCD i turned to blue, since i liked it better too :P

hope u all enjoy.

PS, the draft block diagram is at www.hocore.com.ar/imgz/draft.bmp

Re: [Linuxsampler-devel] New logo

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

Es geschah am Montag, 30. August 2004 22:30 als th...@ho... schrieb:
> hehehe, well, thanks 4 the feedback, folowing rui's idea, i have meda a n=
ew
> logo. the crystal finish is somewhat unfinished and lame becouse i had to
> format my computer and havent installed some tools yet, but can be worked
> on. I personally like the flat one best, so i have made 2 images completly
> equal (1 flat, 1 skewed) and posted them at
> http://www.hocore.com.ar/imgz/logoskew.jpg
> http://www.hocore.com.ar/imgz/logoflat.jpg
>
> and thats about it, i=B4ll start a poll on the forum to see wich one u li=
ke
> best

The galaxy idea is cool, but the S itself in the middle could IMO have a bi=
t=20
more outlines, like the current logo:

 http://cvs.linuxsampler.org/pix/LinuxSampler_Logo_296x198.png

here btw is the source vector graphic file of the current logo:

 http://www.linuxsampler.org/artwork/LinuxSampler_Logo.svg

CU
Christian

Re: [Linuxsampler-devel] Last one today

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

Es geschah am Dienstag, 31. August 2004 00:19 als th...@ho... schrieb:
> well, im heading to the university now, but i was able to finish a little
> something over the skin most people liked
>
> http://www.hocore.com.ar/imgz/front1-1.jpg
>
> there it is :P
>
> hope u all enjoy

How about making it more blue, especially the display?

CU
Christian

Re: [Linuxsampler-devel] Last one today

[Mark K. <mk...@co...>]

th...@ho... wrote:
> well, im heading to the university now, but i was able to finish a little 
> something over the skin most people liked
> 
> http://www.hocore.com.ar/imgz/front1-1.jpg
> 
> there it is :P
> 
> hope u all enjoy
> 
> PS. i actually don´t know if this skins can be imported in QT or how that is 
> done (i really dont know anything about QT, i based the design on what can be 
> made in VB6, so if there is any restriction, please inform me)

Groovy stuff. I especially like the way the panel looks lighter on the 
edges than the center. All quite cool!

- Mark

[Linuxsampler-devel] Last one today

[<th...@ho...>]

well, im heading to the university now, but i was able to finish a little 
something over the skin most people liked

http://www.hocore.com.ar/imgz/front1-1.jpg

there it is :P

hope u all enjoy

PS. i actually don´t know if this skins can be imported in QT or how that is 
done (i really dont know anything about QT, i based the design on what can be 
made in VB6, so if there is any restriction, please inform me)

Re: [Linuxsampler-devel] New logo

[Mark K. <mk...@co...>]

th...@ho... wrote:
> hehehe, well, thanks 4 the feedback, folowing rui's idea, i have meda a new 
> logo. the crystal finish is somewhat unfinished and lame becouse i had to 
> format my computer and havent installed some tools yet, but can be worked 
> on. I personally like the flat one best, so i have made 2 images completly 
> equal (1 flat, 1 skewed) and posted them at
> http://www.hocore.com.ar/imgz/logoskew.jpg
> http://www.hocore.com.ar/imgz/logoflat.jpg
> 
> and thats about it, i´ll start a poll on the forum to see wich one u like best
> 

I like the glactical swirl, but looking at it I wonder about the left 
part of the swirl going straight up, thus making an L, and the rest of 
the swirl looking like the S.

I like the looks alot.

- Mark

[Linuxsampler-devel] New logo

[<th...@ho...>]

hehehe, well, thanks 4 the feedback, folowing rui's idea, i have meda a new 
logo. the crystal finish is somewhat unfinished and lame becouse i had to 
format my computer and havent installed some tools yet, but can be worked 
on. I personally like the flat one best, so i have made 2 images completly 
equal (1 flat, 1 skewed) and posted them at
http://www.hocore.com.ar/imgz/logoskew.jpg
http://www.hocore.com.ar/imgz/logoflat.jpg

and thats about it, i´ll start a poll on the forum to see wich one u like best

Re: [Linuxsampler-devel] first post

[Rui N. C. <rn...@rn...>]

Hi Jorge,

> Hi all, my name is jorge luis carrieres (AKA ThoR), and this is the
> first post i make on the devel list. i am not a great C++ programmer,
> only do things on VB6. However, i consider myself a talented Graphical
> designer, so i would like to contribute to the project on that area.
> on
> http://www.hocore.com.ar/imgz/front1.jpg
> http://www.hocore.com.ar/imgz/front2.jpg
> http://www.hocore.com.ar/imgz/logo.jpg
>
> are some ideas i have had. thoug i dont know what half the things on the
> QT control do, i cant be of much more assistance untill i get more
> specifications (jeje, like width, height, color depth, general idea).
> i have also posted there an idea of logo, that if liked can work on.
>

Yeah, front1 looks cool. The logo is also whirlcool :) however I guess
Chris has come up with one too (as seen on linuxsampler.org homepage).

As you might guess already, all this artwork should be tunneled to
qsampler, which is the one GUI to linuxsampler server engine. There, your
logo seems better than the sluggish one I drew (look on qsampler homepage
;). If you can handle a suggestion I would prefer to have the whirl a
lil'bit skewed, aligned on a main diagonal, and without the linux(s)ampler
lettering, of course (see attachement for the concrete idea). A
crystal-like finishing would be awesome :)

Cheers, and welcome.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...

Re: [Linuxsampler-devel] first post

[Mark K. <mar...@co...>]

On Mon, 2004-08-30 at 09:35, th...@ho... wrote:
> Hi all, my name is jorge luis carrieres (AKA ThoR), and this is the first post i 
> make on the devel list. i am not a great C++ programmer, only do things on 
> VB6. However, i consider myself a talented Graphical designer, so i would like 
> to contribute to the project on that area.
> on
> http://www.hocore.com.ar/imgz/front1.jpg
> http://www.hocore.com.ar/imgz/front2.jpg
> http://www.hocore.com.ar/imgz/logo.jpg

Wow! I especially like #1 and #3.
> 
> are some ideas i have had. thoug i dont know what half the things on the QT 
> control do, i cant be of much more assistance untill i get more specifications 
> (jeje, like width, height, color depth, general idea). i have also posted there an 
> idea of logo, that if liked can work on.
> I have also set up a forum (if this was not made in the past for a reason, andi 
> made a mistake by doing it i am very sorry, and will kill it right away, if not, i 
> can hand over the administration to anyone u find fit).
> 
> the forum is at 
> 
> http://p208.ezboard.com/blinuxsampler
> 
> 
> ThoR
> 

thanks for showing up!

- Mark

[Linuxsampler-devel] first post

[<th...@ho...>]

Hi all, my name is jorge luis carrieres (AKA ThoR), and this is the first post i 
make on the devel list. i am not a great C++ programmer, only do things on 
VB6. However, i consider myself a talented Graphical designer, so i would like 
to contribute to the project on that area.
on
http://www.hocore.com.ar/imgz/front1.jpg
http://www.hocore.com.ar/imgz/front2.jpg
http://www.hocore.com.ar/imgz/logo.jpg

are some ideas i have had. thoug i dont know what half the things on the QT 
control do, i cant be of much more assistance untill i get more specifications 
(jeje, like width, height, color depth, general idea). i have also posted there an 
idea of logo, that if liked can work on.
I have also set up a forum (if this was not made in the past for a reason, andi 
made a mistake by doing it i am very sorry, and will kill it right away, if not, i 
can hand over the administration to anyone u find fit).

the forum is at 

http://p208.ezboard.com/blinuxsampler


ThoR

Re: [Linuxsampler-devel] example LSCP scripts (was: trials)

[Robert J. <rj...@sp...>]

s=F6ndagen den 29 augusti 2004 15.35 skrev Christian Schoenebeck:
> Es geschah am Sonntag, 29. August 2004 14:41 als Robert Jonsson schrieb:
> > Got it to work eventually, not entirely stable but not bad either.
> > Current problem is that I only seem able to select patch 0. Is this
> > expected with the current version or am I missing something?
>
> You should be able to select any instrument from a .gig file. Maybe you're
> referring to the GUI behavior?=20

Ah, yes, silly of me. I was indeed mostly trying the GUI and getting a bit=
=20
confused with naming conventions and things.

I got it working finally, lovely! Still a bit to go but=20
getting closer all the time ;).

As you might know the thing I'm trying to get to work right now is Drumkit=
=20
from Hell. First I note that linuxsampler takes 204mb of memory when loadin=
g=20
both the close and rear micked kits. Instinctively it's a bit much but then=
=20
again there are alot of samples...
I got it to crash quite easilt also, just playing this setup, I will=20
investigate this more.=20
I also had X vanish a few times while testing linuxsampler. My guess is tha=
t=20
linuxsampler gets kicked/crashes from jack, jack freezes qjackctl, somethin=
g=20
bad happens, qjackctl-->X-->poof.

Ahh, here's a backtrace of one of the crashes, seems mostly unusable though=
,=20
optimized binary I presume, I will compile for debug later:

(gdb) bt
#0  LinuxSampler::gig::EGADSR::Process(unsigned,=20
RTEList<LinuxSampler::Event>*, LinuxSampler::Event*, double, double)=20
(this=3DVariable "this" is not available.
) at EGADSR.cpp:151
#1  0x400a073f in LinuxSampler::gig::Voice::Render(unsigned) (this=3DVariab=
le=20
"this" is not available.
) at Voice.cpp:529
#2  0x400945ad in LinuxSampler::gig::Engine::RenderAudio(unsigned)=20
(this=3D0x80608d8,
    Samples=3D512) at Engine.cpp:433
#3  0x400bfffe in LinuxSampler::AudioOutputDevice::RenderAudio(unsigned)=20
(this=3D0x80511c0,
    Samples=3D512) at AudioOutputDevice.cpp:251
#4  0x400d1b8b in LinuxSampler::AudioOutputDeviceJack::Process(unsigned)=20
(this=3DVariable "this" is not available.
)
    at AudioOutputDeviceJack.cpp:155
#5  0x400d1fc4 in LinuxSampler::__libjack_process_callback(unsigned, void*)=
=20
(nframes=3DVariable "nframes" is not available.
)
    at AudioOutputDeviceJack.cpp:208
#6  0x40142566 in jack_stop_freewheel () from /usr/lib/libjack.so.0
#7  0x00000200 in ?? ()
#8  0x080511c0 in ?? ()
#9  0x000005ba in ?? ()

=2D--
As for drum specific things, it is common in drumbanks to have the hihat on=
=20
several keys (as is the case here too), since a hihat is monophonic by natu=
re=20
these keys are often grouped together so only one of them can produce sound=
=20
at the time.
This does not seem to be the case here, I have no idea how things like this=
=20
work with GIG files or if it is at all possible or if the bank infact is=20
programmed for this. But my gut feeling is that it should be possible and=20
that the bank should support it.
The remaining question is then: Is it known how this works in the file form=
at=20
and is it implementable?

There are other ways to solve this so I'm not stranded but it would be good=
 to=20
know if this might work later on.

I noticed the ECHO ON in the script which is a good thing indeed. Would it =
be=20
possible to extend this to outputting text in the terminal on the server si=
de=20
also?
I'm not sure if it's the right way to do it but I imagine it would be quite=
=20
usable for debugging when running the GUI and linuxsampler in separate=20
terminals. I would for sure have liked it while trying to get the GUI to=20
dance.

All for now, keep up the good work!

/Robert

=2D-=20
http://spamatica.se/music/

[Linuxsampler-devel] example LSCP scripts (was: trials)

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

Es geschah am Sonntag, 29. August 2004 14:41 als Robert Jonsson schrieb:
> Got it to work eventually, not entirely stable but not bad either. Current
> problem is that I only seem able to select patch 0. Is this expected with
> the current version or am I missing something?

You should be able to select any instrument from a .gig file. Maybe you're 
referring to the GUI behavior? Actually the GUI works with current LS CVS, 
but it doesn't display channel informations correctly at this point.

For those of you who prefer ro run LS entirely on the console and don't want 
to read the whole LSCP doc, I attached two example LSCP scripts which show 
how to setup a LS session (including automatic connection to other JACK 
clients and ALSA sequencer clients). Both scripts setup only one sampler 
channel, but extending them to multiple sampler channels should be trivial 
for you.

As always use e.g. 'cat yourscript.lscp | netcat -t localhost 8888' to send 
the script to the running LinuxSampler instance.

CU
Christian

Re: [Linuxsampler-devel] trials

[Robert J. <rj...@sp...>]

> > 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.
>
> Ah, thanks for the explanation, will get me a bit further.

Hi again,

Got it to work eventually, not entirely stable but not bad either. Current 
problem is that I only seem able to select patch 0. Is this expected with the 
current version or am I missing something?

/Robert



-- 
http://spamatica.se/music/

[Linuxsampler-devel] Layer & Crossfades

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

Hi!

I planned to add support for layer and crossfades to the Gigasampler
engine in the next days. Unfortunately I don't have any .gig file that
uses that feature. Can somebody provide me a free .gig file that uses
layers / crossfades or can somebody create me a tiny little .gig for that?
I just need something to test, no matter how it sounds.

CU
Christian

Re: [Linuxsampler-devel] trials

[Robert J. <rob...@da...>]

On Thursday 26 August 2004 00.17, Christian Schoenebeck wrote:
> Es geschah am Mittwoch, 25. August 2004 22:03 als Robert Jonsson schrieb:
> > Hi guys,
> >
> > Back yet from your respective vacations? :-)
>
> Jo! :)

Jaha ;)

>
> > 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.

Ah, nice, a new checkin! :) I'll try this too later.
>
> > 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.

Ah, thanks for the explanation, will get me a bit further.

/Robert

Re: [Linuxsampler-devel] trials

[Robert J. <rj...@sp...>]

On Wednesday 25 August 2004 21.48, Mark Knecht wrote:
> On Wed, 2004-08-25 at 13:03, Robert Jonsson wrote:
> > Hi guys,
>
> Hi.
>
> > Back yet from your respective vacations? :-)
> >
> > I tried to get linuxsampler+qsampler working tonight. So far it is less
> > than spectacular.
>
> Bummer...
> <SNIP>
>
> > I had built linuxsampler from cvs and qsampler from the latest version
> > which might account for this discrepancy?
>
> I have had the best ressults from building everyting from Rui's LS page.
> It seems that all ends of the pipe are consistent this way.
>
> http://www.rncbc.org/ls/

Ah, didn't know these existed. I'll check it out later.

/Robert

-- 
http://spamatica.se/music/

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 LS 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 LS 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

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

Re: [Linuxsampler-devel] trials

[Mark K. <mar...@co...>]

On Wed, 2004-08-25 at 13:03, Robert Jonsson wrote:
> Hi guys,


Hi.
> 
> Back yet from your respective vacations? :-)
> 
> I tried to get linuxsampler+qsampler working tonight. So far it is less than 
> spectacular.

Bummer...
<SNIP>
> I had built linuxsampler from cvs and qsampler from the latest version which 
> might account for this discrepancy?
> 
I have had the best ressults from building everyting from Rui's LS page.
It seems that all ends of the pipe are consistent this way.

http://www.rncbc.org/ls/

[Linuxsampler-devel] trials

[Robert J. <rj...@sp...>]

Hi guys,

Back yet from your respective vacations? :-)

I tried to get linuxsampler+qsampler working tonight. So far it is less than 
spectacular.

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)

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?

---
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.

There's something I'm missing, I'm sure... I'd be grateful for some insight.

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.

All for tonight, keep up the good work! 

/Robert


-- 
http://spamatica.se/music/

Re: [Linuxsampler-devel] Dynamic Engine Loader

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

Es geschah am Mittwoch, 18. August 2004 10:45 als Pieter Palmers schrieb:
> Any ideas on this 'own' file format? I've been thinking about it and
> probably the nicest I've seen is the approach of Hydrogen: simply tar-gz
> the (wav) samples and include an XML file to describe the 'soundbank'.

XML: vote++
tar-gz: not sure about that, I would probably prefer FLAC compression for 
lossless audio formats (.wav, .aiff, etc.) and for already compressed audio 
file formats you don't need compression anyway (e.g. mp3).

> Any ideas on what the engine should support? (i.e. wish list)
> I'm starting with a simple WAV player that supports multiple loop
> points, and then I'll add some filters (copy-paste from the GIG engine I
> presume).

Don't aim too high. Having the gig engine features in our own engine is a good 
start. If that works we replace the synthesis parts one by one by more up to 
date features.

> It might be a good idea to generalise some of the 'helper' classes that
> are used by the GIG engine. The DiskThread for instance: I also need
> disk streaming if the sample is too big. Since the current diskstreamer
> is in the gig namespace, I have to copy it into my own namespace. Well,
> actually I don't really need to do that, but not doing so would
> introduce a depency to the gig engine.

Yeah, many parts of the gig engine should be extracted and generalized to base 
classes. We haven't done it yet, because for the first upcoming release, 
solely the gig engine is planned to be included.

> It might be better to have some helper classes (filters, ADSR,
> DiskThread, ...) separate from the engines. This way the engine mainly
> handles the file format and engine specifics. It would surely make it
> easier to implement new engines.

Actually the filters are already generalized (see 
src/engines/common/BiquadFilter.h). For the gig Engine we just compose some 
of these filters with custom parameters, so it (hopefully) sounds like the 
original Gigasampler filters.

Btw, all generalized engine classes (means all classes which are used to 
compose an engine but are not specific to one particular engine) should be 
placed into src/engines/common. E.g. the LFO class is already there as well.

> I was more thinking of engines as .lo libraries kind of dynamic loading.
> If I'm not mistaking, the approach you propose compiles all
> drivers/engines into the executable.

Not sure if you know it already; we planned dynamic engine recompilation, so 
the user can customize his own engines and compile it on the fly via LSCP 
(using a convenient GUI for example), so for that stage we need what you 
propose. But for the time being I think it's sufficient when we start to 
statically compile all engines into our library.

> >We already load audio output drivers and MIDI input drivers dynamically
> > (see src/network/lscpserver.cpp line 358 / 374 et seqq.). We use factory
> > classes for this (src/drivers/audio/AudioOutputDeviceFactory.cpp and
> >src/drivers/midi/MidiInputDeviceFactory.cpp) which resolve the given
> > strings and create an instance of the desired class. Unfortunately this
> > can't be solved as elegant in C++ as it can be in other languages like
> > Java (Java reflections API) so we're forced to use preprocessor macros in
> > the driver classes, so the driver classes actually register themselves
> > the factory. This is definitely one big feature that should be added in a
> > future standard of C++ IMO.
>
> I don't quite get what you're saying, but I'll look into the code and
> probably understand this better.

That code just does this:

	AudioOutputDevice* pDevice;
	...
	if (desired_driver == "Alsa") pDevice =
	    new AudioOutputDeviceAlsa(driver_parameters);
	else if (desired_driver == ...
	...

Just in a more elegant way and a bit more complex, because the driver 
parameters (e.g. to create a device) are dynamically as well.

> What I'm missing in the LSCP draft is a way to send generalized
> configuration to the sampler engine. What I mean with 'generalized' is a
> send/receive mechanism that allows a (G)UI to configure some engine
> specific parameters. This probably is not nescessary for the GIG engine,
> but I think it should be available. It could be solved by using MIDI
> sysex stuff, but I dislike that. In my opinion the MIDI communication
> should be strictly limited to the real-time events, whilst the LSCP
> communication serves all non-realtime UI to the sampler (and engine). In
> an analogy with a hardware sampler, I see LSCP as the "front-panel" to
> "sampler backend" communciation mechanism, which should be separate from
> the MIDI communication. From a practical point of view: the MIDI stuff
> is real-time, and the LSCP stuff is non-realtime. Those shouldn't be mixed.

Exactly, that's how it was planned; LSCP is not meant for realtime operation. 
What engine parameters exactly do you have in mind?

CU
Christian

Re: [Linuxsampler-devel] Dynamic Engine Loader

[Pieter P. <pi...@jo...>]

Christian Schoenebeck wrote:

>Es geschah am Sonntag, 8. August 2004 11:30 als Pieter Palmers schrieb:
>
>>Hi all,
>>
>
>Hi and sorry for the late response, I just came back from holidays while 
>Vladimir is still enjoying it it seems.
>
>
>>I've started writing an engine for linuxsampler for more
>>
>
>Great!
>
>
>>(like multiple loop points). The gig engine is also more instrument
>>oriented, while this engine should be more oriented towards the drumloop
>>type of sampling. And there is currently no gig format file editor for
>>linux that I know of, so...
>>
>
>Right, we discussed adding the possibility to edit or create .gig files, but 
>we ended that an own format would be a better idea.
>
>
Any ideas on this 'own' file format? I've been thinking about it and 
probably the nicest I've seen is the approach of Hydrogen: simply tar-gz 
the (wav) samples and include an XML file to describe the 'soundbank'.

Any ideas on what the engine should support? (i.e. wish list)
I'm starting with a simple WAV player that supports multiple loop 
points, and then I'll add some filters (copy-paste from the GIG engine I 
presume).

It might be a good idea to generalise some of the 'helper' classes that 
are used by the GIG engine. The DiskThread for instance: I also need 
disk streaming if the sample is too big. Since the current diskstreamer 
is in the gig namespace, I have to copy it into my own namespace. Well, 
actually I don't really need to do that, but not doing so would 
introduce a depency to the gig engine.

It might be better to have some helper classes (filters, ADSR, 
DiskThread, ...) separate from the engines. This way the engine mainly 
handles the file format and engine specifics. It would surely make it 
easier to implement new engines.

>>Anyway, I was wondering if there are plans for supporting the dynamic
>>loading of the engines (i.e. like with ladspa plugins). I inserted my
>>engine into the linuxsampler code tree, and I have the impression that
>>this feature is intended.
>>
>
>Yes, dynamic engine loading is planned of course. This should be done via the 
>"LOAD ENGINE" LSCP command:
>
>http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#rfc.section.5.4.2
>
>But at the moment, as we only have one engine yet, we only simply check if the 
>engine name is either "gig" or "GigEngine" when the "LOAD ENGINE" command was 
>issued (see src/network/lscpserver.cpp line 448 et seqq.).
>
>
>>I would like to implement a dynamic engine loader, but I was wondering
>>if there are already some thoughts on how this should be done.
>>
>
I was more thinking of engines as .lo libraries kind of dynamic loading. 
If I'm not mistaking, the approach you propose compiles all 
drivers/engines into the executable.

>We already load audio output drivers and MIDI input drivers dynamically (see 
>src/network/lscpserver.cpp line 358 / 374 et seqq.). We use factory classes 
>for this (src/drivers/audio/AudioOutputDeviceFactory.cpp and 
>src/drivers/midi/MidiInputDeviceFactory.cpp) which resolve the given strings 
>and create an instance of the desired class. Unfortunately this can't be 
>solved as elegant in C++ as it can be in other languages like Java (Java 
>reflections API) so we're forced to use preprocessor macros in the driver 
>classes, so the driver classes actually register themselves the factory. This 
>is definitely one big feature that should be added in a future standard of 
>C++ IMO.
>
I don't quite get what you're saying, but I'll look into the code and 
probably understand this better.

>Anyway... implementing dynamic loading of engines can be almost identically 
>done the same as it's already done for the audio and MIDI drivers. There's 
>only one issue: for loading the drivers we also introduced a some how complex 
>system of dynamic driver parameters. That way the GUI frontends don't have to 
>know which drivers are implemented, what parameters these drivers support or 
>need, what these parameters do, etc.
>For loading sampler engines I think we could simply drop that dynamic 
>parameters approach. Or do you think there will be engines in future which 
>could require special parameters for loading the engine?
>
>
I don't have a clue. Maybe when my idea of the new engine gets a little 
less blurry...

What I'm missing in the LSCP draft is a way to send generalized 
configuration to the sampler engine. What I mean with 'generalized' is a 
send/receive mechanism that allows a (G)UI to configure some engine 
specific parameters. This probably is not nescessary for the GIG engine, 
but I think it should be available. It could be solved by using MIDI 
sysex stuff, but I dislike that. In my opinion the MIDI communication 
should be strictly limited to the real-time events, whilst the LSCP 
communication serves all non-realtime UI to the sampler (and engine). In 
an analogy with a hardware sampler, I see LSCP as the "front-panel" to 
"sampler backend" communciation mechanism, which should be separate from 
the MIDI communication. From a practical point of view: the MIDI stuff 
is real-time, and the LSCP stuff is non-realtime. Those shouldn't be mixed.

Greets,

Pieter

-- 
*---------------------------------------------------------------------*
| Ir. Pieter Palmers                                                  |
| ESAT-MICAS Research Assistant                                       |
| Departement Elektrotechniek, ESAT-MICAS                             |
| Faculteit toegepaste wetenschappen, K.U. Leuven                     |
| Kasteelpark Arenberg 10                                             |
| B-3001 Leuven-Heverlee, Belgium                                     |
| Tel.   : (32) 16 32.10.70                                           |
| Fax    : (32) 16 32.19.75                                           |
| E-mail : Pie...@es...                         |
| Web    : http://www.esat.kuleuven.ac.be/micas/People/Pieter_Palmers |
*---------------------------------------------------------------------*

[Linuxsampler-devel] Hello Linux-Samper-er's....

[Mark K. <mar...@co...>]

While it's been excessively quiet here for the last 6-8 weeks I was
quite happy to see that Christian is busy filing away updates to our
favorite Linux-based sampler.

just saying hi!

- Mark