Feature request: 200 ms fades for playback, Mackie protocol

WaveLab
1

Is there a way to give customer feedback ? I installed WaveLab for the first time and I miss:

  • Mackie protocol for transport control with my PreSonus Faderport
  • Fades when starting/stopping playback need to be longer (not only click protection)

The first one is clear I guess. And I will not configure my Faderport to non-mackie, because Bitwig and LUNA can handle Mackie well.

The second one: With cheap headphones the current way is not a problem (only click detection). But when I wear good planar headphones via a headphone amp, the sound is instantly super loud and I jump and stop/play A LOT in my sessions, maybe every 3 seconds sometimes when I scan through a master. Then I need a little bit of fade in and out, maybe not more than 100 or 200 ms.

(Also workarounds are welcome to know, thank you. Esp. for the fade topic. Thank you.)

2

The length of a fade is the size of the ASIO block size.
I usually recommend 512 at a minimum, but this is much less than 100 milliseconds.
But you could try 2048.

3

Awesome workaround, I will give it a try, maybe it’s already sufficient to tame at least the first transient. Thank you.

4

I gave you false hope. I verified the code, and the fade length is actually the minimum between the ASIO block length and 10 milliseconds.

5

Thank you, Philippe.

Colored tick marks in the master meter at 0, 6 and 12 dB would also be helpful for my particular case, by the way, so my eyes can do a sanity check in an instant. (I think bx_meter colors -6 and -12 as a visual example of what I mean).

It’s great having everything important showing up immediately. I should have switched earlier to WaveLab.

6

Good idea