beetbox / beetbox/mediafile

MediaFile: More general comments field in ID3

Open
#10 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
120
Forks
41
PR merge metrics
No merged PRs in 30d

Description

An outgrowth of #1043, courtesy of @kiefermat.

Apparently, some software uses `COMM` frames with funky `desc` fields to store comments. (Most software uses an empty `desc` field.) We should probably read these various frames and interpret them as comments.

The question gets a little trickier when writing. I lean toward automatically "standardizing" these fields when MediaFile needs to _update_ the tag—i.e., we should drop any frames with custom `desc` fields and just preserve the `desc`less frame. That would require a bit more machinery than we currently have in `MP3DescStorageStyle`.

Contributor guide

Open the contributing guide

Research direction

Start by reading the existing ID3 comment handling and MP3DescStorageStyle, then review the context in issue #1043. Determine how COMM frames with custom desc fields should be read and how updates should standardize them while preserving the desc-less frame; done means both behaviors are covered consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
audio-video-rtc
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.