Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[J-Ro]

Ok, the following was an issue that kept me busy most of the night. I'd appriceate any help anyone can provide.

Yesterday I installed (fresh after uninstalling and deleting Library files) MJ 8.0.336 and re-imported all of my 23Gb MP3 library. I then went to listen to an album and in the Album tree view and there was only one track of 18 (track 15 coincidentally). Posted my what happend and JimH suggested looking by location and low and behold they were there. Apparently the tags were not imported and the files were tagged with the file name.

I looked through the rest of my files and approximately 30% of them had similar problems. Either no tag info was imported like above or one or two of the fields was missing, most frequently the genere field. I repeatedly attempted clearing the library and re-importing the media with no success.

After further inspection I determined that the majority of the problems were with files encoded using Windows Media Player. Although most files created with WMP had no problems it seemed that some of them were missing info.

After a couple hours inspecting changing and removing ID3(v1 & v2) tags I decided to revert to MJ 8.0.351. Guess what, problem solved. All tag info is where it should be and imported perfectly.

So by the process of deduction can I confidently say that this is a bug?

Let me know

[JimH]

Could be a bug, but not likely.  More likely is a difference in how programs handle tagging.

Try a search here for tagging and then a search on google for ID3v1 and ID3v2 tagging.

The ID3v2 library was also recently updated in MJ.  It comes from a 3rd party.

[Mirko]

I can add a "bug":

If there are ID3-Tags 1 and 2, MJ chooses the version 1 I think, because some long titles are cut ("..") off. To my knowledge, the title-field ist 32byte in length in version 1. But this should not be a problem in v2?

Anyway. I also have to manually update the imported files. But it's not really an issue...

[KingSparta]

ID3v1 Tag Limits Are 30 Chrs

Id3v1.1 Limits The Comment Field To 28 Chrs, This Is Due To The Added Track #

With Id3v2 There Really (In A Way) Is No Limit In Size. Some Programs May Limit The Imput From the User however.

[J-Ro]

I think it's important that I restate something.

The tags are imported correctly in 8.0.315 and are not in 8.0.336..

I have tried this more than 5 ways, including fresh MJ installs and fresh XP installs. It seems that when the only variable is the version of MJ is when the problem occurs.

J

[Nikolay]

J,

We will try to reproduce this problem.  We switched to new version of ID3 library in build 8.0.323, so that might be the problem.

Nikolay

[KCComp]

This problem majes MJ useless to me.  It happens on almost all files where the artist is >30 characters in MP3v2 format, e.g. "Stevie Ray Vaughan and Double Trouble".

KC

[JimH]

> where the artist is >30 characters in MP3v2 format

That sounds like a problem with ID3v1 vs ID3v2 tags.  May or may not be a bug in the tagging library.

[J-Ro]

Again I'd like to restate that this behavior is only exhibited in 8.0.336 and is not a problem in 8.0.315 or 8.0.318.

[hottuna]

I upgraded to 336 today and found that the update speed of tags had deteriorated to the point of being useless. The first time this happened to me it was when I was using id3v2 tags, even after I turned them off the problem remained this time.

When I reverted to 8.0.320 the problem disappeared.

[rar2667]

I'd like to chime in that after upgrading to build 336, when I try to manually change info in tag, I get "MJ failed to update tag...".

I checked the Option setting for enabling tagging and it was on. Nothing else had file in use and I checked the read-only flag.

Could this be related to the new tagging lib?

[Rob Marques]

Well, I might as well add that I am experiencing "minor glitches" in tagging my mp3 library. I receive errors with "unable to update tags"...blah blah blah, file may be read only or tagging may be turned off, etc. The actual TAG is updated, but what ISN'T updated is file renaming. I have just been manually renaming the affected file in question. This also happened to me today, and after receiving the error I checked to see what wasn't changed so I could manually do the rest. What perplexed me is that everything was done, tags were updated and files were renamed... the error was totally random...

I use build 336 as well.

Speed doesn't seem to be an issue with me on my 1.2Ghz Athlon w/ 384Mb RAM.

As a side note, Someone mentioned WMP. I have had HUGE problems in the past with files tagged in Winbloze Media Player in the capacity that other apps wouldn't properly read the tags, tags not being written, etc. That was one of my major reasons for wanting to get away from it besides the HORRIBLY slow encoding algorithms. That and the library management just plain sucked. =O

Anyway, keep up the good work on the updates. MJ has well been worth my investment.

Rob

[JimH]

This should be fixed in the 8.0.343 build:

http://www.musicex.com/cgi-bin/interact/NeoBoard.pl?Action=ShowPost&Board=inter&Post=12778

It had to do with the new library reporting an ID3V2 tag was there, even if the tag was empty.