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
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
