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

Re: [Linuxsampler-devel] midi mapping qsampler

[Christopher C. <st...@tr...>]

QSampler is not a completed implementation. It does not do mappings like 
it should. You will need to use Fantasia to do your mappings.

Markus W. Kropp wrote:
> hi there
>
> today i tried to map the sonatina symphony orchestra in the midi mapping function of qsampler. first i saved for the first three instruments. then i added
> some more instruments to the midi map. i tried to save, but it doesn´t react. i could only "save as", what was well for the first time. then i added some
> more instruments to the midimap and "save as" again - now i got errors: "Some settings could not be saved ..." and my midimaps-settings were empty and
> overwritten!
>
> i got some xruns in jack, too (not at first, but i don´t know exactly ...) and i don´t know as it makes this failure (i will try and report) ...
>
> is this a known bug in qsampler? or is there a limit of instruments, i can midimap?
>
> now i try to edit the lscp-file to midimap my instruments *hmpf*
>
> greetings!
>
>
> -----
> Musix-Blog - Über meine Kompositionen - http://www.musix-de.blogspot.com
> Musix-Wiki - Den Computer zum Komponieren einrichten - http://www.musix-wiki.org
>
> Klavierunterricht in Köln - http://www.koelnklassik.de/klavierunterricht.htm
>
> Markus W. Kropp
> Buchholzstr. 36
> 51061 Köln
> Tel.:0221-4719703
>
> kr...@ko...
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

[Linuxsampler-devel] midi mapping qsampler

[Markus W. K. <kr...@ko...>]

hi there

today i tried to map the sonatina symphony orchestra in the midi mapping function of qsampler. first i saved for the first three instruments. then i added
some more instruments to the midi map. i tried to save, but it doesn´t react. i could only "save as", what was well for the first time. then i added some
more instruments to the midimap and "save as" again - now i got errors: "Some settings could not be saved ..." and my midimaps-settings were empty and
overwritten!

i got some xruns in jack, too (not at first, but i don´t know exactly ...) and i don´t know as it makes this failure (i will try and report) ...

is this a known bug in qsampler? or is there a limit of instruments, i can midimap?

now i try to edit the lscp-file to midimap my instruments *hmpf*

greetings!


-----
Musix-Blog - Über meine Kompositionen - http://www.musix-de.blogspot.com
Musix-Wiki - Den Computer zum Komponieren einrichten - http://www.musix-wiki.org

Klavierunterricht in Köln - http://www.koelnklassik.de/klavierunterricht.htm

Markus W. Kropp
Buchholzstr. 36
51061 Köln
Tel.:0221-4719703

kr...@ko...

Re: [Linuxsampler-devel] example script generates errors

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

On Wednesday 14 March 2012 11:36:57 Markus W. Kropp wrote:
> I tried to use the example script from your homepage, thzat explains how to
> connect LinuxSampler automatically to Jack. Following options of your
> script generates errors in Qsampler, because Qsampler cannot find the
> output:
> 
> SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 0 JACK_BINDINGS='alsa_pcm:playback_1'
> SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 1 JACK_BINDINGS='alsa_pcm:playback_2'
> 
> I changed the "alsa_pcm:playback_1" to "system:playback_1" and similar *_2
> 
> Please patch this into your script for others, would be nice.

Yes, you are right, the main client name is now "system" on JACK2 / jackdmp. 
But how is it with JACK1? Isn't that still using the old name "alsa_pcm"?

CU
Christian

[Linuxsampler-devel] example script generates errors

[Markus W. K. <kr...@ko...>]

Hi there developers,

I tried to use the example script from your homepage, thzat explains how to connect LinuxSampler automatically to Jack. Following options of your script
generates errors in Qsampler, because Qsampler cannot find the output:

SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 0 JACK_BINDINGS='alsa_pcm:playback_1'
SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 1 JACK_BINDINGS='alsa_pcm:playback_2'

I changed the "alsa_pcm:playback_1" to "system:playback_1" and similar *_2

Please patch this into your script for others, would be nice.

I am working on Debian-Sid with Jack, ALSA, LinuxSampler, Frescobaldi, Renoise and some Softsynths and Effects.


Greetings!

Markus3000 aka Musix


-----
Musix-Blog - Über meine Kompositionen - http://www.musix-de.blogspot.com
Musix-Wiki - Den Computer zum Komponieren einrichten - http://www.musix-wiki.org

Klavierunterricht in Köln - http://www.koelnklassik.de/klavierunterricht.htm

Markus W. Kropp
Buchholzstr. 36
51061 Köln
Tel.:0221-4719703

kr...@ko...

Re: [Linuxsampler-devel] multiple LSs or lscps

[Christopher C. <st...@tr...>]

