Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chord symbol playback not export to MIDI #24515

Closed
4 tasks done
MarcSabatella opened this issue Sep 6, 2024 · 2 comments · Fixed by #24590
Closed
4 tasks done

Chord symbol playback not export to MIDI #24515

MarcSabatella opened this issue Sep 6, 2024 · 2 comments · Fixed by #24590
Assignees
Labels
MIDI Issues related to MIDI input/export, or MIDI devices P1 Priority: High regression MS4 Regression on a prior release

Comments

@MarcSabatella
Copy link
Contributor

Issue type

Import/export issue

Description with steps to reproduce

  1. Create score with grand staff
  2. Add chord symbols
  3. Export to MIDI
  4. Play or import resulting MIDI file

Result: chord symbol playback is not there

Supporting files, videos and screenshots

Here is the result using chord-symbol-export.zip:

Screen.recording.2024-09-06.3.10.53.PM.webm

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

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: github-musescore-musescore-0b3dd00

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Debian 12

Additional context

This worked up through 4.3.2 on my system (there were reports in the past about it not working on for everyone) but no longer does in 4.4.1.

See original report in #23240 which also claims the chords are missing in MuscXML export. but I cannot reproduce that. Just a glitch with which staff of a grand staff the chords are attached to, but this isn't a regression (at least not vs 4.3.2)

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
@Jojo-Schmitz
Copy link
Contributor

@cbjeukendrup cbjeukendrup added the MIDI Issues related to MIDI input/export, or MIDI devices label Sep 6, 2024
@RomanPudashkin RomanPudashkin self-assigned this Sep 9, 2024
@RomanPudashkin RomanPudashkin added the P1 Priority: High label Sep 9, 2024
igorkorsukov pushed a commit to igorkorsukov/MuseScore that referenced this issue Sep 10, 2024
rpatters1 added a commit to rpatters1/MuseScore that referenced this issue Sep 10, 2024
* master:
  added show graphics info to diagnostics
  added switching graphics api
  added websocket api
  gp-import: fixed arpeggio direction for gp5
  musescore#12753: Removed a redundant non-null check
  fix musescore#24515
  VST: process sequences separately, not all at once (same as in FluidSynth)
  gp-import: fixed arpeggio duration for gp4 files
  Allow manual XML formatting in headers/footers
  Speed up palette search further by using a single instance loader for the More elements popup
  Speed up palette search by having one right-click mouse area instance
  Speed up palette search and close by having one instance of the context menu
  Some more optimizations to the palette search
  Windows: also deploy other TLS backends
  SetupAppImagePackaging.cmake: Fix WINDOW_MANAGER_CLASS
  Fix disappearing fingering number
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MIDI Issues related to MIDI input/export, or MIDI devices P1 Priority: High regression MS4 Regression on a prior release
Projects
Development

Successfully merging a pull request may close this issue.

5 participants