I proudly own the EastWest Quantum Leap Symphonic Orchestra.
The sad thing is, that to use it in an effective way one has to have LOADS
of ram and preferrably multiple machines.

So since i dont especially need Realtime, i thought if anyone else had the
idea to use big Sample players like EWQLSO in conjunction with Csound. I
guess combined with some high level score generation this could be a very
powerful combination.I am on windows XP by the way.

I will tryout out some VST plugin examples but if anyone has had any success
in this task, please be so kind to share your experience. (and possibly some
lines of code?). 


Thanks a lot everybody,

Cheers,
dk.



-- 
View this message in context: http://www.nabble.com/Using-EWQLSO-with-Csound-tf4303984.html#a12251050
Sent from the Csound - General mailing list archive at Nabble.com.

I'm not familiar with this library, do you have access to the actual
samples themselves? If so it shouldn't be any problem to set this up. If
  the library comes in a closed box virtual instrument interface then it
might be a bit trickier as you will most likely still need all that ram
to power the actual software that plays the samples. I see that more and
more sample libraries are being shipped with their own soft-samplers
meaning that most end-user doesn't have access to the samples they paid
for unless they use the software that comes with the library.

Rory.




David Kamp wrote:
> I proudly own the EastWest Quantum Leap Symphonic Orchestra.
> The sad thing is, that to use it in an effective way one has to have LOADS
> of ram and preferrably multiple machines.
> 
> So since i dont especially need Realtime, i thought if anyone else had the
> idea to use big Sample players like EWQLSO in conjunction with Csound. I
> guess combined with some high level score generation this could be a very
> powerful combination.I am on windows XP by the way.
> 
> I will tryout out some VST plugin examples but if anyone has had any success
> in this task, please be so kind to share your experience. (and possibly some
> lines of code?). 
> 
> 
> Thanks a lot everybody,
> 
> Cheers,
> dk.
> 
> 
> 

Yeah unfortunately its like that. It has its own interface based on the
kontakt player and the samples are hidden in .nks files. 

Basically there is the library f. ex. :
EWQLSO_Wooodwinds_part1.nks  (size 2GB)
EWQLSO_Wooodwinds_part2.nks  (size 2GB)
:::and so on until woodwinds 9. (so quite a lot of data)

and then there are the small patches for the kontakt player f. ex.:
WoodwindEnsemble1.nki    (size 17 KB).







-- 
View this message in context: http://www.nabble.com/Using-EWQLSO-with-Csound-tf4303984.html#a12251624
Sent from the Csound - General mailing list archive at Nabble.com.

well this sounds very similar to the garritan setup.

does it come with it's own VST host application? (so that in the case of
garritan for example, you can host a number of Kontakt players in the
Garrtan Studio app, & target them via virtual midi cables or the like...)
but then this is essentially "real time" - & hence u r limited by CPU
limitations. Kontakt sampler does have a direct from disk streaming
capability. is that not included in your software's version of Kontakt
player?

I agree with your synopsis re: the potential of scripting scores for these
orchestra sims. Loading garritan via the VST opcodes was a bit of a pain
when i tried it - but if you were going to render a long piece straight to
file it might be worth the wait for all the VSTinst & their associated .fxb
files to load every time you run csound (the "pain" part)

I am, of course, presently attempting to use Python to:

*host multiple Csound insts to 
*target separate kontakt players on separate -Q output channels

in order to

*script create the midi files via python with all associated randomisations,
cc controllers, key switches, gaussian randomisation of start times for
identical parts shared by ensemble players etc..

however as anyone who has read my thread on the subject will realise, i
still have an outstanding issue with this that i need assistance to
address.....

.....

.....

Other than this gripe, after my initial dabblings with Python (to do the
type of things i think you (we) are talking about) i'd definately suggest
exploring it as a means to this end.

I'm happy to share my code to date - but it's still very much a work in
progress, not fully tested (rewrote some more of it today), specifically
targets garritan, & works in with my own sco creating "meta language" - so
it's pretty idiosyncratic, & you may be better off just starting as I did,
from first principles.

otherwise, i also watch this thread with a vague to active interest
depending on what it spews up.

not feeling 100% today. both brain & fingers near cessation of useful
functionality.


David  Kamp wrote:
> 
> Yeah unfortunately its like that. It has its own interface based on the
> kontakt player and the samples are hidden in .nks files. 
> 
> Basically there is the library f. ex. :
> EWQLSO_Wooodwinds_part1.nks  (size 2GB)
> EWQLSO_Wooodwinds_part2.nks  (size 2GB)
> :::and so on until woodwinds 9. (so quite a lot of data)
> 
> and then there are the small patches for the kontakt player f. ex.:
> WoodwindEnsemble1.nki    (size 17 KB).
> 
> 
> 
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Using-EWQLSO-with-Csound-tf4303984.html#a12252192
Sent from the Csound - General mailing list archive at Nabble.com.

Looks like the samples are all bundled into those .nks files. I wonder 
is there a way of extracting the actual samples? I'm sure it would be 
pretty straight, albeit illegal, but one would need to have access to 
the file-format which I'm pretty sure Native Instruments won't be 
sharing with any of us any time soon...

Rory.


David Kamp wrote:
> Yeah unfortunately its like that. It has its own interface based on the
> kontakt player and the samples are hidden in .nks files. 
> 
> Basically there is the library f. ex. :
> EWQLSO_Wooodwinds_part1.nks  (size 2GB)
> EWQLSO_Wooodwinds_part2.nks  (size 2GB)
> :::and so on until woodwinds 9. (so quite a lot of data)
> 
> and then there are the small patches for the kontakt player f. ex.:
> WoodwindEnsemble1.nki    (size 17 KB).
> 
> 
> 
> 
> 
> 
> 

A few thoughts / suggestions -

Depending on whether you have access to the full version of kontakt  
and whether you can actually open those files within it - you might  
be able to at least get your paws on the samples in the "instruments"  
and perhaps export or extract them somehow if you really wanted to  
without knowing the format.

However - I'm not sure that's in your best interest.  Usually the  
sample players have built in settings for improving the overall sound  
of the samples by themselves - sometimes  it helps and sometimes it  
does not.  It seems like your best bet in this case is to use some  
software, be it Csound, PD, Max or anything that can generate MIDI  
events, and send the events to a virtual port that can be read from  
your sequencer.

As far as non-realtime goes ... once you have the recorded MIDI  
events - in most sequencers you can bounce tracks one at a time or  
altogether in non-realtime.  However, I have found that because most  
plugin formats (namely VST) use a different processing method in non- 
realtime (which is usually not tested as well) you may experience  
undefined behavior and/or crashes.  (I remember a case with an older  
version of Garritan that had this problem).

greg


On Aug 21, 2007, at 6:55 AM, Rory Walsh wrote:

> Looks like the samples are all bundled into those .nks files. I  
> wonder is there a way of extracting the actual samples? I'm sure it  
> would be pretty straight, albeit illegal, but one would need to  
> have access to the file-format which I'm pretty sure Native  
> Instruments won't be sharing with any of us any time soon...
>
> Rory.
>
>
> David Kamp wrote:
>> Yeah unfortunately its like that. It has its own interface based  
>> on the
>> kontakt player and the samples are hidden in .nks files. Basically  
>> there is the library f. ex. :
>> EWQLSO_Wooodwinds_part1.nks  (size 2GB)
>> EWQLSO_Wooodwinds_part2.nks  (size 2GB)
>> :::and so on until woodwinds 9. (so quite a lot of data)
>> and then there are the small patches for the kontakt player f. ex.:
>> WoodwindEnsemble1.nki    (size 17 KB).
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>