It would seem some users have had issues mapping Play/Pause... try today's 4.0.8 update and see if the problem persists.
I'm midimapping Rekordbox(v4.0.7) to Lemur(v5.3.2). I'm sending a midi CC message, range 0 to 127, from a Lemur custom button in "pad" mode. Immediately after mapping PlayPause (Deck 1), deck 1 will begin to stutter playing. It sounds like a stuttering pattern, one-second long, consisting of "play-stop, play-stop, play-stop, stop" and then repeats over and over again until the song ends. I try to press the Play/Pause button on deck 1 with my mouse, to try to stop or interrupt the stuttering. This allows the song to play (if I'm lucky) but the stuttering starts again if I try to pause the song. The only way to stop the song completely is to either let the song reach the end or delete the midimapping to PlayPause deck 1.
I've tried inverting the CC range from 127 to 0, to no avail.
I've tried using Lemur's custom button in "switch" mode, to no avail.
*AS I'M WRITING THIS* I'm tinkering around with settings and have found a solution that works (or at least I hope it continues to work) which is this...
I had PlayPause mapped as follows "Function-PlayPause, Deck-1, MIDI IN-B023, Type-Button, MIDI OUT-B023,". I now have the MIDI OUT mapped to nothing, which is to say PlayPause is now mapped as follows "Function-PlayPause, Deck-1, MIDI IN-B023, Type-Button, MIDI OUT- ".
I assume this means I had a MIDI feedback problem. All my other MIDI mappings have their MIDI OUT mapped to their same MIDI INs and I haven't had a problem with them. So now I don't know if it's just improper MIDI routing that I had or if it really was a Rekordbox problem. In either case, I'm posting this in case anyone else has a similar problem. I know there were other problems regarding midimapping PlayPause, so perhaps this can shed some light on those.
I would appreciate a response from a Pioneer tech, so I can find out If I was doing something wrong or not.
Post ist für Kommentare geschlossen.
It would seem some users have had issues mapping Play/Pause... try today's 4.0.8 update and see if the problem persists.