rosea.grammostola wrote:
> On 03/12/2012 11:21 PM, Christopher Cherrett wrote:
>> Nicola Pandini wrote:
>>> Il 12/03/2012 17:53, Christian Schoenebeck ha scritto:
>>>> Sure, but maybe a "MIDI instrument map" is a better way for you to achieve
>>>> such a flexible configuration. This feature allows you to define a MIDI program
>>>> change map with instruments, thus to turn the sampler in some standard General
>>>> MIDI sound generator. For each entry you define at least a MIDI bank select and
>>>> program change number and a sound file (.gig, .sfz, .sf2 ) to be loaded. For
>>>> each entry you can also define a volume factor (for fine tuning your
>>>> performance) and a load strategy. The latter defines whether the sound shall be
>>>> loaded:
>>>> a) immediately and always kept in memory ("PERSISTENT"), or
>>>> b) instead be loaded on demand and freed automatically when its not in use
>>>> anymore on any sampler part ("ON_DEMAND") or
>>>> c) be loaded on demand, but kept in memory afterwards even if not used anymore
>>>> by any sampler part ("ON_DEMAND_HOLD")
>>>>
>>>> http://www.linuxsampler.org/api/draft-linuxsampler-
>>>> protocol.html#MIDI%20Instrument%20Mapping
>>>>
>>> Hi, I'm interested in your thread, because I'm also trying to find a way
>>> to menage my live sets.
>>> I play drum pads live, and I often need to pick up a different drum kit
>>> in every song I play.
>>> I find the "MIDI instrument map" the best way to load instruments, but
>>> is it possible to create an entry that is formed by two or more
>>> instruments? For example, in the first song I need only a drumkit, but
>>> in the second I want a different drumkit AND a piano.
>>> Until now, I create a big lscp file with all the instruments (sfz) I
>>> need to play in my gig, and select them with the locc-hicc opcodes.
>>>
>>>         thanks
>>>
>> You can do this in Open Octave Studio beta 1 coming out soon. We load
>> the instruments on the fly. No need for an lscp at all. Our instruments
>> contain all the information linuxsampler needs to load the instrument.
>> You load up your instrument into fantasia and map it, Open Octave Studio
>> can then import the instrument with all it's mappings and then you never
>> need to load the lscp or fantasia again.
>>
>> When you want the instrument you simply add a track and select the
>> instrument you want that track to be:
>> http://www.openoctave.org/docs/getting_started/Create-Track-2012.1-Beta1.pdf
>>
>> You can now change the instrument on the fly and it will reload
>> linuxsampler on the fly. No more need to have huge lscp templates. Only
>> use what you need.
> Ok, but for getting those instruments, you need lscp templates right?
> One lscp per instrument or one big template with all the instruments?
> On how do you create those instruments?
>
> \r
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Open Fantasia or load an existing lscp. Open oomidi. Go to the 
Instrument Editor and Import Instruments. oomidi will allow you to pull 
your instrument mappings from linuxsampler and create an idf instrument 
for oomidi to use with all your mappings contained in the idf. From 
there you just add a track, select your new instrument and linuxsampler 
is loaded with the lscp, ports, routing on the fly.

One day the Fantasia step will be gone as well. So it can all be done in 
oomidi. Some day :)

Thanks!

