-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
feat: support for Matroska Video containers #3729
Comments
Not really following the request here. Are you suggesting that beets would be organizing Matroska container formats? |
yes, matroska is general purpose mediacontainer, which is efficient not only for video, but also for audio only streams, so it would be good to have support for it, it's much more simple to deal with one container for all audio encoders then supporting whole zoo of containers each with own benefits and limitations. |
This could potentially be out of scope of what beets does or depending on how you envision the metadata be manipulated. I'm unsure if any of the plugins would continue to work with a new format. I do understand that Matroska is a container and not an encoding, thus perhaps unravelling an MK* and manipulating the files within the contain could be possible. But I lack the knowledge of how metadata within Matroska Video containers work. I would like some more input from other maintainers as this is pretty much out of my depth at this point. |
at this point my request is: one reason to do so: unified way to manage metadata (tags, covers, lyrics) with different audio encoders, which otherwise introducing some complications. |
So for example...
Beets would potentially open the |
even simpler, treat
but as i know handling container itself have some complications, for example musicbrainz picard still does not support mka because of problems with matroska in mutagen |
i guess best approach is just handle first found audiostream for start. |
beets is also reliant on support in mutagen, and once that's there, support needs to be added to mediafile |
Indeed! I think the first step for any novel format requests is to look into what it would take to add support in Mutagen---or if there is already a feature request ticket there. For Matroska, there is: quodlibet/mutagen#3 Since there's no specific action for beets itself to take for now, let's close this issue. If you're interested in making this work, please consider contributing to the Mutagen feature. |
whole request is in request name.
The text was updated successfully, but these errors were encountered: