#295437 - 18/03/2007 15:18
Importing ID3v1, not v2
|
new poster
Registered: 11/03/2002
Posts: 10
|
I just noticed that when I import mp3s, only the ID3v1 info is importing, even though there are ID3v2 tags as well. If remove the v1 tags before importing, I get no tag info imported at all.
I used to get v2 tags as normal. Recently I installed Windows Vista on my PC, so I had to reinstall Emplode, EAC (which creates the tags while ripping) and Tag&Rename (which does some post-rip tag tweaking).
I'm using Emplode 2.0, which is the same version I used before when it worked right.
Any help would be appreciated.
|
|
Top
|
|
|
|
#295438 - 18/03/2007 17:22
Re: Importing ID3v1, not v2
[Re: sjthomp]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31600
Loc: Seattle, WA
|
I believe you are running into this problem.
|
|
Top
|
|
|
|
|
#295439 - 18/03/2007 19:52
Re: Importing ID3v1, not v2
[Re: sjthomp]
|
new poster
Registered: 11/03/2002
Posts: 10
|
Okay, I figured it out. After some experimenting, I found that I could fix it in Tag&Rename. The v2 tags looked fine in T&R, and in other programs like Winamp, but they weren't being read by Emplode. After playing around with the T&R settings, I found that if I unchecked the option to "Write Unicode data into ID3v2 tags" then the v2 tags were fine in Emplode as well.
I don't know what Unicode data is, but Emplode doesn't like it.
|
|
Top
|
|
|
|
|
#295440 - 18/03/2007 21:24
Re: Importing ID3v1, not v2
[Re: sjthomp]
|
addict
Registered: 02/08/2004
Posts: 434
Loc: Helsinki, Finland
|
Quote:
I don't know what Unicode data is, but Emplode doesn't like it.
Hmm, does Unicode cause problems with Emplode? What about Jemplode? I've got some files with umlauts and such that don't appear correctly on Jemplode running on my Mac, but seem to display properly on the Empeg itself. I just assumed it was my Mac.
|
|
Top
|
|
|
|
|
#295441 - 19/03/2007 13:31
Re: Importing ID3v1, not v2
[Re: sjthomp]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31600
Loc: Seattle, WA
|
Quote:
I found that if I unchecked the option to "Write Unicode data into ID3v2 tags" then the v2 tags were fine in Emplode as well.
AHA! Great information. I will add that to the FAQ entry. Good sleuthing.
Quote:
I don't know what Unicode data is, but Emplode doesn't like it.
Unicode is where you can do things like Kanji characters, or any character sets that contain more than 256 possible symbols. It requires two bytes per character instead of one byte. This is not supported in emplode at all.
|
|
Top
|
|
|
|
|
#295442 - 19/03/2007 13:35
Re: Importing ID3v1, not v2
[Re: petteri]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31600
Loc: Seattle, WA
|
Quote:
Hmm, does Unicode cause problems with Emplode? What about Jemplode? I've got some files with umlauts and such that don't appear correctly on Jemplode running on my Mac, but seem to display properly on the Empeg itself. I just assumed it was my Mac.
If it displays properly on the player, you're not doing unicode. You're doing extended ASCII. Different thing.
Unicode= Two bytes per character.
Extended ASCII= Still one byte per character, but the 256-byte font set includes (in the higher part of the range) things like accents and umlauts.
If extended ascii characters aren't showing up right in Jemplode, I'm not sure what to do in that case. Maybe it's as simple as assigning a different font to the Java interpreter or something.
|
|
Top
|
|
|
|
|
#295443 - 19/03/2007 15:40
Re: Importing ID3v1, not v2
[Re: tfabris]
|
carpal tunnel
Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
|
Unicode does not specify an encoding method, and the most common encoding method (UTF-8) isn't two-bytes per character: each character will be encoded as either 1, 2, 3, or 4 bytes. The next most common (UTF-16), will encode characters as either 2 or 4 bytes.
And, while we're talking about it, "extended ASCII" is kind of a generic term. It only specifies an 8-bit encoding where characters 0 through 127 are the same as ASCII (which is a 7-bit encoding), but it doesn't say anything about what characters 128 through 255 are. The most common are probably MS-Windows' "Code Page 1252" and ISO-8859-1, also known as "Latin-1", which encode mostly Western European characters there. Other "extended ASCII" sets exist for other sets of languages.
_________________________
Bitt Faulk
|
|
Top
|
|
|
|
|
#295444 - 19/03/2007 16:42
Re: Importing ID3v1, not v2
[Re: tfabris]
|
carpal tunnel
Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
|
Quote:
Unicode is where you can do things like Kanji characters, or any character sets that contain more than 256 possible symbols. It requires two bytes per character instead of one byte. This is not supported in emplode at all.
That's true for Emplode 2.0/player v2.00. That combination supports Latin-1 tags only. Emplode 2.0 treats all non-Unicode tags as Latin-1, and cannot read Unicode tags, whether UTF-8 or UTF-16. The player itself treats the tag database as Latin-1.
Emplode 2.10/player v3 include partial support for Unicode tags; Emplode will read them correctly, and correctly write them to the player, but cannot display them in its own UI. Emplode 2.10 treats non-Unicode tags as being in the local code page, and can read both UTF-8 and UTF-16 Unicode tags. The player itself treats the tag database as UTF-8.
Peter
|
|
Top
|
|
|
|
|
#295445 - 19/03/2007 21:56
Re: Importing ID3v1, not v2
[Re: sjthomp]
|
veteran
Registered: 08/05/2000
Posts: 1429
Loc: San Francisco, CA
|
I've been having this problem forever. I edit the IDv3 tags SO CAREFULLY in WinAmp, then drag and drop em into emplode only to get NO TAG!
Can't find any setting within WinAmp that fixes it...
I'd prefer not to use another program to get it to work. Any advice?
Ok, tried it in jemplode - works like a charm. It's empeg only...
- Thanx
- Jon
|
|
Top
|
|
|
|
|
|
Previous Topic
Index