Author Topic: false 100% similarity  (Read 116439 times)

hsei

  • Jr. Member
  • **
  • Posts: 70
    • View Profile
Re: false 100% similarity
« Reply #240 on: October 31, 2010, 19:53:18 »
@admin: The last posts would better fit to wishlist.

TBacker

  • Jr. Member
  • **
  • Posts: 3
    • View Profile
Re: false 100% similarity
« Reply #241 on: October 31, 2010, 19:56:20 »
c) Normalizing to the highest peak of a sample/excerpt would not be an good idea. The standard approach for comparison in the frequency domain is to normalize to the overall average (or in other words: the component at frequency bin 0).

I guess my point wasn't clear in this respect.  I basically meant that the amplitudes of the two samples should be made to match (in the compare procedure) before frequency analysis to insure the best accuracy.
« Last Edit: October 31, 2010, 19:58:04 by TBacker »

Admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
    • View Profile
    • https://www.smilarityapp.com
Re: false 100% similarity
« Reply #242 on: November 01, 2010, 17:40:10 »
Thanks for your comments, we think about some modifications in algorithms, but this is not simple as seems.

GIL

  • Jr. Member
  • **
  • Posts: 5
    • View Profile
Re: false 100% similarity
« Reply #243 on: January 07, 2011, 12:28:58 »
I understand the performance limitation, but I would prefer to be able to set the sample length.
Better wait than erase the wrong track.

7b683d4548

  • Jr. Member
  • **
  • Posts: 4
    • View Profile
Re: false 100% similarity
« Reply #244 on: January 10, 2011, 13:33:03 »
How about uniquely identifying a song based on discogs release, amplifind id, musicbrainz unique id or such?

Ought to save you lots of scanning.





« Last Edit: January 10, 2011, 13:42:50 by 7b683d4548 »

hsei

  • Jr. Member
  • **
  • Posts: 70
    • View Profile
Re: false 100% similarity
« Reply #245 on: January 10, 2011, 20:18:18 »
The clue point of similarity is that it works just by comparing two tracks acoustically, not by comparison with a database entry. Musicbrainz IDs are no longer updated, they were replaced by Picard IDs (PUID). Both cover only part of released material. If you are not in mainstream you may get matches for only a a minor fraction of your candidates (I get typically less than 10%). Additionally, the problem of different instances of the same recording (with differing quality) isn't adressed at all.

Admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
    • View Profile
    • https://www.smilarityapp.com
Re: false 100% similarity
« Reply #246 on: January 10, 2011, 20:57:28 »
How about uniquely identifying a song based on discogs release, amplifind id, musicbrainz unique id or such?

Ought to save you lots of scanning.


Main idea of Similarity to don't depend on any Online databases or something. Similarity uses own mechanism of "acoustic fingerprint". Many files don't contain any information ID, they need to calculate this is ID via mathematic. It is time consuming calculation that Similarity can do itself.

mitul

  • Jr. Member
  • **
  • Posts: 10
    • View Profile
Re: false 100% similarity
« Reply #247 on: March 06, 2012, 18:43:12 »
So how many of the suggestion are implemented in latest version? Specially inquiring about taking samples at different locations rather then first minute of song. If it is not implemented then is on timeline?

Admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 664
    • View Profile
    • https://www.smilarityapp.com
Re: false 100% similarity
« Reply #248 on: March 08, 2012, 18:47:54 »
So how many of the suggestion are implemented in latest version? Specially inquiring about taking samples at different locations rather then first minute of song. If it is not implemented then is on timeline?
We working on cofigurable comparing algorithm, bu it will be after introducing image comparing.

mitul

  • Jr. Member
  • **
  • Posts: 10
    • View Profile
Re: false 100% similarity
« Reply #249 on: May 01, 2014, 16:09:14 »
Checking progress of this post....