Hi

I am very new to PD

I am passing cw_binaural rotation data from a 3D engine.
I do this at set intervals. Let's say every 100 ms

In order to try to smooth/interpolate the transitions I am trying to use something like

[Yrotation\
|
[line 0 100]
|
[dac~]

Unless I am rotating very slowly, I am getting signifcant pops/clicks. If I rotate really slowly, it works fine.

cw_binaural pops/clicks if you move it too quickly on its own with a number box too, but you need to move it very quickly. If I'm effectively "capping" rotation rate to 100 ms I'd expect any rotation I pass to work without popping.

I have tried to increase the rate of rotation data and also played around with the time taken for line to interpolate, but there is little significant difference with regards to popping/clicking.

I'll test some more when I get home, I just thought I'd ask here to see if anyone has a better method, or if I'm overlooking something obvious.

Thanks

The Cosin function does wrap the values around, but if you are rotating in a direction, at some point the sound is going to start moving in the opposite direction.

In the interests of resolving this thread:

I was able to escape the 0-360 constraints on the .Net side before passing to PD, by creating running rotation counters like the patch expects.

I use Mathf.DeltaAngle to work out the shortest path in degrees between two eulers, so I can always add the result to the counter after passing the previous and current rotation values.

For Mathf.DeltaAngle, the difference between 359 and 4 is 5 degrees, not 355 degrees.

Thanks. That helps

I've implemented line~ and decreased both intervals to 20 ms. It is only clicking in a particular point now, and that is when the 3D engine rotation snaps from 360 to 1. cw_binaural seems to expect the number to elegantly be rolled over to 361.

I am still trying to think of how to deal with that.