Thanks Jon - the only “true” reply, perhaps I wasn’t clear enough to say that I am writing my own server.

Do you have a transaction flow for the comms between client and server perhaps ? The Adobe one is not that clear to me.

Cheers,

Pieter

On 23/01/2018, at 3:35 AM, Jon V. <sybersnake@gmail.com> wrote:

Its the SetChunkSize packet.

000000  02 00 00 00 00 00 04 01 00 00 00 00 00 00 10 00   ................
received basic [ChunkFormat= 0, ChunkChannel= 2]
received header [ChunkFormat= 0, ChunkChannel= 2, TimeStamp(ms)= 0, Size(bytes)= 4, Stream= 0, Type= SetChunkSize]
completed packet [ChunkFormat= 0, ChunkChannel= 2, TimeStamp(ms)= 0, Size(bytes)= 4, Stream= 0, Type= SetChunkSize, Payload= {Size= 4096}], payload [00 00 10 00]

On Sun, Jan 21, 2018 at 4:43 AM, Pieter De Wit <pieter@insync.za.net> wrote:
Hi Guys,

I am trying to make a RTMP server that has access to the frames that are sent by the client. I have tried the following approaches

1) Code RTMP myself
2) use librtmp

On 1) I am failing on a “packet” sent that I can’t decode (I think) this is the hex dump of the packet:

[0000] 0x02 0x00 0x00 0x00 0x00 0x00 0x04 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x10 0x00

I get it right after the handshake is completed. I am using OBS as my client

On 2) I don’t seem to have any example servers - where can I find one ?

Thanks,

Pieter
_______________________________________________
rtmpdump mailing list
rtmpdump@mplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump

_______________________________________________
rtmpdump mailing list
rtmpdump@mplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump