You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the demo js, I believe it processes the wav header as well as the data :(.
the ffmpeg options are:
'-i', 'pipe:0',
'-acodec', 'pcm_s16le',
'-ar', 22050,
'-ac', 1,
'-f', 'wav',
'-v', 'fatal',
'pipe:1'
these are better, providing only the raw samples:
'-i', 'pipe:0',
'-map', '0:a',
'-acodec', 'pcm_s16le',
'-ar', 22050,
'-ac', 1,
'-f', 'data',
'-v', 'fatal',
'pipe:1'
The fingerprints produced are different.
It is quite odd that the fingerprints are SO different just for a few added bytes at the start.... quite a few common fingerprints, but >75% are different, and not just offset by time.
The text was updated successfully, but these errors were encountered:
in the demo js, I believe it processes the wav header as well as the data :(.
the ffmpeg options are:
'-i', 'pipe:0',
'-acodec', 'pcm_s16le',
'-ar', 22050,
'-ac', 1,
'-f', 'wav',
'-v', 'fatal',
'pipe:1'
these are better, providing only the raw samples:
'-i', 'pipe:0',
'-map', '0:a',
'-acodec', 'pcm_s16le',
'-ar', 22050,
'-ac', 1,
'-f', 'data',
'-v', 'fatal',
'pipe:1'
The fingerprints produced are different.
It is quite odd that the fingerprints are SO different just for a few added bytes at the start.... quite a few common fingerprints, but >75% are different, and not just offset by time.
The text was updated successfully, but these errors were encountered: