You're welcome, hopefully you'll be able to get it resolved.

Nyn

[quote="nynaevelan"]I am running Vista [/quote]Ah. That's more than sufficient to explain the difference.

I think I've now isolated the cause and will file a bug report.

Many thanks for your help Nyn.

[url]http://www.mediamonkey.com/wiki/index.php/Media_Monkey_fails_to_update_tags_for_.wma_files[/url]

Check out this knowledge base article [url=http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=92&nav=0,5]WMA Tracks can't Play, Tag, Burn, or be Analysed[/url] as it seems to apply. I don't know which minimum version of WMP MediaMonkey requires.

[quote="chrisjj"]

Nyn, does your succeeding installation by any chance have an upgrade of Windows Media codecs, e.g. have you installed Windows Media Player 10 or 11? E.g. Add/Remove Programs shows Windows Media Format Runtime 10 or 11.

(My failing installation is plain WinXP SP2, having Windows Media Player 9.)[/quote]

I am running Vista and it came pre-installed with WMP 11 and I have no way of uninstalling it and nothing shows in Add/Remove Programs.

Nyn

> How can we determine the cause of our different results?

I find this failure does not occur on MP3 or FLAC, just (so far) WMA.

Nyn, does your succeeding installation by any chance have an upgrade of Windows Media codecs, e.g. have you installed Windows Media Player 10 or 11? E.g. Add/Remove Programs shows Windows Media Format Runtime 10 or 11.

(My failing installation is plain WinXP SP2, having Windows Media Player 9.)

It's probably best to create a debug log and send it together with the file. The log might show why this is happening.

> I followed your instructions for everything except the 1190 part, I used 1209.

Thank you. I have just repeated using 1209 and I get the same failure.

> are you sure these files are not write-protected?

1) Mp3tag makes tag edits fine 2) The Read-only status is unchecked.

How can we determine the cause of our different results?

Ok:

Just went and installed 1190 and re-ran test and I am still able to save changes to wma files prior to making any options adjustments. As Lowlander asked, are you sure these files are not write-protected? Does the same thing happen in any of the 3.1 betas?

Nyn

I followed your instructions for everything except the 1190 part, I used 1209. I will reinstall 1190 to confirm if you wish.

Nyn

> there is no need to be curt or rude.

Sorry Nyn, there was no intention to be curt or rude. Just to eliminate the doubt from ambiguity in your statement. I do appreciate your time.

> I mean if I have the update checked then the tags are saved

That's clear - thanks.

> And I did try it first with the default installation and no changes

So (again for avoidance of doubt), you followed the steps I gave, using a fresh default installation of 1190, and including using that particular WMA file?

On 3.1.0.1212 it also saved the tags for me.

[quote="chrisjj"]> It works as it should in 3.1.01209 as long as "update tags when editing properties" is checked

"update tags when editing properties" is checked, since (as I said) this is a default installation.

Are you saying the reported behaviour is "works as it should?"[/quote]

You know I am taking MY time to try to offer you assistance, there is no need to be curt or rude. Now with that said, I mean if I have the update checked then the tags are saved, if I do not have it checked the tags are not synced and the tracks are located in the unsynced node. And I did try it first with the default installation and no changes, I chnaged the options to see if it made a difference, which it did.

Nyn

Yes, when tested in 1209 nynaevelan is reporting that the files tags get updated correctly. This is why I asked if you tested in the latest beta as you have been testing those. As the beta's have improvements, bugs found in old versions might already have been resolved so if you have the beta version installed it's best to test with that to prevent reporting fixed bugs.

> It works as it should in 3.1.01209 as long as "update tags when editing properties" is checked

"update tags when editing properties" is checked, since (as I said) this is a default installation.

Are you saying the reported behaviour is "works as it should?"