Re: [Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

On 03/13/2012 04:54 PM, rosea.grammostola wrote:
> On 03/13/2012 11:00 AM, Christian Schoenebeck wrote:
>> On Tuesday 13 March 2012 10:30:24 rosea.grammostola wrote:
>>> If I try to load multiple instances, one replaces the other
>>>
>>> cat Template1.lscp | nc localhost 8888
>>>
>>> cat template2.lscp | nc localhost 8888
>>>
>>> Template 2 replaces template 1. They are not both loaded.
>>
>> The sampler has no idea that you want to replace the whole session
>> with the
>> 2nd file.
>>
>> To achieve what you are doing, you have to place a "RESET" command at the
>> beginning of your LSCP files.
>>
>> http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#RESET
>
> Hmm to be clear, I want to have BOTH files loaded, not one replaced by
> the other. And in my template files RESET seems to be set. So that's why
> it is replacing the other template.
>
> On the other hand when I remove RESET, both are loaded but only audio
> outs are shown in patchage, without the names
>
> http://imageshack.us/photo/my-images/819/selection020a.png/

This is how it looks with only that lscp loaded


http://img100.imageshack.us/i/selection021.png/

Re: [Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

On 03/13/2012 11:00 AM, Christian Schoenebeck wrote:
> On Tuesday 13 March 2012 10:30:24 rosea.grammostola wrote:
>> If I try to load multiple instances, one replaces the other
>>
>> cat Template1.lscp | nc localhost 8888
>>
>> cat template2.lscp | nc localhost 8888
>>
>> Template 2 replaces template 1. They are not both loaded.
>
> The sampler has no idea that you want to replace the whole session with the
> 2nd file.
>
> To achieve what you are doing, you have to place a "RESET" command at the
> beginning of your LSCP files.
>
> http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#RESET

Hmm to be clear, I want to have BOTH files loaded, not one replaced by 
the other. And in my template files RESET seems to be set. So that's why 
it is replacing the other template.

On the other hand when I remove RESET, both are loaded but only audio 
outs are shown in patchage, without the names

http://imageshack.us/photo/my-images/819/selection020a.png/

Re: [Linuxsampler-devel] multiple LSs or lscps

[Markus W. K. <kr...@ko...>]

Hm. I think it´s more helpful to start one linuxsampler on port 8888 and another on port 8889. then you can do this:

cat Template1.lscp | nc localhost 8888

cat template2.lscp | nc localhost 8889 <--- REMEMBER!

this should work. you can now connect each linuxsampler in jack or whatever you want to do woth this two samplers. and: with this setup you don´t need to
reset something.

greetings!


Am Tue, 13 Mar 2012 11:00:18 +0100
schrieb Christian Schoenebeck <sch...@li...>:

> On Tuesday 13 March 2012 10:30:24 rosea.grammostola wrote:
> > If I try to load multiple instances, one replaces the other
> > 
> > cat Template1.lscp | nc localhost 8888
> > 
> > cat template2.lscp | nc localhost 8888
> > 
> > Template 2 replaces template 1. They are not both loaded.
> 
> The sampler has no idea that you want to replace the whole session with the 
> 2nd file.
> 
> To achieve what you are doing, you have to place a "RESET" command at the 
> beginning of your LSCP files.
> 
> http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#RESET
> 
> CU
> Christian
> 
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel



-----
Musix-Blog - Über meine Kompositionen - http://www.musix-de.blogspot.com
Musix-Wiki - Den Computer zum Komponieren einrichten - http://www.musix-wiki.org

Klavierunterricht in Köln - http://www.koelnklassik.de/klavierunterricht.htm

Markus W. Kropp
Buchholzstr. 36
51061 Köln
Tel.:0221-4719703

kr...@ko...

Re: [Linuxsampler-devel] multiple LSs or lscps

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

On Tuesday 13 March 2012 10:30:24 rosea.grammostola wrote:
> If I try to load multiple instances, one replaces the other
> 
> cat Template1.lscp | nc localhost 8888
> 
> cat template2.lscp | nc localhost 8888
> 
> Template 2 replaces template 1. They are not both loaded.

The sampler has no idea that you want to replace the whole session with the 
2nd file.

To achieve what you are doing, you have to place a "RESET" command at the 
beginning of your LSCP files.

http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#RESET

CU
Christian

Re: [Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

On 03/12/2012 03:42 PM, Christian Schoenebeck wrote:
> On Sunday 11 March 2012 20:34:43 rosea.grammostola wrote:
>> Is it possible to run multiple instance of Linuxsampler or load multiple
>> lscp files (via commandline) into LinuxSampler?
>
> Both is possible. You can run multiple instances of linuxsampler, but you
> should then override the TCP port on which the other instances shall listen to
> by launching the sampler like:
>
> 	linuxsampler --lscp-port 8889
> 	linuxsampler --lscp-port 8890
> 	...
>
> However usually it doesn't make much sense to run several instances of the
> server. Especially it will waste more resources, e.g. global audio buffers
> which cannot be shared among several sampler instances.
>
> And of course you can also feed several LSCP files into the sampler, even at
> the same time. You don't need to spawn new sampler instances for that.

If I try to load multiple instances, one replaces the other

cat Template1.lscp | nc localhost 8888

cat template2.lscp | nc localhost 8888

Template 2 replaces template 1. They are not both loaded.

\r

Re: [Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

On 03/12/2012 11:21 PM, Christopher Cherrett wrote:
> Nicola Pandini wrote:
>> Il 12/03/2012 17:53, Christian Schoenebeck ha scritto:
>>> Sure, but maybe a "MIDI instrument map" is a better way for you to achieve
>>> such a flexible configuration. This feature allows you to define a MIDI program
>>> change map with instruments, thus to turn the sampler in some standard General
>>> MIDI sound generator. For each entry you define at least a MIDI bank select and
>>> program change number and a sound file (.gig, .sfz, .sf2 ) to be loaded. For
>>> each entry you can also define a volume factor (for fine tuning your
>>> performance) and a load strategy. The latter defines whether the sound shall be
>>> loaded:
>>> a) immediately and always kept in memory ("PERSISTENT"), or
>>> b) instead be loaded on demand and freed automatically when its not in use
>>> anymore on any sampler part ("ON_DEMAND") or
>>> c) be loaded on demand, but kept in memory afterwards even if not used anymore
>>> by any sampler part ("ON_DEMAND_HOLD")
>>>
>>> http://www.linuxsampler.org/api/draft-linuxsampler-
>>> protocol.html#MIDI%20Instrument%20Mapping
>>>
>> Hi, I'm interested in your thread, because I'm also trying to find a way
>> to menage my live sets.
>> I play drum pads live, and I often need to pick up a different drum kit
>> in every song I play.
>> I find the "MIDI instrument map" the best way to load instruments, but
>> is it possible to create an entry that is formed by two or more
>> instruments? For example, in the first song I need only a drumkit, but
>> in the second I want a different drumkit AND a piano.
>> Until now, I create a big lscp file with all the instruments (sfz) I
>> need to play in my gig, and select them with the locc-hicc opcodes.
>>
>>        thanks
>>
> You can do this in Open Octave Studio beta 1 coming out soon. We load
> the instruments on the fly. No need for an lscp at all. Our instruments
> contain all the information linuxsampler needs to load the instrument.
> You load up your instrument into fantasia and map it, Open Octave Studio
> can then import the instrument with all it's mappings and then you never
> need to load the lscp or fantasia again.
>
> When you want the instrument you simply add a track and select the
> instrument you want that track to be:
> http://www.openoctave.org/docs/getting_started/Create-Track-2012.1-Beta1.pdf
>
> You can now change the instrument on the fly and it will reload
> linuxsampler on the fly. No more need to have huge lscp templates. Only
> use what you need.

Ok, but for getting those instruments, you need lscp templates right?
One lscp per instrument or one big template with all the instruments?
On how do you create those instruments?

\r

Re: [Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

On 03/12/2012 05:53 PM, Christian Schoenebeck wrote:
> On Monday 12 March 2012 18:14:10 rosea.grammostola wrote:
>> Thanks for your reply. There certainly are no stupid questions... I
>> thought, just ask, but it's actually possible!?!
>
> Yes, it is definitely possible to spawn multiple instances of the sampler. But
> right now I cannot imagine a scenario in practice where this would make sense.
>
> For example if you want to leverage a SMP/multi core system, or a system with
> multiple independent hard discs, you could simply create (in the same sampler
> instance) multiple JACK audio output devices (assuming JACK2 or JACKMP), like:
>
> CREATE AUDIO_OUTPUT_DEVICE JACK
> CREATE AUDIO_OUTPUT_DEVICE JACK
> ...
>
> (or do that with some clicks in Fantasia or QSampler). For each audio output
> device in the sampler, a separate audio rendering thread and disk streaming
> thread is spawned. And by connecting a part to one of those audio output
> devices you can control which audio rendering thread&  disk streaming thread
> the part shall be part of.
>
>> A typical situation is that you have made a template for let say
>> bigband. One or two types of instruments are not in a typically bigband,
>> but then you have a midi file / composition with that instruments, or
>> just want to try how it sounds. Then it's nice if you have the
>> possibility to try it without rewriting the template first.
>
> Sure, but maybe a "MIDI instrument map" is a better way for you to achieve
> such a flexible configuration. This feature allows you to define a MIDI program
> change map with instruments, thus to turn the sampler in some standard General
> MIDI sound generator. For each entry you define at least a MIDI bank select and
> program change number and a sound file (.gig, .sfz, .sf2 ) to be loaded. For
> each entry you can also define a volume factor (for fine tuning your
> performance) and a load strategy. The latter defines whether the sound shall be
> loaded:
> a) immediately and always kept in memory ("PERSISTENT"), or
> b) instead be loaded on demand and freed automatically when its not in use
> anymore on any sampler part ("ON_DEMAND") or
> c) be loaded on demand, but kept in memory afterwards even if not used anymore
> by any sampler part ("ON_DEMAND_HOLD")
>
> http://www.linuxsampler.org/api/draft-linuxsampler-
> protocol.html#MIDI%20Instrument%20Mapping
>
> On most master keyboards you can define "performances" which will send the
> appropriate MIDI program change messages to the sampler. So you would just
> need to select the respective performance on your master keyboard and you are
> ready to play.
>
> You can also manage MIDI instrument maps with the two GUI frontend
> applications.

