Error 40201 SIBELIUS

<Back to search Results English

Avid Knowledge Base

Error 40201 Undefined external error (MMSSystem/out) when launching
Sibelius
Error 40201 or Error 40206: this error may occur in Sibelius 7 up to the latest version.

Last Updated : July 5, 2022

Products Affected : Sibelius, Sibelius First, Sibelius Ultimate

Error 40201 / 40206 MMSSYSTEM/ IN or OUT

This problem usually occurs when another audio application is trying to use the MIDI input or output device (you can tell
which by whether the error says MMSYSTEM IN or OUT). Please make sure that you are only using Sibelius while
working on a project.

Here is how to fix this issue.

1. Open Sibelius then open any score.

2. Go to Play tab.

3. Under Mixer, click the small box. (Playback Devices)

4. Click Audio Engine Options... on the lower-left corner of the window.

5. Change the interface by clicking the drop-down box and choose Primary Sounds Driver (DS).
6. Close everything and restart Sibelius.

Note: If you are using ASIO4ALL as your interface then we recommend you download Sibelius Sounds from your Avid
account to prevent getting this error message.
Attachment(s)

Related Articles
 Error 40201 Undefined external error (MMSSystem/out) when launching Sibelius
 Media Composer quits at Initializing plugin: AMPIPluginDSM.avx
 AAE error 2 During Playback in Pro Tools
 AAE error 35 was encountered
 Exception: AMPI subsystem error, ErrorMessage:Permission denied (13) when
launching Media Composer

The Sibelius Forum

Help with Sibelius - Support & Discussion of Sibelius Music Notation Software for Musicians &
Composers

Skip to content

SearchAdvanced search
  Quick links

 FAQ

 Login

 Register

 Board indexSibelius DiscussionPlayback Problems

Error 40201 MMSYSTEM/OUT

Post Reply

SearchAdvanced search

Report Post | 7 posts • Page 1 of 1

Poo2uhaha

Posts: 2
Joined: Tue Dec 26, 2017 8:45 pm

Sibelius Version: First 8

Operating System: Windows

 Quote

Post by Poo2uhaha » Tue Dec 26, 2017 8:48 pm

I was planning on purchasing sibelius first, but decided to try out the trial first.

Every time it launches, when I progress past the "continue with trial or activate" window,
the program launches with the error 40201 undefined external error.

Not only does this disable sounds from sibelius but also from all other outputs on my
system. Oddly, it disables the playing of any media such as in youtube or spotify, and
pauses anything already playing. Very curious.

Any solutions to this error would be helpful. I would also like to know where to install the
sibelius first 8 sounds instead of just having the basic midi configuration, once the former
issue is resolved.
Top
 andyg

Posts: 1718
Joined: Tue Feb 14, 2006 8:55 pm

Sibelius Version: 7.1.3 and 6.2

Operating System: Windows

 Quote

Post by andyg » Tue Dec 26, 2017 11:17 pm

IIRC, this is what happens when you use General MIDI sounds with an ASIO audio engine.
Check the Audio Engine settings in Sibelius and make sure it uses something else like DS
sound.

Many apps will take control of the audio and mute anything else - normal! There's usually a
setting that will release the audio when Sibelius is in the background.

The Sounds installer will put them in the right place. Let it do its own thing!
Top

WhySme

Posts: 3
Joined: Wed Jun 13, 2018 4:05 pm

Sibelius Version: 7.5

Operating System: Windows

 Quote

Post by WhySme » Wed Jun 13, 2018 4:07 pm

I had the same problem (error 40201 MMSYSTEM/OUT) I changed the driver tot a DS and
now SIbelius crashes every time I try to start it...

What can/should I do?

Top

MikeLyons

Posts: 1601
Joined: Fri Jun 24, 2016 7:20 pm

Sibelius Version: Ult. 2021.12/7.5/6.2

Operating System: Windows

 Quote
Post by MikeLyons » Thu Jun 14, 2018 6:40 am
Before going the route of deleting the plogue engine folder, tell us what actual DS device
you are using, what OS you're on and whether the audio drivers are truly up-to-date.

The MMSYSTEM error is what you get with both a MIDI device like MS Wavetablesynth and
an ASIO or WASAPI driver selected in your config. TBH, you are far better off using ASIO in
terms of the quality of sounds provided in VSTi libraries and if your sound card has a driver
for it, you should use it.

You only need MIDI synth sounds if you have not installed the Sib sounds or any other
library. It is not needed if you have a MIDI keyboard connected to your MIDI interface
which has it's own built-in sounds. If you use an external soundcard that will have its own
drivers which will avoid the issue.
Sib 6.2, 7.5 and 2023.6, Windows 11, 32GB RAM, 16TB 7200RPM Storage, 2TB SSD, Note
Performer 3.3.2, EWQLSO, EWQLSC, Harmony Assistant and some others. mike@mike-
lyons.co.uk

Top

WhySme

Posts: 3
Joined: Wed Jun 13, 2018 4:05 pm

Sibelius Version: 7.5

Operating System: Windows

 Quote

Post by WhySme » Thu Jun 14, 2018 6:48 am

MikeLyons wrote:Before going the route of deleting the plogue engine folder, tell us what
actual DS device you are using, what OS you're on and whether the audio drivers are truly up-
to-date.

The MMSYSTEM error is what you get with both a MIDI device like MS Wavetablesynth and an
ASIO or WASAPI driver selected in your config. TBH, you are far better off using ASIO in terms
of the quality of sounds provided in VSTi libraries and if your sound card has a driver for it, you
should use it.

You only need MIDI synth sounds if you have not installed the Sib sounds or any other library. It
is not needed if you have a MIDI keyboard connected to your MIDI interface which has it's own
built-in sounds. If you use an external soundcard that will have its own drivers which will avoid
the issue.
So I am running windows 10 on a ASUS laptop, I am not sure which DS device but I think it
was called "windows DS" or something.
But now I cannot change the driver in Sibelius (no drivers are shown anymore) and
everytime I open a file and click on a note Sibelius shuts down...
Top

WhySme

Posts: 3
Joined: Wed Jun 13, 2018 4:05 pm

Sibelius Version: 7.5

Operating System: Windows

 Quote

Post by WhySme » Thu Jun 14, 2018 7:37 am

Ok, I updated... still didn't work ... I pushed some buttons, restarted Sibelius 100 times
and all of a sudden I got the Error 40201 message again and Sibelius did not crash

Now I am using my zoom as an audio interface and everything works again!

Top

MikeLyons

Posts: 1601
Joined: Fri Jun 24, 2016 7:20 pm

Sibelius Version: Ult. 2021.12/7.5/6.2

Operating System: Windows

 Quote

Post by MikeLyons » Thu Jun 14, 2018 11:30 am

Now that everything appears to be working, can you post a screenshot of your Playback
devices window and the Audio Engine options dialog?

I'm on Windows 10 pro too. The incompatibility between ASIO/WASAPI and MIDI is a pain,
but it's not insurmountable.
Sib 6.2, 7.5 and 2023.6, Windows 11, 32GB RAM, 16TB 7200RPM Storage, 2TB SSD, Note
Performer 3.3.2, EWQLSO, EWQLSC, Harmony Assistant and some others. mike@mike-
lyons.co.uk

Top