Feature Request: Dynamic Range Support

[jtwrace]

Would it be possible to offer Dynamic Range Support. Say if I use JRiver MC21 to analyze the audio files but have Minimserver read that information.

http://wiki.jriver.com/index.php/Dynamic_Range

http://wiki.jriver.com/index.php/Analyze_Audio

[simoncn]

(27-09-2015 19:09)jtwrace Wrote:  Would it be possible to offer Dynamic Range Support. Say if I use JRiver MC21 to analyze the audio files but have Minimserver read that information.

http://wiki.jriver.com/index.php/Dynamic_Range

http://wiki.jriver.com/index.php/Analyze_Audio

If this information is stored in a file's tags, MinimServer can read those tag values and use them for indexing or tag formatting. Is this what you have in mind?

[jtwrace]

(27-09-2015 21:04)simoncn Wrote:  

(27-09-2015 19:09)jtwrace Wrote:  Would it be possible to offer Dynamic Range Support. Say if I use JRiver MC21 to analyze the audio files but have Minimserver read that information.

http://wiki.jriver.com/index.php/Dynamic_Range

http://wiki.jriver.com/index.php/Analyze_Audio

If this information is stored in a file's tags, MinimServer can read those tag values and use them for indexing or tag formatting. Is this what you have in mind?

Yes but where would it be displayed within say Lightning DS from AURALiC? This is just a feature they would have to add; right?

[jtwrace]

This is the report that JRiver MC21 produces which is also within the tag.

[simoncn]

(27-09-2015 21:10)jtwrace Wrote:  This is the report that JRiver MC21 produces which is also within the tag.

I'm not sure whether this information is in the file tags or just in the MC database. If it is in the file tags, MinimServer can read it. You could (for example) use tag formatting to include this information in the COMMENT tag value, which MinimServer sends to the control point in the dc:description XML property. It is up to the control point whether (and how) it shows the dc:description information to the user.

[Patatorz]

(27-09-2015 22:15)simoncn Wrote:  

(27-09-2015 21:10)jtwrace Wrote:  This is the report that JRiver MC21 produces which is also within the tag.

I'm not sure whether this information is in the file tags or just in the MC database. If it is in the file tags, MinimServer can read it. You could (for example) use tag formatting to include this information in the COMMENT tag value, which MinimServer sends to the control point in the dc:description XML property. It is up to the control point whether (and how) it shows the dc:description information to the user.

Dynamic Range can also be tagged into the files with DR Meter (http://dr.loudness-war.info/) (Follow the links in order to download the right version windows or with foobar).
In this case the DR Meter soft is creating a tag into the file "DYNAMIC RANGE". According to what i can see it seems that Jriver 21 is also creating a tag inside the file with this information.

In this case how to manage a sorting by dynamic range for example on minimserver ?

[simoncn]

(10-10-2015 18:10)Patatorz Wrote:  Dynamic Range can also be tagged into the files with DR Meter (http://dr.loudness-war.info/) (Follow the links in order to download the right version windows or with foobar).
In this case the DR Meter soft is creating a tag into the file "DYNAMIC RANGE". According to what i can see it seems that Jriver 21 is also creating a tag inside the file with this information.

In this case how to manage a sorting by dynamic range for example on minimserver ?

You can do this by adding the tag name to the indexTags property (just like any other tag).