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

Batch conversion silently fails (and buggy MSCX conversion) #23458

Open
ThePython10110 opened this issue Jul 3, 2024 · 2 comments
Open

Batch conversion silently fails (and buggy MSCX conversion) #23458

ThePython10110 opened this issue Jul 3, 2024 · 2 comments
Labels
cli Issues related to MuseScore's command line interface community Issues particularly suitable for community contributors to work on needs info More information is required before action can be taken P2 Priority: Medium regression MS4 Regression on a prior release

Comments

@ThePython10110
Copy link

ThePython10110 commented Jul 3, 2024

Issue type

Import/export issue

Bug description

Attempting to run a batch convert does absolutely nothing. It must have at some point, because I have converted files in MS4 previously, but not anymore. The JSON file is formatted correctly, and there is no error code. There's no way I can find to get any kind of debug information (-d/--debug doesn't work).

Fortunately, I was generating the JSON file with a Python script, so I just skipped the JSON and made my script convert every file individually with -o. This led me to another issue: Converting to .mscx files randomly fails sometimes. Retrying the conversion (sometimes multiple times) seems to work. It's not VST related, since it happened to a score that didn't have VST's (unless the built-in reverb counts). It doesn't happen with MP3, MIDI, PDF, MXL, or MusicXML file types (I haven't tested any others). It does seem to depend on the score, since some seem to fail most of the time, and some never fail. It doesn't seem to matter which instruments the score includes (one score only had guitar, and one only had piano and strings).

Steps to reproduce

Batch convert issue

  1. Create a batch convert JSON file.
  2. Run <path to MuseScore4.exe> -j <path to JSON file>
  3. Silently fails.

Other conversion issue

  1. Try to convert a whole bunch of files
  2. About a third (?) will fail to convert to .mscx

Screenshots/Screen recordings

No response

MuseScore Version

4.3.2

Regression

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

Operating system

OS: Windows 10 Version 2009, Arch.: x86_64

Additional context

No response

@muse-bot muse-bot added the regression MS4 Regression on a prior release label Jul 3, 2024
@ThePython10110 ThePython10110 changed the title Batch conversion silently fails Batch conversion silently fails (and buggy MSCX conversion) Jul 3, 2024
@bkunda bkunda added the community Issues particularly suitable for community contributors to work on label Jul 5, 2024
@bkunda bkunda added the cli Issues related to MuseScore's command line interface label Jul 5, 2024
@bkunda bkunda moved this to In the further future in MuseScore Studio Backlog Jul 5, 2024
@bkunda bkunda added the P2 Priority: Medium label Jul 5, 2024
@bemain
Copy link

bemain commented Nov 4, 2024

How do you generate parts individually using -o? Or maybe you don't do that?

@pacebes
Copy link
Contributor

pacebes commented Nov 5, 2024

It does seem to depend on the score, since some seem to fail most of the time, and some never fail. It doesn't seem to matter which instruments the score includes (one score only had guitar, and one only had piano and strings).

Could you provide us with a score that fails most of the time and the json ??

@cbjeukendrup cbjeukendrup added the needs info More information is required before action can be taken label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Issues related to MuseScore's command line interface community Issues particularly suitable for community contributors to work on needs info More information is required before action can be taken P2 Priority: Medium regression MS4 Regression on a prior release
Projects
Status: Available
Status: In the further future
Development

No branches or pull requests

6 participants