MMA changes Release Date [#13300]

[MaximusPrime]

I'm tagging my files in MMW only with the release year, since the latest Beta of MMA, it is refilled with 01.01. of the year. Example: Tag in MMW: 2007 - Tag in MMA 01.01.2007

[rusty]

Hi,

I tested this with the current MMA (595) and MMW 4.1.12 and can't replicate (tested with OGG, MP3, and Flac tracks). i.e. when I look at the tracks in MMA, the date appears as '2012' rather than the format you described.

Can you think of anything unique to your scenario that might be resulting in this behavior?

-Rusty

[MaximusPrime]

No, nothing special.
All my tracks are mp3 and I only sync playlists via Wifi to MMA.
Latest MMA Beta and latest MMW Beta.
I will delete all my music from the phone at the weekend and resync and report here if this still happens.

[rusty]

Also, if it occurs, can you send me a sample track for which it occurs (you can post a link to a file stored on dropbox/mediafire/etc...)?

Thanks!

-Rusty

[MaximusPrime]

Resync didn't help. DM is coming to you rusty.
Thanks

[rusty]

Maximus,

Thanks for the file. I'm able to replicate over wi-fi sync.

Tracked at: http://www.ventismedia.com/mantis/view.php?id=13300

-Rusty

[MaximusPrime]

Maximus,

Thanks for the file. I'm able to replicate over wi-fi sync.

Tracked at: http://www.ventismedia.com/mantis/view.php?id=13300

-Rusty

Thanks a lot, the original problem is solved. But the same issue appears while streaming music from mmw to mma via Upnp server. So, when looking into the properties box there's 01/01/2014 instead of only 2014

[Peke]

Thanks a lot, the original problem is solved.

As confirmed For MMW -> MMA UPnP you should open new Topic with Wishlist that MMA represent date as is in MMW and not by standard.

For UPnP date format MUST be compliant to [ISO 8601] and SHOULD be compliant to [RFC 3339] or it fails standard.

More Info at http://www.upnp.org/specs/av/UPnP-av-Co ... 060531.pdf

Description: The dc:date property contains the primary date of the content. The format MUST be
compliant to [ISO 8601] and SHOULD be compliant to [RFC 3339]. See
http://dublincore.org/documents/dces

Examples:
• 2004-05-14
• 2004-05-14T14:30:05
• 2004-05-14T14:30:05+09:00

[rusty]

Maximus,

To elaborate, MM originally implemented date over UPnP in the way that you requested. The problem was that because it wasn't standard compliant, content failed to render to some devices (as described at http://www.ventismedia.com/mantis/view.php?id=13198).

That's why we had to change the implementation to follow the standard.

But maybe it would be a good idea to allow users to configure this (I agree that it makes sense for content to appear over UPnP as it does in MMW).

Tracking at: http://www.ventismedia.com/mantis/view.php?id=13395

-Rusty