home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
MPTagThat
MPTagThat - The Mediaportal Tag Editor
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="rsbrux" data-source="post: 850801" data-attributes="member: 49539"><p><a href="https://forum.team-mediaportal.com/members/hwahrmann.10391/" target="_blank">hwahrmann</a>,</p><p>Many thanks for the new version. It's amazing how much functionality you have packed into it!</p><p>In reviewing the settings, I noticed some minor spelling errors in the English version:</p><p style="margin-left: 20px">"Ripping" is spelled correctly in the heading "Ripping/Conversion", but is spelled "Riping" 3x at the bottom of the "General" section.</p><p>I was scouring the settings in hope of finding a way to increase the size of the music sample used to "Identify File"s as I have been getting quite a few "false positive" IDs. Attached is a particularly humorous example. The track in question is actually "It's a Man's World" performed by James Brown. It is particularly funny that the albums offered are mostly plausible, despite the incorrect identification of the track. What would a track by "Los Bravos" be doing on "The Very Best of James Brown"? Would it be possible to implement some kind of "plausibility check" in MpTagThat to prevent such self-contradictory results, or are you depending strictly on the information provided by the MusicBrainz API? I can imagine that such a plausibility check, even if possible, might be non-trivial, but would it at least be possible to have the option of using a larger sample to generate the hash? I would be willing to wait longer for the results, if it reduces the number of erroneous matches.</p></blockquote><p></p>
[QUOTE="rsbrux, post: 850801, member: 49539"] [URL='https://forum.team-mediaportal.com/members/hwahrmann.10391/']hwahrmann[/URL], Many thanks for the new version. It's amazing how much functionality you have packed into it! In reviewing the settings, I noticed some minor spelling errors in the English version: [INDENT=1]"Ripping" is spelled correctly in the heading "Ripping/Conversion", but is spelled "Riping" 3x at the bottom of the "General" section.[/INDENT] I was scouring the settings in hope of finding a way to increase the size of the music sample used to "Identify File"s as I have been getting quite a few "false positive" IDs. Attached is a particularly humorous example. The track in question is actually "It's a Man's World" performed by James Brown. It is particularly funny that the albums offered are mostly plausible, despite the incorrect identification of the track. What would a track by "Los Bravos" be doing on "The Very Best of James Brown"? Would it be possible to implement some kind of "plausibility check" in MpTagThat to prevent such self-contradictory results, or are you depending strictly on the information provided by the MusicBrainz API? I can imagine that such a plausibility check, even if possible, might be non-trivial, but would it at least be possible to have the option of using a larger sample to generate the hash? I would be willing to wait longer for the results, if it reduces the number of erroneous matches. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
MPTagThat
MPTagThat - The Mediaportal Tag Editor
Contact us
RSS
Top
Bottom