musescore / musescore/MuseScore

Error messages when creating score from Bigband template

Open
#32,666 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Mar 20, 2026.

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

Description

Issue type

Other type of issue

Description with steps to reproduce
  1. start MuseScore Studio from the terminal
  2. Create a new score
  3. pick the Jazz/Bigband template
  4. fill in some info
  5. Observe multiple errors in the terminal window.

Here is a short summary of the error messages:
20:55:18.128 | ERROR | main_thread | DockWindow::restorePageState | Could not restore the state of "Notation" !
20:55:18.235 | ERROR | 125295571007168 | SynthResolver::resolveSynth | invalid audio source params for trackId: 0
20:55:18.301 | ERROR | 125295571007168 | SynthResolver::resolveSynth | invalid audio source params for trackId: 1
20:55:18.304 | ERROR | 125295571007168 | SynthResolver::resolveSynth | invalid audio source params for trackId: 2
20:55:18.317 | ERROR | 125295571007168 | SynthResolver::resolveSynth | invalid audio source params for trackId: 3
...logfi
20:55:19.480 | ERROR | 125295571007168 | SynthResolver::resolveSynth | invalid audio source params for trackId: 17

Supporting files, videos and screenshots

logfiles_bigbandtemplate.zip

In which versions of MuseScore Studio is this issue present?

OS: Ubuntu 24.04.4 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.7.0-260317043, revision: github-musescore-musescore-e51c5a2

Regression

No.

Operating system

Ubuntu 24.04.4 LTS

Additional context

There should be no Error messages

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.