96K ??

Music Manic · Post by **Music Manic** » Wed Jul 28, 2004 11:10 pm

Gave vdat a go with 96k today.very nice recordings,but when I add other plugins I soon reach PCI overload.Timeworks suffer mostly and are very buggy.
Try compressor using soft knee and it glitches like crazy.
Don't think Pulsar can manage it on my PentiumIII SDRAM.
How are you guys getting on with DDRAM or even PCI express?Any joy.
Does anyone know which plugins can run on which samplerates?
Also will Pulsar ever be programmed for 88.2k?
Thanks

at0m · Post by **at0m** » Wed Jul 28, 2004 11:28 pm

Problems arise when loads of atoms or modules are locked to the same DSP for phase consistency. When the load is too high for a single chip, the sample-rate is too high for the batch locked to a single chip. So it's not a bug really, it's a limitation by design. It's to choose best quality at most common samplerate instead of an option to run it at 96kHz, which is marginally used IMO. Sometimes the device/module even requires phase consistency for it to work at all.

STW did their best in making the ultimate mastering compressor that would fit on a pulsar1. IMO they did a great job at it... The same goes for Minimax' filter and some Flexor modules, for example some of the monophonic stuff, that won't work at 96kHz.

Maybe we'll get phase consistency over multiple chips one day. It was announced for v4, don't think it's implemented for now. Cos 96kHz is superb for synthesis...

If you have a 88.2kHz digital master clock, Pulsar can slave to it. Afaik the manual mentions anything from 30-100kHz as a possible samplerate...

My 2cents.

Music Manic · Post by **Music Manic** » Mon Aug 02, 2004 12:09 pm

Sorry,meant compressor-x.
How does scope deal with phase consistency then?