blocks|key|3829298|text|您可以在RFC+2326+"Real+Time+Streaming+Protocol+(RTSP)"中获得所有功能。你需要"10.12嵌入式(交错)二进制数据“：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3829299|3829300|流数据(如RTP包)由ASCII元符号(24个十六进制)封装，后跟单字节通道标识符，后跟封装的二进制数据的长度，以网络字节顺序显示为二进制、双字节整数。流数据紧随其后，没有CRLF，但包括上层协议报头。每个$块恰好包含一个上层协议数据单元，例如一个RTP分组。|blockquote|3829301|3829302|3829303|这里也有一个小例子：|3829304|+S->C:+$\000{2+byte+length}{"length"+bytes+data,+w/RTP+header}
+S->C:+$\000{2+byte+length}{"length"+bytes+data,+w/RTP+header}
+S->C:+$\001{2+byte+length}{"length"+bytes++RTCP+packet}|code-block|syntax|javascript|3829305|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ietf.org/rfc/rfc2326.txt^0|4|1A|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|13|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|C|$]]|$1|L|3|M|5|N|7|17|8|@]|9|@]|C|$O|P]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

You have it all in <a href="http://www.ietf.org/rfc/rfc2326.txt" rel="nofollow">RFC 2326 "Real Time Streaming Protocol (RTSP)"</a>. You need "10.12 Embedded (Interleaved) Binary Data":

<blockquote>
 Stream data such as RTP packets is encapsulated by an ASCII dollar sign (24 hexadecimal), followed by a one-byte channel identifier, followed by the length of the encapsulated binary data as a binary, two-byte integer in network byte order. The stream data follows immediately afterwards, without a CRLF, but including the upper-layer protocol headers. Each $ block contains exactly one upper-layer protocol data unit, e.g., one RTP packet.
</blockquote>

There is a small example there as well:

<pre><code> S-&gt;C: $\000{2 byte length}{"length" bytes data, w/RTP header}
 S-&gt;C: $\000{2 byte length}{"length" bytes data, w/RTP header}
 S-&gt;C: $\001{2 byte length}{"length" bytes RTCP packet}
</code></pre>

