EXS 24 Logic Sampler Users Group

I like this (amongst lots of other things!) :-

Gigasampler File Format Import
The EXS24 can now import files stored in the Gigasampler format (.gig). This
function is found in the 'Options' menu of the EXS24. Tip: In order to
playback long audio files, the EXS24 Virtual Sample Memory extension should
be installed.

Ben Hall
www.benhall.co.uk

--- Ben Hall <ben@...> wrote: 
> I like this (amongst lots of other things!) :-
Personally I like the multiple VSTi audio outputs. What I'd like more
is for them to release the Gold update fixing the Gold bugs too....

~Pev

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

> I like this (amongst lots of other things!) :-
> Gigasampler File Format Import
> The EXS24 can now import files stored in the Gigasampler format (.gig).
This
> function is found in the 'Options' menu of the EXS24. Tip: In order to
> playback long audio files, the EXS24 Virtual Sample Memory extension
should
> be installed.


Has anyone tested yet to see if EXS imports *all* dimensions from Giga
files? And does it actually have multiple articulations now, as was shown
off before? 

Curious,
Jeremy
http://www.ixks.com/~sadus

At 09:56 AM 6/08/02 -0500, you wrote: 
>
> > I like this (amongst lots of other things!) :-
> > Gigasampler File Format Import
> > The EXS24 can now import files stored in the Gigasampler format (.gig).
> This
> > function is found in the 'Options' menu of the EXS24. Tip: In order to
> > playback long audio files, the EXS24 Virtual Sample Memory extension
> should
> > be installed.
>
>
> Has anyone tested yet to see if EXS imports *all* dimensions from Giga
> files? And does it actually have multiple articulations now, as was shown
> off before? 


Don't know about that yet. I am testing a few right now. It certainly loads the
Giga Piano and the sustain pedal brings in the resonance model. In Cool Vibes
the mod wheel switches between damped and undamped and that is working too. So
far so good. :-)

For the first time I am playing it through my favourite compressors and
reverbs. Fantastic!

The EXS24 multi-out capability will be good but if we need to set up five
auxillaries for a drum kit and can't save that entire setup the advantage over
the current workarounds for EXS 24 is diminished -- at present I load multiple
copies of a drum kit or cut it into sections for easy recall. Assigning to a
set of different auxillaries is only a little quicker -- it would be great if
you could do this once and save the entire setup with named auxillaries (eg
Snare, Kick, Hats etc)

Regards,
murray

> Sure -- you can save the EXS24 instrument with a bunch of 
> outputs assigned to the groups eg Snare Group to outputs 3-4. 
> But then you need to create an Auxillary or three and in their 
> input sections you need to select the output 3-4 of Instrument 
> 3 or whatever. I suppose a couple of well setup autoloads 
> where your drums are already assigned to the right set of 
> named auxillaries would pretty well do the trick . 

Ahhh.. Yeah, that definitely sounds like the way to go.

Btw did they fix velocity crossfading?

If this is still 'broken' if you have a patch with multiple velocity layers,
does EXS24 just pick whichever one is closest to the velocity you play at,
or does it only play the lowest or highest velocity layer, or what?

Happy 5.2'ing!
Jeremy
http://www.ixks.com/~sadus

Jeremy wrote: 
>
> > Sure -- you can save the EXS24 instrument with a bunch of 
> > outputs assigned to the groups eg Snare Group to outputs 3-4. 
> > But then you need to create an Auxillary or three and in their 
> > input sections you need to select the output 3-4 of Instrument 
> > 3 or whatever. I suppose a couple of well setup autoloads 
> > where your drums are already assigned to the right set of 
> > named auxillaries would pretty well do the trick . 
>
> Ahhh.. Yeah, that definitely sounds like the way to go.
>
> Btw did they fix velocity crossfading?
>
> If this is still 'broken' if you have a patch with multiple velocity layers,
> does EXS24 just pick whichever one is closest to the velocity you play at,
> or does it only play the lowest or highest velocity layer, or what?


