posted 20 February 2010 02:50            

wavetableGrumbles.kym

I had a lovely day today building a new synth in Kyma and making patches with it (see attached wavetableGrumbles.kym).

Incorporated into the design is a chorus module I found in the Share section of the tweaky called OmniChorus - lovely.

the last step was to then put two copies of the synth into a timeline. As you do, one for bass the other for a pad. BUT on run of the timeline I get an error saying:

The wavetable named #feedback_chorusB is never read after it is written at time 0.109375 seconds on processor 4.
The wavetable named #feedback_chorusB is never read after it is written at time 0.109375 seconds on processor 4.

I figured that given there were two copies of the OmniChorus unit within this timeline Kyma had issues with the (identical) naming of the connections (wavetables) used in the feedback loops within the two different OmniChoruses.

I tested this theory by expanding a copy of OmniChorus, finding the feedback loops (there were two because its a stereo effect) and renaming the the feedback wavetables from:

feedback_chorusA and feedback_chorusB

to:

feedback_chorusA1 and feedback_chorusB1

and also renaming the object at the right most part of the signal flow to:

Omni Chorus. Mono Input Expanded1

this process was repeated to produce a sound called "Omni Chorus. Mono Input Expanded2"

drag the two new OmniChorus sounds into a time line and it worked, no errors.

Grumble Mode ON

Is it possible to avoid this workaround?

I would have thought that objects that do feedback (delays, memory writers, feedback loops) SHOULD be able to have multiple instances within a timeline without having to muck around with (expanding and then) uniquely naming every instance of a connection (or wavetable) particularly when used in a sound that has been encapsulated as a class like the OmniChorus.

it would certainly mean that sounds encapsulated as classes would be much much more re-usable.

Grumble mode OFF

posted 20 February 2010 16:16            

I understand it's a user defined class but it does seem odd that Kyma cannot automatically handle this sort of issue. I've seen examples of different objects with the same name in structures before implying that there is some underlying unique identifier, is it not possible to extend that identification to objects like the the named memory used for wavetables, delays and feedback loops?

Simmilar to the 'Private' name used in delays where Kyma does handle this.

Regards,
Sean
Sean

posted 21 February 2010 21:17            

omni_chorus_multi.kym

Try the attached sound and see if works better for you. I don't know how to do the 'private' thing but at least in this version, you can just input a unique name for each instance within a timeline or sound and it should work fine.

It will also handle being nested inside a midivoice if you wanted each synth voice to have its own unique chorus.

Also included is the original expanded sound so if you want to muck around in it and re-save as a class, it may be easier now.

posted 23 February 2010 01:32            

updatedOmniChorus.ktl

The wavetable named #feedback is written more than once at time 0.046875 seconds

See attached timeline.