Problem With the OSC Interface
Hi MuseScore.
I am supporting Musadario, who is trying to get my MidiSightReader plugin to work (see https://musescore.org/en/node/267051).
I have recently bought a new laptop which runs Windows 10 Home (64-bit) and now the plugin does not fully work when using MuseScore 2.1.0.
The plugin starts OK, but after displaying a copyright message it should turn the first note of the score red (by using on OSC command). This often does not happen, but occasionally does. When I play the notes on my midi keyboard, they do turn green correctly on the screen.
When I run the plugin again, it should turn all the notes in the score back to black, but this is not happening.
I am using 64-bit Java version 1.8.0_144.
Previously the plugin worked on 32-bit Windows Vista.
So, my question is why is the OSC interface not fully working on Windows 10? It partially works, as the notes reliably turn green, but why do they not turn red or black reliably?
Any thoughts?
Thanks
Don.
Comments
I just noticed no one replied to this in 3 months. Do you still need help?
In reply to I just noticed no one… by ericfontainejazz
Low priority - I expect you guys are busy & I don't have much time myself either.
Someone reported a problem with my MidiSightReader plugin recently & now that I have 64-bit Windows 10, I find that the OSC bit that changes the colour of notes in MuseScore does not seem to be reliable.
The plugin uses some Java code (compiled with a 32-bit compiler) to call your OSC interface.
- Does the 32-bit Java running under 64-bit Windows cause problems?
- I tested the 32-bit Java on Ubuntu & it seemed to work fine.
Strange.
In reply to Low priority - I expect you… by DonH
Sorry for not replying. I'm trying out latest MuseScore 3.0 on windows, and I'm able to control it via OSC. The 32-bit vs 64-bit should be irrelevant, because OSC speaks at a higher level. Are you still having a problem. Can you detect the OSC events in another program?