I have tried using Max MSP, but I can’t receive any MIDI information when using virtual MIDI ports and the ‘Both’ option in Liberation’s MIDI section
have you set the correct midi port in the MIDI send/receive panel?
This is a pretty tried and tested system so if you’re not getting data it’s likely to be a configuration issue.
Cheers!
Seb
Hey Alem,
Thanks for the screenshots - looks like you’re almost there.
A few thoughts:
- MIDI ports are lighting up green - that suggests the connection is working and MIDI messages are being received or sent by Liberation.
- You’re using MaxMSP to test - while that can work, it can be a bit opaque if you’re not already familiar with Max. If you want to double-check things more easily, I’d recommend using a DAW like Ableton Live or Logic, or even a simpler MIDI monitor app (like MIDI Monitor for macOS). That’ll make it much easier to confirm if messages are being sent and received properly.
- You’re using the ‘BOTH’ option - just a heads up that using BOTH can cause a feedback loop if your MIDI input and output are the same virtual port (like IAC). That can easily flood Liberation with messages and crash it. Best to test SEND and RECEIVE modes separately until you’re confident in the setup.
- Assuming you’re using IAC Bus in macOS - make sure it’s enabled in Audio MIDI Setup, and that both Liberation and Max are using the correct IAC port.
Let me know how you get on if you try with a DAW or MIDI monitor instead - that should help rule out whether it’s a Liberation config issue or something in the Max patch.
Cheers,
Seb
I usually work with Max/MSP and Resolume. Ableton has Max for Live and runs smoothly.
Using ‘midiin’ with a ‘print’ object works as a MIDI monitor.
Honestly, because I don’t use MaxMSP, I’ve got no idea why it’s not working in your setup - but if the MIDI ports in Liberation are lighting up green, that usually means the connection itself is fine.
At this point, I’d probably try testing with a MIDI monitor app or a DAW just to confirm MIDI is going out from Liberation correctly. If that works, then it’s almost certainly something in Max’s config or routing that’s blocking it.
Let me know what you find!
cheers
Seb
Update: If I create 2 different MIDI ports, it works in both directions. But now the problem is that when I play one clip, it sends one message to activate it. However, when I change the clip, it sends two messages: one to deactivate the previous clip and another to activate the current one. This behavior is not possible to handle with TouchOSC.
**Update 2: After a few minutes, it stops working.
That’s why I bought an APC40 
This is normal behaviour. The system sends a note on when the clip starts and a note off message when it stops.
