Regression from 4.2b3 to 4.3
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
Hi there,
I just upgraded Twonky from 4.2b3 to 4.3 on my Debian Sid box, serving files to a DSM-320.
I must report a regression: the first file I watch on my TV works just fine. When the file is finished, I start a second one and it invariably stutters for the first 5 seconds and then the screen goes black. At this point the only thing I can do is to turn off the DSM-320 and then turn it on again. After this, the file plays just fine.
As you can imagine this can be pretty annoying: do you have any comments? Thanks for any help!
I just upgraded Twonky from 4.2b3 to 4.3 on my Debian Sid box, serving files to a DSM-320.
I must report a regression: the first file I watch on my TV works just fine. When the file is finished, I start a second one and it invariably stutters for the first 5 seconds and then the screen goes black. At this point the only thing I can do is to turn off the DSM-320 and then turn it on again. After this, the file plays just fine.
As you can imagine this can be pretty annoying: do you have any comments? Thanks for any help!
-
- Posts:17
- Joined:Fri Sep 16, 2005 12:49 pm
I'm having exactly the same problems with a DSM320 and twonky running on a debian NSLU2 (already reported here: http://www.twonkyvision.de/forum/viewtopic.php?t=3000). 4.2b3 is the last version without those problems...
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
there´s a thread from me one down where the admin spends a little bit time to help to get .avi´s back to the linktheater.
i send mails, called their phone (a nice lady tells me that there is only email n forum support.. she don´t know anything...), and make posts.
The next few days i´ll check the nero upnp-server... if it´s better, im no longer PAYING twonky-user..
sorry guys, but 3 betas and then the whole house is out of .avi´s is not professional! seems to be the end of a good server.. this is like many other companies died.. internet/life is fast, to die even faster...
i send mails, called their phone (a nice lady tells me that there is only email n forum support.. she don´t know anything...), and make posts.
The next few days i´ll check the nero upnp-server... if it´s better, im no longer PAYING twonky-user..
sorry guys, but 3 betas and then the whole house is out of .avi´s is not professional! seems to be the end of a good server.. this is like many other companies died.. internet/life is fast, to die even faster...
afaik there is no way to go back, because the licence-system is changed.. a few users say that only 4.1 is quite functional. but test it better, don´t know where u wanna get this files . sry.auslander wrote:since Twonky hasn't bothered to fix this issue yet, where can I download the 4.2b3 so that I can have a functional server that I *paid* for?
Thanks
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
I do have a backup of the 4.2b3 directory, but as mentioned if they changed the licensing system the "older" clients might be shut off sooner or later anyway.
I'll check back other free software alternatives, I chose Twonky over free (as in beer) programs because it was *better* for my needs.
Please twonky developers, don't hesitate to give us nightly builds and the like to try things out!
I'll check back other free software alternatives, I chose Twonky over free (as in beer) programs because it was *better* for my needs.
Please twonky developers, don't hesitate to give us nightly builds and the like to try things out!
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
4.4 Beta2 is released, and they claim to have changed the way they communicate with the d-link. My previous use-case given in the mantis doesn't crash the unit anymore, but after a while of playing video, the current video keeps playing nicely, but the unit doesn't respond to the remote or the power-button, so they need to do more changes.
-
- Posts:17
- Joined:Fri Sep 16, 2005 12:49 pm
I just also tried 4.4beta2 on my NSLU2 with a DSM-320:
I can't use the 'jump to a certain time' - feature any more. The box is getting data, sometimes sound snippets are played but it doesn't get to continue properly. On the other hand, it wasn't so easy to get a complete lockup like it was before! Obviously, there's still something wrong...
I can't use the 'jump to a certain time' - feature any more. The box is getting data, sometimes sound snippets are played but it doesn't get to continue properly. On the other hand, it wasn't so easy to get a complete lockup like it was before! Obviously, there's still something wrong...
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
-
- Posts:17
- Joined:Fri Sep 16, 2005 12:49 pm
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
I took the liberty do to a bit of research.
I have tested four different servers (twonky, fuppes, mediatomb, ushare) and surprisingly only ushare works fine.
This probably means that it is not strictly twonky's fault, but it might be an unfortunate mix of shared libraries and firmware. On my DSM-320 I am running 1.07eu, the server runs Debian Sid AMD64.
So, let's dig up the dependencies:
Now, ushare is the only software to use libupnp and it's the only one that does NOT use libdl. I am no programmer so I can't really say if that might be the problem, but hey, it's a lead.
cytochrome, ogre_x are you running twonky on linux too? If yes, then we might have a platform specific problem.
Twonky developers, please give a sign in this thread
Thanks everyone for any additional info!
I have tested four different servers (twonky, fuppes, mediatomb, ushare) and surprisingly only ushare works fine.
This probably means that it is not strictly twonky's fault, but it might be an unfortunate mix of shared libraries and firmware. On my DSM-320 I am running 1.07eu, the server runs Debian Sid AMD64.
So, let's dig up the dependencies:
Code: Select all
jack@nostromo:~/Desktop$ ldd /usr/local/twonkymedia/twonkymedia
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf7f91000)
libdl.so.2 => /lib32/libdl.so.2 (0xf7f8d000)
libc.so.6 => /lib32/libc.so.6 (0xf7e50000)
/lib/ld-linux.so.2 (0xf7fc0000)
jack@nostromo:~/Desktop$ ldd /usr/bin/fuppes
libuuid.so.1 => /lib/libuuid.so.1 (0x00002b38281b5000)
libtag.so.1 => /usr/lib/libtag.so.1 (0x00002b38283b8000)
libMagick++.so.9 => /usr/lib/libMagick++.so.9 (0x00002b382860e000)
libMagick.so.9 => /usr/lib/libMagick.so.9 (0x00002b38288a0000)
libavformat.so.1d => /usr/lib/libavformat.so.1d (0x00002b3828e31000)
libavcodec.so.1d => /usr/lib/libavcodec.so.1d (0x00002b38290b6000)
libtheora.so.0 => /usr/lib/libtheora.so.0 (0x00002b3829706000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00002b3829839000)
libraw1394.so.8 => /usr/lib/libraw1394.so.8 (0x00002b3829b17000)
libavutil.so.1d => /usr/lib/libavutil.so.1d (0x00002b3829c1d000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00002b3829e27000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x00002b3829f52000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00002b382a057000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00002b382a273000)
libpcre.so.3 => /usr/lib/libpcre.so.3 (0x00002b382a4b1000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00002b382a5d0000)
libfuppes.so.0 => /usr/lib/libfuppes.so.0 (0x00002b382a836000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00002b382aaf9000)
libm.so.6 => /lib/libm.so.6 (0x00002b382ae00000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002b382b083000)
libc.so.6 => /lib/libc.so.6 (0x00002b382b291000)
libz.so.1 => /usr/lib/libz.so.1 (0x00002b382b5e2000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00002b382b7f9000)
libWand.so.9 => /usr/lib/libWand.so.9 (0x00002b382ba72000)
liblcms.so.1 => /usr/lib/liblcms.so.1 (0x00002b382bcaf000)
libtiff.so.4 => /usr/lib/libtiff.so.4 (0x00002b382bee4000)
libjasper.so.1 => /usr/lib/libjasper.so.1 (0x00002b382c03d000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x00002b382c192000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00002b382c2b5000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00002b382c4d9000)
libXt.so.6 => /usr/lib/libXt.so.6 (0x00002b382c5ea000)
libSM.so.6 => /usr/lib/libSM.so.6 (0x00002b382c84c000)
libICE.so.6 => /usr/lib/libICE.so.6 (0x00002b382ca54000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00002b382cb6f000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x00002b382cd73000)
libdl.so.2 => /lib/libdl.so.2 (0x00002b382cf83000)
libdc1394_control.so.13 => /usr/lib/libdc1394_control.so.13 (0x00002b382d187000)
liba52-0.7.4.so => /usr/lib/liba52-0.7.4.so (0x00002b382d297000)
libgsm.so.1 => /usr/lib/libgsm.so.1 (0x00002b382d3a2000)
/lib64/ld-linux-x86-64.so.2 (0x00002b3827f98000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00002b382d4b3000)
libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0x00002b382d5b5000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00002b382d7b7000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00002b382d9d2000)
jack@nostromo:~/Desktop$ ldd /usr/bin/mediatomb
libmysqlclient_r.so.15 => /usr/lib/libmysqlclient_r.so.15 (0x00002b77fe253000)
libmagic.so.1 => /usr/lib/libmagic.so.1 (0x00002b77fe55f000)
libid3-3.8.so.3 => /usr/lib/libid3-3.8.so.3 (0x00002b77fe770000)
librt.so.1 => /lib/librt.so.1 (0x00002b77fe8b1000)
libmozjs.so.0d => /usr/lib/libmozjs.so.0d (0x00002b77feabb000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00002b77fed7e000)
libz.so.1 => /usr/lib/libz.so.1 (0x00002b77fefe3000)
libexif.so.12 => /usr/lib/libexif.so.12 (0x00002b77ff1fa000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00002b77ff42c000)
libm.so.6 => /lib/libm.so.6 (0x00002b77ff733000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002b77ff9b6000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00002b77ffbc4000)
libc.so.6 => /lib/libc.so.6 (0x00002b77ffddf000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00002b7800131000)
libnsl.so.1 => /lib/libnsl.so.1 (0x00002b7800365000)
/lib64/ld-linux-x86-64.so.2 (0x00002b77fe036000)
libnspr4.so.0d => /usr/lib/libnspr4.so.0d (0x00002b780057d000)
libdl.so.2 => /lib/libdl.so.2 (0x00002b78006b7000)
jack@nostromo:~/Desktop$ ldd /usr/bin/ushare
libupnp.so.2 => /usr/lib/libupnp.so.2 (0x00002aee6de7c000)
libthreadutil.so.2 => /usr/lib/libthreadutil.so.2 (0x00002aee6e0a0000)
libixml.so.2 => /usr/lib/libixml.so.2 (0x00002aee6e2a5000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00002aee6e4b0000)
libc.so.6 => /lib/libc.so.6 (0x00002aee6e6cc000)
/lib64/ld-linux-x86-64.so.2 (0x00002aee6dc5f000)
cytochrome, ogre_x are you running twonky on linux too? If yes, then we might have a platform specific problem.
Twonky developers, please give a sign in this thread
Thanks everyone for any additional info!
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
I have empirically tested the server on Windows and the problem is not present there. Since my only 24/7 machine runs linux (ClarkConnect 4.1) I really want it to work.
I have confimed that the problem is there on Fedora Core 6 as well.
So, yes, it seems to be a Linux problem. Below is the ldd output for 4.2Beta3, which is the latest version that works.
I have confimed that the problem is there on Fedora Core 6 as well.
So, yes, it seems to be a Linux problem. Below is the ldd output for 4.2Beta3, which is the latest version that works.
Code: Select all
4.2Beta3
[root@moosewall]# ldd /opt/TwonkyMedia/twonkymedia
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00579000)
libc.so.6 => /lib/tls/libc.so.6 (0x00858000)
/lib/ld-linux.so.2 (0x001f9000)
4.4Beta3
[root@moosewall]# ldd /opt/TwonkyMedia-4.4Beta3/twonkymedia
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00c39000)
libdl.so.2 => /lib/libdl.so.2 (0x0021b000)
libc.so.6 => /lib/tls/libc.so.6 (0x00996000)
/lib/ld-linux.so.2 (0x001b8000)
-
- Posts:17
- Joined:Fri Sep 16, 2005 12:49 pm
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
Thanks guys!
It looks like that the use of libdl is the main change in between the two versions. Now, I have read a bit about libdl itself, and it looks like it is a quite basic library, but honestly (as I said, IANAProgrammer) that's our best bet so far.
Just for sake of completeness, could you report here the version of kernel and glibc/libc6?
On my box:
It looks like that the use of libdl is the main change in between the two versions. Now, I have read a bit about libdl itself, and it looks like it is a quite basic library, but honestly (as I said, IANAProgrammer) that's our best bet so far.
Just for sake of completeness, could you report here the version of kernel and glibc/libc6?
On my box:
Code: Select all
jack@nostromo:~$ uname -r
2.6.20-1-amd64
jack@nostromo:~$ dpkg -l libc6*
libc6 2.5-9
libc6-dev 2.5-9
libc6-i386 2.5-9
-
- Posts:17
- Joined:Fri Sep 16, 2005 12:49 pm
Here are my data:
Have a nice sunday!
Code: Select all
slug:~# uname -r
2.6.18-4-ixp4xx
slug:~# dpkg -l libc6
libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
Here are my stats:
Code: Select all
[moosewall ~]$ uname -r
2.6.9-42.cc
[moosewall ~]$ rpm -qa|grep libc
glibc-2.3.4-2.36
libcap-1.10-20
libc-client-2002e-14
glibc-common-2.3.4-2.36
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
I just checked for libdl in other versions, and they didn't start using it until 4.3:
and since it stopped working in 4.2 Beta 4 before 4.2 was released we can at least say that the problem should lie elsewhere.
Yes, I'm getting annoyed as well, since I reported this in february...
Ps. I can't start ushare on my machine,
Code: Select all
[]# ldd /opt/TwonkyMedia-4.2.1/twonkymediaserver
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00bb7000)
libc.so.6 => /lib/tls/libc.so.6 (0x00111000)
/lib/ld-linux.so.2 (0x00ab7000)
[]# ldd /opt/TwonkyMedia-4.3/twonkymediaserver
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00441000)
libdl.so.2 => /lib/libdl.so.2 (0x00af8000)
libc.so.6 => /lib/tls/libc.so.6 (0x00459000)
/lib/ld-linux.so.2 (0x007c5000)
Yes, I'm getting annoyed as well, since I reported this in february...
Ps. I can't start ushare on my machine,
Any Ideas how I can get a little more information out of ushare as to whats wrong?Initializing UPnP subsystem ...
Cannot initialize UPnP subsystem
Stopping UPnP Service ...
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
I finally figured out what I had done wrong when trying to add the multicast route, so this should make Twonky somewhat happier I think - however no changes in the crashing behavior on my DSM-320.
Ps. uShare started OK after adding the multicast route, and I haven't been able to reproduce the video crashing the DSM-320 with that one - maybe something for the Twonky developers to look into.
Ps. uShare started OK after adding the multicast route, and I haven't been able to reproduce the video crashing the DSM-320 with that one - maybe something for the Twonky developers to look into.
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
An Update from Christian on the issue - bad news I'm afraid.
It looks like we will have to look for another product or get another mediastreamer. Its a bit sad since Twonky worked so well before.
I don't agree that the release notes should state that the DSM-problem has been fixed, since it's still there in Linux, but anyway this means that the Twonkyserver as of 4.2Beta4 is useless for serving video from Linux to DSM-320. That should be stated in the RevisionHistory as a non-feature.twonky-christian wrote:on the DMS-320
we changed the communication with the D-Link and it is now able to play much more videos - so the notes are correct
we did not address the bug that the D-Link DSM-320 can not play back DivX from our Linux server - this is not fixed (and looks like we can not fix it at all)
Anyway - the revision history stays valid
It looks like we will have to look for another product or get another mediastreamer. Its a bit sad since Twonky worked so well before.
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
-
- Posts:30
- Joined:Sat Feb 11, 2006 1:44 pm
I'd have to query something in the update from Christian. He stated that the problem was only with DivX playback from Linux servers. I'm having the problem of the DSM-320 locking up with MPEG videos on all versions from 4.2b4 onwards. So I think this is a bigger problem, i.e. all videos, than he is making out....
BTW I really like 4.2b3. It's the only version of any media server that allows me to use my DSM properly. So thanks to every one at Twonky for it!
However, I think that if the problem can't/won't be fixed, then DSM-320 Linux users should be directed by Twonky to use 4.2b3, and the old license scheme should be continued indefinitely, for this version on Linux This will allow people to have properly working software that they have paid for.
BTW I really like 4.2b3. It's the only version of any media server that allows me to use my DSM properly. So thanks to every one at Twonky for it!
However, I think that if the problem can't/won't be fixed, then DSM-320 Linux users should be directed by Twonky to use 4.2b3, and the old license scheme should be continued indefinitely, for this version on Linux This will allow people to have properly working software that they have paid for.
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
I agree on the 4.2beta3 part - it's working great on linux. I'm just annoyed that the bug has been ignored for a number of months and the fact that I paid for a year worth of upgrades (which is kind of useless when you can't run the newer versions of the software)
I really can't understand that a serious software company can't make a diff between the codebase for 4.2beta3 and 4 when the problems appeared. But then again this is the problem with proprietary software - if too few users complain the problem won't get fixed.
Since uShare works serving XviD content from Linux to DSM-320 there might be something for the twonky team to analyze there.
I really can't understand that a serious software company can't make a diff between the codebase for 4.2beta3 and 4 when the problems appeared. But then again this is the problem with proprietary software - if too few users complain the problem won't get fixed.
Since uShare works serving XviD content from Linux to DSM-320 there might be something for the twonky team to analyze there.
- twonky-christian
- Lynx Technology Staff
- Posts:1123
- Joined:Fri Sep 10, 2004 3:16 pm
- AV Hardware:PC
- Location:Berlin
- Contact:
Hi,
you may try to change the clients.db file on Linux to get the DSM-320 to work:
Try these settings:
ID:006
NA:D-Link DSM320
PX:800
PY:600
TX:120
TY:90
XM:DLINKTHUMB
DX:REDSONIC
AV:no-m3u
DD:DSM-320
HH:dma/1.0 redsonic
XM:FORCERES
XM:DLNANO
DB:FIX
MT:aif,aiff audio/aiff
MT:avi video/avi
MT:divx video/x-msvideo
MT:flac audio/flac
MT:lpcm,pcm audio/lpcm
MT:m4a,mp4.a,3gp.a,m4b audio/mp4
MT:mp1,mp2 audio/mpeg
MT:mp4 video/MP4V-ES
MT:mpg,m1v,mpe video/MP1S
MT:ogg audio/x-ogg
MT:ts video/mpeg
MT:wav audio/wav
XM:gif NORES
It may also be worthwile to change the mime type for the extensions where you see the problems....
Christian
you may try to change the clients.db file on Linux to get the DSM-320 to work:
Try these settings:
ID:006
NA:D-Link DSM320
PX:800
PY:600
TX:120
TY:90
XM:DLINKTHUMB
DX:REDSONIC
AV:no-m3u
DD:DSM-320
HH:dma/1.0 redsonic
XM:FORCERES
XM:DLNANO
DB:FIX
MT:aif,aiff audio/aiff
MT:avi video/avi
MT:divx video/x-msvideo
MT:flac audio/flac
MT:lpcm,pcm audio/lpcm
MT:m4a,mp4.a,3gp.a,m4b audio/mp4
MT:mp1,mp2 audio/mpeg
MT:mp4 video/MP4V-ES
MT:mpg,m1v,mpe video/MP1S
MT:ogg audio/x-ogg
MT:ts video/mpeg
MT:wav audio/wav
XM:gif NORES
It may also be worthwile to change the mime type for the extensions where you see the problems....
Christian
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
Hi,
Didn't work for me, however it might be something with the client adaption.
When I installed the new server and rebooted the d-link I got only three menu alternatives (music, pictures, video). Usually I get a bit more graphical start menu.
I tried my XviD and it played fine and didn't crash on the second one.
My theory is that Twonky doesn't set the client adaption until next reboot of the D-link.
Rebooted the d-link, and now I got the usual graphical start-menu. Tried my XviD, and BOOM D-link crashes about 20 seconds into the second XviD.
So the question is, what does the entry in clients.db look like when the server hasn't yet set the client type?
Didn't work for me, however it might be something with the client adaption.
When I installed the new server and rebooted the d-link I got only three menu alternatives (music, pictures, video). Usually I get a bit more graphical start menu.
I tried my XviD and it played fine and didn't crash on the second one.
My theory is that Twonky doesn't set the client adaption until next reboot of the D-link.
Rebooted the d-link, and now I got the usual graphical start-menu. Tried my XviD, and BOOM D-link crashes about 20 seconds into the second XviD.
So the question is, what does the entry in clients.db look like when the server hasn't yet set the client type?
- twonky-christian
- Lynx Technology Staff
- Posts:1123
- Joined:Fri Sep 10, 2004 3:16 pm
- AV Hardware:PC
- Location:Berlin
- Contact:
-
- Posts:75
- Joined:Tue Sep 05, 2006 7:12 am
- AV Hardware:ClearOS 5.1 Linux server (4.4.18)
ClearOS 5.1 Linux server (5.1.3)
PS3
HDX-HD1000 - Location:Stockholm, Sweden
- Contact:
Code: Select all
ID:000
NA:-/-
DB:AUTO
ID:001
NA:Generic Media Receiver
XM:DLNA15
I guess that you rewrote the client adaption layer between 4.2b3 and b4, so that's why you have a hard time finding the settings used then?
-
- Posts:26
- Joined:Sat Nov 11, 2006 10:15 am