easytag issueshttps://gitlab.gnome.org/GNOME/easytag/-/issues2024-03-27T15:07:23Zhttps://gitlab.gnome.org/GNOME/easytag/-/issues/8Easytag Destroys ogg Vorbis files!!2024-03-27T15:07:23ZGhost UserEasytag Destroys ogg Vorbis files!!As of easytag 2.4.3, using easytag to tag ogg Vorbis files permanently destroys them. EasyTag advertises support of ogg Vorbis tagging, this should be removed immediately, and easytag should immediately be updated to refuse to attempt to...As of easytag 2.4.3, using easytag to tag ogg Vorbis files permanently destroys them. EasyTag advertises support of ogg Vorbis tagging, this should be removed immediately, and easytag should immediately be updated to refuse to attempt to process ogg Vorbis files until it can do so safely.
When editing ogg vorbis files in easytag, after they are saved, the files contain
```
Negative or zero granulepos (-104) on Vorbis stream outside of headers. This file was created by a buggy encoder
```
Which renders them unplayable by `mpv`https://gitlab.gnome.org/GNOME/easytag/-/issues/100EasyTag corrupts Ogg Opus files2024-03-08T20:17:07ZMatthew WoehlkeEasyTag corrupts Ogg Opus filesEasyTag seems to consider any Ogg Opus file that it hasn't tinkered with as "modified", even when no changes have been made. This alone seems suspicious.
Additionally, every time Easytag saves a `.ogg` file, it gets a new comment *appen...EasyTag seems to consider any Ogg Opus file that it hasn't tinkered with as "modified", even when no changes have been made. This alone seems suspicious.
Additionally, every time Easytag saves a `.ogg` file, it gets a new comment *appended*. Easytag should replace/update the comment as it does for e.g. `.flac`.
However, the real problem is worse. EasyTag is actually **corrupting** the very beginning of Ogg Opus files. (Details to follow.)https://gitlab.gnome.org/GNOME/easytag/-/issues/93Add Missing fields: Release Date AND Original Date2024-02-18T17:05:01ZRuben BladesAdd Missing fields: Release Date AND Original DateIt would be niche to have also the commonly used field "Original Date" or "Release Date" visible. ANd it would be nice to copy the content with one click to "Date".
Especially for older Music Date is often the Release Date of the CD whi...It would be niche to have also the commonly used field "Original Date" or "Release Date" visible. ANd it would be nice to copy the content with one click to "Date".
Especially for older Music Date is often the Release Date of the CD which today is a complete useless Info.
For Example: An ALn´bum from the 70s might have as Date 1991 because the CD was released 1991.
Thanks you!https://gitlab.gnome.org/GNOME/easytag/-/issues/60CDDB lookup on gnudb.org not working2024-02-18T17:04:34ZJohn BennettCDDB lookup on gnudb.org not workingTrying to use CDDB lookup in Easytag, was working a 'while' back (several months..), but now is only 'partially' working ie will find the names of albums when using "search selected files", but when an album is selected, a "404 Not Found...Trying to use CDDB lookup in Easytag, was working a 'while' back (several months..), but now is only 'partially' working ie will find the names of albums when using "search selected files", but when an album is selected, a "404 Not Found" error results. ![image](/uploads/0439a7657df06002d24fe4b02d602c4c/image.png)
Using the gnudb config: ![image](/uploads/a6195b032c8fb9c5c8ed3a54ed8449dd/image.png)
Wondering what the fix is?
Trying in both Opensuse Leap 15.2, and Ubuntu LTS 20.04. Easytag V2.4.3.
If I attempt to use the gnudb proxy, get an "Cannot resolve host 'http://proxy.gnudb.org' error.
Thanks.https://gitlab.gnome.org/GNOME/easytag/-/issues/97Wish: Which id3 Version is used2024-02-18T17:04:03ZRuben BladesWish: Which id3 Version is usedIf I change from Mixxx or Picard to easytag It often wishes to save the files again. I suppose its the use of a different id3-Version.
Could you show the actual used Version in the info field above (where size, bitrate sampling rate etc...If I change from Mixxx or Picard to easytag It often wishes to save the files again. I suppose its the use of a different id3-Version.
Could you show the actual used Version in the info field above (where size, bitrate sampling rate etc is shown).
The more Info are shown in that field, the better. Thanks!https://gitlab.gnome.org/GNOME/easytag/-/issues/98Wish: fetch cover function2024-02-18T17:03:49ZRuben BladesWish: fetch cover functionWould be nice to have taht one.
ThanksWould be nice to have taht one.
Thankshttps://gitlab.gnome.org/GNOME/easytag/-/issues/99Make Scanner always visible under Tags2024-02-18T17:03:38ZRuben BladesMake Scanner always visible under TagsThe Scanner is a useful tool to fill metainfo. Its not very handy to click everytime, if you have a bunch of albums to fill.
On the right side is a lot of free and unused space and the Scanner dialogue is really small, in fact its one on...The Scanner is a useful tool to fill metainfo. Its not very handy to click everytime, if you have a bunch of albums to fill.
On the right side is a lot of free and unused space and the Scanner dialogue is really small, in fact its one one line. It would easyly fit on the right side, permanently visible.
Alternatively, it could be optional or movable like in GIMP.
Thanky you!https://gitlab.gnome.org/GNOME/easytag/-/issues/95Error: Sorting multiple albums by clicking on the tabs above is not working r...2024-02-18T14:50:54ZRuben BladesError: Sorting multiple albums by clicking on the tabs above is not working rightIf I have more than one album by the same Artist selected (left, in the tree), I sometimes wish to sort for Comments, Album name,year etc, but this is not working in Plasma KDE. Something is changing, but not in an understandable way and...If I have more than one album by the same Artist selected (left, in the tree), I sometimes wish to sort for Comments, Album name,year etc, but this is not working in Plasma KDE. Something is changing, but not in an understandable way and not above the entire visible songs.
Thank youhttps://gitlab.gnome.org/GNOME/easytag/-/issues/94Wish: Put The Album Cover fields under the tag fields (not with tabs)2024-02-18T14:46:37ZRuben BladesWish: Put The Album Cover fields under the tag fields (not with tabs)Right Now I have two tabs, but today ppl have at least 24" or higher monitors, so there is plenty of space on the right, under the tags.
Alternativly one coud movge the tab down, likee its possible in GIMP
Thank you!Right Now I have two tabs, but today ppl have at least 24" or higher monitors, so there is plenty of space on the right, under the tags.
Alternativly one coud movge the tab down, likee its possible in GIMP
Thank you!https://gitlab.gnome.org/GNOME/easytag/-/issues/92taglib 2 compatibility2024-02-01T09:44:24ZThomas Klausnertaglib 2 compatibilityeasytag needs fixes to build with taglib 2.
Antonio Rojas proposed these for arch
https://gitlab.archlinux.org/archlinux/packaging/packages/easytag/-/blob/main/taglib-2.patch?ref_type=heads
and they work for me too.easytag needs fixes to build with taglib 2.
Antonio Rojas proposed these for arch
https://gitlab.archlinux.org/archlinux/packaging/packages/easytag/-/blob/main/taglib-2.patch?ref_type=heads
and they work for me too.https://gitlab.gnome.org/GNOME/easytag/-/issues/91DATE tag in Ogg files is misinterpreted as year.2023-12-11T09:54:37ZŁukasz StelmachDATE tag in Ogg files is misinterpreted as year.When easytag reads an Ogg file it assigns the value of the `DATE` tag to `FileTag->year` (see [ogg.c:947](https://gitlab.gnome.org/GNOME/easytag/-/blob/e7586fc9332ce66eb9bef222a490aeded0365e47/src/tags/ogg_tag.c#L947)). [Later](https://g...When easytag reads an Ogg file it assigns the value of the `DATE` tag to `FileTag->year` (see [ogg.c:947](https://gitlab.gnome.org/GNOME/easytag/-/blob/e7586fc9332ce66eb9bef222a490aeded0365e47/src/tags/ogg_tag.c#L947)). [Later](https://gitlab.gnome.org/GNOME/easytag/-/blob/e7586fc9332ce66eb9bef222a490aeded0365e47/src/file_list.c#L342) the value is considered invalid if it is longer than four characters which is against the Vorbis Comment [specification](https://www.xiph.org/vorbis/doc/v-comment.html) which defines the tag as
> Date the track was recorded
easytag edits the tag automatically and drops month and year information.https://gitlab.gnome.org/GNOME/easytag/-/issues/90Icons are not displaying correctly in easy tag flatpak installation2023-09-01T22:13:14ZJerry AlabasterIcons are not displaying correctly in easy tag flatpak installation# Version Info
easytag: flatpak install, version 2.4.3
sway: v 1.7
libwlroots10: v 0.15.1-6
Debian Bookworm
# Flatseal Icon Permissions
`/usr/share/icons:ro`
`/home/user/.icons:ro`
# Problem
The tool bar buttons, "next file", "last...# Version Info
easytag: flatpak install, version 2.4.3
sway: v 1.7
libwlroots10: v 0.15.1-6
Debian Bookworm
# Flatseal Icon Permissions
`/usr/share/icons:ro`
`/home/user/.icons:ro`
# Problem
The tool bar buttons, "next file", "last file", "save selected file" and so on are absent, I can click on them, float over them to get a description, but the icon is missing. What should I do to get them back?
# Note
Please let me know what other info I should provide, this is what I can think of thus far. Thanks for reading!https://gitlab.gnome.org/GNOME/easytag/-/issues/89Fix some compiler warnings2023-08-06T16:23:15ZLucian MalyFix some compiler warningsThis is a great tool and I use it often! I've recently upgraded to Red Hat Enterprise Linux release `9` (Plow) with GCC `11.3.1`.
I am trying to build EasyTag from @hexchain branch [hexchain/easytag:fix-compiler-warnings](https://gitlab...This is a great tool and I use it often! I've recently upgraded to Red Hat Enterprise Linux release `9` (Plow) with GCC `11.3.1`.
I am trying to build EasyTag from @hexchain branch [hexchain/easytag:fix-compiler-warnings](https://gitlab.gnome.org/hexchain/easytag/-/tree/fix-compiler-warnings) which is still unmerged after 2 years: !6
But I am now getting new compiler errors:
```
src/tags/libapetag/info_mac.c: In function ‘info_mac_read’:
src/tags/libapetag/info_mac.c:175:64: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
175 | stream_info->Version = stream_info->EncoderVersion = header->ver;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:176:35: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
176 | stream_info->Channels = header->channels;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:177:37: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
177 | stream_info->SampleFreq = header->sampleRate;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:178:32: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
178 | stream_info->Flags = header->formatFlags;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:179:80: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
179 | stream_info->SamplesPerFrame = monkey_samples_per_frame(header->ver, header->compLevel);
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:183:36: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
183 | stream_info->PeakLevel = header->peakLevel;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:185:33: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
185 | stream_info->Frames = header->totalFrames;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:188:36: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
188 | + header->finalFrameBlocks;
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
src/tags/libapetag/info_mac.c:202:45: error: array subscript ‘struct macHeader[0]’ is partly outside array bounds of ‘guint8[16]’ {aka ‘unsigned char[16]’} [-Werror=array-bounds]
202 | + header->headerBytesWAV) > 0
| ^~
src/tags/libapetag/info_mac.c:103:12: note: while referencing ‘header_buffer’
103 | guint8 header_buffer[MAC_FORMAT_HEADER_LENGTH];
| ^~~~~~~~~~~~~
```
My `./configure` is clean:
```
Linker ..................: gcc
CDDB support ............: yes
MP3 file support ........: yes
ID3v2.3 tags support ....: yes (id3lib-3.8.3)
Ogg Vorbis file support .: yes
Ogg Speex file support ..: yes
Ogg Opus file support ...: yes
FLAC file support .......: yes
MP4 file support ........: yes
WavPack support .........: yes
NLS/gettext .............: yes
Nautilus actions ........: yes
Tests during make check .: yes
Install prefix ..........: /usr/local
```
Any help would be appreciated!
CC: easytag-list@gnome.org @ac000 @hexchainhttps://gitlab.gnome.org/GNOME/easytag/-/issues/15Redesign the application and adapt to GTK4 and the modern GNOME HIG2023-07-30T07:43:39ZGhost UserRedesign the application and adapt to GTK4 and the modern GNOME HIGWould be great to see EasyTAG getting the newer GNOME design and changing the old titlebar for a headerbar with the buttons and hiding the menubar as per HIG. Thank you, otherwise nice app.Would be great to see EasyTAG getting the newer GNOME design and changing the old titlebar for a headerbar with the buttons and hiding the menubar as per HIG. Thank you, otherwise nice app.https://gitlab.gnome.org/GNOME/easytag/-/issues/35Appstream metadata fails to validate with appstream-util from appstream-glib-...2023-07-29T11:07:36ZHeiko BeckerAppstream metadata fails to validate with appstream-util from appstream-glib-0.7.16```
if test -f "data/easytag.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate ${d}data/easytag.appdata.xml; fi \
&& touch data...```
if test -f "data/easytag.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate ${d}data/easytag.appdata.xml; fi \
&& touch data/easytag.appdata.valid
data/easytag.appdata.xml: FAILED:
? tag-missing : <content_rating> required [use https://odrs.gnome.org/oars]
? tag-missing : <release> required
```https://gitlab.gnome.org/GNOME/easytag/-/issues/53Make it possible to edit all ID3 v2.4 tags2023-07-29T11:06:27ZTukusej’s SirsMake it possible to edit all ID3 v2.4 tagsI wish I could edit all ID3 v2.4 tags in EasyTag. There was a similar request in 2013 ([archived mailing list](https://mail.gnome.org/archives/easytag-list/2013-March/msg00024.html)) and there is/was a bug filed at [Bugzilla](https://bug...I wish I could edit all ID3 v2.4 tags in EasyTag. There was a similar request in 2013 ([archived mailing list](https://mail.gnome.org/archives/easytag-list/2013-March/msg00024.html)) and there is/was a bug filed at [Bugzilla](https://bugzilla.gnome.org/show_bug.cgi?id=689426) (filed in 2012, last modified in 2018), however I could not find an issues here at GNOME Gitlab.
Some said in the mailing list that the UI would be cluttered. I don’t think so, because in ET v2.4.3, we use tabs in (what I call) the tag editor (right pane with the form / tag fields). There we already have `Common` and `Images` tabs, so we could add a third one with additional ID3 tags (additional = all that are not listed in `Common` tab).
Another possibility is to add a preference to toggle viewing additional tags in the `Common` tab, which would be set to `false` by default, but when a user would set it to `true`, they would see all the tags in the `Common` tab.
I personally don’t care _how_ it would be implemented, I’d just like to see this implemented.https://gitlab.gnome.org/GNOME/easytag/-/issues/74GUI checkboxes are wrong making it hard to select a fill tag.2023-07-28T21:28:28ZKen ArromdeeGUI checkboxes are wrong making it hard to select a fill tag.Go into Easytag. Select some files. Click the "CDDB Search" button. Search using selected files.
Select a result and some tracks.
No "Fill Tags" checkboxes are selected and "Apply" is greyed out. So far, this is expected.
Click an...Go into Easytag. Select some files. Click the "CDDB Search" button. Search using selected files.
Select a result and some tracks.
No "Fill Tags" checkboxes are selected and "Apply" is greyed out. So far, this is expected.
Click any of the checkboxes. "Apply" is still greyed out, even though it should be active. Unclick that checkbox. "Apply" is now active, even though there are no checkboxes. Click the checkbox and "Apply" is inactive again. This makes it difficult to apply to a single fill tag.
The workaround is to click on a checkbox (causing Apply to become greyed), then click a second checkbox (which makes it active), then unclick the second checkbox (Apply remains active).
Easytag version is 2.4.3, 64 bit on Mageia Linux 8.0.https://gitlab.gnome.org/GNOME/easytag/-/issues/63Add support for metadata in WAV format files2023-07-28T20:04:42ZTiago d'AlmeidaAdd support for metadata in WAV format filesI've some WAV audios, but EasyTag do not recognize them.
- Fedora 34 - 38
- GNOME 40 - 44
- EasyTag v2.4.3 via flatpakI've some WAV audios, but EasyTag do not recognize them.
- Fedora 34 - 38
- GNOME 40 - 44
- EasyTag v2.4.3 via flatpakhttps://gitlab.gnome.org/GNOME/easytag/-/issues/68Support Theora video file format (with .ogv extension)2023-07-28T13:43:13ZSughoshaSupport Theora video file format (with .ogv extension)The same way Ogg files contain Vorbis Comments, [Theora](https://theora.org) files also contain the same kind of tags. Reading and editing their tags just like MP4 but with the same format of .ogg files would be useful. For reference, [A...The same way Ogg files contain Vorbis Comments, [Theora](https://theora.org) files also contain the same kind of tags. Reading and editing their tags just like MP4 but with the same format of .ogg files would be useful. For reference, [A documentation](https://theora.org/doc/Theora.pdf) is there for reference, having 6.3 section for comment header.https://gitlab.gnome.org/GNOME/easytag/-/issues/43Add support for metadata in webm files2023-07-28T13:42:16ZJérémy LalAdd support for metadata in webm fileswebm implements a tag specification:
http://wiki.webmproject.org/webm-metadata/global-metadata
It shares some tags with id3 tags.
It would be great if easytag allowed us to edit those tags:
(title, artist, etc... all tags that have an i...webm implements a tag specification:
http://wiki.webmproject.org/webm-metadata/global-metadata
It shares some tags with id3 tags.
It would be great if easytag allowed us to edit those tags:
(title, artist, etc... all tags that have an id3 key in that specification).