I’m having an Ablenet problem with this beta and 2.7.4.
With an M1 MBP connected to a Win10 pc via an Ethernet cable, the Mac shows 2 hosts connected and the PC shows 1 host connected. Jumping around the setlist on the Mac moves the PC, but jumping around the setlist on the PC does not control the Mac.
Both are running Live 11.
The computers can ping each other.
Both computers have WiFi turned off.
This sounds a bit like the PC isn’t able to automatically detect your Mac on the network. If you’re using AbleSet’s automatic configuration, could you check if manually entering the IP address of your Mac in AbleNet’s settings fixes the issue?
If it doesn’t, maybe there’s a firewall on your Mac that disallows incoming connections, or one on your PC that disallows outgoing connections?
Either way, could you send me log packages from both computers so I can take a closer look?
I don’t have an Oakboard Mini 2 to test this on my end, unfortunately, but does AbleSet work with other MIDI controllers on your machine? What do the MIDI mapping settings look like on your end?
The settings are as standard and still have issue if I change the mappings to the direct actions instead of OSC. If there were a way to disable the automatic-grab of the Oakboard, that would be a simple solution so that I could just map directly to the AbleSet M4L device, but a fix would be nice.
Can do more extensive testing for you—I have a MIDI Monitor app that could get more detailed information from the Oakboard Mini 2 if needed.
That all looks correct to me. Does it make a difference if you start AbleSet before Ableton Live? You could also check if the Oakboard Mini 2 is completely disabled in Live. As far as I know, if you’re on Windows, MIDI devices can only be used by one application at a time.
If this doesn’t help, could you send me a log package so I can take a closer look? You can create one by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package”.
