1249: error tagging files in folder

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: 1249: error tagging files in folder

Re: 1249: error tagging files in folder

by andig » Tue Jun 09, 2009 1:36 am

Finally! Together with some problems with iPod Sync this is _the_ most annoying problem I've had with the otherwise excellent MM. Please let me know if you need more tracks for testing...

Re: 1249: error tagging files in folder

by rusty » Mon Jun 08, 2009 3:11 pm

Andig,

Thanks--I was able to replicate. Tracked at:
http://www.ventismedia.com/mantis/view.php?id=5746

-Rusty

Re: 1249: error tagging files in folder

by andig » Mon Jun 08, 2009 3:19 am

Can still replicate in 1251. However, this does not affect all tracks, only some. I've uploaded sample track to http://videodb.net/track.mp3

Please download, change track# (using F2 in track list), refresh folder (F5) -> track# is gone again.

Re: 1249: error tagging files in folder

by Bex » Sun Jun 07, 2009 2:18 pm

Cant replicate either..

Re: 1249: error tagging files in folder

by nohitter151 » Sun Jun 07, 2009 2:09 pm

Hm, not replicable here in build 1251.

Re: 1249: error tagging files in folder

by andig » Sun Jun 07, 2009 7:30 am

The issue had previously been posted here http://www.mediamonkey.com/forum/viewto ... 38#p169538 the solution using (library node instead of computer node) is not solution.

1249: error tagging files in folder

by andig » Sun Jun 07, 2009 7:28 am

Problem: mm is apparently unable to edit id3 properties. This has been observed on multiple files.

1) select hd folder, change track# on single file (sofar empty)
2) -> file list is updated with track#
3) refresh folder
4) -> track# is empty again
5) show file properties -> tack# is indeed empty

Debug log (inconclusive): http://videodb.net/mm_tag.log

This is a real annoyance- especially as the problem is not apparent at first. Any chance investigating this (longstanding) issue for 3.1?

Top