Ok, so if you have one big template with all your samples, it doesn't 
hurt the performance of you system. Having them in the template, doesn't 
mean they are loaded in memory (ON_DEMAND_HOLD). So a bigger template 
doesn't necessarily eat more system resources.

\r

Re: [Linuxsampler-devel] multiple LSs or lscps

[Christopher C. <st...@tr...>]

Christian Schoenebeck wrote:
> On Monday 12 March 2012 22:45:43 Nicola Pandini wrote:
>> I play drum pads live, and I often need to pick up a different drum kit
>> in every song I play.
>> I find the "MIDI instrument map" the best way to load instruments, but
>> is it possible to create an entry that is formed by two or more
>> instruments? For example, in the first song I need only a drumkit, but
>> in the second I want a different drumkit AND a piano.
> That would require the sampler to support loading more than one instrument per
> part, which is currently not meant to be in the scope of the sampler.
>
> However usually it works like this: master keyboards (usually) allow to
> configure "performances" with split zones. For each zone the master keyboard
> allows you to assign a MIDI program change number and MIDI channel. And since
> split zones may overlap on the keyboard, you can also create layered sounds
> this way. So this would exactly do the thing you described.
>
> To make it clear: when you select/recall a "performance" on your master
> keyboard, the keyboard will send for each defined split zone the zone's bank
> select&  program change number on the zone's MIDI channel. This way you can
> switch/load multiple sampler sounds on multiple sampler parts automatically by
> just pressing one button on your master keyboard.
>
> CU
> Christian
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
We do this with epic mode. One click it creates all needed tracks with 
the instruments you need and you can transpose them into any range you 
need for that moment you are playing. So you can map any number of 
instruments to any part of the keyboard on the fly and play them all as 
if they were one instrument.

