I recently upgraded Twonky from 5.1.9 to 6.0.37 and then 6.0.38 on my WD My Book Live serving to a Panasonic Viera P50GT30.
Both the 6.0.3n versions appear to have an issue in presenting month 12 dates (specifically video files) on the Viera as they are incorrectly interpreted . . . . . the month ('12') is being interpreted as the year so, for example, a file added on the 19th December 2011 (12/19/11) is presenting as the 19th January 2012 (01/19/12), 12/30/11 as 01/30/12 ect ect. Files legitimately added this month (say on the 4th) present correctly, and in the correct order, as 01/04/12.
When viewing by 'date' or 'year' views the files are also incorrectly placed within the 2012 -> 01 & 2012 folders respectively, the 2011 -> 12, and 2011 folders however contain some, but not all, of the incorrectly identified files but all consistently showing the incorrectly formed dates. The files appearing within the 2011 vs. 2012 folders are unique to the particular folder and not duplicated across both.
On reverting back to version 5.1.9 the files are correctly ordered and placed correctly and as would be expected. In all other respects both the 6.0.3n releases seem without issue.
I have attempted multiple combinations of re-scanning and DB rebuilds without success. The files also present incorrectly through a standalone Sony Bravia player however WD2go presents the dates corredctly. There is also nothing to distinguish the files from those being handled correctly. NOTE: possibly of interest the Bravia 'all video' view presents files aphabetically and not ordered by date (they are on the Viera) so the issue does not apply in that view - the folder view exaclty replicates the problem however - could this be an issue with the Viera presenting in date order within the all video view? Is this controlled by server or client?
Does anyone have a suggestion as to a fix for this as, unfortunately, I rely on date ordering for video above other sort orders and would like to see this fixed so I can run the current release.
I have currently reverted back to version 5.1.9 in the hope that a fix will be forthcoming for this issue.
Can anyone help?