CPS vs. Reaktor (was: Re: CPS Announcement MPEG-4 SA)

From: Niels Gorisse (niels@bonneville.nl)
Date: Sun Feb 27 2000 - 12:00:42 EST


Hi,

>Have you checked if it wasn't implemented in sfront either ?

Sfront has a reverb, but doesn't include the correct parameters too.

>Macros will use more cpu I suppose, will we get all SAOL core opcodes in a
>future implementation ?

No! Macro's do NOT use more CPU time; that's one of the special things
about the macro structure of CPS (it does take more time in MAX).

>I see. Wouldn't a separate panel look more "hardware like" ? I mean, the most
>convenient layout of visual controllers on a panel is not necessarily the
most

Perhaps you are right. But debugging a patch is a lot easier with direct
graphic feedback. Perhaps hiding all wires is a solution.

>Will you be able to "program change" instruments in your orchestra via
MIDI as
>well ?

Sure! - that's why it is going to be a single object with normal inputs,
and not an option in a Menu! Note that this is not SAOL compatible of course.

(VST plugin)
>Excellent. When do we get that ?

One thing at the time please. First it will run in a browser, then save as
saol, then the rest. Note that the plugin architecture of CPS is already
VST-ready, so it is only a matter of connecting the Java interface to it..

>> A real disadvantage of Reaktor is the lack of graphical feedback. In CPS
>> you can place a 'numberField' or any other Display object in your
>> calculation at any point, and by doing so see what's going on (not only
>> controlRate value's but also audio signals). Believe me, that is a relief!
>
>I agree it's a good thing, but reaktor does have it too (in any case
Generator
>1.5 had it) : if you let your mouse wander over a wire you get it's value
>(control OR audio). Also they have VU-meters for graphical feedback, plus a
>"scope" module to see the shape of the signal.

OK. I didn't know the 'wire' mouseOver thing.

>> Conceptually, it doesn't have low-level MIDI like CPS does, so you cannot
>> use it for algoritmic composition for example. There's no way to manipulate
>> MIDI at all!!
>
>Not as such, but as what they call control signals (which are events just
like MIDI)

But you can't actually do anything with the 'control signals', besides
attaching them to audio modules. Can I record MIDI in a table, or us an
algorithmic formula to generate MIDI output with Reaktor?

>
>> Well, CPS is also capable of delivering pretty low latency,
>
>What latency do you get inputToOutput when you use your PC running CPS as a
>hardware effect with a basic sb 16 card for example ?

I do not have numbers, but you might check it yourself with the
lessLatency.cps example.

>How does cps compare with current sfront cpu-wise BTW ?

Well, CPS is very realtime compared to sfront, which is nearly realtime.
But that is not really a fair comparisation; sfront is really 100% MPEG-4
SA compatible, including every little detail, in contrast to CPS. You could
say that sfront is everything doing in the 'sampleprecision' way of CPS; if
you would run the same orchestra in sfront and in CPS everything with
'sampleprecision', then the difference would get significantly less.

Niels Gorisse
Bonneville



This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 11:46:37 EST