No big deal :)

Re: [Linuxsampler-devel] multiple LSs or lscps

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

On Monday 12 March 2012 22:45:43 Nicola Pandini wrote:
> I play drum pads live, and I often need to pick up a different drum kit
> in every song I play.
> I find the "MIDI instrument map" the best way to load instruments, but
> is it possible to create an entry that is formed by two or more
> instruments? For example, in the first song I need only a drumkit, but
> in the second I want a different drumkit AND a piano.

That would require the sampler to support loading more than one instrument per 
part, which is currently not meant to be in the scope of the sampler.

However usually it works like this: master keyboards (usually) allow to 
configure "performances" with split zones. For each zone the master keyboard 
allows you to assign a MIDI program change number and MIDI channel. And since 
split zones may overlap on the keyboard, you can also create layered sounds 
this way. So this would exactly do the thing you described.

To make it clear: when you select/recall a "performance" on your master 
keyboard, the keyboard will send for each defined split zone the zone's bank 
select & program change number on the zone's MIDI channel. This way you can 
switch/load multiple sampler sounds on multiple sampler parts automatically by 
just pressing one button on your master keyboard.

CU
Christian

Re: [Linuxsampler-devel] multiple LSs or lscps

[Christopher C. <st...@tr...>]

Nicola Pandini wrote:
> Il 12/03/2012 17:53, Christian Schoenebeck ha scritto:
>> Sure, but maybe a "MIDI instrument map" is a better way for you to achieve
>> such a flexible configuration. This feature allows you to define a MIDI program
>> change map with instruments, thus to turn the sampler in some standard General
>> MIDI sound generator. For each entry you define at least a MIDI bank select and
>> program change number and a sound file (.gig, .sfz, .sf2 ) to be loaded. For
>> each entry you can also define a volume factor (for fine tuning your
>> performance) and a load strategy. The latter defines whether the sound shall be
>> loaded:
>> a) immediately and always kept in memory ("PERSISTENT"), or
>> b) instead be loaded on demand and freed automatically when its not in use
>> anymore on any sampler part ("ON_DEMAND") or
>> c) be loaded on demand, but kept in memory afterwards even if not used anymore
>> by any sampler part ("ON_DEMAND_HOLD")
>>
>> http://www.linuxsampler.org/api/draft-linuxsampler-
>> protocol.html#MIDI%20Instrument%20Mapping
>>
> Hi, I'm interested in your thread, because I'm also trying to find a way
> to menage my live sets.
> I play drum pads live, and I often need to pick up a different drum kit
> in every song I play.
> I find the "MIDI instrument map" the best way to load instruments, but
> is it possible to create an entry that is formed by two or more
> instruments? For example, in the first song I need only a drumkit, but
> in the second I want a different drumkit AND a piano.
> Until now, I create a big lscp file with all the instruments (sfz) I
> need to play in my gig, and select them with the locc-hicc opcodes.
>
>       thanks
>
You can do this in Open Octave Studio beta 1 coming out soon. We load 
the instruments on the fly. No need for an lscp at all. Our instruments 
contain all the information linuxsampler needs to load the instrument. 
You load up your instrument into fantasia and map it, Open Octave Studio 
can then import the instrument with all it's mappings and then you never 
need to load the lscp or fantasia again.

When you want the instrument you simply add a track and select the 
instrument you want that track to be:
http://www.openoctave.org/docs/getting_started/Create-Track-2012.1-Beta1.pdf

You can now change the instrument on the fly and it will reload 
linuxsampler on the fly. No more need to have huge lscp templates. Only 
use what you need.

Come by irc.freenode.net #openoctave if you need any support

