Additional field positions will be randomized (Meta-Editor)

Good morning

We are a GLAM organization and using Audacity since many years for digitizing 78 rpm gramophone records.

It’s very nice that we can add additional fields in the Metadata editor and since “Kelson’s report” your team have fixed the bug for saving the new fields.

Weeks ago I have created a XML file with the additional required fields and gave them a fixed position in the column:
(capital letter=Audacity predefined fields)

ARTIST
Vocal range
ALBUM
TITLE
TRACK NO.
GENRE
YEAR
COMMENTS
Label
Catalogue number
Order number
Matrix/StamperID
Released
Recorded
Coupling
Cutout date
Place
Description
Composer
Lyricist
Music arranger
Conductor
PD CH
PD EU
PD USA
PD INT

I have saved the template inside the correct folder inside Audacity.

PROBLEM:
Even thought the template is defined as standard, Audacity removed fields and/or the additional fields will be randomized by every start in a different sequence. For our worker’s it’s very difficult to work because the positions of the fields are randomized by every new created audio file and the error rate is increasing rapidly. For us it’s very important to save the exact data.

Can you please fix the problem?

Many thanks and best regards,
Carl

Hi Carl,

What is GLAM?

Because you have the fix for http://bugzilla.audacityteam.org/show_bug.cgi?id=440, do I assume you are using Audacity 2.1.3-alpha from the Nightly Builds page? Please see the pink panel at the top of the page.

When you say the template is defined as standard, do you mean you used the “Set Default” button? Are you adding metadata then exporting to a previously non-existent audio file, or importing an existing audio file that already contains metadata and adding to that?

In what application are the fields random? Only in Audacity, or in some other application that is playing the exported files?

I can’t reproduce the problem at the moment with three custom fields, but could you attach your saved XML template file so we can experiment with it? In particular I don’t understand how you have “Vocal Range” listed second amongst the predefined fields. Please see here for how to attach files: https://forum.audacityteam.org/t/how-to-attach-files-to-forum-posts/24026/1

Thanks for your help.


Gale

Dear Gale

Thank you for your quick answer…

This is the original source code of my XML file which I have set as default mask inside Audacity:

<tags>
    <tag name="Label" value=""/>
    <tag name="Catalog number" value=""/>
    <tag name="Order number" value=""/>
    <tag name="Matrix/StamperID" value=""/>
    <tag name="1st release date" value=""/>
    <tag name="1st recording date" value=""/>
    <tag name="Coupling date" value=""/>
    <tag name="Cutout date" value=""/>
    <tag name="Place of recording" value=""/>
    <tag name="COMMENTS" value=""/>
    <tag name="Description" value=""/>
    <tag name="Author/Composer" value=""/>
    <tag name="Lyricist" value=""/>
    <tag name="Music arranger" value=""/>
    <tag name="Conductor" value=""/>
    <tag name="ARTIST" value=""/>
    <tag name="Vocal range" value=""/>
    <tag name="TRACKNUMBER" value=""/>
    <tag name="ALBUM" value=""/>
    <tag name="TITLE" value=""/>
    <tag name="Content" value=""/>
    <tag name="GENRE" value=""/>
    <tag name="YEAR" value=""/>
    <tag name="PD CH" value=""/>
    <tag name="PD EU" value=""/>
    <tag name="PD USA" value=""/>
    <tag name="PD INT" value=""/>
    <tag name="References" value=""/>
    <tag name="Source" value=""/>
</tags>

Audacity 2.1.3-alpha-Mar 6 2016. The attachement was not allowed (PDF-Print-Screen) and I can add you the source code which Audacity made after starting meta data editor mask when I have recorded a new audio file from a 78 rpm gramophone record inside our ELP Laser turntable. The example show you that Audacity randomized the fields by loading the default template. Yes just Audacity randomized the fields by using the XML template.

Example:

<tags>
    <tag name="PD EU" value=""/>
    <tag name="TRACKNUMBER" value=""/>
    <tag name="Matrix/StamperID" value=""/>
    <tag name="Description" value=""/>
    <tag name="PD CH" value=""/>
    <tag name="TITLE" value=""/>
    <tag name="YEAR" value=""/>
    <tag name="Cutout date" value=""/>
    <tag name="ALBUM" value=""/>
    <tag name="ARTIST" value=""/>
    <tag name="Lyricist" value=""/>
    <tag name="PD INT" value=""/>
    <tag name="Title/Work" value=""/>
    <tag name="PD USA" value=""/>
    <tag name="1st recording date" value=""/>
    <tag name="References" value=""/>
    <tag name="GENRE" value=""/>
    <tag name="1st release date" value=""/>
    <tag name="COMMENTS" value=""/>
    <tag name="Order number" value=""/>
    <tag name="Place of recording" value=""/>
    <tag name="Label" value=""/>
    <tag name="Coupling date" value=""/>
    <tag name="Music arranger" value=""/>
    <tag name="Source" value=""/>
    <tag name="Catalog number" value=""/>
    <tag name="Performer" value=""/>
    <tag name="Author/Composer" value=""/>
    <tag name="Vocal range" value=""/>
    <tag name="Content" value=""/>
</tags>

A GLAM organization is a Gallery, Library, Archive or Museum. We are an archive - a charitable organization specialized in the conservation and utilization of public domain music and film material.

We are recording new audio files (non existing files) with Audacity by using a ELP Laser turntable and other turntables with a RME Fireface 800.

For better understanding - here are links of some articles about audio files inside our archive. It’s important for another archives around the globe, our users and Wikimedia Commons that we added all existing information inside the meta data mask. It’s a must to add a source-URL to the orginal article inside our MediaWiki with all the References (Copyright investigation/Rightsclearing) because our organization is under control of the goverment.

Jelly Roll Morton - Winin’ Boy Blues (Fox Trot)
http://pool.publicdomainproject.org/index.php?title=Bluebird-b10429b

Part of a complete opera recording:
http://pool.publicdomainproject.org/index.php/Hmv-db8453-2ba2363

Best regards,
Carl

I don’t see any note in the code about why the tags are saved in a different order to that entered or why the logic is as it is.

I have not found any workaround by editing the saved file manually.

I see no evidence with even 20 added tags that any are not saved.

If the tag order was correctly preserved, how would you move the information from the tags in the exported file to your online page? Perhaps if you use a spreadsheet, you can write a macro to set the order.

We can add the bug to our bug tracker but it would not be the highest priority to fix it I am afraid.


Gale