I/O Bug report

• Oct 26, 2020 - 22:43
Reported version
3.5
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project

Editing I/O in preferences issues:
1) I/O preferences always open under factory settings.
2) Changes in preferences in I/O window retained while preferences window is open
3) Changes made on this page are reverted to factory setting once window is closed.
4) Midi input via electric is prevented


Comments

I was attempting to use an electric keyboard to use midi input. The program is able to detect the keyboard, however due to this issue I was unable to input with the keyboard. Have a good day

Severity S1 - Blocker S3 - Major
Status active needs info

Are you on the current version (3.5.2)? One of the earlier 3.5 releases had a bug where this dialog would not "take" unless you changed some other setting as well, but it should be fine now.

If you are still seeing this with 3.5.2, please let us know which OS, and any other unique properties of your particular system.

Frequency Once Few
Reported version 3.x-dev 3.5

I encountered this issue while attempting to change midi output latency in a bid to fix another problem.
I've tried the fix from the earlier 3.5 release, switching to jack, saving, then opening preferences again and changing back but then the box would no longer select my keyboard.
API and Device settings will save fine.
The attached file shows the preferences Musescore defaults to on a restart with my keyboard plugged in.
Pressing "restart Audio and Midi Devices" does not cause my keyboard to show up if it was unplugged when Musescore is opened.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.2.311459983, revision: 465e7b6

Attachment Size
Screenshot (15).png 146.83 KB

In reply to by roylanmessing

Are you saying you are using JACK? If not, then selecting it shouldn't be expected to work. And if you are using JACK, what you are describing is a different problem from what is described here.

Can you explain step by step, without reference to JACK< step by step to reproduce the problem you are seeing?