From a report in this
post in
this thread.
Reaper 6.04rc2 and before, Windows 10 x64. Verified with a Presonus Faderport 16 in Studio One mode(via CSI) and the MCU+MCUXT drivers that come with Reaper on both a fully customized Reaper and a fresh portable install. I've asked for further verification from other motor fader users.
Problem
Reaper records wonky volume automation (-edit-) if there is volume automation playing back within the block of tracks covered by a control surface.
IF there is volume automation that is being played back and sent back to the control surface for moving the fader, the newly recorded volume automation on another track that overlaps timewise with previous recordings will be rubbish.
For example, if there's automation on track 6 , your control surface is showing you tracks 1-8, and you record volume automation on track 1,2,3,4,5 or 7 and 8, while the automation on track 6 is in Read,Latch, Latch Preview or Touch mode, and thus a fader on the control surface representing track 6 is moving as a result, the newly recorded volume automation will look as it does in the screenshot(check the session link for an immediate result as well).
If however the control surface is displaying tracks 9-16 for example, and none of the tracks have volume automation on it that could move a fader, and you're recording volume automation on any of the tracks 9-16, it'll record like it does in the upper track in the screenshot.
Also, this 'rectifier'/'shit-quantizer' effect only applies to those parts of your volume automation recordings that time-wise overlap with existing recordings on tracks that fall within the display range of your control surface.
I hope that's clear enough.
Reproduce- Create twice the number of tracks your control surface(with moving touch sensitive faders) has.
- Record some volume automation on one of the tracks.
- Record some volume automation on one of the tracks that falls in to the block of tracks being displayed by your control surface within the same time range of your first volume automation recording. You should get ugly stuff as shown in the screenshot on the second track.
- Since this only applies to recorded volume automation that overlaps time-wise with other recorded volume automation that is displayed by a control surface, record some volume automation on another track within the same block of tracks being displayed by your control surface, before, during and after recorded volume automation on another track in the same block.
A second shot to demonstrate that effect for good measure
Session with some zero-audio and the automation tracks (16 kB)