blocks|key|48432|text|获取PPS非常简单，实际上不需要解析数据包。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|48433|我猜，您的SPS请求将需要进入数据包(我认为您不需要担心WS+msg“无效数据包”。|48434|在PT中使用0x09的Type如何？|48435|有关数据包的描述，请参阅here|offset|length|48436|在answer+here中解包RTP的示例实现|48437|尝试在here上查找与RTSP控制和SDP+over+TCP相关的更多信息。如果您正在查看RTSP会话/对话的详细信息，以及有关视频中各个轨道的控制协议选择的消息详细信息。如果你可以在不转向SDP+/+RTCP的情况下得到你的答案，那么很明显，这会更快/更好。|48438|entityMap|0|LINK|mutability|MUTABLE|url|http://www.networksorcery.com/enp/protocol/rtp.htm#PT,%2520Payload%2520Type|1|https://stackoverflow.com/questions/10171542/rtsp-rtp-client-streaming-timestamp-live555/10195274#10195274|2|http://tools.ietf.org/id/draft-ietf-mmusic-sdp-tcpmedia-00.txt^0|0|0|0|C|4|0|0|8|4|1|0|3|4|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@$H|13|I|14|1|15]]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@$H|17|I|18|1|19]]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@$H|1B|I|1C|1|1D]]|A|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]]]

Getting PPS is IMO straightforward and does not really require parseing the packet.

Your request for SPS , im guessing , will require getting into the packet ( i dont think you need to worry about WS msg 'invalid packet'. 

What about using Type at PT at 0x09 ?

see <a href="http://www.networksorcery.com/enp/protocol/rtp.htm#PT,%20Payload%20Type" rel="nofollow noreferrer">here</a> for packet description

sample implementations of unpacking RTP in the answer <a href="https://stackoverflow.com/questions/10171542/rtsp-rtp-client-streaming-timestamp-live555/10195274#10195274">here</a>

try looking <a href="http://tools.ietf.org/id/draft-ietf-mmusic-sdp-tcpmedia-00.txt" rel="nofollow noreferrer">here</a> for more info related to RTSP control and SDP over TCP. If you are getting into inspecting the details of the RTSP session/conversation and the messaging details about control protocol selection for the respective tracks in your video. If u can get your answer without a diversion into SDP / RTCP then , obviously, thats faster/better.

blocks|key|48469|text|以下是TCP/RTP的数据包格式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|48470|[$+-+1byte][Transport+Channel+-+1byte][RTP+data+length+-+2bytes][RTP+data]|code-block|syntax|javascript|48471|剩下的就像upd一样|48472|有关更多信息，请阅读process+raw+rtp+packets|offset|length|48473|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/7665217/how-to-process-raw-udp-packets-so-that-they-can-be-decoded-by-a-decoder-filter-i^0|0|0|0|A|N|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

this is the packet format for TCP/RTP :

<pre><code>[$ - 1byte][Transport Channel - 1byte][RTP data length - 2bytes][RTP data]
</code></pre>

the rest is like upd

for more info read <a href="https://stackoverflow.com/questions/7665217/how-to-process-raw-udp-packets-so-that-they-can-be-decoded-by-a-decoder-filter-i">process raw rtp packets</a>

blocks|key|48493|text|只要解释一下，我也在为此工作，如果你想在TCP上使用RTSP，请小心你的套接字读取代码。合适的socket进程如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|48494|while+(socket.connected)+{
++char+magic+=+socket.read+a+char;
++if+(magic+==+'$')+{++//+is+a+RTP+over+TCP+packet
+++++byte+channel+=+socket.read+1+byte;
+++++unsigned+short+len+=+socket.read+2+byte;+//+len+=+((byte1+&+0xFF)+<<+8)+%2B+(byte2+&0xFF);
+++++int+readTotal+=+0;
+++++byte+rtpPacket[len];
+++++while+(readTotal+<+len)+{
+++++++++//+read+remaing+bytes+to+rtpPacket+from+index+readTotal
+++++++++int+r+=+socket.read(rtpPacket,+readTotal,+len+-+readTotal);+
+++++++++if+(r+>+0)
++++++++++++readTotal+%2B=+r;
+++++++++else++++//+-1+means+socket+read+error
++++++++++++break;+++
+++++}
+++++//+now+we+get+full+RTP+packet,+process+it!
+++++call+back+channel,+rtpPacket;
++}+else+{++//+is+RTSP+protocol+response
+++++string+array+header;
+++++while+(line+=+socket.readline()+!=+null)+{
++++++++if+(line+==+"")+{
+++++++++++int+body_len+=+Parse+header+"Content-Length";
+++++++++++byte+body[body_len];
+++++++++++int+readBody+=+0;
+++++++++++while+(readBody+<+body_len)+{
++++++++++++++int+r+=+socket.read(body,+readBody,+body_len+-+readBody);
++++++++++++++if+(r>0)
++++++++++++++++readBody+%2B=+r;
++++++++++++++else
++++++++++++++++break;
+++++++++++}

+++++++++++//+Now+we+get+full+header,+body+of+RTSP+response,+process+it
+++++++++++Callback+header,+body;+++
++++++++}+else+{
+++++++++++header.add(line);
++++++++}
+++++}
++}
}|code-block|syntax|javascript|48495|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Just explain something, I'm working for this as well, If you want use RTSP over TCP, please be careful about your socket reading code.
The suitable socket process like below:
<pre><code>while (socket.connected) {
 char magic = socket.read a char;
 if (magic == '$') { // is a RTP over TCP packet
 byte channel = socket.read 1 byte;
 unsigned short len = socket.read 2 byte; // len = ((byte1 &amp; 0xFF) &lt;&lt; 8) + (byte2 &amp;0xFF);
 int readTotal = 0;
 byte rtpPacket[len];
 while (readTotal &lt; len) {
 // read remaing bytes to rtpPacket from index readTotal
 int r = socket.read(rtpPacket, readTotal, len - readTotal); 
 if (r &gt; 0)
 readTotal += r;
 else // -1 means socket read error
 break; 
 }
 // now we get full RTP packet, process it!
 call back channel, rtpPacket;
 } else { // is RTSP protocol response
 string array header;
 while (line = socket.readline() != null) {
 if (line == &quot;&quot;) {
 int body_len = Parse header &quot;Content-Length&quot;;
 byte body[body_len];
 int readBody = 0;
 while (readBody &lt; body_len) {
 int r = socket.read(body, readBody, body_len - readBody);
 if (r&gt;0)
 readBody += r;
 else
 break;
 }

 // Now we get full header, body of RTSP response, process it
 Callback header, body; 
 } else {
 header.add(line);
 }
 }
 }
}
</code></pre>

I want to retrieve some video data from a device with RTSP. 

RTSP over UDP works well, but I need it over TCP.

After issuing the RTSP commands, I receive RTPs but I do not how to handle them here.
The payload is as follows: $[channel - 1 byte][length - 2bytes][data]

The thing is that I receive such packets and sometimes further packets where channel is 10 or 99 etc. 

So could anyone please provide some input on how to handle the payload ?

Grabbing video with RTSP over TCP

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我想从带有RTSP的设备中检索一些视频数据。UDP上的RTSP工作得很好，但我需要TCP上的RTSP。在发出RTSP命令后，我收到了RTSP，但我不知道如何在这里处理它们。有效载荷如下：$channel -1字节数据问题是，我会收到这样的数据包，有时还会收到通道为10或99等的其他数据包。那么，谁能提供一些关于如何处理有效负载的输入？

问使用TCP上的RTSP抓取视频
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用TCP上的RTSP抓取视频EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用TCP上的RTSP抓取视频
EN