[New Feature] Dynamic Range import from MAAT DROffline report?

Hello, i'm running MP3tag under macOS since years and very happy with it.

I'm also analyzing all my file with MAAT DROffline mkii under macOS. This software is not tagging any files, just producing a txt file with all the dynamic ranges for the individual titles and for the album.

Wouold like to see, if in a future release, MP3Tag could import the information of the txt from DROffline and tag the "Dynamic Range" for titles and "Album Dynamic Range" for albums in order to be managed through servers like minimserver and Tune ?

Thanks for your support

I am not sure if this would really be a new feature as there is already the function Convert>Text file - Tag.

You would have to adapt the text file accordingly or create a suitable mask to assign the data to fields.

@ohrenkino thanks for your feedbacks. Seems i missed this option. I just tried on few titles and work fine. I would need to find a way to customize the export of DROffline or to have a customized import template into MP3 Tag :grinning_face:

Or you import the data into a temporary tag field, distibute the individual pieces to dedicated fields and then delete that tag field again. This could probably all be achieved with an action group so that it would require only 2 clicks.

If you require further assistance or suggestions, a sample text file source would be nice.

Thanks a lot for your support ! A usual DROffiline output is like this : Microsoft OneDrive
Seems i cannot customize the export. So either i can do everything within MP3 Tag either i would need to go through a bit of IA and automatization to format the txt file in order to ease the import in MP3 Tag

It has been tested under Windows. I don't know if this is true for Mac too.

There are at least 2 big problems to use Convert Textfile -> Tag:

  1. The first character of your file name in your TXT output file must not be a space
    (no spaces in front of the tracknumber!)
  2. It seems that a file extension is needed
    (for the recognition of the matching music track)

This is how the first two example tracks would need to be modified prior to import:

If you can modify your DROffiline output like the above example for the first track, this Format String would work:

%_filename_ext% | %My_Format% | %My_SR% | %My_WL% | %My_Max_TPL% | %My_LUFSi% | %My_DR% |

This results in the following imported example data for the first track:
Track #1:

Track #2:

Note:
As I don't have any *.aif tracks, I used a .mp3 track for my tests.
That's why my test tracks #1 and #2 have an .mp3 extension in the above screenshot of the modified TXT file, rather than an .aif extension.

This is my suggestion:
Create an action group with the following actions:

  1. Import the whole text file with an action of the type "Import text file" into the field with the name e.g. IMPORT.
  2. Create an action of the type "Import tag fields"
    Source string: $regexp($regexp(%import%,.+$replace(%_filename_ext%,'(','\(',')','\)')(.+?)\n.*,$1),\s+\|\s+,==)

Target format string: ==%dummy%==%format%==%word_length%==%max_tpl%==%lufsi%==%dr_pmf%==
3. Create an action of the type "Remove fields": IMPORT

The source format string should create an output like
==.aif==192k==24==-2.68==-20.50==14==
The parts between the == then get assigned to the fields named in the target format string.
I have no clue which fields the players use to display or use the values - so that would have to be investigated by users of these players and adapted accordingly.

Thanks @LyricsLover and @ohrenkino will have a look today

Just a quick note for future readers:

The mentioned tool MAAT DROffline does not measure dynamic range in MP3 or AAC and other lossy-encoded music formats. Original statement:

The pre-defined file selection only offers these 5 types:
Select File

For the Mac version use

$regexp($regexp(%import%,.+|\n$replace(%_filename_ext%,'(','\(',')','\)')(.+?)\n.*|\n,$1),\s+\|\s+,==)