By marguloops
Fri Aug 20, 2021 9:24 pm
YakirBT wrote:Hi everyone,
An issue with Q links (Project mode)
Firmware 2.10 MPC Live Standalone mode:
-reset preferences - done.
-opening empty project.
-assigning q links in project mode (tried several destinations)
-saving project
-shut down mpc
-turning back on and load the saved project.
-Q links missing. Forgotten.
Anyone else has encountered this issue?
Thanks in advance
*My last hope on my side is to make some free space in the internal drive. Gonna try it out and update if it helped.
Yes, I believe that I (and another user on the Reddit MPC forum) have both found this issue, but described it a little differently.
Effect parameters for plugins on Return and Submix tracks cannot be mapped. Or rather, they *can* be mapped but cannot be recalled when the project is re-opened the next time.
This applies to both Q-Links and MIDI Learn. I first discovered this problem with MIDI Learn because I have a performance template that uses MIDI mappings to both Submix and Return effects, none of which work when the project is loaded in MPC 2.10.
I then used Q-Links on the Project page hoping it would serve as a workaround and found the exact same problem: the parameter can be assigned to the knob, and works until you close the project or shut down the MPC. The next time the project is opened, they don't work.
I mention this as a problem with mapping effect parameters on Submixes and Returns because of my performance template uses MIDI Learn mappings to mixer parameters (volume, mute, etc.) on these track types and they work just fine. The other user I discussed this problem with experimented with mapping effect parameters on other track types (Drum, Keygroup) and found them to work fine and be saved properly.
This is what I know so far! Very curious to know if anyone else has discovered related issues and can help zero in on exactly what's going on here. It's a huge bummer for me that will probably drive me back to 2.9.1