-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: None
-
Component/s: Lookup & Match
-
None
-
Environment:All
Picard parses the response from Acoust ID servers after looking up tracks using fingerprint. The track field in the response is always ignored here. Is this voluntary or bug ?