Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-991

Allow calculating AcoustID fingerprints for matched recordings

      A number of users want to help populating the AcoustID/MB matches, but the interface in Picard is not always intuitive, esp. if you do the "cluster→lookup" workflow, so the files aren't run through fpcalc before being matched to MB Releases/Recordings.

      One way to do this would be to allow Submit AcoustIDs (and Scan, probably) to work for entries in the right-hand pane, as long as they don't already have a matching AcoustID:Recording pairing.

      See also https://community.metabrainz.org/t/submitting-acoustids-scan-button-greyed-out/215793/3?u=freso and https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3835804/

          [PICARD-991] Allow calculating AcoustID fingerprints for matched recordings

          Philipp Wolfer added a comment - https://github.com/metabrainz/picard/pull/1423

          I started implementing this by adding a separate action which only generates the fingerprints without doing a lookup.

          Testing this shows that we need some kind of display of files having a fingerprint generated as requested in PICARD-34. Currently the user cannot see whether a file has a fingerprint generated or not and hence such an action becomes very intransparent.

          Philipp Wolfer added a comment - I started implementing this by adding a separate action which only generates the fingerprints without doing a lookup. Testing this shows that we need some kind of display of files having a fingerprint generated as requested in PICARD-34 . Currently the user cannot see whether a file has a fingerprint generated or not and hence such an action becomes very intransparent.

          Zas added a comment -

          outsidecontext i assign this ticket to you, it would be great if we could implement this, my last attempt wasn't great at all (https://github.com/metabrainz/picard/pull/987 but it missed the point).

          Zas added a comment - outsidecontext i assign this ticket to you, it would be great if we could implement this, my last attempt wasn't great at all ( https://github.com/metabrainz/picard/pull/987 but it missed the point).

          PICARD-1223 should be taken into account also. The basic goal here is allowing to generate and submit AcoustIds without this causing the automatic matching and loading of data.

          Philipp Wolfer added a comment - PICARD-1223 should be taken into account also. The basic goal here is allowing to generate and submit AcoustIds without this causing the automatic matching and loading of data.

          Freso added a comment -

          Freso added a comment - There is discussion about this happening at https://community.metabrainz.org/t/suggestions-for-changing-how-acoustid-scanning-and-lookups-work/217527?u=freso

            outsidecontext Philipp Wolfer
            freso Freso
            Votes:
            9 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2.3.0b1