Thanks!

Re: [Linuxsampler-devel] multiple LSs or lscps

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

On Monday 12 March 2012 18:14:10 rosea.grammostola wrote:
> Thanks for your reply. There certainly are no stupid questions... I
> thought, just ask, but it's actually possible!?!

Yes, it is definitely possible to spawn multiple instances of the sampler. But 
right now I cannot imagine a scenario in practice where this would make sense.

For example if you want to leverage a SMP/multi core system, or a system with 
multiple independent hard discs, you could simply create (in the same sampler 
instance) multiple JACK audio output devices (assuming JACK2 or JACKMP), like:

CREATE AUDIO_OUTPUT_DEVICE JACK
CREATE AUDIO_OUTPUT_DEVICE JACK
...

(or do that with some clicks in Fantasia or QSampler). For each audio output 
device in the sampler, a separate audio rendering thread and disk streaming 
thread is spawned. And by connecting a part to one of those audio output 
devices you can control which audio rendering thread & disk streaming thread 
the part shall be part of.

> A typical situation is that you have made a template for let say
> bigband. One or two types of instruments are not in a typically bigband,
> but then you have a midi file / composition with that instruments, or
> just want to try how it sounds. Then it's nice if you have the
> possibility to try it without rewriting the template first.

Sure, but maybe a "MIDI instrument map" is a better way for you to achieve 
such a flexible configuration. This feature allows you to define a MIDI program 
change map with instruments, thus to turn the sampler in some standard General 
MIDI sound generator. For each entry you define at least a MIDI bank select and 
program change number and a sound file (.gig, .sfz, .sf2 ) to be loaded. For 
each entry you can also define a volume factor (for fine tuning your 
performance) and a load strategy. The latter defines whether the sound shall be 
loaded:
a) immediately and always kept in memory ("PERSISTENT"), or
b) instead be loaded on demand and freed automatically when its not in use 
anymore on any sampler part ("ON_DEMAND") or
c) be loaded on demand, but kept in memory afterwards even if not used anymore 
by any sampler part ("ON_DEMAND_HOLD")

http://www.linuxsampler.org/api/draft-linuxsampler-
protocol.html#MIDI%20Instrument%20Mapping

On most master keyboards you can define "performances" which will send the 
appropriate MIDI program change messages to the sampler. So you would just 
need to select the respective performance on your master keyboard and you are 
ready to play.

You can also manage MIDI instrument maps with the two GUI frontend 
applications.

CU
Christian

Re: [Linuxsampler-devel] Ardour3 + linuxsampler plugin

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

On Monday 12 March 2012 18:04:54 David Robillard wrote:
> Perfect, thanks a lot.  I will try to get the LV2 stuff working.

No problem.

> It seems implicit that the .gxnn files are in the same directory as the
> main .gig, so simply telling the host about them should work fine.  If
> those paths are referred to in state anywhere, the modified versions
> would have to be used... (already done for the .gig)

Yes, the extension files are always in the same directory as the main .gig file, 
all share the same file base name (file name without file type extension) and the 
numbers (".gx01", ".gx02", ...) are consecutive.

CU
Christian

