Audiotool board archive

volume automation for samples bug

Perdition · started 2019-04-24 19:19 · updated 2019-09-11 01:28

This has been a thing for a while, but pretty much if I try to automate the volume on a audiotrack low to high to have a sweep type of effect the beginning of the sample will click. Sometimes if I change the automation just a tiny bit the click goes away and it sounds find, but then it just comes right back...completely random.
here's a current draft where it happens (bar 91) https://www.audiotool.com/app/#/h51blxu9qu

Comments (7)

2019-04-24 22:31 · 2019-04-24

Whoa ... that took me a while to reproduce: https://www.audiotool.com/app/#/8pepy7euffo
It seems we have a general bug in our automation.

Sometimes automation changes seem to be ignored when there's no need for interpretation, e.g. between samples (which is fine).

As soon as the sample starts to play, the automation (internally) jumps to the right value.
Somehow some previous value will be used for the first (few?) computation steps. This can only be heard, when using a sample that starts with a click/snap!
It's really tricky to reproduce since some automation changes affect the glitch and some do not. For example: a ramp-down before the glitch only fixes the problem when a sample is played at the same time.

Maybe related: I looped around bar 91 where sample starts. Whenever the playback head jumped back I could hear the volume maxed out for a few ms. It seems the automation applies values that lie in the future or past.

An (ugly) workaround until this gets fixed: playing a sample that starts soft (or has silence* at its start) before the actual sample should remove the click. (* real silence, not a delayed start as you're using).

Thank you for reporting this. I remember some similar reports but AFAIK they couldn't be reproduced. I'll redirect them here if I find them.

Known As I · reply
2019-04-24 22:43 · 2019-04-24

I tested the suggested workaround for bar 91 and 95. Seems to work.

Known As I · reply
2019-04-24 22:53 · 2019-04-24

Thank you. This was the one I had in mind. I won't mark it as duplicate for now because you had the issue without any automation. But I believe they share the same cause.

Perdition · reply
2019-04-24 23:00 · 2019-04-24

Thank you

anonymous user
2019-08-29 09:00 · 2019-08-29

Fix available next update.