Reply to thread

Message

<blockquote data-quote="georgius" data-source="post: 728113" data-attributes="member: 107951">Re: AW: Re: IPTV/DVB-IP in MP: Support for http, rtp and udpYes, you're right actually is not working (all RTP code is commented). I'm planning to add support as soon as possible, but I don't know any RTP stream. I can simulate streams with VLC, but it's not as real stream.I choose non-blocking sockets, so on any of network methods code did't stop. Filter must periodicaly check requests in DoBufferProcessingLoop() method and also gather data from network (doesn't matter if UDP or HTTP). Also gathering data must periodicaly check if filter don't stopping its work.10 ms is enough time to give other threads some time to work (at least for DoBufferProcessingLoop() and in case of received data for FillBuffer() too). Because non-blocking sockets are used, the recvfrom() method exits immediately if no data received. It can cause high CPU load, if no data available and gathering thread is always checking if data are received. Also internal socket buffer is set to much higher value (from 32 KB to 1MB), which should be enough - if gathering thread waits longer, data are not lost.Friendly, I didn't compare polling and winsock implementation. I just reverted to old code (the code in TvService 1.1.3 on SVN) because it was working (your version wasn't working - at least for me).</blockquote>

[QUOTE="georgius, post: 728113, member: 107951"] [b]Re: AW: Re: IPTV/DVB-IP in MP: Support for http, rtp and udp[/b] Yes, you're right actually is not working (all RTP code is commented). I'm planning to add support as soon as possible, but I don't know any RTP stream. I can simulate streams with VLC, but it's not as real stream. I choose non-blocking sockets, so on any of network methods code did't stop. Filter must periodicaly check requests in DoBufferProcessingLoop() method and also gather data from network (doesn't matter if UDP or HTTP). Also gathering data must periodicaly check if filter don't stopping its work. 10 ms is enough time to give other threads some time to work (at least for DoBufferProcessingLoop() and in case of received data for FillBuffer() too). Because non-blocking sockets are used, the recvfrom() method exits immediately if no data received. It can cause high CPU load, if no data available and gathering thread is always checking if data are received. Also internal socket buffer is set to much higher value (from 32 KB to 1MB), which should be enough - if gathering thread waits longer, data are not lost. Friendly, I didn't compare polling and winsock implementation. I just reverted to old code (the code in TvService 1.1.3 on SVN) because it was working (your version wasn't working - at least for me). [/QUOTE]

Verification