Re: [Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

On 03/12/2012 03:42 PM, Christian Schoenebeck wrote:
> On Sunday 11 March 2012 20:34:43 rosea.grammostola wrote:
>> Is it possible to run multiple instance of Linuxsampler or load multiple
>> lscp files (via commandline) into LinuxSampler?
>
> Both is possible. You can run multiple instances of linuxsampler, but you
> should then override the TCP port on which the other instances shall listen to
> by launching the sampler like:
>
> 	linuxsampler --lscp-port 8889
> 	linuxsampler --lscp-port 8890
> 	...
>
> However usually it doesn't make much sense to run several instances of the
> server. Especially it will waste more resources, e.g. global audio buffers
> which cannot be shared among several sampler instances.
>
> And of course you can also feed several LSCP files into the sampler, even at
> the same time. You don't need to spawn new sampler instances for that.
>
>> This would give you more possibilities and especially more flexibility.
>
> What are you trying to achieve?

Thanks for your reply. There certainly are no stupid questions... I 
thought, just ask, but it's actually possible!?!

A typical situation is that you have made a template for let say 
bigband. One or two types of instruments are not in a typically bigband, 
but then you have a midi file / composition with that instruments, or 
just want to try how it sounds. Then it's nice if you have the 
possibility to try it without rewriting the template first.

I'm really impressed by this excellent application and especially like 
the new SFZ developments.

Thanks.

\r

Re: [Linuxsampler-devel] Ardour3 + linuxsampler plugin

[David R. <d...@dr...>]

On Mon, 2012-03-12 at 15:31 +0100, Christian Schoenebeck wrote:
> On Sunday 11 March 2012 20:26:35 David Robillard wrote:
> > Because the host needs to know where all the files are to make session
> > archival possible.
> 
> Yes, makes sense.
> 
> > > Anyway, if you really need to enumerate all files, tell me, then I will
> > > patch libgig for this task.
> > 
> > That would be great, thanks.
> 
> Please update libgig and linuxsampler from svn. The EngineChannel class now 
> has a method:
> 
> 	String EngineChannel::InstrumentFileName(int index)
> 
> additionally to the already existing, equal named method without argument. So 
> calling this new method with argument zero is equivalent as calling the method 
> without argument, that is it will return the file name of the "main" instrument 
> file (e.g. "foo.gig"), where as calling the method with argument 1, 2, 3, ... 
> will return the name of the respective extension file (e.g. "foo.gx01", 
> "foo.gx02", "foo.gx03", ...). It will return an empty string if index is out 
> of bounds (e.g. end of extension file list exceeded).

Perfect, thanks a lot.  I will try to get the LV2 stuff working.

It seems implicit that the .gxnn files are in the same directory as the
main .gig, so simply telling the host about them should work fine.  If
those paths are referred to in state anywhere, the modified versions
would have to be used... (already done for the .gig)

Thanks,

-dr

Re: [Linuxsampler-devel] multiple LSs or lscps

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

On Sunday 11 March 2012 20:34:43 rosea.grammostola wrote:
> Is it possible to run multiple instance of Linuxsampler or load multiple
> lscp files (via commandline) into LinuxSampler?

Both is possible. You can run multiple instances of linuxsampler, but you 
should then override the TCP port on which the other instances shall listen to 
by launching the sampler like:

	linuxsampler --lscp-port 8889
	linuxsampler --lscp-port 8890
	...

However usually it doesn't make much sense to run several instances of the 
server. Especially it will waste more resources, e.g. global audio buffers 
which cannot be shared among several sampler instances.

And of course you can also feed several LSCP files into the sampler, even at 
the same time. You don't need to spawn new sampler instances for that.

> This would give you more possibilities and especially more flexibility.

What are you trying to achieve?

CU
Christian

Re: [Linuxsampler-devel] Ardour3 + linuxsampler plugin

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

On Sunday 11 March 2012 20:26:35 David Robillard wrote:
> Because the host needs to know where all the files are to make session
> archival possible.

Yes, makes sense.

> > Anyway, if you really need to enumerate all files, tell me, then I will
> > patch libgig for this task.
> 
> That would be great, thanks.

Please update libgig and linuxsampler from svn. The EngineChannel class now 
has a method:

	String EngineChannel::InstrumentFileName(int index)

additionally to the already existing, equal named method without argument. So 
calling this new method with argument zero is equivalent as calling the method 
without argument, that is it will return the file name of the "main" instrument 
file (e.g. "foo.gig"), where as calling the method with argument 1, 2, 3, ... 
will return the name of the respective extension file (e.g. "foo.gx01", 
"foo.gx02", "foo.gx03", ...). It will return an empty string if index is out 
of bounds (e.g. end of extension file list exceeded).

Let me know if you need something else.

CU
Christian

[Linuxsampler-devel] multiple LSs or lscps

[rosea.grammostola <ros...@gm...>]

Hi,

Is it possible to run multiple instance of Linuxsampler or load multiple 
lscp files (via commandline) into LinuxSampler?

This would give you more possibilities and especially more flexibility.

\r

Re: [Linuxsampler-devel] Ardour3 + linuxsampler plugin

[David R. <d...@dr...>]

On Sun, 2012-03-11 at 14:58 +0100, Christian Schoenebeck wrote:
> On Saturday 10 March 2012 19:52:21 David Robillard wrote:
> > > > > Those are so called "extension files" of the Giga format. Those were
> > > > > introduced by Tascam to circumvent the 2GB file size limit of the
> > > > > RIFF format, on which the Giga format is based on.
> > > > > 
> > > > > See method:
> > > > > 
> > > > > void File::LoadSamples(progress_t* pProgress);
> > > > > 
> > > > > in src/gig.cpp of the libgig sources.
> > > > 
> > > > Thanks.  I'll wade around and figure out how to get at this information
> > > > from LS.
> > > 
> > > You mean how to retrieve in the LV2 plugin code whether a .gig file
> > > "wants" extensions files and the list of those extension files? Or what
> > > else do you need exactly?
> > 
> > Yes, essentially I need to enumerate *all* files that are used.
> 
> Really? What is the purpose to enumerate all used files in the LV2 session? 
> Because from sampler perspective, only the "main" instrument file name has to 
> be passed when loading a session. The sampler (or in this case libgig) will 
> then automatically detect and retrieve the list of extension files from the 
> main gig file and load the extension files automatically.

Because the host needs to know where all the files are to make session
archival possible.

The Lilv (and thus Ardour) implementation, for example, makes symlinks
to all those files in the session directory, and the plugin state refers
to those instead.  That way all external file references are transparent
and you can make a deep archive with tar -h.  This is so, e.g., I can
roll up a session I've been working on, send it to you, and it will
actually work; or when you're finished a piece you can archive it and be
sure all the component bits are archived along with it.

> Anyway, if you really need to enumerate all files, tell me, then I will patch 
> libgig for this task.

That would be great, thanks.

-dr

Re: [Linuxsampler-devel] Ardour3 + linuxsampler plugin

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

On Saturday 10 March 2012 19:52:21 David Robillard wrote:
> > > > Those are so called "extension files" of the Giga format. Those were
> > > > introduced by Tascam to circumvent the 2GB file size limit of the
> > > > RIFF format, on which the Giga format is based on.
> > > > 
> > > > See method:
> > > > 
> > > > void File::LoadSamples(progress_t* pProgress);
> > > > 
> > > > in src/gig.cpp of the libgig sources.
> > > 
> > > Thanks.  I'll wade around and figure out how to get at this information
> > > from LS.
> > 
> > You mean how to retrieve in the LV2 plugin code whether a .gig file
> > "wants" extensions files and the list of those extension files? Or what
> > else do you need exactly?
> 
> Yes, essentially I need to enumerate *all* files that are used.

Really? What is the purpose to enumerate all used files in the LV2 session? 
Because from sampler perspective, only the "main" instrument file name has to 
be passed when loading a session. The sampler (or in this case libgig) will 
then automatically detect and retrieve the list of extension files from the 
main gig file and load the extension files automatically.

Anyway, if you really need to enumerate all files, tell me, then I will patch 
libgig for this task.

> 
> > > (That 32-bit limit really sucks...)
> > 
> > Not thaaat bad. ;-) The workaround with extension files is a bit ugly,
> > but it works on all systems. And I'm sure it will be easily resolved for
> > LV2 as well.
> 
> Well, it's pretty annoying/ugly here (these *%*^&% non-self-contained
> sample banks will be the death of me), but I mean in general.  I've
> looked in to using RIFF for things before realizing the 32-bit limit
> ruins that idea... oh well.