When I saw the Logic 5 demo in about March -- the beta 5.2 was being used. The
set of extra parameters which open up when you click the 0011  button was huge
-- thirty or forty from memory and it included velocity crossfades. That set of
parameters is the same size as in 5.0 now -- no Vel Crossfades. :-(
In view of this I doubt this is implemented with Giga format either.

Can anyone say what happened there -- probably wasn't working properly I guess.
Is it likely to come in future versions of 5.2.x -- I am on PC here. 

Regards,
Murray

Having sorted out multi outs in the EXS - does anyone know how you use the
multitimbrality of any multitimbral virtual instruments?

In other words, how do you use one instrument on ch1 and set it to output 3,
use a different instrument on ch2 and set it to ch4 etc, without multiple
virtual instruments being needed?

I thought this was one of the main ideas of the multi outputs?

Regards

David Tobin

Wow and Flutter ltd

David Tobin wrote: 
>
> Having sorted out multi outs in the EXS - does anyone know how you use the
> multitimbrality of any multitimbral virtual instruments?
>
> In other words, how do you use one instrument on ch1 and set it to output 3,
> use a different instrument on ch2 and set it to ch4 etc, without multiple
> virtual instruments being needed?
>
> I thought this was one of the main ideas of the multi outputs?


I don't think this is what they had in mind -- I could be wrong but I think it
is just about giving you a chance to apply different processing to different
sounds or to route sounds to different surround positions. 

Regards,
M

This is implemented slightly differently depending on each virtual
instrument.

With Model-E, for example, you simply select the MIDI channel you want and
then assign the sound and its output. Simple.
Now, to play the different channels you will have to send from a different
MIDI channel on your keyboard or set up some sort of transformer in your
environment to change the incoming MIDI channel to the desired one.
Make sure that your logic Audio Instrument's "MIDI cha" is set to "all".
Also make sure you set up Aux channels with inputs set as the outputs from
your virtual synth.

Hope this helps,

Matt

> Having sorted out multi outs in the EXS - does anyone know how you use the
> multitimbrality of any multitimbral virtual instruments?
> 
> In other words, how do you use one instrument on ch1 and set it to output 3,
> use a different instrument on ch2 and set it to ch4 etc, without multiple
> virtual instruments being needed?
> 
> I thought this was one of the main ideas of the multi outputs?
> 
> Regards
> 
> David Tobin
> 
> Wow and Flutter ltd

At 04:22 AM 7/08/02 +1000, you wrote: 
>
> This is implemented slightly differently depending on each virtual
> instrument.
>
> With Model-E, for example, you simply select the MIDI channel you want and
> then assign the sound and its output. Simple.
> Now, to play the different channels you will have to send from a different
> MIDI channel on your keyboard or set up some sort of transformer in your
> environment to change the incoming MIDI channel to the desired one.
> Make sure that your logic Audio Instrument's "MIDI cha" is set to "all".
> Also make sure you set up Aux channels with inputs set as the outputs from
> your virtual synth.
>
> Hope this helps,


Thanks for the info Matt -- I had no idea they were going to be supporting this
capability. 
I will try it on Sync Modular. 
Interesting that the Emagic instruments are not multitimbral. 
You could do great things live  with the EXS 24/ ES2 etc with this capability.

Regards,
Murray

Murray wrote: 
> Sounds nice -- do you think us PC guys will see this? If you can't 
> say -- well never mind -- we'll all know in time I s'pose ;-)

Hey, wait a minute.. Sascha Franck's not an Emagic employee is he? Maybe
you're just mistaking him for Sascha Kujawa? 

Anyway personally I *think* this feature (since they are working on it for
sure) will be given to everyone including Windows users eventually.. If
nothing else, you'd think the lack of velocity crossfades would be
considered a bug to be fixed in a future bugfix release, especially since it
used to work in the past and was broken at some point. 

Until some new gizmo is implemented that *requires* OS X I'm really hoping
Emagic will be very liberal with their definition of a "bugfix" and continue
to update EXS for both platforms equally until they're truly prevented from
doing so.

Jeremy
http://www.ixks.com/~sadus

David Tobin wrote:
> Having sorted out multi outs in the EXS - does anyone know how you use the
> multitimbrality of any multitimbral virtual instruments?
>
> In other words, how do you use one instrument on ch1 and set it to output
3,
> use a different instrument on ch2 and set it to ch4 etc, without multiple
> virtual instruments being needed?

You need to cable a multiinstrument to the virtual instrument object.
The output routing will then be done on the instrument itself.

> I thought this was one of the main ideas of the multi outputs?

Personally I prefer having multiple instances opened. Using a
multiinstrument kinda defeats my more or less intensive usage of linked
environment windows (small channel strip floating on top of my arrange
etc.).

Regards,
Sascha

> David Tobin wrote:
>> Having sorted out multi outs in the EXS - does anyone know how you use the
>> multitimbrality of any multitimbral virtual instruments?
>> 
>> In other words, how do you use one instrument on ch1 and set it to output
> 3,
>> use a different instrument on ch2 and set it to ch4 etc, without multiple
>> virtual instruments being needed?
> 
> You need to cable a multiinstrument to the virtual instrument object.
> The output routing will then be done on the instrument itself.
> 
Sorry, but I don't follow how you set up the multi instrument...

What USB port setting do you give it etc - I'm being a bit slow tonight!!!

