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

Make file-specific variables and metadata available to tagger script

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.5.0b1
    • 1.0
    • Scripting
    • None

      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"?

        1.
        		 Allow applying tagger scripts to existing metadata (not just MB metadata) Sub-task Closed Calvin Walton
        2.
        		 make %_extension% available in TaggerScript Sub-task Closed Calvin Walton
        3.
        		 Make _bitrate (and other bitrate variables, when/if added) available to tagger script Sub-task Closed Calvin Walton

            outsidecontext Philipp Wolfer
            voiceinsideyou voiceinsideyou
            Votes:
            7 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:

                Version Package
                2.5.0b1