Depends for what you want to use it. If its a custom application you can also 
just use 64 bit RIFF chunk offsets instead of 32 bit ones of the original RIFF 
format and that's it.

Some people also did it like this: they placed all RIFF chunks into the first 2 
GB of the file, and e.g. placed their huge audio sample data after all those 
RIFF chunks and used 64 bit file offsets to reference the sample data from RIFF 
chunks. However Tascam decided not to do that for the Gig format, in favor of 
the extension files solution, because there are many systems which still have a 
2 GB file size limit in general.

CU
Christian

Re: [Linuxsampler-devel] Giga vs SFZ: CONFIG_EG_MIN_RELEASE_TIME too big for current audio fragment size & sampling rate!

[rosea.grammostola <ros...@gm...>]

On 03/10/2012 09:23 PM, rosea.grammostola wrote:
> On 03/10/2012 09:20 PM, Andreas Persson wrote:
>> On 2012-03-10 21:12, rosea.grammostola wrote:
>>> On 03/10/2012 08:59 PM, Andreas Persson wrote:
>>>> gdb linuxsampler
>>>
>>> $ gdb linuxsampler core
>>> GNU gdb (GDB) 7.4-debian
>>> Copyright (C) 2012 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later
>>> <http://gnu.org/licenses/gpl.html>
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law. Type "show
>>> copying"
>>> and "show warranty" for details.
>>> This GDB was configured as "x86_64-linux-gnu".
>>> For bug reporting instructions, please see:
>>> <http://www.gnu.org/software/gdb/bugs/>...
>>> Reading symbols from /usr/bin/linuxsampler...done.
>>> [New LWP 9175]
>>> [New LWP 9512]
>>> [New LWP 9509]
>>> [New LWP 9174]
>>>
>>> warning: Can't read pathname for load map: Input/output error.
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library
>>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>> Core was generated by `linuxsampler'.
>>> Program terminated with signal 11, Segmentation fault.
>>> #0 0x00007f8afb13b088 in LinuxSampler::EG::CalculateFadeOutCoeff(float,
>>> float) ()
>>> from /usr/lib/linuxsampler/liblinuxsampler.so.3
>>>
>>
>> Did you forget the "bt" command? That's what gives you the stack trace.
>>
>> Anyway, it looks like you're not running the latest code (I committed
>> the fix today, three hours ago).
>
> I updated after your mail, svn up, dpkg-buildpackage

Sorry, dpkg-buildpackage needs more parameters I think. Anyway, I 
rebuild again properly and it seems to work!!!

Gracias!