Here below the full transcript - Hopefully this will keep Reaper users from purchasing the unit for now.It's an unfortunate situation as we I can't really tell when and if Reaper/Presonus will allow for such integration and while I adore the faderport as a hardware unit I just can't experience the same workflow I have in Reaper in Studio One - Reaper is, to me, a much more well thought daw and it sort of feels like even though the Faderport is allegedly a MUI universal controller (aka no problem with Reaper on paper) customer will be forced to eventually transition to Studio One.
Unfortunately I can't get the Faderpot to respond as it should in Reaper (latest version updated May 12th 2019) - I have reached out to Presonus a number of times and even they have given up.
#MIXBUS 32C SCROLL BY PAGE DRIVER#
Presonus claim Reaper are developing a native driver but its the first I have heard about it. Presonus won't make a dedicated Reaper MCU mode like they have Logic, Sonar and Cubase and the Logic mode with the latest firmware is actually worse thatn the 1.10 firmware and standard MCU mode they offered. I am moving my mixes to Harrison Mixbus because it supports the FP16 in native mode and is pretty much fully featured. I am not slating the project at all but there's no point recommending it to frustrated users who are not satisfied with the MCU protocol.
The unit isn't recognised in native mode with the CSI (when i tried it) and has to be run in MCU mode which has its own limitations. I managed to get the volume sliders to work but then it started behaving erratically. I mean it doesn't work properly with the Faderport and still doesn't send anything to display like track names, volume, pan information. While CSI is still in Alpha, it's not "handy" to be set up, but what do you mean by "drive the FP8/16 effectively" ?
0 kommentar(er)
