MuseScore distroys the MIDI-interface that VirtualMidiSynth has created.
About MuseScore running on Windows PC:
After last update of VirtualMidiSynth 2.1 from Coolsoft, working with MuseScore has been very annoying. I use to make the note sheet with MuseScore, then save as MusicXML. Then play it - maybe change it again with MuseScore, save and play the MusicXML-file. Somehow MuseScores make the MIDI-interface crash. Until the new version of VirtualMidiSynth this was no problem - starting playing VirtualMidiSynth did a reset on the interface. But this has changed, VirtualMidiSynth does not stop and must be terminated (forced) by the taskmanager. Again and again and ...
Who is to blame? I think it is MuseScore, that somehow takes over the interface and does not restore it. The error message that comes from VirtualMidiSynth is: "Error Opening MIDI-stream. Error Code: 4. BASS_ERROR_BUFLOST: The sample buffer was lost. This happens with my player (MidiAndMusicXmlPlayer) and with Windows Mediaplayer.
Note: Finale does not have this behaviour.
Can this be fixed?
Kind regards
Mogens Lundholm
Comments
Here is what appears to be a problem between Music XML Player and Virtual MIDI Synth.
The problem may be the result of MuseScore's MusicXML output, or the way the Music XML Player interprets it.
That's because bug is outside of MuseScore, so you should look for the problem mostly in software that uses (exported) MusicXML. (If there is no serious error in MusicXML)
If you attach the file that creates the problem here, it is easier to examine and decide.
In reply to Here is what appears to be a… by Ziya Mete Demircan
No no no. Note that Windows Media player behaves the same way. Note that Finale does not crash VirtualMidiSynth. The fact is that VirtualMidiSynth crashes exactly when MuseScore starts. The MusicXml-output from MuseScore is OK and it is necessary to restart VirtualMidiSynth by opening taskmanager and stop it. The problem is that MuseScore and VirtualMidiSynth do not live peacefully together. The worst situation for us users: both parts claims the the other part is responsible. Have already contacted Coolsoft - they think MuseScore is the problem.
I will make a recipe and send a test file.
In reply to No no no. Note that Windows… by Mogens Lundholm
I always keep both MuseScore and Virtual MIDI Synth open.
Most of the time I work in both software. (MuseScore and Sekaiju -> VMS)
Even if I used the same SoundFont for both, I didn't see a problem.
In reply to No no no. Note that Windows… by Mogens Lundholm
To get the error:
My system is Windows 8.1
Hope you can reproduce it.
/Mogens
In reply to To get the error:… by Mogens Lundholm
I followed the same steps.
No problem here.
Both work and play at the same time.
(Win7)
In reply to I followed the same steps… by Ziya Mete Demircan
Strange - and you started MuseScore while playing? And uses VirtualMidiSynth 2.1? And it was definitely the Oud voice?
I will install both on a Windows 10 machine and see what happens. Wonder if settings could affect the behaviour: The I/O-tab in MuseScore says PortAudio and MME.
In reply to Strange - and you started… by Mogens Lundholm
It works on the WIN10 machine!
Thanks for testing.
PS: Hopefully users of my program do not have the problem. I can do as you do - open MuseScore from the beginning and keep it open.
In reply to Strange - and you started… by Mogens Lundholm
Yes.
I arranged everything in VMS just like yours. (The version of VMS that I have doesn't have a shared connection. Default Sekaiju on VMS#1, MediaPlayer on VMS#3) ver:2.0.1
I have installed oud.sf (you can see it in the picture)
I turned on Musescore and load "oud.sf" to it and set it as default, I turned it off.
First I turned on the media player and play CDEFGAB.mid with loop.
Then I opened Musescore and play CDEFGAB.mscz with loop.
In reply to I followed the same steps… by Ziya Mete Demircan
It works on the WIN10 machine!
Thanks for testing.
PS: Hopefully users of my program do not have the problem. I can do as you do - open MuseScore from the beginning and keep it open.
In reply to No no no. Note that Windows… by Mogens Lundholm
,
In reply to "Note that Windows Media… by underquark
I mean: Windows media player stops playing (no sound but progressbar still moves) when MuseScore starts and an error message comes. The error message must come from VirtualMidiSynth.
I have the same problem, with Audacity and the other MIDI players I use. But it only occurs when I unplug output audio devices that are assigned as default output audio devices.
If VirtualMIDISynth driver 2.2.1 has Output audio device set to Default device and
Default Output Audio Device is removed and changes to another device, the following error occurs when trying to stream MIDI.
Error Code: 4. BASS_ERROR_BUFLOST
The quick manual fix is to go to the options menu in VirtualMIDISynth driver 2.2.1, and change Output audio device to a specific device and press apply button. Then again change output audio device back to default device and press apply button. This will trigger the VirtualMIDISynth driver 2.2.1 to update default device to the current existing default device.
In reply to I have the same problem,… by Carl Lochen
This problem is related to VMS.
Version 2.3.0 is released.
Please test it.
http://coolsoft.altervista.org/en/virtualmidisynth#download
In reply to This problem is related to… by Ziya Mete Demircan
Thanks, already did, and it works like a charm.
https://coolsoft.altervista.org/en/forum/thread/588
In reply to Thanks, already did, and it… by Carl Lochen
Not on my computer(Win8). Backed once again to VirtualMidiSynth 1.15.2.
In reply to Not on my computer(Win8). … by Mogens Lundholm
Thanks for that info. I myself use the latest version of Windows 10. You should notify Coolsoft in the thread link I provided.
https://coolsoft.altervista.org/en/forum/thread/588