TagInspector on Windows - looking for an equivalent that shows character-encoding
up vote
0
down vote
favorite
So I came across this article, which describes a tool called 'TagInspector'. Here's the containing article: https://lachlanwetherall.com/2014/09/holden-mylink-and-the-cover-art-conundrum/
The link to TagInspector shown in the article, goes to a Linux-centric website, that offers both Linux and Windows kits for TagInspector.
The bad news (for me) was that both Windows kits (32-bit and 64-bit) contain just a single file, a .exe, and when I run that, on both Win-10 and Win-7 computers, I get 'unknown runtime error 123', when I try to open any MP3 file.
(I sent a msg, via the 'Contact' tab, to that TagInspector distributing site, alerting them to that problem with their Windows'
kits. I don't know if/when I might ever get a fix for the problem.)
So, MEANWHILE, what my bottom-line issue now is, is how to find some ALTERNATE freeware 'id3-tag'-displaying software that, as this one
does, not only displays the VERSION# of ide-tags, but also shows the
CHARACTER-ENCODING in use. Specifically, whether the encoding is
ISO8859-1 or UTF16-BOM(Unicode).
[ If you read the article, it shows a screenshot, and explains why
this level of detail is needed, to resolve issues with album-cover
artwork not appearing correctly on certain in-vehicle touch-screen music players. His article pertains to in-vehicle consoles containing
"MyLink" firmware, whereas my vehicle (a 2015 Subaru) contains "StarLink" firmware. ]
So, my question is simply: Can anyone point me to some other id3-tag displaying software that, like TagInspector does additionally show the character-encoding? I'd want something that is offered in a
Windows-edition.
[ I have been using some freeware called "MP3tag", but I see no way to get it to show/confirm the character-encoding of the id3 tags. ]
TIA...
id3 id3v2 id3-tag
asked Nov 10 at 19:18
Dave
1,14121117
add a comment |
up vote
0
down vote
favorite
So I came across this article, which describes a tool called 'TagInspector'. Here's the containing article: https://lachlanwetherall.com/2014/09/holden-mylink-and-the-cover-art-conundrum/
The link to TagInspector shown in the article, goes to a Linux-centric website, that offers both Linux and Windows kits for TagInspector.
The bad news (for me) was that both Windows kits (32-bit and 64-bit) contain just a single file, a .exe, and when I run that, on both Win-10 and Win-7 computers, I get 'unknown runtime error 123', when I try to open any MP3 file.
(I sent a msg, via the 'Contact' tab, to that TagInspector distributing site, alerting them to that problem with their Windows'
kits. I don't know if/when I might ever get a fix for the problem.)
So, MEANWHILE, what my bottom-line issue now is, is how to find some ALTERNATE freeware 'id3-tag'-displaying software that, as this one
does, not only displays the VERSION# of ide-tags, but also shows the
CHARACTER-ENCODING in use. Specifically, whether the encoding is
ISO8859-1 or UTF16-BOM(Unicode).
[ If you read the article, it shows a screenshot, and explains why
this level of detail is needed, to resolve issues with album-cover
artwork not appearing correctly on certain in-vehicle touch-screen music players. His article pertains to in-vehicle consoles containing
"MyLink" firmware, whereas my vehicle (a 2015 Subaru) contains "StarLink" firmware. ]
So, my question is simply: Can anyone point me to some other id3-tag displaying software that, like TagInspector does additionally show the character-encoding? I'd want something that is offered in a
Windows-edition.
[ I have been using some freeware called "MP3tag", but I see no way to get it to show/confirm the character-encoding of the id3 tags. ]
TIA...
id3 id3v2 id3-tag
asked Nov 10 at 19:18
Dave
1,14121117
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
So I came across this article, which describes a tool called 'TagInspector'. Here's the containing article: https://lachlanwetherall.com/2014/09/holden-mylink-and-the-cover-art-conundrum/
The link to TagInspector shown in the article, goes to a Linux-centric website, that offers both Linux and Windows kits for TagInspector.
The bad news (for me) was that both Windows kits (32-bit and 64-bit) contain just a single file, a .exe, and when I run that, on both Win-10 and Win-7 computers, I get 'unknown runtime error 123', when I try to open any MP3 file.
(I sent a msg, via the 'Contact' tab, to that TagInspector distributing site, alerting them to that problem with their Windows'
kits. I don't know if/when I might ever get a fix for the problem.)
So, MEANWHILE, what my bottom-line issue now is, is how to find some ALTERNATE freeware 'id3-tag'-displaying software that, as this one
does, not only displays the VERSION# of ide-tags, but also shows the
CHARACTER-ENCODING in use. Specifically, whether the encoding is
ISO8859-1 or UTF16-BOM(Unicode).
[ If you read the article, it shows a screenshot, and explains why
this level of detail is needed, to resolve issues with album-cover
artwork not appearing correctly on certain in-vehicle touch-screen music players. His article pertains to in-vehicle consoles containing
"MyLink" firmware, whereas my vehicle (a 2015 Subaru) contains "StarLink" firmware. ]
So, my question is simply: Can anyone point me to some other id3-tag displaying software that, like TagInspector does additionally show the character-encoding? I'd want something that is offered in a
Windows-edition.
[ I have been using some freeware called "MP3tag", but I see no way to get it to show/confirm the character-encoding of the id3 tags. ]
TIA...
id3 id3v2 id3-tag
asked Nov 10 at 19:18
Dave
1,14121117
So I came across this article, which describes a tool called 'TagInspector'. Here's the containing article: https://lachlanwetherall.com/2014/09/holden-mylink-and-the-cover-art-conundrum/
The link to TagInspector shown in the article, goes to a Linux-centric website, that offers both Linux and Windows kits for TagInspector.
The bad news (for me) was that both Windows kits (32-bit and 64-bit) contain just a single file, a .exe, and when I run that, on both Win-10 and Win-7 computers, I get 'unknown runtime error 123', when I try to open any MP3 file.
(I sent a msg, via the 'Contact' tab, to that TagInspector distributing site, alerting them to that problem with their Windows'
kits. I don't know if/when I might ever get a fix for the problem.)
So, MEANWHILE, what my bottom-line issue now is, is how to find some ALTERNATE freeware 'id3-tag'-displaying software that, as this one
does, not only displays the VERSION# of ide-tags, but also shows the
CHARACTER-ENCODING in use. Specifically, whether the encoding is
ISO8859-1 or UTF16-BOM(Unicode).
[ If you read the article, it shows a screenshot, and explains why
this level of detail is needed, to resolve issues with album-cover
artwork not appearing correctly on certain in-vehicle touch-screen music players. His article pertains to in-vehicle consoles containing
"MyLink" firmware, whereas my vehicle (a 2015 Subaru) contains "StarLink" firmware. ]
So, my question is simply: Can anyone point me to some other id3-tag displaying software that, like TagInspector does additionally show the character-encoding? I'd want something that is offered in a
Windows-edition.
[ I have been using some freeware called "MP3tag", but I see no way to get it to show/confirm the character-encoding of the id3 tags. ]
TIA...
id3 id3v2 id3-tag
id3 id3v2 id3-tag
asked Nov 10 at 19:18
Dave
1,14121117
asked Nov 10 at 19:18
Dave
1,14121117
asked Nov 10 at 19:18
Dave
1,14121117
asked Nov 10 at 19:18
Dave
1,14121117
asked Nov 10 at 19:18
Dave
1,14121117
1,14121117
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Ok, I've resolved this issue to my satisfaction.
(1) I updated an old Linux machine that had been on moth-balls, and
installed the Linux kit offering of TagInspector. It works fine on Linux
and I was able to confirm the character-encoding of the id3-info in the MP3 files in question.
(2) More importantly, after re-reading the initial article mentioned, it
appears that it must be the 'nature-of-the-beast'...i.e. that id3 version 1
tags are (always) encoded in ISO8859_1, whereas id3v2.x are (always) encoded
in UTF-16_BOM. As a result, I now see no further NEED to continue to
use TagInspector. My original app..."Mp3tag" will fulfill my needs
for an id3-tag application.
Cheers...
answered Nov 11 at 15:26
Dave
1,14121117
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Ok, I've resolved this issue to my satisfaction.
(1) I updated an old Linux machine that had been on moth-balls, and
installed the Linux kit offering of TagInspector. It works fine on Linux
and I was able to confirm the character-encoding of the id3-info in the MP3 files in question.
(2) More importantly, after re-reading the initial article mentioned, it
appears that it must be the 'nature-of-the-beast'...i.e. that id3 version 1
tags are (always) encoded in ISO8859_1, whereas id3v2.x are (always) encoded
in UTF-16_BOM. As a result, I now see no further NEED to continue to
use TagInspector. My original app..."Mp3tag" will fulfill my needs
for an id3-tag application.
Cheers...
answered Nov 11 at 15:26
Dave
1,14121117
add a comment |
up vote
0
down vote
Ok, I've resolved this issue to my satisfaction.
(1) I updated an old Linux machine that had been on moth-balls, and
installed the Linux kit offering of TagInspector. It works fine on Linux
and I was able to confirm the character-encoding of the id3-info in the MP3 files in question.
(2) More importantly, after re-reading the initial article mentioned, it
appears that it must be the 'nature-of-the-beast'...i.e. that id3 version 1
tags are (always) encoded in ISO8859_1, whereas id3v2.x are (always) encoded
in UTF-16_BOM. As a result, I now see no further NEED to continue to
use TagInspector. My original app..."Mp3tag" will fulfill my needs
for an id3-tag application.
Cheers...
answered Nov 11 at 15:26
Dave
1,14121117
add a comment |
up vote
0
down vote
up vote
0
down vote
Ok, I've resolved this issue to my satisfaction.
(1) I updated an old Linux machine that had been on moth-balls, and
installed the Linux kit offering of TagInspector. It works fine on Linux
and I was able to confirm the character-encoding of the id3-info in the MP3 files in question.
(2) More importantly, after re-reading the initial article mentioned, it
appears that it must be the 'nature-of-the-beast'...i.e. that id3 version 1
tags are (always) encoded in ISO8859_1, whereas id3v2.x are (always) encoded
in UTF-16_BOM. As a result, I now see no further NEED to continue to
use TagInspector. My original app..."Mp3tag" will fulfill my needs
for an id3-tag application.
Cheers...
answered Nov 11 at 15:26
Dave
1,14121117
Ok, I've resolved this issue to my satisfaction.
(1) I updated an old Linux machine that had been on moth-balls, and
installed the Linux kit offering of TagInspector. It works fine on Linux
and I was able to confirm the character-encoding of the id3-info in the MP3 files in question.
(2) More importantly, after re-reading the initial article mentioned, it
appears that it must be the 'nature-of-the-beast'...i.e. that id3 version 1
tags are (always) encoded in ISO8859_1, whereas id3v2.x are (always) encoded
in UTF-16_BOM. As a result, I now see no further NEED to continue to
use TagInspector. My original app..."Mp3tag" will fulfill my needs
for an id3-tag application.
Cheers...
answered Nov 11 at 15:26
Dave
1,14121117
answered Nov 11 at 15:26
Dave
1,14121117
answered Nov 11 at 15:26
Dave
1,14121117
answered Nov 11 at 15:26
Dave
1,14121117
1,14121117
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242546%2ftaginspector-on-windows-looking-for-an-equivalent-that-shows-character-encodin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
