View Full Version : problem with 7605 140.023 and twonkyserver 6.0.28

11-13-2010, 05:02 PM
my system is 7605 with latest firmware 140.023 and DLNA server Twonkymedia

since today i use Twonky server 5.1.6, i see with no problem all AVI and MKV files (exept for subtitle and fast-back forward but i think it is problem of dlna software)

i upgraded server from 5.1.6 to the latest 6.0.28

TV now say me always this error "unsupported file not able to execute"
i see correctly the directory tree but all files are an icon like this "X"
when i try to play the file (all) i see the error "unsupported file not able to execute"

i rollback my server to 5.1.6 and all return ok

i try 6.0.28 with other dlna/upnp client and i see all files

so the problem i think is in the firmware of tv

11-20-2010, 08:34 AM
the problem is incorrect value in the DB of twonky server, i am working to help twonky to correct this issue

11-24-2010, 06:12 AM
i made many tests with twonky technichan

philips tv 2010 (i own 7605 but i understand it is the same with 8605 and 970x) send a non standard signature to a dlna get

twonky recognize it as generic and not "philips tv"

please philips people , in the next firmware, make a better dlna implementation !!!
and adding support to subtitle and fast/back forward :)

thank you


11-24-2010, 08:47 AM
i tried another dlna server : tvmobili
same problem
a tvmobili technichan answer in a post of they forum to another user "This is most liekly a mime-type issue with the Philips TV"
same idea of twonkymedia technichan

11-24-2010, 08:49 AM

did you test version 140.25 of the firmware?


11-24-2010, 10:00 AM
yes same error :(

11-28-2010, 07:57 PM
Well, maybe it's better when Twonky reverts back to the playback approach that was implemented in 5.1.5 (or anything before the v6.xx branch).

I had a look at some network traffic dumps that have been recorded during interaction between my 9705K and Twonky (tested 5.1.5 and 6.0.28): they stuff a lot of DLNA-specific information in the protocolInfo header that was not there before 6.0.28. Now they explicitly dictate the MIME type; they left the playability decision to the device itself before the new release.

The latter would be a far more convenient approach; and it sure would prevent some evil things.