// -----------------------------------------------------------------------------
//
// MQ Tama Snares Sample Set
// Tama Star Classic Performer (Birch) 14"x5.5" tuned for woody sound
// recorded on May 13th 2007 by Mike and Gia McCue www.harmoniccycle.com
//
// -----------------------------------------------------------------------------
// Acoustic Snare:
<group> key=38 loop_mode=one_shot
<region> lovel=000 hivel=015 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 01.wav
<region> lovel=016 hivel=024 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 02.wav
<region> lovel=025 hivel=033 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 03.wav
<region> lovel=034 hivel=042 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 04.wav
<region> lovel=043 hivel=047 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 05.wav
<region> lovel=048 hivel=052 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 06.wav
<region> lovel=053 hivel=057 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 07.wav
<region> lovel=058 hivel=064 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 08.wav
<region> lovel=065 hivel=069 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 09.wav
<region> lovel=070 hivel=074 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 10.wav
<region> lovel=075 hivel=079 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 11.wav
<region> lovel=080 hivel=084 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 12.wav
<region> lovel=085 hivel=089 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 13.wav
<region> lovel=090 hivel=094 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 14.wav
<region> lovel=095 hivel=099 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 15.wav
<region> lovel=100 hivel=104 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 16.wav
<region> lovel=105 hivel=109 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 17.wav
<region> lovel=110 hivel=114 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 18.wav
<region> lovel=115 hivel=119 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 19.wav
<region> lovel=120 hivel=127 sample=MQ Tama Snares\MQ TamaStarClassic14x5birch 20.wav

I think it's just a case of expecting too much out of Studio Instruments.  As I noted early on, it is what it is.  If more expressive results are required it really is a case of right tool for the right job.  For most people (note, I'm not one of them as I paid full retail for it back in 2007), it is a throw in with Sonar or other Cakewalk products and it's not seen much, if any development time since it was released.  

If someone asked me for recommendations for an "expressive" sample library, it would not be in my top 10 list, but it does serve a purpose and provides a usable multi-instrument library for adding some sampled instruments to a mix or as a mock-up for quick compositions which later might be replaced with a more suitable sample library.

One of the benefits of Sonar X1 Producer is that it includes Dimension Pro which is what, if I was restricted to using included instruments for keys, strings, or non-synth bass lines, I would probably use instead of Studio Instruments; it is definitely more expressive, add to it the benefits of having a synthesis engine more capable than that of Studio Instruments, it just seems a more capable choice.

I hope I'm not coming across as offending as it's not my intent. It just seems to be a case of expecting too much from Studio Instruments (which I've tried to make clear - I still use, knowing what it is capable of, and what it is not).  

Did Cakewalk ever fix the out of tune bass samples that were sent out with Dimension Pro's "Real Bass" bass samples?

mike_mccue


Did Cakewalk ever fix the out of tune bass samples that were sent out with Dimension Pro's "Real Bass" bass samples?

Yes. they melodyned them.

I hope I'm not coming across as offending as it's not my intent. It just seems to be a case of expecting too much from Studio Instruments (which I've tried to make clear - I still use, knowing what it is capable of, and what it is not).  

No worries Jind.

bitflipper


You can look at the sfz files with Notepad and see which ones have velocity layers and which ones don't. I've never used the Studio Instruments except for some cursory experiments, so I opened a few sfz's to have a look.

Velocity layers in sfz files are defined by lovel and hivel keywords, so I used grep (a DOS command line search utility) to quickly identify which sfz files in the bass folder contained them, .....

Hey bitflipper,
 
you do know that grep came from unix, like most useful things in both MS and Apple operating systems ?.
 
I was using grep before Dos was even Dos !.
 
I find it interesting how MS and Apple seem to paint the picture that they've come up with all these cool things, where in
reality most of the good stuff in their operating systems is taken from the world of Unix/Linux.
 
Dennis Ritchie who died last October was the father of all the computing goodness we benefit from these days.
 
He invented the Unix O/S and the 'C' programming language (which is used to write most of the O/Ses we use today)
 - amongst many other great things.
Even the good old mouse came from Xerox labs. Steve Jobs and Bill gates both took the mouse when they were given a
tour of Xerox labs.  Nothing to do with MS or Apple.
 
 
Cheers - Cliff

Layers may be more "authentic" for sampling "real" instruments, but they are not needed for velocity response.

Bingo.

Yes, I am an old UNIX guy from way back, long before Linux existed. DOS, of course, was inspired by CP/M, which in turn was inspired by UNIX (which was inspired by MULTICS). Many of the old UNIX command-line tools were ported to DOS back in the day, which eased my own adoption of DOS. I still have them. Haven't used awk for a long time, but grep gets almost daily use even now.

Fond memories of "Edlin" then?!

Just a suggestion if you are still having issues here - try recording some midi playing the SI via your midi keyboard and playing as softly and loudly as you can, then look at the recorded track in the prv - that will show the actual recorded velocities against each note so you can see if the problem is with your controller (velocity curves etc) or the SI itself - you could also manually edit some prv track to see if manually input velocities gives the dynamic range you are looking for.