dual-core causing update loop.....

[woodslanding]

I want two different faders in different parts of the workspace to display the same data, and mutually update each other.

So I have:

buss1-->onlyIfChanged-->fader-->buss2

and elsewhere:

buss2-->onlyIfChanged-->fader-->buss1

problem is, if either fader is moved quickly, the whole thing gets into a loop where it oscillates between two values. This started happening when I switched to dual core mode (I was running out of processing power, and getting clicks in the audio.)

Is there a way to assure two objects don't get processed with different cores? How are the cores allocated?

thanks,
-eric

[bsork]

The distribution is per track: For dual core, tracks 1, 3, 5.. are allocated to the first core, and tracks 2, 4, 6... to the other. Similarly for quad core where the first core runs tracks 1, 5, 9...

Except for moving the patches to tracks running on the same core, maybe you could try to insert a WaitOne or two? I haven't got time to test anything myself right now and I don't have a clear idea of where to put the module(s), but I wouldn't be surprised if a little experimentation with this would solve the problem.

[woodslanding]

I did try the wait one, and it just slowed down the oscillation. I still couldn't adjust the value.....

I put it between the buss in and one of the onlyIfChanged modules. I'll try some other combinations.

-e

[woodslanding]

Oh, also, I did try putting both patches on the same track, and it didn't help....

[bsork]

Too bad, I think Senso will have to chime in on this subject,