musescore / musescore/MuseScore
Batch generate images ("image capture")
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Allow users to select multiple areas of a score for later export as images. (Likely after or in conjunction with the re-introduction of the "image capture" feature.)
Possible workflow:
- For each desired image, select the measures to be included, and invoke the "Image Capture" function
- Rather than clicking the button to confirm image creation, click another button that adds these measures to a list of excerpts, and, if desired, provide a filename for the future image
- Use a dialog box etc. to select options for the images to be exported (margins/padding, size, image format, resolution, etc.)
- Invoke a function to batch-produce the desired images
Problem to be solved
In previous MuseScore versions that had the Image Capture feature, it was unwieldy to produce a large number of images from a file, involving using the mouse to draw rectangles. For images with, say, consistent margins, this required precision with the mouse or later cleanup in a graphics editor. Once captured, the images couldn't be easily re-generated -- for example, if the user captured a bunch of images and then decided they needed to be in a different notation font, they would have to start over.
Prior art
No response
Additional context
I'm working on a large project with many small musical excerpts. My current solution is to use LilyPond to fill a folder with files that I can batch-process into images. This gives me the flexibility to change my mind about fonts, spacing, size, etc., and quickly regenerate all the images to meet the new requirements. This solution works, but I'd much rather use MuseScore!
Checklist
- This request follows the guidelines for reporting issues
- I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the planned re-introduction of the Image Capture feature and how selected score measures could be recorded for later export. Define the batch workflow, image options, filenames, and regeneration behavior, then confirm the design supports exporting multiple excerpts consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100