[mythtv] RE: New version of windows filters (was: Mythweb andWindows Media Player over Samba)

[bobnvic at everestkc.net]

Torbjörn Jansson wrote:
> > Here is the relevant part of my mythbackend log using -v all:
> > 2004-05-17 21:55:35 WriteBlock(): Aborting WriteBlock, write
> > to socket failed!
> > 2004-05-17 21:55:35 2       -1
> > 
> > I installed the 0.6.2 filters on my desktop and was able to connect
> > to the backend and watch the recording.  Here's the logfile:
> 
> It's strange that it works on one computer and not the other.
> Is it posibel that you have different types of networks on those two
> computers? I think I remember you said something about wirless lan 
> or maybe that was someone else.
> Or is there different versions of windows on those two computers?

Both the laptop and desktop have winxp sp1.  The backend is connected
to the wireless router via 11g.  The desktop is connected directly to 
the wireless router via 100T and the laptop is connected to the wireless
router via 11g (infrastructure network), so the laptop definitely has 
more latency than the desktop, which would support what you say below.

> I think I have an idea on whats going on and I think I can 
> reproduce the
> problem, actualy I think when I increased the request size from 
> 65536 to 128000 I got the same problem.
> 
> Maybe someone that know a bit more about the mythtv network 
> protocol can answer this question:
> During filtransfer does mythbackend expect data to be read from 
> the data socket during a REQUEST_BLOCK command?
> When request block returns with a response all data shod have been 
> readright?
> 
> So if someone (me) desides to first send a REQUEST_BLOCK and then 
> wait for
> it to complete before reading from the socket bad thing will 
> happen, unless
> the default buffer windows uses for the socket happends to be 
> larger than the request size.
> 
> That woud explain why it worked on some computers and not others.
> 
> > However, the sound was slightly off and would become several
> > seconds delayed after seeking.  I use a PVR-250 to record,
> > then transcode to MPEG-4, and I had not edited the recording.
> > I watched an MPEG-2 recording that hadn't finished transcoding
> > and the sound was in sync both before and after seeking, however
> > the player did crash on me a couple of times when seeking.
> > 
> > Any idea why one computer would get the writeblock error and not
> > the other?  Is the audio snyc issue a known problem with transcoded
> > recordings? 
> > 
> 
> The file you had a/v sync problems was a mpeg4/rtjpeg (nupplevideo 
> type)file right?

Yes, it was mpeg4 nuv transcoded from mpeg2 in mythtv, no cuts.

> It may be caused by how I fixed the transcodeing support, when I 
> did it I
> realized I may have caused some a/v sync problems if the audio 
> timestamps is
> not in sync with the video timestamps at the new position.

Thanks,
Bob C