Launcpad Pro not connecting, manual selection of Launchpad Pro Mk2 profile does nothing either

[FakenameMusic]

Hi there,
I bought a Lauchpad Pro to use with Playtime 2 but it does not auto-connect.
I tried manually loading the supplied Launchpad Pro Profile through the main Playtime 2 UI "Controller" page, selecting the relevant "Main Profile" and the MIDI IN/OUT for the device, but this does nothing either.

The device works fine with Ableton and Reaper has no problem seeing / using it as a MIDI device.

Has anyone had a similar issue and may have advice?
Thanks

[helgoboss]

Video for setting up the Launchpad Pro: https://www.youtube.com/watch?v=tkyNCGOVumw

Automatic setup also takes care of configuring your REAPER MIDI device preferences correctly. For automatic setup to work, remove your manually created controller first. Also, if you have tried to select the Launchpad Pro in ReaLearn as input or output, undo that (must not be used there, otherwise it's considered an override and won't work).

Maybe you plugged it in before Playtime was running? In that case, Playtime won't bother to pick it up.

[FakenameMusic]

OK, good news, some progress at least:

The first time I went through the same sequence of adding the controller as you suggested before and it didn't work.
helgobox1.log

The second time I deleted the 3 Launchpad related midi inputs and the output from Reaper's MIDI IN/OUT config pages so that Reaper was starting from a blank slate of not knowing the device at all- and it worked! So perhaps the problem is not the name, but related to Reaper's way of handshaking the device when it's first connected, and how that is interacting with the autodetect in Playtime 2? In short: once I made Reaper think I was connecting the device for the first time, the auto detect in Playtime worked.
helgobox - deleted device.log

Hopefully that will be of help to you.

[helgoboss]

Thanks for checking. The logs still don't contain anything useful, really weird.

But now it would be interesting to check: What's the exact name of the Launchpad Pro in the list of REAPER output devices? Maybe the "2-" prefix is gone?

[FakenameMusic]

Sorry I should have made it more explicit: the "2-" is still in the name.
I tried changing the Device Alias in the MIDI setup page, but that made no difference.
The only thing that made the difference was to remove the device entirely from Reaper's MIDI I/O setup pages.
That's what I meant when I was suggesting that the problem was not the name.

[helgoboss]

Oh man, this info brings us back to zero. Now I have no idea what it could be.

[helgoboss]

@FakenameMusic Could I ask you for another test?

I had a look in the code and there is really absolutely no way this could have worked if the output device name is not exactly "Launchpad Pro". My assumption is that you left the controller in the list before trying it again? Or that the output device name changed to exactly "Launchpad Pro"?

If you don't mind, could you try the following? I tried to make the instructions a bit more accurate.

1. Disconnect your Launchpad
2. Remove your Launchpad from the controller list within Playtime (make sure it's not there anymore).
3. Make REAPER forget all Launchpads within the MIDI input and output device preferences
4. Close any project that you have open (we want REAPER to show a completely empty project on the next start)
5. Quit REAPER
6. Open the Windows command line app
7. Enter the following commands (this should start REAPER while logging to a file):

   set HELGOBOX_LOG=debug
   "PATH_TO_YOUR_REAPER\REAPER.exe" > "%USERPROFILE%\Downloads\helgobox.log"
   

8. Start Playtime within REAPER (using the button)
9. Go to Settings => Controllers
10. Connect your Launchpad again and wait at least 20 seconds (does Playtime auto-add a controller when you do this?)
11. Delete the track containing Playtime
12. Quit REAPER
13. Reply within this issue, attaching the file "helgobox.log" in your Downloads directory (alternatively, you can also send it to [email protected])

Thanks!

[FakenameMusic]

OK, interesting! I'm not at home at the moment, but as soon as I get back I'll do this and make a screen cap of me doing this. It's quite possible that yesterday, one of the times I forced reaper to forget the controller that I missed one of the inputs or the output. I'll get back to you a little later. 🙌

…

On Thu 29 Aug 2024, 09:27 Benjamin Klum, ***@***.***> wrote: @FakenameMusic <https://github.com/FakenameMusic> Could I ask you for another test? I had a look in the code and there is really *absolutely no way* this could have worked if the *output* device name is not exactly "Launchpad Pro". My assumption is that you left the controller in the list before trying it again? Or that the *output* device name changed to exactly "Launchpad Pro"? Interesting, picking the controller preset manually should actually not be necessary as it typically picks this automatically. That's why it's in the advanced settings. But maybe this didn't work since the rest of the automatic detection also didn't work. If you don't mind, could you try the following? I tried to make the instructions a bit more accurate. 1. Disconnect your Launchpad 2. Remove your Launchpad from the controller list within Playtime (make sure it's not there anymore). 3. Make REAPER forget all Launchpads within the MIDI input *and output* device preferences 4. Close any project that you have open (we want REAPER to show a completely empty project on the next start) 5. Quit REAPER 6. Open the Windows command line app 7. Enter the following commands (this should start REAPER while logging to a file): set HELGOBOX_LOG=debug "PATH_TO_YOUR_REAPER\REAPER.exe" > "%USERPROFILE%\Downloads\helgobox.log" 8. Start Playtime within REAPER (using the button) 9. Go to Settings => Controllers 10. Connect your Launchpad again and wait at least 20 seconds (does Playtime auto-add a controller when you do this?) 11. Delete the track containing Playtime 12. Quit REAPER 13. Reply within this issue, attaching the file "helgobox.log" in your Downloads directory (alternatively, you can also send it to ***@***.***) Thanks! — Reply to this email directly, view it on GitHub <#1140 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKU6V3FNPMMB3FFSPDCWRQTZT3LORAVCNFSM6AAAAABNIBJHZ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANBYGQYTONA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[FakenameMusic]

OK, so long story short: auto detection didn't work until I changed the device name to take out the "2-". Once I took out the "2-" it worked.

Here is a video of the first time I tried (that it didn't work) and also the log generated:
I'm sure all you want is the log, but the video will at least perhaps let you see if I did something stupid.
They are still uploading / processing with Youtube as I type this, so if they are not visible now, or look very low quality, wait a while til YouTube does it's processing on it's end and then look again.

helgobox-29-08 A.log
and the video:
https://youtu.be/xxxxcccccccccc

Here's the second time where the rename worked and auto connection worked:
helgobox 29-08 B.log
https://youtu.be/ccccccccccccccvc

[helgoboss]

Thanks! That's good news. Will fix this in #1143.