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

Make file-specific variables available to tagger script

    Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: None
    • Component/s: Scripting
    • Labels:
      None

      Description

      There are many individual tickets for allowing the technical variables in scripting, but they all are blocked by the (current) design of tagger scripting - that is it operates on metadata retrieved from elsewhere (+ plugins) and so at the point it runs, the files linked to that abstract metadata are irrelevant. Doing it this way does have many advantages in simplicity and clarity.

      There are technical problems with implementing this such as:

      • if multiple files are currently linked to an abstract track, what do you do? Ignore them both? How do you "merge" the metadata?
      • you would then have to re-evaluate tagger script every time a file is moved/linked. Will this be a problem? (performance? complexity/predictability?)
      • how about the relationship with plugins - if you re-evaluate the tagger script every time will this lead to some inconsistencies with the plugin "lifecycle"?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kepstin Calvin Walton
                Reporter:
                voiceinsideyou voiceinsideyou
              • Votes:
                4 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: