The VideoLAN Forums

Oh, as far as why those numbers? Because 0x44A4 is 0x80 more than 0x4424, and my suspicion on seeing that was one bit in the type is actually part of the size. But I haven't been able to find anything which documents that.

None. The sum of my knowledge is Windows Media Player plays the stream, Silverlight plays the stream, mplayer plays the stream, VLC opens a connection and does not play the stream, and the above appears to be the difference. The stream URL is there and open, so it should be evident, at least, that t...

This patch fixes it, but i don't know if it's "right" --- /Users/shadow/Source/vlc/modules/access/mms/mmsh.c 2011-01-11 02:51:15.000000000 -0500 +++ modules/access/mms/mmsh.c 2011-01-16 20:13:15.000000000 -0500 @@ -948,6 +910,10 @@ p_ck->i_type = GetWLE( p_sys->buffer); p_ck->i_size = GetW...

Something's weird with GetWLE apparently; in the cases where the type is 0x44A4 i set it to 0x4424 and add 0x80 to the size, the stream plays fine.

So what does this mean?

[0x1030078a0] access_mms access error: invalid chunk FATAL (0x44a4)
[0x1030078a0] access_mms access error: EOF!

if i remove the error i can get skippy audio. still looking at *why*

running in --verbose=2 from a command line I get nothing but I'm betting you mean something else?

fwiw it's mms://wmc1.den.liquidcompass.net/WWCDFM

something recently changed with a stream I listen to and now VLC won't open it. other tools still do. i've looked at what's up with TCPdump and nothing obvious is happening. the stream simply stops being acked (tcp-wise) as if we have stopped bothering to service it. i'm perfectly happy to get my ha...