Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Free J2ME .jar mp3/ogg player? (Read 8416 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Free J2ME .jar mp3/ogg player?

I'm having a bit of a problem with my Sony Ericsson K800i; I think it's a problem with the firmware, but it's definitely not reading my ID3 tags properly (they're neatly tagged with both ID3v1 and ID3v2), so I've decided to give the idea of a third-party player a go.

After Googling a bit, I came across KD Player, which allegedly works with my phone, but I was unable to get that working (it wouldn't find my files), and so I've decided to move on.

My problem is; I can't find any players.

KD Player doesn't do .ogg, but since my entire collection is Vorbis (I've had to convert 400 files to mp3 to play them), I'd prefer something supporting that.

If anyone has any ideas, it'd be greatly appreciated.

Free J2ME .jar mp3/ogg player?

Reply #1 –
You haven't mentioned the actually used ID3 versions so far. Did you use the ID3v2.3 or the industrially unpopular ID3v2.4 format to tag the files? If it was the latter, then the issue would be clear: The phone tries to read the ID3v2.4 tags and fails at the attempt, without falling back to the ID3v1 ones. My K610i behaves the same way, converting the character encodings to ID3v2.3 fixes the problem. MP3tag can do that. Simply set the default MPEG encoding to ID3v2.3 ISO 8859-1, select the whole MP3 collection and save all tags via the context menu.

If you used foobar2000 to encode the collection, then it was most likely tagged with ID3v2.4 due to the converter writing this version by default. Otherwise, MP3tag displays the tagging format in the file properties, though it doesn't differ between ID3v2.3 ISO 8859-1 and UTF-16. Due to poor implementations, unicode tends to be a bit troublesome with some hardware devices as well, though it's part of the 2.3 standard.


This is the only solution that comes to my mind. I don't know of any possibilities to get Vorbis working in this case.

Edit: Bleh, grammar!

Free J2ME .jar mp3/ogg player?

Reply #2 –
Dude; I cannot describe how much I love you right now. Though I'm on Linux, I got Mp3tag working fine in Wine, and it worked a treat. Turns out it was tagged as 2.4 before; now it works great. Thanks man!

Free J2ME .jar mp3/ogg player?

Reply #3 –
Quote from: MenZa on
Though I'm on Linux, I got Mp3tag working fine in Wine.

Doh! In this case EasyTag or Kid (KDE) would have done the job as well. EasyTag is the one used by myself to get rid of compatibility issues caused by Amarok, which uses TagLib (an ID3v2.4 writer) for its ID3 tagging.

Edit: Just noticed that the packet's name is kid3, not kid. But easytag looks better to me anyway, though they're both by far not as advanced as MP3tag.

Free J2ME .jar mp3/ogg player?

Reply #4 –
I've actually tried using both; and the 2.4 encoding was done with Kid3. EasyTag seems rubbish, and though Kid3 was set to 2.3 (libid), Mp3tag read it as ID3v2.4.