Nuked my database a while back and decided that it was time to re-do replay gain. Especially since it is faster.

Anyway, selected 5000+ files and it did a few fine then I get a core error message. Tried to get it to write a log file (fighting me on this right now). Cancelled the scan tried a single album, no luck, same thing. Closed fb2k and a small message window popped up. Should have screen shot it but it said something to the effect of 8000+ meta_handle leaks. Sound right?

Hm.. I've RG-scanned/tagged approx. 5000 files (mostly mp3, some mpc, flac and ape also) with 0.7.2 beta 6 just now, and it worked flawlessly for me..

What kind of error message was it ? If it was a crash, you should have failure.txt file with exact info in your foobar2000 directory.

There was no crash. It still is reporting errors, the Core message anyway. I'm trying to see if I can get the handle leak message again. If so I'll screen shot it and let you see for yourself.

edit:spelling

Is this the message you see ?

No.

What does it mean when you get that one, exactly?
I got it once, but then it said: "resync successful"


I remember a while back, some 0.7 betas had this in between some MP3 files.

That means that the mpeg (mp3) file has been corrupted in one way or another. just one missing bit, etc.. You may not hear it, but its there.. this is very typical on files downloaded of p2p neworks where they are resumed from all over the place, etc, etc..

sometimes resync is successful, sometimes not..

Installed this build over again. Errors were still popping up from core message window so I disabled the pop-up notification on errors. Not able to reproduce the meta handle leak message I had gotten earlier.

Files are marked as being R/G'd now. Don't know if this helps, but it seemed like it was always giving the error message as soon as files were being updated (adding the info to the meta-data). Had replay gain scan the files as multiple albums.

Also, is there a way to re-enable core error message pop-up without uninstall-reinstall? Maybe shouldn't have done that, but quite annoying when it was coming up with every album.

If I understood correctly, then :
components->show console->options

Thanks.

Had a thought about this today. Is there the possibility that having the tags not being written (have my reasons) when info changes cause this? It was at the end of each album when the console message popped up.

Maybe I'm grasping at straws here...

Either I'm blind or you forgot to post contents of the error message you are constantly getting. Sorry, I can't be more helpful here.

Sorry, not posting when all they say is this:

WARNING (CORE) : Verboten!
WARNING (CORE) : Verboten!
WARNING (CORE) : Verboten!
WARNING (CORE) : Verboten!
WARNING (CORE) : Verboten!
WARNING (CORE) : Verboten!
WARNING (CORE) : Verboten!

This is the only error message I've gotten lately. It occurs as mentioned above, right after album is scanned. The files do show an "A" so I am assuming that they are indeed R/G'd.

From File Info (one track):

replaygain_track_gain = -5.83 dB
replaygain_track_peak = 1.069862
replaygain_album_gain = -5.48 dB
replaygain_album_peak = 1.165489

I cannot reproduce the other.

I was asking if perhaps someone changed their configuration to not update files (tags) if that might induce the same behavior for them.

Preferences => database => uncheck "don't write modified tags to files".

So...(dumb question, beware), is this the only cure?

I didn't want to have foobar actually modify the tags. I *thought* it would just use meta-data for R/G information. And my limited knowledge of this is that meta-data is just info foobar uses internally for its database without any need to actually update the files tags.

How am I doing so far?

I (hate to admit this) do have a need for the most unsavory of tags.

ID3v2 supports ReplayGain info, but only in a proprietary manner that should not affect other software. (Unless that software is prone to removing comments with custom descriptions, which would also affect Media Jukebox RG info.)

If you need ID3v2 + ID3v1, ask Peter. If you need APEv2 in addition to those... why?


Oh wait. Speaking of removing fields that are unsupported, the ID3v2 reader cannot store unsupported picture chunks in the database, and by the time the file reaches the tag writer, the old tag has already been removed. So, of course, there is no way of preserving embedded images, unless I decide to add a mechanism for storing that mess as some text encoded string in the database.

That's the big stickler there. I'm pretty sure MC-MJ uses ID3v2 for storing its R/G info. Hence, the reason I'm reluctant to let fb2k write tags. It's either one or the other. And I have a big dislike for using MP3Gain to modify the files. Don't ask....



Yes on the first. No on the second. I did kind of bug Matt a bit to see if there is a possibilty for using apev2 tags in mp3's. Not happening this version, but not completely ruled out either.



This isn't really a concern for me. MC has the ability to be pointed at the folder images (cover art) are stored in. I never really liked the idea of an image embedded in an mp3 anyway.

I did not bother supporting MJ RG tags because their target volume is 6dB louder, and because their scanner operates on samples that have already been clipped and converted to 16 bit integers.

Are they? I thought current standard of R/G was 89db, whereas MC uses 83db. Or is it -89 & -83 making the difference?

The rest I'll trust what you say. I've heard it mentioned that MC does some screwy things with playback.

That is actually a very good point: MJ's replaygain is not compatible with other replaygain implementations, because they use custom tags and a different target volume.

I prefer the more "standard" and widespread method of foobar2000 (less chance of a "player lock-in"). And it's album gain support. Does MJ/MC support album gain yet ?

To the best of my knowledge, no.