# \[X\] WAV tags saved by Mp3tag v2.83i default config fails to show in MediaMonkey V4.1.3.1708

**URL:** https://community.mp3tag.de/t/x-wav-tags-saved-by-mp3tag-v2-83i-default-config-fails-to-show-in-mediamonkey-v4-1-3-1708/19238
**Category:** No Bugs
**Created:** [August 17, 2017, 8:28pm UTC](https://community.mp3tag.de/t/x-wav-tags-saved-by-mp3tag-v2-83i-default-config-fails-to-show-in-mediamonkey-v4-1-3-1708/19238 "2017-08-17T20:28:00Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [August 17, 2017, 8:28pm UTC](https://community.mp3tag.de/t/x-wav-tags-saved-by-mp3tag-v2-83i-default-config-fails-to-show-in-mediamonkey-v4-1-3-1708/19238/1 "2017-08-17T20:28:00Z")

</div>

If I take a file made by GoldWave with WAV tag that shows fine in MediaMonkey V4.1.3.1708 and save it in Mp3tag v2.83i (with default config), the tag fields fail to show in MediaMonkey.

Mp3tag v2.81i - OK  
 ![](http://i.imgur.com/Rwpt0zy.png)

Windows 7 Explorer - OK  
 ![](http://i.imgur.com/RxlUFGP.png)

MediaMonkey V4.1.3.1708 - faulty  
 ![](http://i.imgur.com/X82zDkN.png)

FooBar 2000 - OK  
 ![](http://i.imgur.com/Vgrcgmc.png)

Hex compare

 ![](http://i.imgur.com/WvVgbCB.png)

I tried working around by changing the config inc. Mp3tag Options Tag Mpeg despite that Help says this should not affect WAV, and I got a result that didn't show the problem and had a different encoding:

 ![](http://i.imgur.com/syD4PLr.png)

but I was unable to reproduce this workaround.

Can anyone suggest what Mp3tag settings will workaround this?

UPDATE - see separate message, to workaround this forum's 'Sorry, but you have posted more images than you are allowed to'.)

---

_[View the full topic](https://community.mp3tag.de/t/x-wav-tags-saved-by-mp3tag-v2-83i-default-config-fails-to-show-in-mediamonkey-v4-1-3-1708/19238)._