musescore / musescore/MuseScore

No preview sound within VST plugin UI (sound still works in playback) – Cherry Audio Surrealistic / Korg M1

Open
#27,142 2 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Mar 16, 2025.

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

Description

Issue type

VST bug

Description with steps to reproduce

To replicate, open the menu of a VST such as the Cherry Audio Surrealistic MG -1 Plus (which is free to download), via the mixer sound select. In the VST pop up, keys can be pressed but will not produce sound. Same issue with the Korg M1 VST, though there keys can't even be pressed. For both of these, sound is heard on playback but not within the plug in menu. Some VST programs like Sforzando produce no audio within or outside of the plugin however, meaning all sound libraries accessed through it will not produce sound.

In addition, the Korg M1 VST would crash musescore up to yesteday but no longer seems to do so. Some other VSTs of mine still do instantly crash the program on selection though, such as the Roland JV 1080.

Supporting files, videos and screenshots

[

DIAGNOSTIC.zip

](url)

Don't have a screen recorder so can't supply any video, sorry.

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Windows 10

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.