This is crazy.


I just realise that it’s maybe the first time in the computer history that a company have such considerations to handle...

Even in the Video world they don’t have that kind of problems... Not on that way. Although storage managing is incomparably bigger (specially for movie production), of course, but they don’t have to sell it on that medium !

VSL PRO Complete took me 3 8 hour days of uncompressing on a Dual G4 1.42Ghz. It's a lot fo DVDs. And the SYMPHONIC CUBE is 5 to 10 times as big! I assume. It may be some kind of a la carte option actually.

Evan Evans

In related news:
http://www.techtree.com/techtree/jsp/showstory.jsp?storyid=53986&s=ln

@Nigel Watson said:

Maybe VSL really does need its own soft interface to become more simply accessible for the user.

Thank you

Nigel

It could be interesting ... you connect your HDD via the USB or FIREWIRE port, active the software and play ! [:)]

@Crystal said:

32bit,Really ?

So guys, you have to update your presentation page, I can read on the ‘About us’ page : « recorded in 24-bit/96 kHz, stereo »

The recordings are made in 24/96, of course, but are saved and processed in 32bit floating throughout the whole production-process; the files are resampled and dithered using our own proprietary tools for the final products.

HTH,

/Dietz - Vienna Symphonic Library

Hi Ditz.

I understand Now. So you need a 32bit step in your process.

This is a bit OT, but... why, exactly ?

There was a discussion on NSS about that point : a piano library in 32bit, but it was a VSTI player, if I remember. So a player have to mix the polyphony.

Our sequencers, soft samplers and audiocard mixers all work now in 32 flt to keep the mixing, processing, or effects at a high level (and without digital distortion risk).

But in a editing process for sample libraries, I don’t understand. Cleaning ? Compression ? Stereo field tweaking ?



Still using Sequoia, I presume ?...

Sorry, Dietz, your question and your competence. But I may copy this from the samplitude/sequioa forum:

@Another User said:

A 32 Bit float file IS a 24 Bit file with extra information, to keep the full resolution above the complete dynamic range. No zeros were added. A 24 bit file looses 1 bit with every -6 dB destructive change. The extra bits in a float file preserve the full resolution (24 bit) also on lowest levels.

regards
Norman

That means a 32bit file is the SAME audio like a 24bit file. But as soon as you render volumes or fx into the file it gets interesting. The original 24bit resolution is preserved to whatever you do with it. You can lower the volume -100dB and it will still have 24 Bit audioresolution.

So speaking for VSL, when they record in 24 bit and would stay in 24 bits, then make the volume and tuning adjustments they would end maybe on 22 bit resolution or something. With 32 bit every bit is preserved.

Correct, Dietz?

That's it, in a nutshell. Thank you!

IOW: The only point where you have to bother about the volume of a 32bit-audio signal is the stage where you leave the floating-point domain and go to a lower (read: integer) bit-depth or convert to analogue.

/Dietz - Vienna Symphonic Library

Thanks mathis and Dietz.

This is instructive.

"William you are off the deep end baby" - Evan Evans
Ironic response, considering the source

"Are you working pro, William?" - Matt1
In other words, I am just scum and not to be paid any attention to? Sorry, I am an on-and-off pro (when I feel like it which is rare considering I am very lazy and I lack the required instinct for self-degradation). Though it WOULD be kind of nice being a complete amateur like my best buddies Schubert, Franck, Bruckner, Borodin, etc., etc., etc. Any other questions Matt1?

William,

Yes, it's a good place to be eh? [;)] intersting sea life.

Evan Evans