View Issue Details

IDProjectCategoryView StatusLast Update
0002431MMW v4Properties/Auto-Toolspublic2006-04-06 19:29
Reporterjiri Assigned To 
PriorityurgentSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version2.5.3 
Summary0002431: Max Sample not stored in APE tags
DescriptionThere is reported in http://www.mediamonkey.com/forum/viewtopic.php?t=8893 that max sample isn't written in APE tags, I'm not sure if it's true.
TagsNo tags attached.
Fixed in build963

Relationships

related to 0002434 resolvedjiri Peak value not stored in MPC tags 

Activities

jiri

2006-03-19 20:10

administrator   ~0007079

Assigning to Peke for a review.

jiri

2006-03-20 11:48

administrator   ~0007082

I just checked the sources, and it's indeed true, max sample isn't stored in file, although its reading would probably work fine. Here is the problematic source code:

FF_RGTrackPeak : Result := FE_FieldUnknown;


I also found that the same problem is there for MPC files.

rusty

2006-03-23 19:38

administrator   ~0007089

fyi, here is what the user mailed me. I've also posted his sample .ape file to the ftp server.

Hi,
 
This is a short APE file to show the problem as described in the "Volume leveling of APE files on Add/rescan" thread in the bug report section.
 
I posted the following detailed description there about volume leveling information getting partially lost on Add/Rescan due to the MaxSample field not being set in the DB.
 
Abel
 
Just to recreate the problem I did this:
 
- took a WAV file clip of about 5 seconds of an audio file that is about 7 db too loud
- compress it to APE (see attached file) with Monkey's Audio 3.99 (windows gui)
- clear my MediaMonkey database
- add/rescan that single file to MediaMonkey
- verify that it played too loud and obviously does not have volume leveling information
- Analyze Volume for that track
- verify in the library window that the leveling info is there (-6.8 db)
- verify that the leveling info is there on the properties>Info page of the file (also shows -6.8 db)
- play the file to verify that it's volume gets levelled (correct)
- clear the library
- add/rescan the single file again
- verify that leveling info is in library table (shows correct as -6.8 db again)
- verify that leveling info is not there in properties>info page for the file (shows as Not Calculated)
- play the file to verify that volume is too loud (and that volume leveling switch has no effect)
 
Some additional remarks:
- "Clipping prevention" setting has no effect on this problem
- "Only analyze tracks with unknown leveling Adjustmen" setting has no effect on this problem
- So far the only thing that fixes it afterwards is "Analyzing Volume" again after add/rescan or to manually set the MaxSample field in the DB to non-zero.
 
Hope this helps to clarify the problem.
 
Abel

peke

2006-03-23 20:52

developer   ~0007090

Due to some none sync. versions between SVN and My own sources and APE was made before I got access to SVN (I think) I never updated/sync it.
SVN Version was out of date (v0.9.3 RC2). Now I updated it to newer version ASAP as Talked with Jiri on IM.

Plugin version info:
 Version : v1.0.0 (Some optimization to Code, Added More Compatibility in reading Standard Track Gain and Track Peak values, Changed writing of Track Gain and Track Peak to Footbar2000 format to support more Compatibility)
 History : v0.9.3 RC2 (Changed UTF-8 Encoding/decoding to Standard Delphi Functions, Some Code optimization)

jiri

2006-03-23 21:04

administrator   ~0007091

As far as I know APE should work fine now, but is also MPC fixed?

Assigning back to Peke for a clarification...

peke

2006-03-23 22:58

developer   ~0007092

APE File is fixed, due to different nature and reading of gain and peak value in MPC I Recreated it in BUG 0002434

jiri

2006-03-30 18:38

administrator   ~0007099

Setting as resolved in build 963.

rusty

2006-04-06 19:29

administrator   ~0007124

Verified 2.5.3.952.