V3.0.3.1140 Date column fails to show non-digit year [#5146]

by **chrisjj** » Tue Apr 02, 2013 10:26 pm

jiri wrote:We'll see whether we find a solution for MM 4.0...

Any progress on this?

by **chrisjj** » Tue Apr 02, 2013 9:29 pm

chrisjj wrote:
jiri wrote:Note that the issue is significantly more complicated than it might seem. Just to name few problems...
Jiri, are these problems overcome, now that you have implemented this for MP3? So can we hope for implementation on WMA soon? Especially since standards-wise WMA allows it whereas MP3 does not.

by **chrisjj** » Wed Jun 10, 2009 7:43 am

OK, thanks for the update.

by **jiri** » Wed Jun 10, 2009 7:42 am

No, there wasn't any change in this area and definitely won't be for MM 3.1, since it would require complex internal changes in MM (i.e. not just for a single format) as I described above. We'll see whether we find a solution for MM 4.0...

Jiri

by **chrisjj** » Sun May 17, 2009 6:56 pm

jiri wrote:Note that the issue is significantly more complicated than it might seem. Just to name few problems...

Jiri, are these problem overcome, now that you have implemented this for MP3? So can we hope for implementation on WMA soon? Especially since standards-wise WMA allows it whereas MP3 does not.

by **chrisjj** » Wed Apr 22, 2009 8:02 am

> Or: http://www.ventismedia.com/mantis/view.php?id=5146

That fits the bill - thanks.

Though "add support for dates that are stored as arbitrary string" seems to be in error, since the required support is already present in FLAC and even in WMA many dates stored as arbitrary string are supported e.g. 1940!. Better I suggest would be "Add WMA (and other) support for year values other than just 2,3,or 4 digits".

by **Mizery_Made** » Wed Apr 22, 2009 7:42 am

Either: http://www.ventismedia.com/mantis/view.php?id=5139
Or: http://www.ventismedia.com/mantis/view.php?id=5146

Maybe?

by **chrisjj** » Wed Apr 22, 2009 7:12 am

> the issue is significantly more complicated than it might seem. Just to name few problems - proper
> presentation of various possible date formats (not everyone wants to see 2004/12/24 as suggested e.g. for OGG)

Perhaps MM is trying to be too clever. The "proper" presentation for a string value is simply as is. That would suit me fine.

> internal handling for fast searches and auto-playlists

See above, surely.

> storage in various formats (e.g. ID3v2.4 allows only yyyy-MM-ddTHH:mm:ss format), etc.

The WMA Year field cannot be mapped to that ID3 field, so MM in trying to force the two to accord is making life very difficult for itself.

by **chrisjj** » Wed Apr 22, 2009 7:05 am

> I added this issue to Mantis

Thanks Jiri, but could you provide the link? I cannot find the entry.

by **jiri** » Tue Jan 06, 2009 4:28 pm

I added this issue to Mantis in order to review it for inclusion in next MM version (not 3.1). Note that the issue is significantly more complicated than it might seem. Just to name few problems - proper presentation of various possible date formats (not everyone wants to see 2004/12/24 as suggested e.g. for OGG), internal handling for fast searches and auto-playlists, storage in various formats (e.g. ID3v2.4 allows only yyyy-MM-ddTHH:mm:ss format), etc. So, we'll try to come with some solution, but I can't be more specific at this moment...

Jiri

by **chrisjj** » Tue Jan 06, 2009 12:39 pm

jiri wrote:Yes, WM/Year is stored as a string (as many other WM attributes), but it's supposed to be used for really for year only, see http://msdn.microsoft.com/en-us/library ... S.85).aspx

Jiri, there is nothing in that MS article or the one I quoted that says this string value must be numeric rather than alphanumeric. "2000 B.C." and "Nineteen hundred" are valid values, as is my original example "1950/1951".

I think the MM design's presumption that the value is always numeric is in error, and MM has no justification in restricting the value to numeric. But even if it must, it really should not wipe out my values (on Sync tags) just because they don't fit its own restrictions. Please would you consider fixing this.

by **jiri** » Tue Jan 06, 2009 12:15 pm

Yes, WM/Year is stored as a string (as many other WM attributes), but it's supposed to be used for really for year only, see http://msdn.microsoft.com/en-us/library ... S.85).aspx

That said, I just noticed that MediaMonkey doesn't support WM/OriginalReleaseTime attribute yet, it will be fixed.

Jiri

by **chrisjj** » Wed Oct 08, 2008 4:42 am

chrisjj wrote:So, here MM Date fields is reading one tag but writing to another. Urk. Devs, any comment??

Please?

by **chrisjj** » Wed Mar 26, 2008 5:37 am

> I tagged them in MM

That works here. But

> so whatever field they get tagged in

"ReleaseDate", I find.

So, here MM Date fields is reading one tag but writing to another. Urk. Devs, any comment??

by **spacefish** » Wed Mar 26, 2008 5:15 am

I tagged them in MM so whatever field they get tagged in is where they are. (Sorry, I have no idea what frame it is.)

V3.0.3.1140 Date column fails to show non-digit year [#5146]

Post a reply

Expand view Topic review: V3.0.3.1140 Date column fails to show non-digit year [#5146]

Re: V3.0.3.1140 Date column fails to show year [#5146]

Re: V3.0.3.1140 Date column fails to show EDIT: YYYY-MM-DD

Re: V3.0.3.1140 Date column fails to show year [#5146]

Re: V3.0.3.1140 Date column fails to show year [#5146]

Re: V3.0.3.1140 Date column fails to show EDIT: YYYY-MM-DD

Re: V3.0.3.1140 Date column fails to show year ...

Re: V3.0.3.1140 Date column fails to show year ...

Re: V3.0.3.1140 Date column fails to show year ...

Re: V3.0.3.1140 Date column fails to show year ...

Re: V3.0.3.1140 Date column fails to show year ...

Re: V3.0.3.1140 Date column fails to show year ...

Re: V3.0.3.1140 Date column fails to show year ...

Re: