[MU4 Issue] Can't edit Kontakt patch/VST after initial playback

Open
#13,198 6 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Aug 31, 2023.

Assessment

This issue has not been assessed yet.

Description

P2 VST

Editing and Navigating Patches

Background

Most libraries have multiple panes to edit their patches.

Problem
  • This cannot be done in MuseScore 4 after the initial playback.
  • Once you have hit "play", the patch only allows you to interact with the last page or screen of the patch used before playback.
  • Other Kontakt-specific buttons and UI work ("Edit Instrument", for example) do work. The volume fader does not update with more playback or returns to normal when pausing (see screenshots).

To Reproduce

  1. Start a score, write a staff.
  2. Open the Mixer and start an instance of Kontakt. Try to navigate around the patch (preferably, a patch with multiple panes/screens/windows/whatever).
  3. Play what you wrote. Your score should sound with the patch's samples.
  4. Try to navigate the patch. You shouldn't be able to. It'll be stuck on the last section/window/pane you used before your first playback attempt. You can interact with that screen alone.
Expected behavior

I should be able to navigate around the patch at any point in the progress of writing. Before, during, and after the first playback (as is the case when loading patches in other DAWs).

Screenshots

Screenshot 2022-09-06 092217
MuseScore 4: Alpha 2. A Kontakt instance with CineHarps. Green lines represent what continues to work after playback, red represents what doesn't. And I have no idea what's going on with the volume meter.

Platform information

Edition: Windows 10 Pro
Version: 21H1
Installed on: ‎Jul ‎26, ‎2021
OS build: 19043.1889
Experience: Windows Feature Experience Pack 120.2212.4180.0

Additional Info.
  • When I am able to revert the instrument to use SoundFonts, playback works fine. I haven't noticed any issues after reverting from a VST... so far.
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.