INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: 0 dB shows as unassigned and as blank line in panes view  (Read 1758 times)

InflatableMouse

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 3978
0 dB shows as unassigned and as blank line in panes view
« on: May 26, 2012, 07:25:33 am »

I ran into a song that after analyzing shows as exactly 0 dB replay gain. When I create a panel for replay gain, 0 dB doesn't show, its a blank line. Selecting it only has the song in it with 0 dB replay gain. But, Unassigned also shows this song.

I've included 2 screenshots to clarify.
Logged

vagskal

  • Citizen of the Universe
  • *****
  • Posts: 1227
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #1 on: May 26, 2012, 11:14:24 am »

Unfortunately MC treats null and the value zero the same, so a field with the value zero (0) is regarded as <empty> and so is a field without any value in it.

You can get zero and null to display as 0 if you put the field inside math(), but I know no way in MC to distinguish between zero and null.
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #2 on: May 26, 2012, 11:24:22 am »

Matt recently adjusted the sense of sameness for floating point.  Looks like this is an edge case that has to be fixed.  There should never be a blank column cell in a pane (as it can't be seen when sorted at the bottom).
Logged
The opinions I express represent my own folly.

vagskal

  • Citizen of the Universe
  • *****
  • Posts: 1227
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #3 on: May 26, 2012, 11:29:26 am »

Matt recently adjusted the sense of sameness for floating point.

Do you mean that MC now will treat 0.0 (or 0,0 in my locale) and null different?
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #4 on: May 26, 2012, 11:51:44 am »

I don't think that's the issue, but rather how MC has to translate certain values for presentation, and then create categories for those values.  I've seen and reported these edge cases a couple of times in the past, where a single field value gets mapped into two categories, often one which shows as a blank value in the pane column.
Logged
The opinions I express represent my own folly.

vagskal

  • Citizen of the Universe
  • *****
  • Posts: 1227
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #5 on: May 26, 2012, 12:48:04 pm »

OK, thanks MrC.

BTW. I am not seeing this with a pane using Track # (which should be integer), i.e. there is no empty line and both zero and null are treated as Unassigned. And I am not seeing this with a pane using Replay Gain (which should be a floating point value with , as decimal point according to my locale) either. Replay Gain is not calculated using MC but imported from the file tags.
Logged

InflatableMouse

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 3978
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #6 on: May 27, 2012, 07:06:14 am »

The Unassigned has dissapeared, I don't know why or how I'm afraid. Maybe it just had to refresh.

The empty field in the pane is still there faithfully showing that one song.
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42323
  • Shoes gone again!
Re: 0 dB shows as unassigned and as blank line in panes view
« Reply #7 on: May 29, 2012, 04:31:17 pm »

This is a challenging issue.

The library does not tightly define a difference between 0 and empty for numeric fields.

So for Replay Gain, we store -0.0001 dB if analysis results in a perfect 0.

But the core search engine in the library uses 0.01 as the match threshold.  This is so that, for example, a replay gain of 6.34221 and 6.34222 will be considered equal (display only goes to two decimals of precision anyway).

I'm not sure the solution in this case.
Logged
Matt Ashland, JRiver Media Center
Pages: [1]   Go Up