Bit detecting is wrong sometimes

[Majik_DS]

(21-01-2014 17:54)simoncn Wrote:  

(21-01-2014 16:43)Majik_DS Wrote:  Did you get it?

I got it and tried it. MinimServer 0.8.1 is correctly identifying this file as 24/96000. Are you by any chance using an older version of MinimServer?

How did you tested that?

[Majik_DS]

Perhaps I found one reason for this behaviour of minim.

I converted the flac tracks with dbpoweramp converter (with help from crossover) instead of Max.

Now minim shows it right. Surprisingly MP3tag shows a frequency of 30464Hz in stead of 96kHz. But iTunes and Minim shows it right now.

What I don't understand is that you wrote your minim shows the right frequency from my file ??!!

[simoncn]

(21-01-2014 18:20)Majik_DS Wrote:  

(21-01-2014 17:54)simoncn Wrote:  I got it and tried it. MinimServer 0.8.1 is correctly identifying this file as 24/96000. Are you by any chance using an older version of MinimServer?

How did you tested that?

I added extra tracing (not available in update 16), set the logging level to Trace, and forced a rescan of this file only by setting a suitable combination of the contentDir and writeAllTags properties. I also checked that this file appears in the 24/96000 index.

[simoncn]

(21-01-2014 19:16)Majik_DS Wrote:  Perhaps I found one reason for this behaviour of minim.

I converted the flac tracks with dbpoweramp converter (with help from crossover) instead of Max.

Now minim shows it right. Surprisingly MP3tag shows a frequency of 30464Hz in stead of 96kHz. But iTunes and Minim shows it right now.

What I don't understand is that you wrote your minim shows the right frequency from my file ??!!

Perhaps the metadata in your MinimServer cache is out of sync with the current contents of the file. This can happen if you update the file without changing its size or modification date. You can rebuild the cache by setting writeAllTags to any value and doing a rescan.

[Majik_DS]

(21-01-2014 21:27)simoncn Wrote:  

(21-01-2014 19:16)Majik_DS Wrote:  Perhaps I found one reason for this behaviour of minim.

I converted the flac tracks with dbpoweramp converter (with help from crossover) instead of Max.

Now minim shows it right. Surprisingly MP3tag shows a frequency of 30464Hz in stead of 96kHz. But iTunes and Minim shows it right now.

What I don't understand is that you wrote your minim shows the right frequency from my file ??!!

Perhaps the metadata in your MinimServer cache is out of sync with the current contents of the file. This can happen if you update the file without changing its size or modification date. You can rebuild the cache by setting writeAllTags to any value and doing a rescan.

No, the fault is in Max.

Every disc I converted with dbpoweramp is now correct in it's settings.

I converted the m4a files with dbpoweramp to m4a files and now everything is correct. Strange.

[simoncn]

(22-01-2014 01:02)Majik_DS Wrote:  No, the fault is in Max.

Every disc I converted with dbpoweramp is now correct in it's settings.

I converted the m4a files with dbpoweramp to m4a files and now everything is correct. Strange.

I'm glad you've found a solution now. The part that I don't understand is why the file you sent me was read OK by MinimServer.

[Majik_DS]

(22-01-2014 10:31)simoncn Wrote:  

(22-01-2014 01:02)Majik_DS Wrote:  No, the fault is in Max.

Every disc I converted with dbpoweramp is now correct in it's settings.

I converted the m4a files with dbpoweramp to m4a files and now everything is correct. Strange.

I'm glad you've found a solution now. The part that I don't understand is why the file you sent me was read OK by MinimServer.

me too