Problem with new score
Here is a score which I just can't get to work. I'm running Mac Ventura 13.0, and this one shouldn't actually have much in it at all. You may see a whole bunch of As in the Women's part. Selecting the first one of these is likely to cause a sustained bleating noise on that note.
It doesn't even seem possible to enter new notes into this, and that was a problem right from the start. This is about the fhird or fourth attempt to create something similar on this system.
Comments
I've loaded the score but am not experiencing any sound problems. Were you by chance using a third party VST or other non-default sound? Can you give more precise steps to reproduce the problem?
As for entering new notes, I didn't experience any problems with that either. Can you give precise steps to reproduce that problem as well?
In reply to I've loaded the score but am… by Marc Sabatella
I think I found the problem now. Not sure if this is something which MU4 should check - particularly for new scores. You may be able to identify it with the score I already uploaded - not sure, but it might show up if you load it.
Load up the "problem" score [which may not be a problem on your system ...].
Go into Preferences.
Go into I/O.
Make sure that both the Midi input and Midi output settings are to No device. If they aren't then there could be a problem with Apple Mac systems - as explained below.
Apple Macs - Macos may be different here from Windows or Linux. In Macos there are special ways to handle audio and Midi, and routes are often handled by something called IAC - which I think stands for ...Inter Application Connection - an architecture for routing used in Macos and maybe also in iOS for iPads.
At some stage in the last month or so I have connected edternal Midi devices, or tried to do Inter App communications. In the image shown here [can you see it?] the MIDI input setting is set to IAC Driver Bus 1.
If the MIDI output setting is also set to IAC Driver Bus 1, then there seems to effectively be feedback, and continuous audio output. It may not be possible to enter notes in this mode. Unless there really is an need for Midi routing, then both settings should be set to No device. When I experienced the problems both input and output settings were to IAC Driver Bus 1.
MU4 could perhaps usefully check this, and at least provide a warning., or alternatively just force the settings to No device and pop up a menu for users asking if they really want to connect any Midi apps or devices using this mechanism.
It is likely to be Apple specific - as discussed previously.
In reply to I think I found the problem… by dave2020X
I gather it is possible to create "MIDI loops" on any operating system, but it's certainly possible macOS makes that mistake easier somehow/. I have no idea if it's even possible for an application to detect when these happen, but if it is, then I agree a warning would make sense. Wouldn't hurt to open an issue on GitHub requesting this possibility be investigated.
In reply to I gather it is possible to… by Marc Sabatella
I assume that the settings are somewhere in the Preferences file. Arguably some users may want to retain non standard settings - or non default settings if they are doing something unusual, but most users won't. A feature to reset that Preferences back to the defaults would overcome problems like this for most people.
It's not that Musescore is unable to know what is happening in this case - the Preferences file should have the details.
In reply to I assume that the settings… by dave2020X
Preferences can be reset, via the button in that dialog.
But the problem with loop detection isn't MuseScore that doesn't know its own settings - it's that in general it's probably impossible to detect which specific settings will result in a loop. That could well on what else is going on with the routing of MIDI on your system, and I don't think MuseScore has access to that information. But maybe somehow it does. If so, the developers who work on that aspect of the code would know, which is why I suggested opening on issue on GitHub suggesting they investigate what might be involved in loop detection.