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 2
Plugin Development
Testbuilds for Native MP2 TV - Updated for 10th AE Update 1 (2014-09-13)!
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: 1101450" data-attributes="member: 82144"><p>Hmmm, the specification is not really clear about this. If the problem is really that pids needs to be present in the SETUP request then surely the SAT>IP server should return non-OK result code? The logs and wireshark trace show that the SETUP (and PLAY) result code is OK, so I don't think this is really the problem... but of course it is easy to add pids to SETUP.</p><p></p><p></p><p>Yes please. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Looking at the wireshark trace, the thing that stands out to me is this:</p><p>[ATTACH=full]155485[/ATTACH]</p><p></p><p>We see the normal sequence: SETUP, OK, PLAY, OK... and then RTP + RTCP start to arrive. No problem with that.</p><p>However pay close attention to the time between the PLAY OK response and the arrival of the first RTCP packet. It seems to be ~1 second... but the specification says:</p><p></p><p></p><p></p><p></p><p>My interpretation of the standard would be that this SAT>IP should start sending RTCP (and empty RTP) as soon as it gets the PLAY request. Instead there is ~800 ms after the PLAY response where zero packets are sent.</p><p></p><p>Kay, do you think that is non-compliant... or normal/okay?</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1101450, member: 82144"] Hmmm, the specification is not really clear about this. If the problem is really that pids needs to be present in the SETUP request then surely the SAT>IP server should return non-OK result code? The logs and wireshark trace show that the SETUP (and PLAY) result code is OK, so I don't think this is really the problem... but of course it is easy to add pids to SETUP. Yes please. :) Looking at the wireshark trace, the thing that stands out to me is this: [ATTACH=full]155485[/ATTACH] We see the normal sequence: SETUP, OK, PLAY, OK... and then RTP + RTCP start to arrive. No problem with that. However pay close attention to the time between the PLAY OK response and the arrival of the first RTCP packet. It seems to be ~1 second... but the specification says: My interpretation of the standard would be that this SAT>IP should start sending RTCP (and empty RTP) as soon as it gets the PLAY request. Instead there is ~800 ms after the PLAY response where zero packets are sent. Kay, do you think that is non-compliant... or normal/okay? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
Testbuilds for Native MP2 TV - Updated for 10th AE Update 1 (2014-09-13)!
Contact us
RSS
Top
Bottom