musescore / musescore/MuseScore

VST Effect Plugin „Vienna MIR Pro 3D“ Settings are not saved

Open
#23,957 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

P2 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
  1. create a new score
  2. add several instruments
  3. go to the mixer and add the plugin "Vienna MIR Pro 3D" for each instrument
  4. in the extra window. Place the instruments in a room
  5. save the score.
  6. close MuseScore
  7. open MuseScore
  8. open the score again
  9. error: The positioning of the instruments is not saved in the plugin.

See attached video.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/a1ac99ea-c7d5-40f3-baf0-f4844e5058be

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

OS: macOS 14.5, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630832, revision: github-musescore-musescore-22b46f2

Regression

No.

Operating system

Mac OS 14.5

Additional context

If I have a score with several instruments, I have to reposition the instruments in the room every time I open a score. Imagine that with 20 or more instruments.

You can download a free 30-day trial version here.

https://www.vsl.co.at/en/Vienna_Software_Package/MIR_Pro_3D

Also remember that you need at least one additional room pack, which is also available as a 30-day trial version. I have Roompack 1

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.