David

OK, lots of improvements, but still no side-chain to another virtual
instrument. What the heck? They did everything but what I wanted. Jeez.

I guess I can send an instrument to a bus and side-chain to the bus. But it
would have been so clever if they had just nailed this on the first take. Oh
well... Jer

Do the next and previous commands work for .exs instruments, 
or just for settings, such as plug in settings?

Thanks

> Do the next and previous commands work for .exs instruments,
> or just for settings, such as plug in settings?

Yes they work for instruments. In fact, it's smart enough to step through
subfolders in the hierarchy in the proper order. It kicks butt!

HELP@... wrote:
> OK, lots of improvements, but still no side-chain to another virtual
> instrument. What the heck? They did everything but what I wanted. Jeez.
>
> I guess I can send an instrument to a bus and side-chain to the bus. But
it
> would have been so clever if they had just nailed this on the first take.
Oh
> well... Jer

Yes, using a bus is the only option.
But (I think this isn't mentioned in the update info): The bus used for this
doesn't have to be present in your environment at all! And of course you
don't need to set anything on the bus itself either.
Just try it: Send something to a non-existing bus and use that bus as a
sidechain input on *whatever* plugin supporting it.
The only drawback: Such non-existing busses don't show up anywhere as used
ones. That's why I hide mine somewhere out of the visible range of my audio
environment.
Apparently using busses was the only technically working solution for that
sort of thing.

Regards,
Sascha

> > Do the next and previous commands work for .exs instruments,
> > or just for settings, such as plug in settings?
>
> Yes they work for instruments. In fact, it's smart enough to step through
> subfolders in the hierarchy in the proper order. It kicks butt!

Actually, this is a bit weird.
For all other plugins there's now some "next/previous" keycommand.
For the EXS there's actually 3 ways of switching through patches/settings:
1) Via MIDI messages (old). These have to be defined in the EXS editor's
"Edit > Preferences" menu.
2) Via the dedicated (new) EXS KCs. This will switch between actual patches.
3) Via the (new) "normal" plugin "next/previous" KCs. These will switch
between plugin settings.

Yeah, admittedly there's a bit of room for confusion...

Regards,
Sascha

David Tobin wrote:
> Sorry, but I don't follow how you set up the multi instrument...

Create one, cable it to the audio instrument object in question (no MIDI out
port required).

> What USB port setting do you give it etc - I'm being a bit slow tonight!!!

As said, no outport setting required at all.

Regards,
Sascha

Maybe I'm missing something, but I can't see the k.c for moving to the
next/previous instrument.

I have looked at the full list and under the EXS k.c's I can see "next
zone/group". Is this relevant, or if not, where is this command?

David T

> Maybe I'm missing something, but I can't see the k.c for moving to the
> next/previous instrument.
> 
> I have looked at the full list and under the EXS k.c's I can see "next
> zone/group". Is this relevant, or if not, where is this command?

For whichever reasons it's under global commands.

Sascha

> For whichever reasons it's under global commands.

You can assign key commands for next/previous EXS instruments as well as
next/previous settings (in any VSTi). Very nice.

> next/previous settings (in any VSTi). Very nice.

Problem is, once you tweak any parameter of a VST, the feature doesn't work
anymore until you open a fresh VSTi in the slot. Could the beta testers out
there pass this along? It is a flaw. Still it's an improvement.

> Problem is, once you tweak any parameter of a VST, the feature doesn't
work
> anymore until you open a fresh VSTi in the slot. Could the beta testers
out
> there pass this along? It is a flaw. Still it's an improvement.

Can't reproduce that over here.
Which keys do you have assigned?

Regards,
Sascha

> Can't reproduce that over here.
> Which keys do you have assigned?

+/- keys on the number pad. Mac.

<HELP@...> wrote:
> > Can't reproduce that over here.
> > Which keys do you have assigned?
>
> +/- keys on the number pad. Mac.

There might be a problem because these are usually assigned to "Parameter
Value Up/Down" (a setting you can't define by yourself), allways working for
the last touched parameter.
On Windows, when you assign something to +/- on the numerical pad, these
settings are somewhat overwritten, it seems as if on Macs it's different. In
that case I would just try to assign some other keys to "Previous/Next
Setting".

Cheers,
Sascha

> There might be a problem because these are usually assigned to "Parameter
> Value Up/Down" (a setting you can't define by yourself), allways working for
> the last touched parameter.
> On Windows, when you assign something to +/- on the numerical pad, these
> settings are somewhat overwritten, it seems as if on Macs it's different. In
> that case I would just try to assign some other keys to "Previous/Next
> Setting".
> 
> Cheers,
> Sascha

Thanks, Sascha. Very good advice!