Re: vls doesn't stop sending...

Heok Kee Oon wrote:
> Hi,
> 
>    There is a NEED for me to find out what frames
> (whether I, P or B) is transmitted or received, so if
> you don't mind, can you send me the codes and some
> instructions? ;)
> 
>    The protocol we've ported to is called SCTP. Some
> more things I've found out:
>    1. Once vlc is connected to vls, a window pops up
> in vlc.
>    2. Data is transmitted from vls to vlc, but nothing
> is shown in the window (all black).
>    3. For a video that takes the vlc about 30 sec to
> play (from disk), the transmission between vls and vlc
> lasts for about 3 min before vls stop sending any
> data. Throughout this period, windows remain black.
> 
>    With only modifications to socket calls in the
> files listed below, I don't quite understand why it
> doesn't play the video.
> 
>    I've attached the log files of both the vlc and vls
> with this mail. Hope that it provides some clues...
> 
> 
> 
> Oon, Heok Kee
> 
> 
> Tristan Leteurtre <[email protected]>
> wrote:
> 
>>Hi Oon,
>>
>>On Thu, Oct 24, 2002, Heok Kee Oon wrote:
>>
>>>   Few questions. Firstly, which function in which
>>>file is responsible for reading and
>>
>>differentiating
>>
>>>the various frames (I, B and P) before splitting
>>
>>and
>>
>>>multiplexing them into a TS stream?
>>
>>The vls does not deal with I,B and P frames, since
>>it is only concerned
>>by the system layer. The splitting/multiplexing is
>>made with PID
>>selecting, not with frame seclection (ES layer).
>>
>>If you *really* need a type_of_frame function for
>>vls, I used to write
>>one some times ago...
>> 
>>
>>>   Secondly, I've successfully switched out the
>>
>>UDP
>>
>>>transport layer and incorporated a new transport
>>
>>layer
>>
>>>protocol for the data transmission. 
>>
>>Which one ? ;)
>>
>>
>>>However, after the
>>>change (probably by accident) my modified version
>>>DOESN'T STOP sending data to the client. This is a
>>>list of files that I've modified:
>>>(...) 
Find out by running (after doing "make distclean" in both directories):

  "diff -urN vls-0.3.3-orig/ vls-0.3.3-modified/ | less"

This will tell you any change you've made to the source code base since 
the original version.


> 2002-10-26 13:28:50 [INFO/Vls]  Browsing modules in directory "/usr/local/lib/videolan/vls"
> 2002-10-26 13:28:50 [WARN/Vls]  Unable to browse directory "/usr/local/lib/videolan/vls" : Error: Could not open directory '/usr/local/lib/videolan/vls': No such file or directory

Add /usr/local/lib to /etc/ld.so.conf and run /sbin/ldconfig afterwards 
(as root of course)

> 2002-10-26 13:29:22 [DEBUG/Vls]  In ps2ts.h line 72 -> New instance of module "mpegconverter:ps2ts"
> 2002-10-26 13:29:22 [DEBUG/local1]  In ps2ts.cpp line 93 -> Mpeg version : 2
> 2002-10-26 13:29:22 [DEBUG/local1]  In ps2ts.cpp line 96 -> Preparsing : yes
> 2002-10-26 13:29:22 [DEBUG/local1]  In ps2ts.cpp line 167 -> Starting to read program "dolby"

Are you using Dolby.vob from the VideoLAN site as reference?


> ------------------------------------------------------------------------
> 
> root@eng91628-cir vlc-0.4.4]# ./vlc > vlc_run.log
> VideoLAN Client - version 0.4.4_2002-10-01 Ourumov - (c) 1996-2002 VideoLAN
> thread info: 3076 has been joined ((unknown):0)
> module: unlocking module `mpeg_vdec'
> input: packet lost by TS demux: current 0, packet 6

Your network dropped some packets. What kind of network do you have?

BTW are you streaming using your new protocol or did you use udp?
-- 
Kind greetings,

Jean-Paul Saman

Software Architect

e-mail (work): [email protected]
phone  (work): 040 27 42909
------------------------------------------------------------
Ordina TA,
Science Park Eindhoven 5602, Postbus 293, 5600 AG Eindhoven
e-mail : [email protected]
phone  : 040 2601200
fax    : 040 2601199

-- 
This is the vls-devel mailing-list, see http://www.videolan.org/vls-devel/
To unsubscribe, please read http://www.videolan.org/lists.html
If you are in trouble, please contact <[email protected]>