Peke wrote:If that is right (I guess it is) there is a bug somewhere. Investigating thx.

Any result, Peke?

you can change that behavior at @ tools > options > library > infer track properties

Not sure if this is related but I had a similar problem. It turns out I was using EAC to generate the wav files and I had the option to automatically generate m3u files turned on. It looked like MM was using the data from the m3u files rather the tags and would ignore changes to the tags that were made by hand. I moved all the auto generated m3u files out of folders that contained the music files and the problem went away.

Sent mail with instructions.

If there's any data/testing I can do to help, let me know.

If that is right (I guess it is) there is a bug somewhere. Investigating thx.

If it's any help, here's a sample of one way (may or may not be *the* way) that the tagging affected the wav I was trying to retag to add the year.

Tags, at end of file, freshly ripped:

LIST’ INFOINAM Cowboys in Africa IART Bush Tetras IPRD Boom in the Night ISFT MediaMonkey 3.0.6 IAAR Bush Tetras itrk 1 IRVA -100

Tags, at end of file, after tagging to add Year:

LIST  INFOINAM Cowboys in Africa IART Bush Tetras IPRD Boom in the Night ISFT MediaMonkey 3.0.6 IAAR Bush Tetras itrk 1 ICRD 1995 IRVA -100 LIST  INFOINAM Cowboys in Africa IART Bush Tetras IPRD Boom in the Night ISFT MediaMonkey 3.0.6 IAAR Bush Tetras itrk 1 ICRD 1995 IRVA -100 LIST6 INFOINAM Cowboys in Africa itrk 1 IRVA -100

Or I could give you the hex, if you like...

For my part it is possible it is WMP 11 not MM. It is installed and I used to use it occasionally. I can't remember now whether the corrupted files were ripped by WMP, I guess they could have been. WMP certainly tags WAVs incorrectly as far as MM and my Sonos kit are concerned so I now avoid it.

I have what seems to me to be the same problem. Recently (last few months, possibly after an update?), I found that when I edit tags on a wav in MediaMonkey, for some wavs the changes don't persist. I can reproduce this with a particular CD I recently ripped -- I rip it in MM, info from freedb writes the tags, I select the songs, edit the tags to add the year (it's an obscure artist), and the change won't "take". (This problem can also arise when I've edited a wav in another application, I cite this particular situation because it's a MM-only scenario.) Is this something you're currently investigating? Would emailing wavs to someone be of any help? MM is my preferred music librarian, precisely because it allows me to manage my music without putting the info into a proprietary database or other external file, so this problem kind of strikes to the heart of what I love about MM.

To elaborate, this seems to be related to WMP. For more info see:
http://www.eggheadcafe.com/software/asp ... gs-in.aspx

We're looking into getting this resolved in MM for 3.1.

-Rusty

@Hovebloke
I have received your file, and after analyze it looks that your files have common issue We will try to analyze this behavior and possibly make support. BTW MM do not lose tags but MM writes correct WAVE WAVEfmt Info Chunk that is used for more than decade.

Than you for reporting this.

Thanks for all your help. I've raised a ticket and hope to get a resolution in due course.

@HoveBloke
The best way is to open support Ticket (unless you already have).

yep send one to the developers and tell them what it is for. they can find the error in the file if any.

also about the microsoft update site. that auto download for updates is only for security updates not all updates
so its a good idea to check the site once a month to see if any were put up there for your system.

I've sent some log files, I can't reproduce the initial problem again though. I still can't tag the already corrupted files so I sent a log from an attempt to do that and another from a normal, successful re-tag.

One last piece of information though. I went back to the Microsoft Update page and found an update for my RealTech NIC which wasn't in the auto-apply section. I have downloaded and updated it now. I don't think it can really be a hardware issue though because all the files are obviously broken in exactly the same way. Fortunately they all still play, I haven't lost anything and I have backups.

The problem is quite hard to reproduce evidently. If I sent in one of the already corrupted WAV files would that help you find precisely what is wrong with it? One is less than 1MB (Yep, 14 seconds long).