version 5.05.2695 I Rip convert a flac to an MP3. Getting a dup .xxxxxx everytime

OK, have been wary of installs since my last experience with 1469 seemingly losing my DB (went to a mm subfolder instead), but will get the current debug version installed when I next have some ripping to do.

I think the main source of the problem is that the temp file (xxxxxx) isn't being released to be removed and returned to the normal MP3 extension file. This is often caused by other applications like Backup or Security software. You could create a debug log (step 4b) which may provide the developers more insight as to why you see this and send it to support: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

Same problem here, cropped up with MM V4 releases 1459 and 1461. When ripping CDs as MP3s, every so often a file turns up that has a filename.mp3.xxxxxx extension. It is listed correctly (ie no xxxxxx extension) in the library listing, but an attempt to play it turns the file grey in the library list. Simply going to Windows Explorer (whilst MM is running) to remove the xxxxxx extension fixes the problem, with MM ungreying the file straight away (file monitor is set to continuous). It is possible that I had other processes running at the same time (eg IPod synch), but I didn't have any such problem with that concurrent activity in MM V3. Should I change the process priority for MM as has been suggested in some other posts?

I haven't seen this reported. It could be your security software causing this issue or a rights issue. If you can't figure out if either of these 2 are at fault you can try creating a debug log as described in the Bug Report forum.

I am using version 3.0.7.1191

wcndave wrote:Did anything ever happen to sort this out?

This is no longer a know issue that I'm aware of. What version of MediaMonkey (Help > About) are you using?

Did anything ever happen to sort this out?

I keep getting about one file in 10 not being able to be written to, and was causing my headache until i saw that i had the XXXXX file still there.

just renaming back to mp3 seems to work, however i have to reboot my machine each time to do that!!

OK, I updated to the latest beta and I can actually see what's going on. It's related to album art. I keep one eye on MM and one on Windows Explorer and can see the .xxxxx file being created and then deleted again as the album art gets tagged to the song. This process is now taking a very long time, and that's where the trouble lies. Basically, some MM process or other is stopping before the tagging is complete, leaving an .xxxxx file. The odd thing, though, is that it always seems to stick on the same song - in other words, if it failed on a song once, rebooting and trying again causes it to stop again.
If I wait eventually all tagging appears to finish now, but it takes upwards of about 15 mins to tag, and it's not as if I have a slow pc.

Very curious.

Lowlander wrote:The .xxxxx is a temporary file that MediaMonkey creates when you make changes to a file like editing tags. In your case MediaMonkey is not able to make the edit, thus the .xxxxx file remains and your file isn't updated.

Do you have this issue only on one (or few files) or on all files? First make sure your files aren't read only if that's not the case you could try creating a debug log and send along a small file that can't be edited.

Cheers. It just happened again, actually. Can't delete the mp3 or the .xxxxx file unless I reboot. How can I view an error log?
edit: ok, I've found out how to do it. I'll send one!

The .xxxxx is a temporary file that MediaMonkey creates when you make changes to a file like editing tags. In your case MediaMonkey is not able to make the edit, thus the .xxxxx file remains and your file isn't updated.

Do you have this issue only on one (or few files) or on all files? First make sure your files aren't read only if that's not the case you could try creating a debug log and send along a small file that can't be edited.

cheers for the reply, NH, I'd already seen them though. I can only assume that either Monkeyrok counts as a 2nd app (logical, in a way, I suppose) or...well, tehre is no or that I can think of
I'll do more testing.

Sorry, I don't know much about it, but see these related posts:

http://www.mediamonkey.com/forum/viewto ... lit=xxxxxx
http://www.mediamonkey.com/forum/viewto ... lit=xxxxxx
http://www.mediamonkey.com/forum/viewto ... lit=xxxxxx

apologies, a shameless bump

I've been having a problem lately with MM, and can't figure out what's causing it.
When using 'autotag from the web', or when synching to my ipod, a new file is created in my folder with the same name as the original mp3, but with the extension .mp3.xxxxx. MM will not complete the task, and cannot be closed, either normally or in Task Manager processes.
I did some testing and can only delete this rogue file after a reboot. However, when attempting the task again (either tagging or synching) it fails on the same mp3, so it's a problem with the file itself.
I did a forum search here and the only things I can find are that this can happen if two apps are using the file at the same time, and that it was fixed in MM2. I'm using 3.03.166 and not using any other apps, unless MonkeyRok counts. One other post suggests that I check ID3v2 in Options, but mine are set correctly. I tried reinstalling, and deleting the database, but the problem persists.
This has happened four times now. Has anyone else been having this problem?