Alpha 4 Bugs/Comments

GSV3MiaC · Post by **GSV3MiaC** » Mon May 07, 2007 10:45 am

Teknojnky wrote:
mgillespie wrote:Bug: If I Terminate the Analysing Volume task from the task bar, it keeps coming back....
You have to uncheck auto analyze files with missing analysis.

This feature should be off by default (IMO).

But as far as I can see it is auto-analysing files which DO already have volume levelling data stored in the tags (at least the data shows on the track list already). These are .ogg files in my case.

Teknojnky · Post by **Teknojnky** » Mon May 07, 2007 11:26 am

You may need to enable a detail column for album volume as alot of my files are not picking up the album volume level (as calculated by dbpoweramp r12).

-----------------------------

Not really related to the above, but while I am still re-scanning my entire library (800ish gigs), thus far alpha 4 has not crashed or locked up yet. Alpha 3 was pretty much unusable due to scanning/freeze ups, but A4 is humming right along.

I look forward to using alpha 4 alot more in the coming days.

o.k.r · Post by **o.k.r** » Mon May 07, 2007 12:38 pm

Alpha4 only finds 270 of my 1546 .m4a files and only 7 of my 46 .wma files when building the new library. No new files found on second rescan.

All mp3 files detected

nojac · Post by **nojac** » Mon May 07, 2007 2:35 pm

o.k.r wrote:Alpha4 only finds 270 of my 1546 .m4a files .....

Same happened to me. Less than 25% of over 1 000 m4a files found...

Edit: Have sent a sample file to Jiri (see below)

Post by **jiri** » Mon May 07, 2007 3:04 pm

Try to e-mail me a file that isn't scanned by MM.

Thanks,
Jiri

dsavereide · Post by **dsavereide** » Mon May 07, 2007 6:02 pm

It only scanned about 285 out of over 6600 when I first started it up. Then I cleared the library and it only scaned one album... which alphabetically is the third artist's first album. (c:\music\artist\album). Note, this is selecting c:\music and then unclicking two sub-directories.

When I specially pick one directory to scan, it doesn't pick anything up.

Then I rescanned the main directory without unchecking any subdirectores and I'm back to the original 285 tracks. Seems to be a fair number of albums, but quite a few only show one or two tracks. I don't see any pattern there.

Whether or not it picked up the album art seems random... I do have pictures for most of my albums. Showing less then half of them now.

----edit---
sent you a file.

robjeeves · Post by **robjeeves** » Mon May 07, 2007 6:08 pm

hi Guys - Think this has been around a while so apologies if it's being dealt with. When I press sync button to sync with my iriver E10 the mouse flashes really fast while Preparing to Sync. not a big drama but annoying

Rob

Diabolic-Destiny · Post by **Diabolic-Destiny** » Mon May 07, 2007 7:18 pm

Teknojnky wrote:
mgillespie wrote:Bug: If I Terminate the Analysing Volume task from the task bar, it keeps coming back....
You have to uncheck auto analyze files with missing analysis.

This feature should be off by default (IMO).

agreed

Teknojnky · Post by **Teknojnky** » Mon May 07, 2007 10:12 pm

The problem mentioned here:

Using dbpoweramp r12 I can scan/apply replay/album gain tags to selected files.

If I use MM to scan/apply replay/album gain tags, these tags will be different than what R12 indicates.

When I scan with R12, these gain setting ARE seemingly read by MM but they are different than what is calculated by MM.

Specific example:

Track A with MM tags: album gain: -4.92, track gain: -6.37, track peak: 1.000000 dB

Track A with R12 tags: album gain: -4.94, album peak: 1.133841, track gain: -6.4, track peak: 1.117101

Track A with Foobar 0.9.4.2 tags: album gain: -4.94, album peak: 1.133841, track gain: 1.11701

The MM generated tags is missing the album peak, and the track peak ALL of them are 1.000000 dB.

edit: I cleared all tags and rescanned a copy of this album files with foobar and added the results above. Foobar and R12 calculated and wrote the same tags.

Is still the same.

While MM does not appear to lock up during the add/rescan by itself, if anything modifes files (outside of MM3) in a monitored folder, MM3 A4 will freeze up.

I've submitted a couple of the error logs during the freeze up, hopefully that is sufficient info.

Post by **jiri** » Tue May 08, 2007 4:18 am

Bug: Global Hotkeys can't be disabled

I guess that you haven't pressed the Apply button, right?

Jiri

Post by **jiri** » Tue May 08, 2007 4:20 am

Bug: Automatic Volume Analyzing doesn't really work for mpc-Files. The Thread stops without any message. Manually Analyzing still works.

Please e-mail me such a file.

Thanks,
Jiri

Post by **jiri** » Tue May 08, 2007 5:06 am

Using dbpoweramp r12 I can scan/apply replay/album gain tags to selected files.

If I use MM to scan/apply replay/album gain tags, these tags will be different than what R12 indicates.

When I scan with R12, these gain setting ARE seemingly read by MM but they are different than what is calculated by MM.

Specific example:

Track A with MM tags: album gain: -4.92, track gain: -6.37, track peak: 1.000000 dB

Track A with R12 tags: album gain: -4.94, album peak: 1.133841, track gain: -6.4, track peak: 1.117101

Track A with Foobar 0.9.4.2 tags: album gain: -4.94, album peak: 1.133841, track gain: 1.11701

The MM generated tags is missing the album peak, and the track peak ALL of them are 1.000000 dB.

edit: I cleared all tags and rescanned a copy of this album files with foobar and added the results above. Foobar and R12 calculated and wrote the same tags.

It's based on differences in how the Track Peak is calculated - MM uses the final values that go to sound card (I'm simplifying a little here) and there certainly Track Peak can't be >1. Foobar uses internal data from mp3 decoding process and there samples can be >1. I.e. it isn't a bug in either application. In order to avoid conflicts in this area, it's good idea to either:
- Directly rip/convert track to mp3 using leveling, i.e. prevent streams where max sample goes to 1.
- Apply volume leveling to already created mp3 tracks in order to decrease gain of such tracks.

Jiri

Big_Berny · Post by **Big_Berny** » Tue May 08, 2007 5:28 am

@jiri: But isn't it correct to use the internal value? Because if the volume is decreased by replaygain with Foobar the track peak will be 1.05 instead of 1.1171 for example, but with you method it stays the same (1.0).

I just think that MM also sould use the standard methods and I'm quite sure that's Foobars method is correct since it's used by a lot of (technical) audiophiles.

And by the way: Isn't that 'internal' track peak used anyway for the clipping-protection?

Big_Berny

GSV3MiaC · Post by **GSV3MiaC** » Tue May 08, 2007 5:38 am

GSV3MiaC wrote: Back to MM 3.0 - I got an error 5 'file in use, can't be replaced' error on decoder.exe and in_vorbis.dll. I had un-installed the old 3.0 version, but maybe I needed to log off, reboot, or sacrifice a couple of goats??

OK this was fixed by logging the user off, logging bck on, and then doing the upgrade. Obviously those files were still open somewhere in explorer for some reason. (Win XP Home, SP2).

GSV3MiaC · Post by **GSV3MiaC** » Tue May 08, 2007 5:39 am

MM lockup (this was with Alpha 4, iirc) - if I ask MM to 'delete from library and disc' a bucnh of files, some of which are not actually on the disc (have been deleted outside of MM) the program locks up.

It did send an error report (somewhere - not m$oft, as far as I could see) so maybe you already have the date?

Alpha 4 Bugs/Comments

Flashing mouse cursor