Twonky Forum

Hi there,

I stream my .mkv-movies after "conversion" with mkv2vob to .mpg to my PS3 using TwonkyMediaServer, which works fine apart from the incorrect movie length, which is always set to 99:59:59 or 596min. As a result, the PS3's progress bar and the remaining playing time does not work.

Does anyone encounter similar problems with the movie length? I'm pretty sure it's a Twonky issue, is there any work-around or even a fix for this problem?

Thanks in advance, Brad

I get the same problem. The time information is present if the same files are on a USB drive connected to my PS3, but not when streamed via TwonkyMedia (in my case 4.4.8 on a Buffalo LinkStation Mini).

When I get the time I might try using some different file extensions to see if that helps.

Hi

New to these forums but i have just encountered this very same problem. I am streaming .M2TS files to my PS3 using a QNAP TS-219 Turbo Station with Twonky version 4.4.14.

I will post my experience and hopefully this may help to get to the bottom of the problem.

So I use RipBot264 to convert my movies. If I check the converted movies properties in Windows XP then it shows the correct length. If I play this file in VLC or Windows Media Player - it again shows the correct length.

However, once I copy the same file over to my NAS and then browse to it from the Twonky UPnP server on my PS3, the length is reported as "99:59:59"

If I then start to stream this file, the timeline bar reflects this incorrect length and none of the scene searching stuff works.

This can't be a problem with the .M2TS container as the length of the movie is reported correctly on my PC in Windows Explorer and in all of the media players I have tried.

The problem therefore must lie with either Twonky itself or how UPnP servers handle .H264 encoded video files.

Comments ? Help ??

Meanwhile I figured out that it is definitely a Twonky issue (and not a file / file format issue): When you copy the file to the PS3 via Twonky, the time lenght is displayed correctly...

I look forward to a fix as well!

Brad

Thanks for the update Brad.

Can I ask what version of Twonky you have ??

If I'm not mistaken there is a new firmware build with Twonky 4.4.17 so I was thinking about giving that a try. Although I can't see any confirmation or even acknowledgement that this is an issue and has been fixed in this firmware version.

I have the same problem.

If i copy the files to the PS3 harddrive all are fine.

my version are 5.0.61 under linux.

Well, I was aware of Twonky version 5 and was kind of hoping that this may have been resolved but apparently not.

Sounds like the guys at Twonky haven't acknowledged this as being an issue and therefore no fix for us.

TBH I'm not impressed as it renders alot of the search functions useless.

I think we need to raise this as being an issue if it hasn't already been done.

My Twonky-Version is 4.4.17 (Twonky V5 does not work on embedded system)

Well, correct me if I'm wrong, but the scene search function of the PS3 generally works even without the correct time lenght - unfortunanetly, it takes hours to jump to the correct scene (I tried to jump to 15 min, which worked after let's say 10min). I have better experience with 120x fast forward (if you press "select" you can see the time counter run with the correct time). When you have reached your scene (e.g. 45:01min), wait 2 minutes, stop the playback and restart it - the PS3 will start the playback at 45:01.

Give it a try (and let me know, if it works for you as well...)

Regards, Brad

I didn't have the patience to wait around when trying to jump to a different scene so it probably does work but just takes a long time to catch up.

If I jump to a scene and then stop and resume play that does work. Maybe its just not possible to have the scene search working (as we would like it to) via DLNA i.e. maybe it can't cope with the stream size etc.

I was looking around at other UPnP media servers but so far haven't found anything which works. I have tried MediaTomb but that didn't even recognise .M2TS encoded files.

The search continues...

Any news about this problem ??