musescore / musescore/MuseScore

Corsair VOID Wired Gaming Headset sound not working

Open
#19,931 2 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Nov 4, 2023.

P3 playback regression MS3
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

General playback bug

Bug description

Hello! I have a problem with Musescore 4 when my output is set to my Corsair VOID Wired Gaming Headset. In the past, few patches before, the program simply crashed but now it doesn't. Instead when I want to write a note it sounds like its written 4 octaves higher, it sounds on a really hight pitch. Also when I want to listen the piece I wrote the tempo is not as intended. It's like the whole program is accelarated. I think the problem might be caused by Corsair's software (ICUE) and Musescore 4 somewhy not working together. I have another headset (ASUS Rep. of Gamers) which works fine with the program. I usually use that since I can't use my Corsair headset. Can you fix it please? Thx. (I have a demonstration video attached) (the Corsair Headset worked with musescore 3)

https://github.com/musescore/MuseScore/assets/119762672/7bd7f649-eab7-4749-bbd4-abdd309c427f

Steps to reproduce
  1. You need a Corsair VOID Wired Gaming Headset with the software ICUE (the headset only works if ICUE is installed)
  2. Use it as main output
  3. Use musescore 4
Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/119762672/ee5e2cfb-7b5e-402e-a824-bec63776112f

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10 64bit

Additional context

CPU: Ryzen 7 3700x
GPU: GTX 1070ti
Memory: 32GB
Using MS Basic and MuseSounds causes the same issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.