Kyma Forum
  Kyma Support
  Timeline Out of Real Time

Post New Topic  Post A Reply
profile | register | preferences | faq | search

next newest topic | next oldest topic
Author Topic:   Timeline Out of Real Time
Nev
Member
posted 03 January 2003 16:58         Edit/Delete Message   Reply w/Quote
Greetings all and Happy New Year!
Been lurking for a while, but I am still very much a Kyma newbie, hence
the following questions:
I have a Capy 66 with 4 cards+full RAM (feel the power! :-0) and I am getting quite a lot of Out of Realtime messages when it still looks like I have open DSP's.
Using levitation.ktl from the Sound Library as an example, DSP1 is maxed
out while procs 2,3,4 are doing almost nothing.

Another example: Scale Vocoder from the prototypes plays fine on its own
spreading its usage out over my 4 DSP's. Upon dropping it onto the Timeline , I get out of Real Time....

I have become reasonably good at reducing number of oscillators,bands etc to make a Sound work. I have played a bit with the ForcedProc (hasn't helped me much).

Any suggestions would be appreciated.

Cheers,
Nev.

IP: Logged

SSC
Administrator
posted 04 January 2003 14:01         Edit/Delete Message   Reply w/Quote
You will often get these messages when working with the Capybara-66 since the Kyma Sound Library was optimized for the Capybara-320, and a basic Capybara-320 is about as powerful as a Capybara-66 with 7 or 8 expansion cards.

When the Capybara runs out of processing power, the maxed-out DSP Status bar indicates the processor that is the most out-of-real-time, and all of the other bars indicate the amount of processing power used *relative* to the maxed-out processor. This means that you cannot tell whether the other DSPs are out of real time.

The timeline itself consumes some DSP power in order to implement panning, to record and playback controller functions, etc.

What you have already said is a good way to alter Sounds to work on the Capybara-66 (reducing the number of oscillators, grains, or bands, reducing the bank size for the Vocoder).

ForcedProcessorAssignment is seldom a good way to squeeze more processing out of your Capybara, since forcing the scheduling of a portion of the signal flow diagram can make it difficult or impossible to schedule the remaining parts.

IP: Logged

All times are CT (US)

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply

Contact Us | Symbolic Sound Home

This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.


Ultimate Bulletin Board 5.45c