I'm relatively new to pd and new to this forum, so thank you for taking time to take a look at my patch:

I'm building this sequencer that is controllable via touchOSC and I want to mute certain steps of the sequence. So I added an array with values either 0 or 1 for the single sequence steps to be muted or not. So now, there is this clicking noise every now and then when the "mute" value changes. Is there an easy fix for this?

I'm running the patch at 48kHz.

click_test.pd

Thanks for any help!

yep, there's several ways to do it, but you can start by putting a message box in front of both you line~ objects with the message $1 5

[tabread mutes]
|
[$1 5 (
|
[line~ ]

this should make the volume ramp up or down over five milliseconds when it changes. the line~ object will change to the new value over the time specified by the second number in the list at the left inlet.

the clicks you're getting now happen when the osc~ output is far from 0 at the block boundaries. the line~ objects change their output abruptly at the block boundaries and the sound of the sine wave going from some value to 0 immediately sounds like a click transient. with a 5ms time value, the line~ will instead wait for a block boundary, and then begin changing to the new value over 5ms.

thanks, that makes sense! this helps a ton.

@LarsXI, I don't understand how this works. The help file for line says it takes a pair of numbers and ramps from one to the other.

But you're passing it a pair of numbers, and it changes from the current value (which the help file alleges it discards when done) to the first parameter, while using the second parameter as a duration, not a target value. How can this be?

@Faranta When you trigger it with a new pair it slides to the new value in a given time and stays there until you send it another pair. So if it is at 0 and you send in [1 1000( it will "go to" 1 in 1000msecs. Then send it [0.5 2000( and it will slide from 1 (last value) to 0.5 in 2 seconds.
line-demo~.pd

[vline~] does the same thing but......... it can be a better option as it "travels" across block boundaries.... it interpolates and can start and stop with sub-sample accuracy.
See doc/3.audio.examples/C04.control.to.signal.pd (the Pd/doc folder in your installation) for an audible demonstration of the difference.