Hi, I appreciate you need photos and videos for a lot of the questions but this is a really simple one. When I turn SeeMusic on it grabs all the midi controllers I have in Abelton and various other programmes and stops them working with anything else but SeeMusic I then have to restart the whole computer to solve this and when I start SeeMusic again it once again stops me being able to use my midi on any other programme. It's a really difficult situation as I require to use SeeMusic and other applications at the same time. It happens on my Mac and My Windows 10 PC. I don't think it's related to the device I use as it happens with everything.
top of page
To test this feature, visit your live site.
essexmusicman
Nov 12, 2021
How to stop SeeMusic taking all your midi devices?
How to stop SeeMusic taking all your midi devices?
2 answers2 replies
Like
Comments (4)
bottom of page
- In Version 4.3.6, released yesterday - I removed the MIDIJack framework, which may possibility eliminate some of the MIDI "port hogging" that was happening. Please give the new version a try and let me know if it helped at all?
As a note - I tried to replicate the issue on Windows - I did experience the issue if I opened up Ableton when SeeMusic was currently connected to the keyboard. However, if I quit SeeMusic, and then reopened Ableton, Ableton then saw the MIDI keyboard again. I didn't need to restart.... also, Ableton retained the connection to the MIDI keyboard if it was connected to the keyboard before opening SeeMusic.
I'm not saying that you aren't experiencing problematic difficulties on your computer - just that in my testing, it was possible to retain the connection to the keyboard in Ableton when opening SeeMusic, as long as the keyboard was connected in Ableton first.
There is generally a limited amount I can help more - the MIDI framework I use is developed by a third party, and I don't have control over the code, unfortunately.
Understood - thank you for reporting this issue. I wasn't fully aware of it previously.
Let me take a look and get back to you.
I believe this is caused by the MIDIJack plugin which I've used in the past as a backup framework option on desktop platforms. However, I recently updated the core MIDI framework and it should be stable now. I should be able to remove the MIDIJack plugin, which should likely fix this issue.
I'll reply with an update as soon as there is one.
Thank you!