On Mon, Jun 4, 2018 at 5:12 PM, Moritz Barsnick <barsn...@gmx.net> wrote:
> [Fixed the reply order for you, please try to avoid top-posting.] > > On Mon, Jun 04, 2018 at 15:26:11 +0530, Robert Clove wrote: > > On Mon, Jun 4, 2018 at 2:22 PM, Steinar H. Gunderson < > > steinar+ffm...@gunderson.no> wrote: > > > Maybe you can replay the raw packets with tcpreplay? > > Thats what i cant do, i am using the windows platform > > Why can't you do that? You do realize that tcpreplay is available for > Windows? (Albeit a bit older and "experimental".) > > If your raw dump happens to be PCAP, then you need some tool which can > disassemble the PCAP payload - that could be Wireshark or, as > mentioned, tcpreplay. > > If it's some other "raw" format, it depends on how it was created or > captured. It could be the pure payload: > https://osqa-ask.wireshark.org/questions/1062/about-rtp-raw-file > > How was the "raw" file created? > What does ffmpeg identify the "raw" file as? > > This is a topic for ffmpeg-user, BTW. > > Moritz > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > ffmpeg output for my file is as follows: *command:* ffmpeg.exe -i my.metadata -i mycapture.rtp output.h264 *output:* ffmpeg version N-91152-g7c333dc6a7 Copyright (c) 2000-2018 the FFmpeg developers [rtp @ 00000000003771c0] *Protocol 'rtp' not on whitelist 'file,crypto'!my.metadata: Invalid data found when processing input* *command:* ffmpeg.exe -protocol_whitelist file,udp,rtp -i my.metadata -i mycapture.rtp output.h264 *output:* ffmpeg version N-91152-g7c333dc6a7 Copyright (c) 2000-2018 the FFmpeg developers [udp @ 00000000003576c0] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) [udp @ 00000000003679c0] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) Incorrect amount of SRTP params [udp @ 0000000000342c40] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) [udp @ 000000000038a1c0] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) Incorrect amount of SRTP params [udp @ 000000000039aa40] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) [udp @ 00000000003aad40] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) Incorrect amount of SRTP params [udp @ 00000000003bb5c0] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) [udp @ 00000000003cb880] 'circular_buffer_size' option was set but it is not sup ported on this build (pthread support is required) Incorrect amount of SRTP params [sdp @ 0000000000342040] Could not find codec parameters for stream 0 (Audio: no ne, 8000 Hz, 1 channels): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [sdp @ 0000000000342040] Could not find codec parameters for stream 1 (Video: no ne, none): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [sdp @ 0000000000342040] Could not find codec parameters for stream 2 (Audio: no ne, 8000 Hz, 1 channels): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [sdp @ 0000000000342040] Could not find codec parameters for stream 3 (Video: no ne, none): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.0 : mono Guessed Channel Layout for Input Stream #0.2 : mono Input #0, sdp, from 'my.metadata': Metadata: title : session Duration: N/A, bitrate: N/A Stream #0:0: Audio: none, 8000 Hz, mono Stream #0:1: Video: none, none, 90k tbr, 90k tbn, 90k tbc Stream #0:2: Audio: none, 8000 Hz, mono Stream #0:3: Video: none, none, 90k tbr, 90k tbn, 90k tbc mycapture.rtp: Invalid data found when processing input _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
