Hi.
I'm having several issues when ripping WAV files with either Exact Audio Copy or the dbPowerAmp rippers.
In Exact Audio Copy the tags that it generates are not for the most part read correctly by Media Monkey.
Even though the Year, Album and Album Artist fields are set, they don't show up in Media Monkey. I've also
noticed that track names with colons in the track title have the information after the colon put into
some other random tag.
In dbPowerAmp all the tags show up just fine, however, if I edit a tag for a WAV file generated by dbPowerAmp
inside of MediaMonkey there is a very high likelihood that the file will be truncated to 4kb and become unplayable!!!!!!!!!!!!!!!!!!
Thanks for any help with these issues.
Issues with WAV files generated b EAC and dpPowerAmp rippers
Moderator: Gurus
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
You might want to include what version of MediaMonkey you are using that exhibits these issues.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
I'm currently using:
Windows Vista 64
Media Monkey 3.0.4.1185
dbPowerAmp CD Ripper R13.1
Exact Audio Copy V0.99 prebeta 4
Windows Vista 64
Media Monkey 3.0.4.1185
dbPowerAmp CD Ripper R13.1
Exact Audio Copy V0.99 prebeta 4
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
3.06 has been the latest stable version for quite some time, you may want to update and check to see if the issue still happens.
New script:
Last.FM Node Now with DJ Mode!
Last.fm + MediaMonkey = Scrobbler DJ!
Tag with MusicBrainz ~ Get Album Art!
Tweak the Monkey! ~ My Scripts Page

Last.fm + MediaMonkey = Scrobbler DJ!
Tag with MusicBrainz ~ Get Album Art!
Tweak the Monkey! ~ My Scripts Page

-
apb1
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
I just tried the same sequence of events and both issues are still present in 3.0.6.
For the file truncation issue I tried changing the album title and that work fine. I then tried changing the track number and the file got truncated and the music file became grayed out in MM.
For the file truncation issue I tried changing the album title and that work fine. I then tried changing the track number and the file got truncated and the music file became grayed out in MM.
-
abp
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
A bit more information about the truncation issue with files generated by dbPowerAmp. Turning off ID tag generation in dbPA does fix the truncation issue with MediaMonkey. I tried turning on tags and disabling all optional tags and truncation ensued. I tried turning on tags and disabling all optional tags, then using the DBPA tag editor to remove all the tags that can't be disabled from the CD ripper...still get truncation.
-
apb1
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
The way I found to reliably repeat the truncation error is to modify the title by adding 3 zeros, then modify the track number by adding 3 zeros inside of MediaMonkey. I have auto-sync turned on...the music file then gets grayed out and is unplayable immediately. I have a 28 Mb WAVE file that is 100% reliably destroyed by MediaMonkey when the tags are edited if there is a way to send it to someone?
-
apb1
Re: Issues with WAV files generated b EAC and dpPowerAmp rippers
I investigated a bit more and it turns out the EAC is a non-issue as it's not actually generating the tags. The random content in tags is just MMs attempt to guess the tag fields.
However, the issue where Media Monkey is 100% reliably corrupting WAV files generated by dbPowerAmp when tags are edited inside of MM is a real issue and *extremely* painful for me. It's very strange since the code for reading the WAV files finds all the tags correctly.
However, the issue where Media Monkey is 100% reliably corrupting WAV files generated by dbPowerAmp when tags are edited inside of MM is a real issue and *extremely* painful for me. It's very strange since the code for reading the WAV files finds all the tags correctly.