Got my Logic 7.0!... woo hoo!

[griels]

PDC has never been an issue with me...

same here

You childish fanboys!

Just thought I'd make things even Wopelka

Seriously, with Space Designer being capable of latency compensation, it probably isn't too big an issue, except for use with the UAD-1/Powercore/Wormhole/the mooted FXTeleport MAC. Although I believe Putte uses a UAD-1 with Logic? How do you handle the latency?

I hear PDC is planned for Logic 7 soon regardless

[spaceman]

any news on those cupholders?

[putte]

Although I believe Putte uses a UAD-1 with Logic? How do you handle the latency?

pff .. what do i know?? ask him ..

[griels]

any news on those cupholders?

Frozen cupholders?

[ericj23]

frappe !

[BitFlipper]

PDC has never been an issue with me... Frankly, I haven't been able to cause a delay with a Dual G5, so far... and with distributed processing, I guess that would be a non issue? ...I can buy another G4 Mac for the price of a UAD-1...

Actually PDC has nothing to with your processor speed. It's a function of the actual algorithm applied to the data, and is fixed for that algorithm, irrespective of how fast (or how fast you might think) your processor is.

Basically, it's a measure of how much the audio stream will be shifted back in time inside the buffer that is passed to the plugin. For instance, a "look-ahead" limiter "looks ahead" by looking at current samples and delaying the signal internally before actually processing it. Zero to do with your processor speed.

Another place where a delay is introduced is whenever you apply FFT to the signal. The signal will be delayed by half the size of the FFT buffer (512, 1024, 2048 etc samples). Again, your processor speed plays zero role in this.

Yes, a faster processor can process that same buffer in a shorter amount of time, but it would still be shifted back in time by the exact same amount of samples.

That's what PDC compensates for.

BitFlipper

[TristezaOrange]

f**king childlish Mac fanboys

You make me sick
































trance

[DHR53]

If I can't do what I want with Logic 7.0 ...I need to forget about making music altogether... Do I need PDC for Space Designer? Hell, I'm still using Silververb...

[mummy]

Hasn't PDC been in Logic for ages, but it just isn't quite complete? It'll be nice to have it in case there's a project coming where it might be an issue

[griels]

Hasn't PDC been in Logic for ages, but it just isn't quite complete? It'll be nice to have it in case there's a project coming where it might be an issue

Ah... That rings a bell... I guess if you use low latencies anyway, the UAD-1 etc should be fine (double 3ms latency is still low, and possibly compensated anyway)... And yes, Space Designer has inbuilt PDC. No cupholders yet though

[nocompromise]

who cares if its got PDC or not? Why is it so important? Aren't you capable of shifting the non-PDC tracks by hand?
In any case, how do u guys know its working correctly? I tend to shift trks about manually anyhow - until they feel right................................................................................................................................................

[griels]

who cares if its got PDC or not? Why is it so important? Aren't you capable of shifting the non-PDC tracks by hand?

It's horribly time consuming. Fortunately there aren't that many plugins that introduce significant latencies. And most of the people here (including myself) have already noted this.

In any case, how do u guys know its working correctly? I tend to shift trks about manually anyhow - until they feel right................................................................................................................................................

It doesn't always work correctly, but in SX3 SIR seems to sound just fine using PDC. It's the plugs with larger delays that are the greater concern in terms of PDC. In my experience, shifting tracks manually is *sometimes* necessary but for the vast majority of situations, it isn't, at least with PDC. Your milage may of course vary

[DHR53]

After messing around with the beast for a few hours, some observations...

1. Seems to be using more cpu, which is to be expected due to interface redesign, and window expansion (mixer etc.)
2. New instruments are pretty cpu intensive... Even the Impulse seems to be hitting the cpu harder, but I guess it's a synth not a sampler...
3. Wish the impulse had drag and drop from the sequencer, rather than the "single midi note plays a pattern thing"... Although I guess you can just program patterns in the matrix...
4. Some kybd. cmmnds don't seem to work properly, maybe I'll have to redo them from the conversion to 7.0?
5. Apple loop implementation is pretty slick! Way better than the old methods with waves and Rex...
6. Overall interface seems to be quicker, drop-down menus etc.

[DHR53]

Maybe my imagination... I think there are a whole lot more presets in here for the instruments... Especially ES2 and EXS24... maybe they consolidated all the stuff?? Hmmm... great sounds!