Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playtime doesn't auto-detect Novation Launchpad Pro with family ID "00 FF" #939

Closed
ndbroadbent opened this issue Jul 22, 2024 · 11 comments
Closed
Labels
bug Something isn't working playtime Related to Playtime realearn Related to ReaLearn
Milestone

Comments

@ndbroadbent
Copy link

ndbroadbent commented Jul 22, 2024

Hello! I've bought a license for Playtime 2 and I would love to use my Novation Launchpad Pro MK2 to control it. I'm struggling to figure out how to get it working.

The ReaLearn => Controllers page is blank in the settings:

Screenshot 2024-07-22 at 4 52 06 PM

I found the "Launchpad Pro mk2 - Live mode" controller preset in the Helgobox / ReaLearn plugin settings, but this doesn't seem to do anything:

Screenshot 2024-07-22 at 4 54 17 PM

Is there a way to get the buttons and LED lights on my Launchpad Pro MK2 in sync with Playtime 2? Thanks!

Is my controller supposed to show up automatically in the ReaLearn => Controllers page?

Here's a screenshot of my MIDI hardware settings in REAPER:

Screenshot 2024-07-22 at 5 03 11 PM
@helgoboss
Copy link
Owner

helgoboss commented Jul 22, 2024

Hi, this controller should be detected by Playtime 2 automatically. For this to work, you need to do this:

  1. Set input back to FX input and output to None (the auto detection is only used if you don't already use the controller explicitly in ReaLearn). On this occasion, you can also set the controller preset and main preset to None.
  2. Disconnect the controller for a few secs
  3. Connect it again (the auto detection currently only reacts to newly connected controllers)

I'm closing this now but feel free to comment to this ticket if this doesn't work for you!

That the "Controllers" panel is completely empty if no controller is set up yet, is bug #940.

@ndbroadbent
Copy link
Author

Hi @helgoboss, thanks for your help! Unfortunately these steps didn't work for me.

I've tried unplugging the USB cable for a few seconds and plugging it back in. I also tried turning it off and then turning it back on, then selecting "Live" mode.

I'm using a Apple MacBook M2 Pro. I can also confirm that the launchpad works fine normally and can be used to trigger MIDI events for Battery 4 drum kits, etc. I'm not sure if this is relevant, but I've connected the launchpad via a 4-port USB hub, and it's not directly plugged into the laptop's USB-C port.

@ndbroadbent ndbroadbent changed the title Request for help with using a Novation Launchpad Pro MK2 with Playtime 2 Request for help with using a Novation Launchpad Pro with Playtime 2 Jul 23, 2024
@ndbroadbent
Copy link
Author

I was taking a look at the available controller options in Ableton Live Lite, and I'm a bit confused about the "MK2" -

Screenshot 2024-07-23 at 12 39 53 PM

I think I might just have a "Launchpad Pro" (not a "Launchpad MK2"). Thanks!

@helgoboss
Copy link
Owner

helgoboss commented Jul 23, 2024

I think you have the correct Launchpad, I might have named it wrong (as there is no Launchpad Pro Mk1).

Okay, now we need to do some analysis. Could you please do the following:

  1. Quit REAPER
  2. Disconnect your Launchpad
  3. Open the macOS Terminal app
  4. Enter the following command line: HELGOBOX_LOG=debug /Applications/REAPER.app/Contents/MacOS/REAPER > $HOME/Downloads/helgobox.log (this should start REAPER)
  5. Start Playtime within REAPER
  6. Connect your Launchpad and wait a few seconds
  7. Quit REAPER
  8. Reply within this issue, attaching the file "helgobox.log" in your Downloads directory (alternatively, you can also send it to [email protected])

Thanks!

@helgoboss helgoboss reopened this Jul 23, 2024
@ndbroadbent
Copy link
Author

Thanks for the instructions! Here's the log file:

helgobox.log

I think I might have found the relevant lines:


  �[2m2024-07-23T13:00:10.860161Z�[0m �[32m INFO�[0m �[1;32mhelgobox::infrastructure::plugin::backbone_shell�[0m�[32m: �[1;32mmsg�[0m�[32m: "Input not yet used. Finding matching controller preset...", �[1;32mout_port_name�[0m�[32m: Focusrite A.E. Ltd - Launchpad Pro 16 - Live Port�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2665

  �[2m2024-07-23T13:00:10.860171Z�[0m �[33m WARN�[0m �[1;33mhelgobox::infrastructure::plugin::backbone_shell�[0m�[33m: �[1;33mmsg�[0m�[33m: "Couldn't automatically create controller for device", �[1;33mout_dev_id�[0m�[33m: 7, �[1;33merror�[0m�[33m: no controller preset matching device�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2977

@helgoboss
Copy link
Owner

Thanks. It looks the "identity reply" of your device (as a response to ReaLearn's MIDI device inquiry) is a bit different from my Launchpad Pro:

F0 7E 00 06 02 00 20 29 51 00 0F 00 00 01 05 04 F7 // reply from your device
F0 7E 00 06 02 00 20 29 51 00 00 00 * F7 // expected pattern

The difference is in the device family member code, indicating that your device might be a different one. The Launchpad Pro Programmers Reference Guide page 19 has "00 00" as family code, not "0F 00". I'm referring to this product: https://downloads.novationmusic.com/novation/launchpad-mk2/launchpad-pro

Novation also has this pretty cool web-based tool Components https://novationmusic.com/components, it should show the name of your device when it's connected. Could you try that?

@ndbroadbent
Copy link
Author

Hi @helgoboss, ah it looks like I have an older Launchpad Pro (MK1) that is not supported by the Components tool.

SCR-20240724-kkcq

I also downloaded the updater tool and updated the firmware from 154 to 182:

image

I ran the instructions above again with the updated firmware (182), and have attached the new log file: helgobox.log

@ndbroadbent
Copy link
Author

ndbroadbent commented Jul 23, 2024

I tried plugging the launchpad pro directly into my laptop (instead of via a USB hub), but that didn't change the identity reply:


  �[2m2024-07-23T23:36:15.468110Z�[0m �[34mDEBUG�[0m �[1;34mhelgobox::domain::audio_hook�[0m�[34m: �[1;34mmsg�[0m�[34m: "Sending MIDI device inquiry...", �[1;34moutput_dev_id�[0m�[34m: MidiOutputDeviceId(7)�[0m
    �[2;3mat�[0m main/src/domain/audio_hook.rs:440

  �[2m2024-07-23T23:36:15.479719Z�[0m �[34mDEBUG�[0m �[1;34mhelgobox::domain::audio_hook�[0m�[34m: �[1;34mmsg�[0m�[34m: "Received MIDI device identity reply", �[1;34mreply�[0m�[34m: RequestMidiDeviceIdentityReply { input_device_id: MidiInputDeviceId(8), device_inquiry_reply: MidiDeviceInquiryReply { message: [240, 126, 0, 6, 2, 0, 32, 41, 81, 0, 15, 0, 0, 1, 8, 2, 247] } }�[0m
    �[2;3mat�[0m main/src/domain/audio_hook.rs:620

  �[2m2024-07-23T23:36:15.487069Z�[0m �[34mDEBUG�[0m �[1;34mhelgobox::infrastructure::plugin::backbone_shell�[0m�[34m: �[1;34mmsg�[0m�[34m: "Resetting MIDI output and input devices to previous state..."�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2633

  �[2m2024-07-23T23:36:15.487487Z�[0m �[32m INFO�[0m �[1;32mhelgobox::infrastructure::plugin::backbone_shell�[0m�[32m: �[1;32mmsg�[0m�[32m: "Received identity reply from MIDI device", �[1;32mout_dev_id�[0m�[32m: 7, �[1;32min_dev_id�[0m�[32m: 8, �[1;32mreply�[0m�[32m: F0 7E 00 06 02 00 20 29 51 00 0F 00 00 01 08 02 F7�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2640

  �[2m2024-07-23T23:36:15.487515Z�[0m �[34mDEBUG�[0m �[1;34mhelgobox::infrastructure::plugin::backbone_shell�[0m�[34m: �[1;34mmsg�[0m�[34m: "Check if input used already used by existing controller..."�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2647

  �[2m2024-07-23T23:36:15.487522Z�[0m �[32m INFO�[0m �[1;32mhelgobox::infrastructure::plugin::backbone_shell�[0m�[32m: �[1;32mmsg�[0m�[32m: "Input not yet used. Finding matching controller preset...", �[1;32mout_port_name�[0m�[32m: Focusrite A.E. Ltd - Launchpad Pro 16 - Live Port�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2665

  �[2m2024-07-23T23:36:15.487531Z�[0m �[33m WARN�[0m �[1;33mhelgobox::infrastructure::plugin::backbone_shell�[0m�[33m: �[1;33mmsg�[0m�[33m: "Couldn't automatically create controller for device", �[1;33mout_dev_id�[0m�[33m: 7, �[1;33merror�[0m�[33m: no controller preset matching device�[0m
    �[2;3mat�[0m main/src/infrastructure/plugin/backbone_shell.rs:2977

I'm in New Zealand, so maybe they use "00 0F" for devices sold in Australia / NZ? Not sure what else might be different about my model.

@ndbroadbent ndbroadbent changed the title Request for help with using a Novation Launchpad Pro with Playtime 2 Request for help with using a Novation Launchpad Pro (MK1) with Playtime 2 Jul 23, 2024
@helgoboss
Copy link
Owner

I just tried my own Launchpad Pro with Components and it gives the same screen as you and is named "Launchpad Pro [MK1]". A bit confusing because the first Launchpad Pro is listed under the "Launchpad MK2" category on the Novation website: https://downloads.novationmusic.com/novation/launchpad-mk2

Mysterious how the family ID is different. However, the devices look the same, have the same name, so I guess my official preset would work with your device. Could you try this in your Playtime project (it's the most manual way to use the presets):

  1. Open the plug-in
  2. Set both input and output to the Launchpad Pro Live Port
  3. Go to the controller compartment and choose preset "Launchpad Pro mk2 - Live mode"
  4. Go to the main compartment and choose preset "Launchpad Pro mk2 - Playtime"

That should make things work for this particular project. If you confirm it works, I will adjust the MIDI identity pattern for the next version so that it covers your family ID as well. Then it should be auto-detected in the next version.

@ndbroadbent
Copy link
Author

Awesome, it's working perfectly now! Thanks very much!

@helgoboss
Copy link
Owner

Okay, then I will relax the detection so that your device is included automatically in the future.

@helgoboss helgoboss added realearn Related to ReaLearn playtime Related to Playtime bug Something isn't working and removed realearn Related to ReaLearn labels Jul 25, 2024
@helgoboss helgoboss changed the title Request for help with using a Novation Launchpad Pro (MK1) with Playtime 2 Playtime doesn't auto-detect Novation Launchpad Pro with family ID "00 FF" Jul 25, 2024
helgoboss added a commit that referenced this issue Jul 25, 2024
This makes logging into a file yield better results
(no special characters).
helgoboss added a commit that referenced this issue Jul 25, 2024
@helgoboss helgoboss moved this from Todo to In Progress in Helgobox Development Jul 25, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Helgobox Development Jul 25, 2024
@helgoboss helgoboss added this to the 2.16.1 milestone Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working playtime Related to Playtime realearn Related to ReaLearn
Projects
Archived in project
Development

No branches or pull requests

2 participants