#193 originalTrackNumber wrong for WMA files

open
nobody
None
5
2013-03-31
2013-03-31
leicray
No

miniDLNA assigns values for upnp:originalTrackNumber which are one less than they ought to be when serving tagged WMA audio files. Files for which the track number is 1 are assigned no upnp:originalTrackNumber value at all, track 2 is assigned a value of 1, track 3 is assigned a vlue of 2, etc. This affects the displayed track order in some UPnP renderers, though not in others. The issue appears to be specific to WMA files as MP3 and FLAC files are not affected.

I have confirmed this behaviour using miniDLNA 1.0.25 running under Linux Mint and it's also a problem on my Netgear ReadyNAS Duo v2 running firmware 5.3.7 which I presume incorporates the latest port of miniDLNA. The values of upnp:originalTrackNumber were viewed using UPnP Inspector on Windows and Linux.

Discussion

  • leicray

    leicray - 2013-04-02

    I've done some more investigation by delving into the sqlite database, files.db, to take a look at the track numbers assigned to WMA files. As expected, the values in each case are 1 less than they ought to be and the first track is assigned a value of 0 (zero) rather than the value being null. Next, I edited the track values in the database for one WMA-encoded album to set them to what they should be. This then fixed the sorting of tracks in KalemSoft Media Player which is the DLNA media renderer on my BlackBerry PlayBook. Screenshots are attached for how one album appears before and after the database edits. (Please, no sniggering at the back from those who recognise the artist and the era.)

     
  • leicray

    leicray - 2013-04-02

    before editing the track numbers

     
  • leicray

    leicray - 2013-04-02

    after editing the track numbers

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks