What is the best approach here? This seems way to uncesserarily complicated to me.
#Groove agent cubase pro
This is the default path for Cubase Pro (or Artist) 8. Download and unzip this file: GrooveAgentONEWin.zip Move the files Groove Agent ONE.vst3 and Groove Agent ONE.bin from the 32-bit and/or 64-bit folder to the corresponding Cubase folder on your system. I would rather tell the MPC Live to remap itself to the way Cubase/Groove Agent is configured (e.g. This is where the file Groove Agent ONE.vst3 needs to be placed. I could off course go through all the PADS in Groove Agent and MIDI-CC learn them to the pads of the MPC, but I am not sure this is the best approach. Groove Agent has a feature called "Use Hardware Controller Mapping", with the Options "Default", "E-Drum Controller 1" and "Yamaha DTX-900", but none of them work. It should start with C1 on the bottom Pad and then go up. The Pad 1 (A1) is assigned to C-2 and PAD 13 (A13) is assigned to C-1. Triggering a pad on the bottom rows, triggers the top row and vice versa. The version of the program you are about to download is 4.2.0. The download is provided as is, with no modifications or changes made on our side.
the TOP and BOTTOM rows of the MPC pad layout is reversed. Each download we provide is subject to periodical scanning, but we strongly recommend you check the package for viruses on your side before running the installation. With PAD perform mode OFF in the MPC, it sends C1 when pressing the A1 pad instead of sending C2. The problem I am facing now is that Cubase/Groove Agent uses a different pad layout than the MPC. I have connected the MPC Live 2 via Midi to my Audio Interface, and when I create a project with a Midi Track/Program on the MPC and configure the Channel accordingly, it does send out MIDI events when I press the pads. This turned out much more troublesome than expected. I know the MPC Live is primarily seen as a standalone device, however I also want to be able to integrate it with my DAW setup.
0 kommentar(er)
