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

Support for tagging WAV files with Broadcast Wave Format

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • 0.15.1
    • Tags & Metadata
    • None

      From http://bugs.musicbrainz.org/ticket/5728

      There is an extension to the WAV format called Broadcast WAV Format:

      http://en.wikipedia.org/wiki/Broadcast_Wave_Format

      Picard could tag WAV files in accordance with this format.

          [PICARD-41] Support for tagging WAV files with Broadcast Wave Format

          Philipp Wolfer added a comment -

          I am closing this as won't do for now. As I wrote above I think in general the Broadcast WAVE standard does not bring tags relevant for our use case.

          Instead we will get support for tagging WAVE files with ID3 as supported by other players (PICARD-1128) and also we can implement reading / writing the INFO chunk (PICARD-1812).

          But if someone has some comment here or sees specific information from the Broadcast WAVE standard that would make sense to support in Picard please comment or better yet create a specific issue for that use case.

          Philipp Wolfer added a comment - I am closing this as won't do for now. As I wrote above I think in general the Broadcast WAVE standard does not bring tags relevant for our use case. Instead we will get support for tagging WAVE files with ID3 as supported by other players ( PICARD-1128 ) and also we can implement reading / writing the INFO chunk ( PICARD-1812 ). But if someone has some comment here or sees specific information from the Broadcast WAVE standard that would make sense to support in Picard please comment or better yet create a specific issue for that use case.

          Philipp Wolfer added a comment -

          It looks to me like this extension is not really relevant to Picard. The specification does not deal at all with the kind of metadata Picard cares about. The extension adds some metadata about the audio itself, such as information on the recording takes.

          The kind of data about the music and the artists involved is not specified here and must still be handled by some other means. So implementing PICARD-1128 for proper tagging of WAV files should be sufficient.

          See also https://tech.ebu.ch/docs/tech/tech3285.pdf

          Philipp Wolfer added a comment - It looks to me like this extension is not really relevant to Picard. The specification does not deal at all with the kind of metadata Picard cares about. The extension adds some metadata about the audio itself, such as information on the recording takes. The kind of data about the music and the artists involved is not specified here and must still be handled by some other means. So implementing PICARD-1128 for proper tagging of WAV files should be sufficient. See also https://tech.ebu.ch/docs/tech/tech3285.pdf

          Kenneth Peard added a comment -

          Will this include support for the RF64/MBWF extensions for supporting multiple channels and files bigger than 4 GB.

          Kenneth Peard added a comment - Will this include support for the RF64/MBWF extensions for supporting multiple channels and files bigger than 4 GB.

            ciccioschumacher Francesco
            voiceinsideyou voiceinsideyou
            Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package