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

Certain scores export as midi incorrectly #26036

Open
4 tasks done
nlfar15562547 opened this issue Jan 9, 2025 · 4 comments
Open
4 tasks done

Certain scores export as midi incorrectly #26036

nlfar15562547 opened this issue Jan 9, 2025 · 4 comments
Assignees
Labels
awaiting reply from user MIDI Issues related to MIDI input/export, or MIDI devices needs review The issue needs review to set priority, fix version or change status etc.

Comments

@nlfar15562547
Copy link

Issue type

Import/export issue

Description with steps to reproduce

  1. download this or this score as midi or mscz
  2. if downloaded as midi, skip to step 5
  3. open the file in musescore
  4. export as midi (any settings really, just make sure to export full score)
  5. open this midi file in fl studio (other trackers might fail)
  6. look at the length of the pattern??? notes will either be stretched to infinity or there will be midi data and channel data off 70k measures in the distance

Supporting files, videos and screenshots

image
image

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

MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

OS: Windows 10 Version 2009 or later, Arch.: x86_64

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
@oktophonie oktophonie added the MIDI Issues related to MIDI input/export, or MIDI devices label Jan 10, 2025
@oktophonie oktophonie added the needs review The issue needs review to set priority, fix version or change status etc. label Jan 10, 2025
@zacjansheski
Copy link
Contributor

This has something to do with the glissandi, if I reduce the score just to this measure, the issue is still appearing

Screenshot 2025-01-10 105504

Deleting and rewriting the glissandi resolves the issue

I'm continuing to investigate, but I have not been able to reproduce this issue in a new score

@zacjansheski
Copy link
Contributor

This does not appear to be recent regression. Opening in 4.2 produces the same results

Maybe these glissandi originally came from a certain type of file import that is causing this?

@nlfar15562547
Copy link
Author

i wouldn't know; im not the person who made the scores;

another thing ive found; exporting every part seperately fixes this issue except on the instruments that contain this error
these midi files appear to be blank, and only contain one single marker

@nlfar15562547
Copy link
Author

on the subject of that specific glissando, soloing the piano track reveals that the glissando doesnt even play

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting reply from user MIDI Issues related to MIDI input/export, or MIDI devices needs review The issue needs review to set priority, fix version or change status etc.
Projects
None yet
Development

No branches or pull requests

3 participants