Skip to content

tagging.py: coverart rework documentation #57

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

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

dconrad5
Copy link
Contributor

@dconrad5 dconrad5 commented Jan 4, 2025

depends on PR #55

@auouymous
Copy link
Member

Is this updated and ready for review now that gpodder/gpodder#1701 has been merged?

@dconrad5
Copy link
Contributor Author

dconrad5 commented Mar 4, 2025

It is now, I just needed to restore the setting "auto_embed_coverart".

No wait, I think I need to rebase it. That should be quick.

@dconrad5
Copy link
Contributor Author

dconrad5 commented Mar 4, 2025

Ok, now it should be good to review.

Copy link
Member

@auouymous auouymous left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably stop using "git master branch", because the auto_embed_coverart used it and was merged in 2013. Perhaps something like "post 3.11.5", "after 3.11.5", or suggestions welcome since those might be seen as 3.11.5 supporting them to some users.

@dconrad5
Copy link
Contributor Author

We should probably stop using "git master branch", because the auto_embed_coverart used it and was merged in 2013. Perhaps something like "post 3.11.5", "after 3.11.5", or suggestions welcome since those might be seen as 3.11.5 supporting them to some users.

Ok, I'll try to make that clearer.

Copy link
Member

@auouymous auouymous left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That "newer than" is perfect, and thank you for looking up the versions for other settings.

@@ -23,7 +23,7 @@ artwork will be preferred if it is present - if not, the channel artwork will be
Note that episode-specific artwork in MP4 files is currently not implemented.

The artwork can optionally be normalized to the desired parameters - size and file type.
By default, it will write 500px baseline JPEGs.
By default, it will baseline JPEGs with the larger side scaled to 500px with the aspect ratio maintained.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does "will baseline JPEGs" mean something, or was that meant to be "will write JPEGs"?

Copy link
Contributor Author

@dconrad5 dconrad5 Apr 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, "baseline" is the opposite of "progressive" JPEG, that being, it will be decoded all at once rather than in increasing resolution (if I recall correctly). Maybe I should say "non-progressive" to make that more clear...?

This probably doesn't matter to people opening the files on a computer, but those with old timey mp3 players often cannot open progressive album art.

Edit: I did miss a word in there as well though, I see now...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, "baseline" is the opposite of "progressive" JPEG, that being, it will be decoded all at once rather than in increasing resolution (if I recall correctly). Maybe I should say "non-progressive" to make that more clear...?

This probably doesn't matter to people opening the files on a computer, but those with old timey mp3 players often cannot open progressive album art.

Edit: I did miss a word in there as well though, I see now...

Done - please see d1a89c7

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

Successfully merging this pull request may close these issues.

2 participants