Hi,
I just upgraded to vdr 1.3.22 and discovered that there are still problems with playback over NFS and 54 MBit WLAN.
When I read the the video files with dd and 8kB blocksize I get a data rate of about 1200 kB/s, and this should be sufficient to playback any recording.
It seems that vdr doesn't fill used buffer aggressively enough. The file reader should keep the buffer at the top limit so that dvbplayer always has enough data available. When I stop playback I get the info that 0 % of the buffer was used.
I also increased various buffer sizes like PLAYERBUFSIZE to 8 MB, but this didn't help this time. In 1.2 this solved any problems most of the time.
I activated DEBUGRINGBUFFERS and set logging to 3 but I don't get any output.
Any ideas?
Emil
Emil Naepflein wrote:
Hi,
I just upgraded to vdr 1.3.22 and discovered that there are still problems with playback over NFS and 54 MBit WLAN.
I hate to say that, but it works fine here, both on the wired lan (my vdr machine is diskless) and on the wireless lan (replaying on a laptop with the xine plugin, either with an nfs mounted directory or live video through streamdev). I have various patches applied, but none of them modifies receiver/player/etc., maybe the combined dvb/ttx subs patch, but I doubt it helps for this matter. Both machines are running a stock mandrake kernel (2.6.3-7mdk on the nfs server, 2.6.8.1-24mdk on the client), both have an atheros based 11g card using the madwifi driver (different cvs versions on the server and client), the server is configured as an access point.
Bye
On Sat, 05 Mar 2005 12:55:09 +0100, Luca Olivetti wrote:
I hate to say that, but it works fine here, both on the wired lan (my vdr machine is diskless)
100 MBit wired is much faster an you get less errors than with 54 MBit wlan.
and on the wireless lan (replaying on a laptop with the xine plugin, either with an nfs mounted directory or live video through streamdev).
Do you use NFS over TCP/IP?
Both machines are running a stock mandrake kernel (2.6.3-7mdk on the nfs server, 2.6.8.1-24mdk on the client),
I have a 2.4.21 kernel on the client and 2.4.19 on server.
both have an atheros based 11g card using the madwifi driver (different cvs versions on the server and client), the server is configured as an access point.
I also use the madwifi driver on the client. The server is connected to a NETGear 108 MBit access point.
A throughput of 1200 KB/s should be enough if buffering works right. And if I specify a 8 MB buffer this covers more than 10 s of playback.
Why does vdr not fill up its input buffer?
Emil
Emil Naepflein wrote:
On Sat, 05 Mar 2005 12:55:09 +0100, Luca Olivetti wrote:
I hate to say that, but it works fine here, both on the wired lan (my vdr machine is diskless)
100 MBit wired is much faster an you get less errors than with 54 MBit wlan.
and on the wireless lan (replaying on a laptop with the xine plugin, either with an nfs mounted directory or live video through streamdev).
Do you use NFS over TCP/IP?
udp
Both machines are running a stock mandrake kernel (2.6.3-7mdk on the nfs server, 2.6.8.1-24mdk on the client),
I have a 2.4.21 kernel on the client and 2.4.19 on server.
maybe nfs support has improved in kernel 2.6
both have an atheros based 11g card using the madwifi driver (different cvs versions on the server and client), the server is configured as an access point.
I also use the madwifi driver on the client. The server is connected to a NETGear 108 MBit access point.
A throughput of 1200 KB/s should be enough if buffering works right. And if I specify a 8 MB buffer this covers more than 10 s of playback.
Well, for me (depending on the channel) it actually works well with a throughput of 400..600KB/s (as reported by gkrellm). My ntp mount options are rsize=8192,wsize=8192
Bye
-
Emil Naepflein -
Luca Olivetti