asked Oct 22 '15 at 09:08 by dharit (81)

Similar to this question. I bounced out an audio track, and I want to do manual fades at the beginning of each transient (say for manual ducking, ie. emulate side-chain compression). I can achieve this by drawing envelopes with the gain expression in the detail editor, but this would mean I would have to write out envelopes by hand for every single transient (lots of work). If I use volume automation, I can copy/paste the automation envelopes I draw out. However, I'm noticing that if I have a volume automation that quickly drops to -infinity, I will get a popping sound. I've tried: - Smoothing the fades out with curves, but I haven't been able to get this to work without pops. I can't get the curve to be wide enough to avoid pops before reaching the limit where the volume duck becomes audibly obvious. - Splitting the audio event and turning on fade-ins and fade-outs for the resulting events. - Splitting the audio event and leaving a gap in between the two events. (This sounds even worse).

If anyone has any advice would love to hear it. In Ableton, I've been able to find an analogous situation using the fades--this is similar to the gain expression in Bitwig in that I can't copy/paste fades and would have to write them all out manually. Using the volume automation and copy/paste-ing the automation envelopes seems to work without pops.

Running Bitwig 10.3 on OSX 10.9.5.

I can confirm this. Did you send a bug report to bitwig?

  — (Oct 23 '15 at 17:04) Solidtrax

I asked Dom and he answered with this:

The automations are actually fine, the only downside currently is that they're buffer accurate and not sample accurate. This means that the timing of automation jitters within the length of one audio buffer, as set up in the preferences. To avoid the pop, just move the automation a tiny bit in front of the event - just a workaround for not as this will change in the future as the automation timing will also be made sample accurate, as with notes and audio events. --

Hope this helps and furthermore we have to be a little patient. ;-)


answered Oct 30 '15 at 12:04 by Solidtrax (1.0k)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Oct 22 '15 at 09:08

Seen: 2,183 times

Last updated: Oct 30 '15 at 12:04