MMSaTe [4125]

by **rusty** » Tue Jun 12, 2012 8:19 am

Hi wick3dsentinel,

I can't replicate the mmsate issue--tried ripping to flac and other formats, + tagging.

Does it always occur for you? Is it specific to a particular CD? What are your ripping settings?

btw, is it possible that these files are from an earlier version of MM ?

Thanks.

-Rusty

by **wick3dsentinel** » Sat Jun 09, 2012 11:09 pm

I'm having the same issue when ripping a cd to flac and I am running 4.0.5.1496.

by **Peke** » Tue Mar 16, 2010 9:59 am

Depends on Audio format, but in the end it would be more than you can listen (fully) in next 10 years (with lossless little less).

1h of MP3s is <100MB * 10 = 1GB * 2000 = 2TB = 20000h+ of non-stop playback (which is around 2.5 Years of playback)

by **active** » Tue Mar 16, 2010 5:22 am

Buck wrote:Count me as another user discovering a bunch of these in my music directory. Can't say when this happened, but I am running 3.2.0.1294. I'll delete these if I can and see if more pop up later.
Thanks
Buck
(maybe I didn't need to buy that 2TB hard drive? - Oh yes, oh yes I did! )

*EDIT*
OK, I believe that I ripped these files at least 2 years ago. It could have been with a beta version. I don't know for certain. After doing a search for mmsate files on my hard drives, I didn't find as many as I thought and again they were ripped a long time ago.
Buck is shutting up now.

Later

How many minutes of audio can fit on a 2TB hard drive?

by **Buck** » Wed Jan 13, 2010 9:24 pm

Count me as another user discovering a bunch of these in my music directory. Can't say when this happened, but I am running 3.2.0.1294. I'll delete these if I can and see if more pop up later.
Thanks
Buck
(maybe I didn't need to buy that 2TB hard drive? - Oh yes, oh yes I did!

)

*EDIT*
OK, I believe that I ripped these files at least 2 years ago. It could have been with a beta version. I don't know for certain. After doing a search for mmsate files on my hard drives, I didn't find as many as I thought and again they were ripped a long time ago.
Buck is shutting up now.

Later

by **Karmapowered** » Mon Dec 28, 2009 3:25 pm

I seem to have the exact same issue.

Is there a setting that I can change to prevent this from happening, or is this still a bug (since 2007, date of the first message in this thread) ?

EDIT : I am using MM version 3.1.1.1261 - Windows XP Home.

by **WarGod** » Sun Dec 27, 2009 8:48 pm

I am running version MM 3.2.0.1294 and just experienced the same problem where files are named with a .MMSate file extension. I installed the MediaMonkey_AAC_Plug-in_1_0_6.exe to rip Audiobooks using the M4B format.

Of several thousand files converted, only one file showed up with the MMSate file extension. The MMSate file appears to be a duplicate, but it can't be deleted without rebooting.

by **gab** » Wed Dec 26, 2007 12:53 pm

Thanks for the update Jiri.

If anyone has ever had an issue where a large number of tracks being rendered unplayable (file sizes shrunk down to almost nothing) I'd appreciate it if you would respond to this thread. I don't know what happened but I lost over 1,000 tracks and the only thing that I recently did was add album art with MM.

by **jiri** » Wed Dec 26, 2007 10:38 am

No, there wasn't any such problem of damaged tracks reported or fixed in any of 3.0 pre-release versions. The only problem fixed was with that MMSaTe files (which wasn't really dangerous though, they were just duplicates that weren't removed properly).

Jiri

by **gab** » Tue Dec 25, 2007 11:18 am

Rusty -

Unfortunately I can't give you any steps other than I tagged the files. Although on further thought I'm not 100% certain it was RC5 that's my recollection.

Just to confirm however, prior to RC5 the issue with the files being destroyed (shrunk in size) was occurring?

gab

by **rusty** » Mon Dec 24, 2007 4:03 pm

gab,

We've not been able to replicate the problem you describe in RC5, though, both problems that you describe did exist in earlier builds.

What makes you so certain that the problem was introduced by RC-5? Can you give any steps to reproduce the problem?

Thx.

-Rusty

by **gab** » Mon Dec 24, 2007 10:26 am

Any comments on this? At this point I've stopped using MM because of the issues described in my previous post.

by **gab** » Sun Dec 23, 2007 1:18 pm

A few additional points on this issue:

(1) These files were created on my system even though i did no conversions. Just tagging files

(2) Although I can't prove a direct link, I believe some of my original files were damaged in the process. I have about 1,000 files that now are unplayable (they have shrunk in size from 4-5 MB to 40 - 80 kbs). I can't prove a direct link however all of this happened after I tagged the files with MM.

(3) I did all of the above with RC5

(4) I also had some files created with "XXXX", not MMSate, as an extension.

gab

by **rusty** » Mon Dec 17, 2007 12:47 am

Note that this is fixed in RC5. If you've used RC4's conversion/auto-conversion functionality much, you'll probably have a few MMSaTe files scatterred around your system. You should do a Desktop Search to find them and delete them.

-Rusty

by **blubb** » Sun Dec 16, 2007 3:57 pm

Just stumbled over this bug by myself and therefore I hope the fix comes soon--cause this bug is kind of annoying ^.^

Looking forward to it.

MMSaTe [4125]

Post a reply

Expand view Topic review: MMSaTe [4125]

Re: MMSaTe [4125]

Re: MMSaTe [4125]

Re: MMSaTe [4125]

2tb hard drive

Re: MMSaTe [4125]

Re: MMSaTe [4125]

Re: MMSaTe [4125]

xxxx and mmsate

MMSaTe fix

Looking forward to it ...