home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
methods of using TV server - discussion thread
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Frodo" data-source="post: 82308" data-attributes="member: 10277"><p>Thats one of the reasons things take a bit longer then expected.</p><p>Most RTSP servers transmit mpeg-2 program streams instead of mpeg-2 transport streams.</p><p>mpeg-2 program files are not meant to be streamed</p><p>If you stream a mpeg-2 program stream to the client then 2 seperate udp streams are send. one for audio and one for video. In this case its both the task of the rtsp server & client to have exact timing and the client has to make sure it reads the audio/video streams</p><p>at the exact same time, if not lipsync issues will arive.</p><p>Now mpeg-2 transport streams are meant for streaming and thats why we're now working on streaming mpeg-2 transport streams.</p><p>With mpeg-2 transport streams only 1 UDP stream is send. This way the client only receives 1 stream and doesnt have todo anything for good a/v sync correction</p><p>Besides that a mpeg-2 transport stream contains internal sync correction for preventing lipsync issues. Meaning that lipsync issues should not occur anymore</p><p></p><p></p><p>The tvserver engine will record in mpeg-2 program stream format (.mpg)</p><p>However although the stream is a normal .mpg file, it probably is not dvd compliant due to the fact that all (DVB) broadcasters dont transmit DVD compliant files. Now most DVD players dont need a true DVD compliant file and will happily play any .mpg file. If you want a true DVD compliant file, you should re-encode it</p><p></p><p></p><p>Frodo</p></blockquote><p></p>
[QUOTE="Frodo, post: 82308, member: 10277"] Thats one of the reasons things take a bit longer then expected. Most RTSP servers transmit mpeg-2 program streams instead of mpeg-2 transport streams. mpeg-2 program files are not meant to be streamed If you stream a mpeg-2 program stream to the client then 2 seperate udp streams are send. one for audio and one for video. In this case its both the task of the rtsp server & client to have exact timing and the client has to make sure it reads the audio/video streams at the exact same time, if not lipsync issues will arive. Now mpeg-2 transport streams are meant for streaming and thats why we're now working on streaming mpeg-2 transport streams. With mpeg-2 transport streams only 1 UDP stream is send. This way the client only receives 1 stream and doesnt have todo anything for good a/v sync correction Besides that a mpeg-2 transport stream contains internal sync correction for preventing lipsync issues. Meaning that lipsync issues should not occur anymore The tvserver engine will record in mpeg-2 program stream format (.mpg) However although the stream is a normal .mpg file, it probably is not dvd compliant due to the fact that all (DVB) broadcasters dont transmit DVD compliant files. Now most DVD players dont need a true DVD compliant file and will happily play any .mpg file. If you want a true DVD compliant file, you should re-encode it Frodo [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
methods of using TV server - discussion thread
Contact us
RSS
Top
Bottom