[FFmpeg-user] Mystery container

[asdffdsa417 at yahoo.co.uk]

>
>> result: if VLC, then sensible output indicating mpegts, H.264. If
>> DVTEL encoder, a warning about a format detection score of 1 followed
>> by warnings and failure.
>
>Can you not share these results? Complete, uncut console output. You
>may even want to share a sample.
>

Sample encoder output here: https://drive.google.com/file/d/0B3r5v3QXiEe-U1JSdW9GdGpodEE/view?usp=sharing

FFprobe guesses the wrong format, so the console output is not very informative, but OK.

DVTEL case:
-----------------------
$ ffprobe dvtel_to_windows_unknown.saved_UDP_data_from_wireshark


ffprobe version N-72963-g907ac20 Copyright (c) 2007-2015 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  configuration: --prefix=/usr/local
[[...snip...]]

  libswresample   1.  2.100 /  1.  2.100

[aac @ 0x346ec40] Format aac detected only with low score of 1, misdetection possible!
[aac @ 0x346f680] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x346f680] Number of scalefactor bands in group (59) exceeds limit (49).
[aac @ 0x346f680] channel element 1.1 is not allocated
[aac @ 0x346f680] Reserved bit set.
[aac @ 0x346f680] Number of scalefactor bands in group (56) exceeds limit (41).
[aac @ 0x346f680] channel element 3.3 is not allocated
[aac @ 0x346f680] invalid band type
[aac @ 0x346f680] channel element 3.12 is not allocated
[aac @ 0x346f680] channel element 1.3 is not allocated
[[...etc...]]
[aac @ 0x24b0c40] Could not find codec parameters for stream 0 (Audio: aac (LTP), 5.1, fltp, 962 kb/s): unspecified sample rate
Consider increasing the value for the 'analyzeduration' and 'probesize' options
dvtel_to_windows_unknown.saved_UDP_data_from_wireshark: Operation not permitted

VLC case (I'm using ffmpeg to stream raw H.264 now, but the results are the same)

------------------------------------------------------------

remote $ ffmpeg -re -i video.mp4 -f h264 udp://10.2.213.251:1234
[ run wireshark capture ]


$ ffprobe ffmpeg_to_windows_saved_UDP_data_h264.h264

ffprobe version N-72963-g907ac20 Copyright (c) 2007-2015 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  configuration: --prefix=/usr/local
  libavutil      54. 27.100 / 54. 27.100
  libavcodec     56. 41.100 / 56. 41.100
  libavformat    56. 36.100 / 56. 36.100
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 17.100 /  5. 17.100
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  2.100 /  1.  2.100
Input #0, h264, from 'ffmpeg_to_windows_saved_UDP_data_h264.h264':
  Duration: N/A, bitrate: N/A
    Stream #0:0: Video: h264 (High), yuv420p, 720x576 [SAR 16:15 DAR 4:3], 12.50 fps, 12.50 tbr, 1200k tbn, 25 tbc


>Can mplayer dump the stream (using "-dumpstream", obviously)?

Recieve and dump the UDP stream? (Would this not be the same as using Wireshark?) Unlike ffmpeg, for the exact same streams, it gives me an error

$ mplayer udp://10.2.213.221:1234

MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing udp://10.2.213.221:1234.
STREAM_UDP, URL: udp://10.2.213.221:1234
Failed to connect to server
udp_streaming_start failed
No stream found to handle url udp://10.2.213.221:1234


Exiting... (End of file)



>Moritz
>
>_______________________________________________
>ffmpeg-user mailing list
>ffmpeg-user at ffmpeg.org
>http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>