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

allow to load multiple images into one book #129

Closed
Bacchushlg opened this issue Mar 21, 2018 · 12 comments
Closed

allow to load multiple images into one book #129

Bacchushlg opened this issue Mar 21, 2018 · 12 comments

Comments

@Bacchushlg
Copy link
Collaborator

Actually it is not possible to create one book out of multiple single images.
Only in case of a multipage TIFF or PDF a book with several pages is created.
It would be fine to allow to add pages to an already open book in order to create one common output file for export.

@hbitteur
Copy link
Contributor

I agree

@hbitteur
Copy link
Contributor

hbitteur commented Aug 8, 2021

Hi Baruch,

I'm thinking about features very similar to the ones provided by PDF-SAM (PDF Split And Merge) utility.
Could you have a look at their site https://pdfsam.org/pdfsam-basic/ and tell me if you feel comfortable with these features (replacing their PDF containers by our BOOK containers, of course).

Rather than re-inventing the wheel...

@hbitteur
Copy link
Contributor

hbitteur commented Aug 8, 2021

Beside Split and Merge, PDF-SAM also allows Extract that might be of interest for you.
See by yourself.

@Bacchushlg
Copy link
Collaborator Author

I seldom have pdf scores as source, mostly I have paper notes. After scanning I mostly do some manual correction (esp. fine rotation and a bit contrast improvement).
Sometimes I make TIFFs from this (could be pdf, too, of course) in order to get the score handled as one to avoid the described problem.
But there is one disadvantage: If I see that my imaging improvement was not successful, the transcription will still run for the complete score (all pages).
Therefore meanwhile I abstain from the latter (for bad score images) and do the transcription page by page.

And here, I come back to the above: a feature to "connect" all open pages to get a common export file.

@hbitteur
Copy link
Contributor

hbitteur commented Aug 8, 2021

So this "connect" action could be equivalent to the "merge" feature of PDF-SAM:

  • Ability to select several books (and perhaps some sheets in these books)
  • And merge everything as a single book

@Bacchushlg
Copy link
Collaborator Author

The important thing is to be able to merge after loading. So pages of a score can be transcribed page by page but then exported as one mxl-file

@hbitteur
Copy link
Contributor

hbitteur commented Aug 8, 2021

To avoid any misunderstanding, let me clarify that I'm trying to define the specifications for Audiveris split & merge features.

In this exercice, PDF-SAM is a good model, it has evolved along many years, it is well documented, etc... My intention is not to push for use of PDF-SAM, but merely to more or less "replicate" the PDF-SAM features and user interface into Audiveris software.

This is the reason why I asked you to review these PDF-SAM features (Split, Merge, Extract) and then tell me if you would be happy with similar features within Audiveris.

We are working at specification level for the time being.

@Bacchushlg
Copy link
Collaborator Author

Ah, ok. This was my mis-understanding.
But, to be honest, this is much more than what I asked for.
I thought of just one "simple" feature: create a common export for all opened tabs, even if they come from different image files.

The only thing that might be necessary is to allow to re-sort the pages (tabs), either by drag-n-drop (like most browsers allow), or by a list window that allows to do the resorting (e.g. similar to what MuseScore shows in the instruments dialog on the right). This would allow to re-open (and transcribe) a single page from the already loaded list of pages (after some image improvements from an external tool)

@hbitteur
Copy link
Contributor

hbitteur commented Aug 8, 2021

I agree that these features may be more than what you strictly need for the specific case you described.
But rather to design something specific, I prefer to stick to a set of well-thought operations.
Granted, implementation may take longer but, doing so, I feel more comfortable with the final suitability for the end-user.

@hbitteur
Copy link
Contributor

hbitteur commented Aug 8, 2021

Let's take your example, using PDF-SAM as the model
I suppose you have:

  • A book B20 of 20 sheets. This book can be the result of the aggregation of smaller books, perhaps including 1-page books, etc, I don't really care.

Now, you have a problem with say sheet 10 for which you need to work on image improvement, or get a better scan, etc.
Then, once you are OK with a new version of image for sheet 10, you need to somehow replace sheet 10 in book B20 by your new version.
So, you make a Merge of the following list:

  1. B20 sheets "1-9"
  2. Your new image 10
  3. B20 sheets "11-"

And you get your new book.

@Bacchushlg
Copy link
Collaborator Author

Bacchushlg commented Aug 8, 2021 via email

@hbitteur
Copy link
Contributor

Commit 0b414c1 provides the feature in development branch.
Handbook to be updated accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants