[1476] some tags disappear / coloumn browser is buggy

Beta Testing for Windows Products and plugins

Moderator: Gurus

Posts: 190
Joined: Wed Jun 18, 2008 1:43 pm
Location: berlin

[1476] some tags disappear / coloumn browser is buggy

Post by heartofhate » Tue Feb 28, 2012 3:29 am

since i have updated to version 4.0.3 i have got a few weird things:
on the MM startup the coloumn browser won't load every artist and sometimes it will jump to one artist with no reason (mostly Rainbow). since i use the coloumn browser often this behauviour is really annoying.

also MM will just delete some tags of some files (at least they do not show up when i restart MM). this happened only twice to me.
the funny thing is that the tags are still there when i go to the properties.

Posts: 45790
Joined: Sat Sep 06, 2003 5:53 pm
Location: MediaMonkey 5

Re: [1476] some tags disappear / coloumn browser is buggy

Post by Lowlander » Tue Feb 28, 2012 11:24 am

1) I can't reproduce. Tried several times on different nodes in the Location node and it opened the Column Browser each time and showed all items.

2) My Computer node, Now Playing node/window or a Library node? I haven't seen missing tags before.
Lowlander (MediaMonkey user since 2003)

Posts: 80
Joined: Wed Jul 04, 2007 6:56 pm

Re: [1476] some tags disappear / coloumn browser is buggy

Post by kookykrazee » Sun Mar 18, 2012 2:10 am

I have recently noticed this, too. The files all come from the same base folder with many subfolders. My setup is:

Drive://#Media/Shows And Demo/Decade/Year/Files

Files are in bunches and singles, all mp3 format, all have been tagged, over the years of collection, yet I have literally thousands of tracks that, to some extent, I have retagged over and over again. I just can't put a finger on why they are doing this.

Posts: 7172
Joined: Tue Apr 29, 2003 3:39 am
Location: Montreal, Canada

Re: [1476] some tags disappear / coloumn browser is buggy

Post by rusty » Tue Apr 24, 2012 10:02 am

Update: heartofhate indicated to me via PM that the problem resolved itself after a clean re-install.
(not to say that there isn't a bug, but rather that a workaround may be a clean install).


Post Reply