Just a thought

The difference between a human player and samples are the speed.

The first piano sample that is fast or close to human playing is Ivory synthogy.
The first orchestral samples that are fast enough to be real are VSL.

Question: How will the new SC interface player use the stac up, down, bowing in the score?

I just now discovered (Solo violin) has "spic marc" for fast passages.
anxious to use "short stacs" in chamber strings.

Calling all herb !---- Calling all Herb !

Actually as a pianist I find that the ArtVista Virtual Grand Piano has a very "human" feel to it. Can't tell the difference to Ivory though as I don't own the latter.

PolarBear

Just heard the sweedish piano sample. It has a lot of presence, up front dry clear sound. Sounds great. It has a cut of much like a playel, but sounds alittle more tamer. I'm having to back of from using Ivory's effects. Different parts of fast passages need effects taken out. Ofcourse thats not real human acoustic, but its more effective. these piano samples seem to keep up with the new and bigger CPU's/memory as they expand. Wish one could say the same towards the sequential programs. 64 bit processing into the atmosphere.

Polar bear
this is a little question to ask. But do you know if one can load single samples in the new VSL upgrade much the same as present way. All the video shows , is using the new player. Which is of course great.

I might just buy a couple of 24 track recorders and get the whole VSL with all its glory. Just the same.

sincerely

R.K. - the Vienna Instruments is a player only software, that means you can't access the samples directly for editing purposes, however you can load a patch and play a specific sample at a specific velocty just as it is now. Loading a single sample only would mean you'd have to load the whole program and use the RAMsave function to free up the memory from the unneeded parts. I didn't read the EULA yet (is it even availible yet?) if it allows some sort of resampling for the licensee. That way you could record single samples into your sampler (most have an editor) and act with them just like you do know with others.

To sum it up - the VIs (i.e. Symphonic Cube products) are wrapped up in a player type. To edit samples or create new programs you'd need to extract them (if that is allowed).

Still I'm not sure I understood your question right as I see you mentioned 24 track recorders (for what purpose you'd think you'd need that)?

All the best,
PolarBear

Thank you for your prompt response " polar bear "

Vie geht und zer gut.

So the new player is actualy the sampler window, and one would treat it just like current loading of sampler window. Therefore one simple articulation at a time is acceptable. Of course that makes sense. But somtimes I lose my senses in the midst of.

If one downloads tracks from computer to 24 track machines, then all restraints of cpu or mamory is relinquished. And Orchestral timbral build ups will have no caps or ceiling. Then everything is possible. Correct ?

und ich wil geten sie das SC. ya

bite

@R.K. said:

If one downloads tracks from computer to 24 track machines, then all restraints of cpu or mamory is relinquished. And Orchestral timbral build ups will have no caps or ceiling. Then everything is possible. Correct ?

Yes, but there's not really that much point. Using a Freeze function (in CubaseSX or Logic) will simply render the entire track down to audio which has very little CPU overhead and even less RAM overhead.

The best approach is start LIVE (lots of RAM/CPU needed) - then use RAMSAVE in the VI to free up RAM, however its still using some RAM and CPU so use the Freeze function(in your sequencer) to free this up even further - in SX3 you can even unload the VST to free up more resource as part of the freezing process.

No need for 24 track tape machines.....

Thanks Tim

In logic , if I remember correctly, one has to install samples in computer's hard drive itself, in a certain place, to gain acces to freezing. Perhaps certain articulations only, that drain ram/cpu. I didin't persue any further , but maybe I should have. Thanks for the reminder. I see thats very important.

sincerely

There are also tools for freezing if your sequencer doesn't support it natively, afaik one is a VST called TapeRecorder or something like that.

I don't think you'd need to freeze all tracks, the CPU usage will be not so high, and it might be enough to only free the RAM with the built-in RAMsave function of the VIs. A 24 track tape recorder seems overkill to me.

Viel Spass mit den Sounds! [;)]
PolarBear

Once you use the ram save feature, aren't you stuck with what was already recorded? I only see this feature useable once you have finished the entire instruments part for the piece but if that's the case wouldn't freeze be even better? Am I missing something here?

Freezing wouldn't allow you to change dynamics later which you can do using the ram saving feature of the VI.

Yes, I tend to agree. The whole RAMSave vs Freezing is an interesting debate.

To me the RAMSave would only come into its own if it was possible to "relearn" a slightly modified sequence or have a 0s preload (thereby no RAM) for each VI. Otherwise its a pretty close call between RAMSAVE and Freezing the whole track.

>>
Freezing wouldn't allow you to change dynamics later which you can do using the ram saving feature of the VI.
>>

As long as you do not cross any velocity switches, right. Therefore an update purge function like you find the concept in K2 is nice. But at least you can edit timing and resequence the notes.

best

@steff3 said:

>>
Freezing wouldn't allow you to change dynamics later which you can do using the ram saving feature of the VI.
>>

As long as you do not cross any velocity switches, right. Therefore an update purge function like you find the concept in K2 is nice. But at least you can edit timing and resequence the notes.

best

I think a purge saves all velocities for a note. I remember seeing something in one of the videos along these lines.