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
WebService and Mobile Access
Popular Plugins
MPExtended
HTTP Live Streaming Issues
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="Oxan" data-source="post: 989941" data-attributes="member: 97484"><p>The MEDIA_ERROR_SERVER_DIED error usually indicates that the codec has encountered a bug and crashed, and shouldn't be related to problems in the video stream. </p><p> </p><p></p><p>MPExtended uses pipes to write the original video stream to the transcoder (ffmpeg/VLC) and to get the transcoded stream back. The error means that a process has closed one of the pipes, and that a subsequent read or write failed. However, that's a totally normal situation when the stream should be stopped. MPExtended kills the transcoder, which closes the pipes before it exits. MPExtended is still copying input data to the pipe and reading output data from the pipe, so it gives an error. It would be a bit neater if we could stop copying the input data and reading the output data before we kill the transcoder, but that'd require some complicated code in the streaming service. This works too, and doesn't hurt anything. </p><p></p><p>If you look closely, you'll see that those errors always happen immediately after a FinishStream call. They're not related to your problem. </p><p></p><p>It's a bit problematic for me to debug your problem, as I can't reproduce it on my system, and there aren't any errors in your logs either. I suspect it might have something to do with the transcoder speed: the transcoder isn't finished with the next segment before the client requests it. I don't have any proof for that though, and it's quite hard to prove without manually inspecting the stream in real-time. The fact that streaming recordings works fine seems to oppose this theory too. </p><p></p><p>It could also be useful to (manually, probably) try a Direct stream of the live TV. If streaming that (i.e. maybe it doesn't playback, but MPExtended keeps sending data) doesn't work either, it's for sure that the problem is in the TsBuffer reading code. However, I'd really expect some more errors in your logs then.</p></blockquote><p></p>
[QUOTE="Oxan, post: 989941, member: 97484"] The MEDIA_ERROR_SERVER_DIED error usually indicates that the codec has encountered a bug and crashed, and shouldn't be related to problems in the video stream. MPExtended uses pipes to write the original video stream to the transcoder (ffmpeg/VLC) and to get the transcoded stream back. The error means that a process has closed one of the pipes, and that a subsequent read or write failed. However, that's a totally normal situation when the stream should be stopped. MPExtended kills the transcoder, which closes the pipes before it exits. MPExtended is still copying input data to the pipe and reading output data from the pipe, so it gives an error. It would be a bit neater if we could stop copying the input data and reading the output data before we kill the transcoder, but that'd require some complicated code in the streaming service. This works too, and doesn't hurt anything. If you look closely, you'll see that those errors always happen immediately after a FinishStream call. They're not related to your problem. It's a bit problematic for me to debug your problem, as I can't reproduce it on my system, and there aren't any errors in your logs either. I suspect it might have something to do with the transcoder speed: the transcoder isn't finished with the next segment before the client requests it. I don't have any proof for that though, and it's quite hard to prove without manually inspecting the stream in real-time. The fact that streaming recordings works fine seems to oppose this theory too. It could also be useful to (manually, probably) try a Direct stream of the live TV. If streaming that (i.e. maybe it doesn't playback, but MPExtended keeps sending data) doesn't work either, it's for sure that the problem is in the TsBuffer reading code. However, I'd really expect some more errors in your logs then. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
HTTP Live Streaming Issues
Contact us
RSS
Top
Bottom