> In my trace which I had analyzed as a proof of concept, HTTP was > perfectly recognized. I had used port 8888, while my Wireshark's HTTP > protocol seems to be configured to > "80,3128,3132,5985,8080,8088,11371,1900,2869,2710". So Wireshark should > be smart enough...
You must be right, the only thing I can think of is if the capture was started after ffmpeg was run and only the chunked content was captured that can’t be decoded without the headers. >> The more important question is if there is an issue: Segmentation Fault 11 > > This is not an issue. I can segment the mpegts chunks just fine. This error > is coming due to the nature of how I am running my server side `-f null -` > to output null to stdin (not how I would normally) for the sole purpose of > testing network transport. You misunderstand, the message isn’t regarding segmenting the stream, it might indicate an issue within ffmpeg itself _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".