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
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Can not watch tv from remote clients
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="mm1352000" data-source="post: 1268326" data-attributes="member: 82144"><p>Thanks for the new log files. Short summary would be that I can't see any significant differences from the previous log files.</p><p></p><p>Interestingly, it appears like the remote client is able to acquire the stream description and duration from the streaming server:</p><p>[2020-02-13 11:16:21,335] [139A7098] [2c38] - CRTSPClient::OpenStream(): duration = 1.180000 s</p><p>[2020-02-13 11:16:21,338] [139A7098] [2c38] - CRTSPClient::OpenStream(): created receiver for sub-session, medium name = video, codec name = MP2T, port = 49302</p><p></p><p>The client just can't start streaming for some reason. Very odd!</p><p></p><p>I wonder if the timeout error message:</p><p>[2020-02-13 11:16:21,338] [139A7098] [2c38] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />etupStreams(): send RTSP SETUP</p><p>[2020-02-13 11:16:21,839] [139A7098] [2c38] - CRTSPClient:<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />etupStreams(): RTSP SETUP timed out</p><p></p><p>...is actually pointing directly to the problem. In other words: rather than a firewall intercepting the communication, maybe the server is just a little slow to respond due to network links (wireless network?) and disk speed (system and/or timeshift disks on the server are HDDs or SSDs?).</p><p></p><p>There are several ways we could move forward from here.</p><p></p><p>Option one would be to actually check the timeout theory. This could be done by using a network traffic monitor such as Wireshark on the client and/or server to confirm that the RTSP SETUP command is sent by the client, received by the server, and acknowledged by the server. Assuming the SETUP acknowledgement is sent by the server, it would be possible to measure how long it takes for the client to receive that acknowledgement. Normally this whole process should be very fast - maybe a tenth of a second at most. The error message quoted above indicates that in your case no acknowledgement was received after half a second.</p><p></p><p>Option two would be to assume the timeout theory is correct, and try to give the server more time to do what it needs to do. This is probably easier than the first option, but again, it does make the assumption that the timeout theory is correct. The mechanism for giving the server more time is to add/modify one of TsReader's settings. TsReader's settings are stored in the Windows system registry. I've attached a zip file containing scripts that should enable you to make the change fairly easily:</p><ol> <li data-xf-list-type="ol">On the remote client, download and extract TsReader_RTSP_registry_settings.zip to a convenient location.</li> <li data-xf-list-type="ol">Close MediaPortal.</li> <li data-xf-list-type="ol">Run (double click) the "set_2_seconds.reg" file to make the change. You may have to click "yes" to accept security warnings.</li> <li data-xf-list-type="ol">Open MediaPortal and test whether TV works.</li> <li data-xf-list-type="ol">(To undo the changes, close MediaPortal and run "reset_to_default.reg".)</li> </ol><p>Please note that changing the contents of the Windows system registry is not something I'd recommend lightly. Some of the most important Windows and program settings are stored in there. Without meaning to frighten you, a bad modification could cause a PC to stop working, break or change the behaviour of installed programs, or open security loopholes. Though I can hand-on-heart say I have zero interest in wrecking your setup, I'd still recommend that you exercise caution. Feel free to have a look at the contents of the scripts (right click -> edit) that I've provided. (The setting I intend to add/change is TsReader's RtspGenericTimeoutInMilliSeconds.)</p><p></p><p>Option three would be to try an alternative way of accessing TV from the server. Specifically: you can configure MediaPortal and TV Server to use shares ("UNC paths") rather than RTSP streaming. The details are in the wiki here:</p><p>[URL unfurl="true"]https://www.team-mediaportal.com/wiki/display/MediaPortal1/Advanced+Options#AdvancedOptions-Multi-seatsetup[/URL]</p><p></p><p>Given that you've mentioned you have shares working already, this might not be a bad option to consider.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1268326, member: 82144"] Thanks for the new log files. Short summary would be that I can't see any significant differences from the previous log files. Interestingly, it appears like the remote client is able to acquire the stream description and duration from the streaming server: [2020-02-13 11:16:21,335] [139A7098] [2c38] - CRTSPClient::OpenStream(): duration = 1.180000 s [2020-02-13 11:16:21,338] [139A7098] [2c38] - CRTSPClient::OpenStream(): created receiver for sub-session, medium name = video, codec name = MP2T, port = 49302 The client just can't start streaming for some reason. Very odd! I wonder if the timeout error message: [2020-02-13 11:16:21,338] [139A7098] [2c38] - CRTSPClient::SetupStreams(): send RTSP SETUP [2020-02-13 11:16:21,839] [139A7098] [2c38] - CRTSPClient::SetupStreams(): RTSP SETUP timed out ...is actually pointing directly to the problem. In other words: rather than a firewall intercepting the communication, maybe the server is just a little slow to respond due to network links (wireless network?) and disk speed (system and/or timeshift disks on the server are HDDs or SSDs?). There are several ways we could move forward from here. Option one would be to actually check the timeout theory. This could be done by using a network traffic monitor such as Wireshark on the client and/or server to confirm that the RTSP SETUP command is sent by the client, received by the server, and acknowledged by the server. Assuming the SETUP acknowledgement is sent by the server, it would be possible to measure how long it takes for the client to receive that acknowledgement. Normally this whole process should be very fast - maybe a tenth of a second at most. The error message quoted above indicates that in your case no acknowledgement was received after half a second. Option two would be to assume the timeout theory is correct, and try to give the server more time to do what it needs to do. This is probably easier than the first option, but again, it does make the assumption that the timeout theory is correct. The mechanism for giving the server more time is to add/modify one of TsReader's settings. TsReader's settings are stored in the Windows system registry. I've attached a zip file containing scripts that should enable you to make the change fairly easily: [LIST=1] [*]On the remote client, download and extract TsReader_RTSP_registry_settings.zip to a convenient location. [*]Close MediaPortal. [*]Run (double click) the "set_2_seconds.reg" file to make the change. You may have to click "yes" to accept security warnings. [*]Open MediaPortal and test whether TV works. [*](To undo the changes, close MediaPortal and run "reset_to_default.reg".) [/LIST] Please note that changing the contents of the Windows system registry is not something I'd recommend lightly. Some of the most important Windows and program settings are stored in there. Without meaning to frighten you, a bad modification could cause a PC to stop working, break or change the behaviour of installed programs, or open security loopholes. Though I can hand-on-heart say I have zero interest in wrecking your setup, I'd still recommend that you exercise caution. Feel free to have a look at the contents of the scripts (right click -> edit) that I've provided. (The setting I intend to add/change is TsReader's RtspGenericTimeoutInMilliSeconds.) Option three would be to try an alternative way of accessing TV from the server. Specifically: you can configure MediaPortal and TV Server to use shares ("UNC paths") rather than RTSP streaming. The details are in the wiki here: [URL unfurl="true"]https://www.team-mediaportal.com/wiki/display/MediaPortal1/Advanced+Options#AdvancedOptions-Multi-seatsetup[/URL] Given that you've mentioned you have shares working already, this might not be a bad option to consider. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Can not watch tv from remote clients
Contact us
RSS
Top
Bottom