Audio fail in Musescore 4.1.1
I began writing a piece about a month ago, at that time everything was running well and I had no issues. A few days ago I discovered that NOW the audio is corrupt (best way I can describe it). The audio is hyper-compressed and the pitches are WAY off.
I have uninstalled and re-installed everything twice. And I have restarted my computer after each reinstall.
Unsure what is going on and extremely frustrated.
Thanks in advance
Comments
Is it possible that this is a sample rate issue? MuseScore currently works best when you set the sample rate of your speakers to 44100 Hz (44.1 kHz).
Also, are you using a soundfont (MS Basic), or Muse Sounds, or a VST plugin?
In reply to Is it possible that this is… by cbjeukendrup
I left everything to default
In reply to I left everything to default by GavinBrUphonium
The default sample rate for your audio device may simply be too high for the libraries used in MuseScore. Find the audio settings (usually in your OS, or in the control software that came with your audio device) and turn the sample rate down to 44.1 or 48 kHz.
In reply to The default sample rate for… by Marc Sabatella
my sample rate on my audio interface is at 41.1 kHz and I'm still having this problem. didn't start occurring until i downloaded 4.1.1 haven't changed any settings
In reply to my sample rate on my audio… by jasontb
Try going lower, if you can.
In reply to my sample rate on my audio… by jasontb
Same problem for me, see ticket here: https://musescore.org/en/node/353627
In reply to Same problem for me, see… by nikojoram
For the record, that's a forum post, not any sort of official issue in the tracker. If you'd like the developers to investigate, please make sure you open an issue on GitHub - https://github.com/musescore/MuseScore/issues
In reply to For the record, that's a… by Marc Sabatella
Thanks a lot for pointing that out!
I was under the impression, that bug reports are collected here, since the forum is titled 'Support and bug reports'
In reply to Thanks a lot for pointing… by nikojoram
It's a place to get support from fellow users here, and includes reporting an experience that might be a bug. Then based on the discussion here, if others are able to reproduce a problem and confirm it is in fact actually a bug in MuseScore and not a configuration problem on your computer or misunderstanding over how MuseScore works, and also confirm that the bug is not already reported on GitHub, then you will be directed to open an issue.
Right now it's not really clear if anyone else can reproduce your issue or not - I've heard of people having problems with the Focusrite products, but nothing so extreme as what you are describing. it would still be nice to get confirming from another user of one of those devices, but meanwhile, your description of the problem and what you've described is clear enough that it is worth opening an issue on GitHub even without independent confirmation.