[MPlayer-users] Netstream quirkyness - 1.0_pre5 vs 1.0_pre7

[Wicher]

Hi there,

After getting MPlayer-1.0_pre7's netstream to compile 
(thanks to these patches:
http://ogmrip.sourceforge.net/patches/netstream-1.0pre7-src.patch and
http://ogmrip.sourceforge.net/patches/netstream-1.0pre7-makefile.patch)

I noticed something very strange. With pre5-MPLayer & pre5 netstream
(working source here:
http://www.huizehennep.demon.nl/MPlayer-1.0pre5-Netstream.tar.bz2),

playing a DVD using mpst:// works fine. In other words,
"mplayer dvd://6" gives the same result as "mplayer
mpst://localhost/dvd://6". With pre7 this is not the case, as reading
the DVD via mpst results in skipping the first 3 minutes of chapter 1 on
the DVD. MPlayer seems to know about this, it displays the time
correctly (it starts at 0:02:54). Specifying -ss <timepos> doesn't help
at all. This doesn't happen if I play the DVD directly with pre7.

Furthermore, both with pre5 and pre7, mplayer mpst:// doesn't like it
when I specify something else than dvd://6:
MPEG-PS file format detected.
MPEG: No audio stream found -> no sound.
MPEG: FATAL: EOF while searching for sequence header.
and crashes:
MPlayer interrupted by signal 11 in module: init_audio_codec

But that could just be a quirky DVD. Also, after each connection,
netstream has to be restarted:
first time:
$ mplayer mpst://localhost/dvd://6
Reading disc structure, please wait...
There are 6 titles on this DVD.
There are 1 chapters in this DVD title.
There are 1 angles in this DVD title.
DVD successfully opened.

second time:
$ mplayer mpst://localhost/dvd://6
Reading disc structure, please wait...
There are 6 titles on this DVD.
There are 21 chapters in this DVD title.
There are 1 angles in this DVD title.
Invalid DVD angle number: 0

Now why does it complain about an angle number all of a sudden?
For my goals (network-distributed mencoding, serving the DVD via
netstream) the need-to-restart-netstream-on-successive-connections is
not a big issue, the can't-specify-anything-but-the-last-chapter issue
is a bigger issue, but the real showstopper is the
start-playing-at-wrong-position issue.

Can anyone confirm these issues? Any ideas on how to fix it?
Regards, Wicher.