Unwanted artefacts in sound

[dkmayer]

@Maed

Does anyone know how to avoid these?

You cannot avoid this with language-triggered sequencing in realtime. I’ve described the reason here:

Imperfection of language-based timing

This goes back to an observation of my colleague Gerhard Eckel. I posted this a while ago on the mailing list, but can’t find it anymore in the archives. As I think it’s an interesting topic I’m reposting it here again for future reference. Timing in general is a crucial topic and practically users are mainly confronted with asynchronicity between server and language, latency, quantization, the Out/OffsetOut differences etc. Sample-accurate timing isn’t relevant in all contexts, nevertheless in…

It can also be observed with Pbind writing:

(
{ Out.kr(~vbus1, MouseX.kr(0.000001, 0.2, 1))}.play;

Pbind(
	\instrument, \Sine2,
	\freq, 400,
	\sustain, 0.1,
	\width, ~vbus1.asMap,
	\amp, 0.3,
	\dur, 0.01
).play;
)

Only options: do it in NRT or server-side. It should be noted also that this unavoidable inaccuracy only plays a role with smooth regular sound material. For many if not most granulation applications it doesn’t play a role in perception.