Re: [FFmpeg-user] aacDecoder_DecodeFrame() failed

2019-12-10 Thread Kung, Andreas
This time I use build in aac decoder instead of fdk.

Sound mute, disappear after

Continuity check failed for pid 257 expected 8 got 9




Carl Eugen Hoyos  於 2019年12月10日 週二 下午8:23寫道:

> Am Di., 10. Dez. 2019 um 08:39 Uhr schrieb Kung, Andreas  >:
> >
> > When I try to play this stream with ffplay, many decode failed occurred.
> >
> > ffplay -infbuf -vn -acodec libfdk_aac
> > https://radio.mcu.edu.tw:8080/hls/a2/index.m3u8
> >
> >
> > [mpegts @ 0x7f97028b7400] PES packet size mismatch sq=0B f=0/0
> > [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 4007
> > [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 1001
> > [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 4004
>
> Complete, uncut console output and libfdk version information missing.
>
> I cannot reproduce the error messages but the stream apparently has a
> bandwidth issue, if it works with other players there may be an unknown
> issue though.
>
> Carl Eugen
> ___
> 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".


ffmpeg.log
Description: Binary data
___
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".

Re: [FFmpeg-user] aacDecoder_DecodeFrame() failed

2019-12-10 Thread Moritz Barsnick
On Tue, Dec 10, 2019 at 15:31:37 +0800, Kung, Andreas wrote:
> ffplay -infbuf -vn -acodec libfdk_aac
> https://radio.mcu.edu.tw:8080/hls/a2/index.m3u8
>
> [mpegts @ 0x7f97028b7400] PES packet size mismatch sq=0B f=0/0
> [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 4007
> [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 1001
> [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 4004
>
> output sound sometimes corrupted or muted.

I get masses of other errors from this stream, incl. TLS errors, a lot
of video errors, and so on.

ffplay has a native AAC decoder, you could try that as well 8as these
errors come from fdk_aac, driven by an external library), but I'm sure
it will also error out.

> I can play the same stream with VLC or Google Chrome.

Interesting. This I don't understand. (Can't reproduce right now, my
Opera won't behave like Chrome and play the m3u8 directly, and I don't
have VLC installed anymore.)

Moritz
___
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".

Re: [FFmpeg-user] aacDecoder_DecodeFrame() failed

2019-12-10 Thread Carl Eugen Hoyos
Am Di., 10. Dez. 2019 um 08:39 Uhr schrieb Kung, Andreas :
>
> When I try to play this stream with ffplay, many decode failed occurred.
>
> ffplay -infbuf -vn -acodec libfdk_aac
> https://radio.mcu.edu.tw:8080/hls/a2/index.m3u8
>
>
> [mpegts @ 0x7f97028b7400] PES packet size mismatch sq=0B f=0/0
> [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 4007
> [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 1001
> [libfdk_aac @ 0x7f96fe890600] aacDecoder_DecodeFrame() failed: 4004

Complete, uncut console output and libfdk version information missing.

I cannot reproduce the error messages but the stream apparently has a
bandwidth issue, if it works with other players there may be an unknown
issue though.

Carl Eugen
___
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".

Re: [FFmpeg-user] FFMpeg stream audio problem

2019-12-10 Thread Csaba
Dear Moritz,

Thank you for your help. I appreciate it.

You wrote:

> It is so incorrect that ffmpeg should trip over the two usage errors
> and report them to you in a very obvious fashion.

> Do you happen to be suppressing your output?

I got the output with the following redirection commands:
./scriptname > scriptname.log 2>&1 &
I do not know what happened.

You wrote:

> Have you tried just reading the input, and not feeding it to the net?:
> $ ffmpeg -f alsa -i plughw:1,0 -f null -

It is operating.

I corrected the errors, thank you.
I would like to stream the soundcard input to the net:
#!/bin/sh
ffmpeg -f alsa -i plughw:1,0 -acodec libmp3lame -ac 1 -f mp3
http://192.168.1.20:8080
 but i got a following error log:

Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, alsa, from 'plughw:1,0':
  Duration: N/A, start: 1576038182.094342, bitrate: 1536 kb/s
Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
[tcp @ 0x562b13aa0340] Connection to tcp://192.168.1.20:8080 failed:
Connection refused
http://192.168.1.20:8080: Connection refused

192.168.1.20 is the IP address of this machine's eth0 card. I would
like to connect to this IP address from another machine on my LAN.
I want direct streaming, without a server.
I have read the following in streaming guide that no built-in server.
I do not know to stream it with icecast2 or other server, i would like
to significantly reduce latency. Streaming with VLC is operating and
it produce latency. I would like to try to streaming with ffmpeg but
it even does not work.

Thank you for your help again.

Best regards: Csaba
___
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".

[FFmpeg-user] RTMP handshaking behind a proxy

2019-12-10 Thread Verachten Bruno
Hi there,

I unfortunately have to stream from behind a proxy. It works on one of my
machines thanks to redsocks. The RTMP handshake goes well, and I can stream
to twitch or youtube.
On another machine, with the same redsocks configuration, the handshake
never finishes, be it with youtube or twitch. The ffmpeg command is just a
copy of an already h.264 encoded stream from rtmp to rtmp.

My question is: is there a random port opened for the negotiation? Where
should I look for the blocking of the handshake?

Here is the command I have and the output:
ffmpeg -i "$SOURCE" -c:v copy -c:a copy -f flv "$YOUTUBE_URL/$KEY"
-loglevel debug
[...]
Splitting the commandline.
Reading option '-i' ... matched as input url with argument 'rtmp://
192.168.1.217:1935/live/stream15'.
Reading option '-c:v' ... matched as option 'c' (codec name) with argument
'copy'.
Reading option '-c:a' ... matched as option 'c' (codec name) with argument
'copy'.
Reading option '-f' ... matched as option 'f' (force format) with argument
'flv'.
Reading option 'rtmp://live-cdg.twitch.tv/app/live_of_myself' ... matched
as output url.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging
level) with argument 'debug'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Successfully parsed a group of options.
Parsing a group of options: input url rtmp://
192.168.1.217:1935/live/stream15.
Successfully parsed a group of options.
Opening an input file: rtmp://192.168.1.217:1935/live/stream15.
[NULL @ 0xc401d0] Opening 'rtmp://192.168.1.217:1935/live/stream15' for
reading
[rtmp @ 0xc40990] No default whitelist set
[tcp @ 0xc41010] No default whitelist set
[tcp @ 0xc41010] Original list of addresses:
[tcp @ 0xc41010] Address 192.168.1.217 port 1935
[tcp @ 0xc41010] Interleaved list of addresses:
[tcp @ 0xc41010] Address 192.168.1.217 port 1935
[tcp @ 0xc41010] Starting connection attempt to 192.168.1.217 port 1935
[tcp @ 0xc41010] Successfully connected to 192.168.1.217 port 1935
[rtmp @ 0xc40990] Handshaking...
[rtmp @ 0xc40990] Type answer 3
[rtmp @ 0xc40990] Server version 13.14.10.13
[rtmp @ 0xc40990] Proto = rtmp, path = /live/stream15, app = live, fname =
stream15
[rtmp @ 0xc40990] Window acknowledgement size = 500
[rtmp @ 0xc40990] Max sent, unacked = 500
[rtmp @ 0xc40990] New incoming chunk size = 20480
[rtmp @ 0xc40990] Creating stream...
[rtmp @ 0xc40990] Sending play command for 'stream15'
[flv @ 0xc401d0] Format flv probed with size=2048 and score=100
[flv @ 0xc401d0] Before avformat_find_stream_info() pos: 13 bytes
read:32868 seeks:0 nb_streams:0
[flv @ 0xc401d0] Unknown type |RtmpSampleAccess
[NULL @ 0xc432a0] nal_unit_type: 7(SPS), nal_ref_idc: 3
[NULL @ 0xc432a0] nal_unit_type: 8(PPS), nal_ref_idc: 3
[NULL @ 0xc432a0] unknown SEI type 229
[h264 @ 0xc432a0] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0xc432a0] nal_unit_type: 8(PPS), nal_ref_idc: 3
[h264 @ 0xc432a0] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0xc432a0] nal_unit_type: 8(PPS), nal_ref_idc: 3
[h264 @ 0xc432a0] nal_unit_type: 6(SEI), nal_ref_idc: 0
[h264 @ 0xc432a0] nal_unit_type: 5(IDR), nal_ref_idc: 3
[h264 @ 0xc432a0] unknown SEI type 229
[h264 @ 0xc432a0] Format yuv420p chosen by get_format().
[h264 @ 0xc432a0] Reinit context to 1920x1088, pix_fmt: yuv420p
[h264 @ 0xc432a0] nal_unit_type: 1(Coded slice of a non-IDR picture),
nal_ref_idc: 3
Last message repeated 5 times
[flv @ 0xc401d0] All info found
[flv @ 0xc401d0] rfps: 29.75 0.015408
[flv @ 0xc401d0] rfps: 29.83 0.010802
[flv @ 0xc401d0] rfps: 29.916667 0.008256
[flv @ 0xc401d0] rfps: 30.00 0.007768
Last message repeated 1 times
[flv @ 0xc401d0] rfps: 29.970030 0.007707
Last message repeated 1 times
[flv @ 0xc401d0] Setting avg frame rate based on r frame rate
[flv @ 0xc401d0] After avformat_find_stream_info() pos: 66491 bytes
read:66491 seeks:0 frames:105
Input #0, flv, from 'rtmp://192.168.1.217:1935/live/stream15':
  Duration: N/A, start: 9159.905000, bitrate: N/A
Stream #0:0, 41, 1/1000: Video: h264 (High), 1 reference frame,
yuv420p(progressive, left), 1920x1080 (1920x1088), 0/1, 29.97 fps, 29.97
tbr, 1k tbn
Stream #0:1, 64, 1/1000: Audio: aac (LC), 48000 Hz, stereo, fltp
Successfully opened the file.
Parsing a group of options: output url rtmp://
live-cdg.twitch.tv/app/live_of_myself.
Applying option c:v (codec name) with argument copy.
Applying option c:a (codec name) with argument copy.
Applying option f (force format) with argument flv.
Successfully parsed a group of options.
Opening an output file: rtmp://live-cdg.twitch.tv/app/live_of_myself.
[rtmp @ 0xc528c0] No default whitelist set
[tcp @ 0xcacff0] No default whitelist set
[tcp @ 0xcacff0] Original list of addresses:
[tcp @ 0xcacff0] Address 52.223.195.16 port 1935
[tcp @ 0xcacff0] Address 52.223.195.119 port 1935
[tcp @ 0xcacff0] Address 52.223.195.169 port 1935
[tcp @ 0xcacff0] Address 52.223.195.205 port 

Re: [FFmpeg-user] Dolby Vision

2019-12-10 Thread Mark Himsley
On Sun, 8 Dec 2019 at 10:03, Ted Park  wrote:
>
> > When I play the file downloaded from that page on an VG 4K Dolby
> > Vision capable TV it plays correctly with the right colours, but the
> > colours are way wrong when decoded/converted with FFmpeg.
> >
> > Should I be expecting Dolby Vision files to decode correctly? I mean,
> > it's very close, but just not quite right.
> I’m not sure, I think so? But when you are transcoding to h264 and yuv420p, 
> the point is sort of moot.

The command line was an example. Encoding to yuv420p should not make
such a difference in the luminance and colours.

As I understand it, FFmpeg (the libav libraries) can convert HLD and
'standard' PQ from HDR to SDR acceptably. (VLC also does the job
admirably). With HLG I imagine that a LUT needs to be applied to
compress the peek whites and deep blacks. I don't quite know what
happens with PQ, perhaps its similar. But with Dolby Vision there is
the sub-layer of metadata.


> > $ ffmpeg -i 'LG Amaze Dolby Vision UHD 4K Demo.ts'  -sws_flags lanczos
> > -filter:v "scale=1920:1080:interl=0,format=yuv420p" -c:v libx264 -crf
> > 18 -an -y out.mkv
>
>
> I think it might have the capability to at least decode and remux the data 
> since the mov demuxer just happens after hevc notices nal unit 62
> > [hevc @ 0x37c9ec0] Skipping NAL unit 62
> > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'LG Amaze Dolby Vision UHD 4K 
> > Demo.ts':
> >  Metadata:
> >major_brand : mp42
> >minor_version   : 1
> >compatible_brands: mp42dby1isom
> >creation_time   : 2017-04-13T20:09:18.00Z
> >  Duration: 00:00:56.20, start: 0.00, bitrate: 28362 kb/s
> >Stream #0:0(und): Video: hevc (Main 10) (dvhe / 0x65687664),
> > yuv420p10le(tv), 3840x2160 [SAR 1:1 DAR 16:9], 27713 kb/s, 60 fps, 60
> > tbr, 60k tbn, 60 tbc (default)
> > ...
> > Stream mapping:
> >  Stream #0:0 -> #0:0 (hevc (native) -> h264 (libx264))
> > Press [q] to stop, [?] for help
> > [hevc @ 0x37f3380] Skipping NAL unit 62
> > [hevc @ 0x37fa1c0] Skipping NAL unit 62
> > [hevc @ 0x380ce80] Skipping NAL unit 62
> > [hevc @ 0x385de80] Skipping NAL unit 62
> > [hevc @ 0x386e700] Skipping NAL unit 62
> > [hevc @ 0x38d8940] Skipping NAL unit 62
> > [hevc @ 0x38e9080] Skipping NAL unit 62
> > [hevc @ 0x38f98c0] Skipping NAL unit 62
> > [hevc @ 0x390a140] Skipping NAL unit 62
> > [hevc @ 0x37f3380] Skipping NAL unit 62
> > [hevc @ 0x37fa1c0] Skipping NAL unit 62
> > [libx264 @ 0x37f2940] using SAR=1/1
> > [libx264 @ 0x37f2940] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
> > [hevc @ 0x380ce80] Skipping NAL unit 62
> > [libx264 @ 0x37f2940] profile Progressive High, level 4.2, 4:2:0, 8-bit
> > [libx264 @ 0x37f2940] 264 - core 157 r2969 d4099dd - H.264/MPEG-4 AVC
> > codec - Copyleft 2003-2019 - http://www.videolan.org/x264.html -
> > options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7
> > psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
> > 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2
> > threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1
> > interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2
> > b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
> > keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf
> > mbtree=1 crf=18.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40
> > aq=1:1.00
> > Output #0, matroska, to 'out.mkv':
> >  Metadata:
> >major_brand : mp42
> >minor_version   : 1
> >compatible_brands: mp42dby1isom
> >encoder : Lavf58.35.100
> >Stream #0:0(und): Video: h264 (libx264) (H264 / 0x34363248),
> > yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 60 fps, 1k tbn, 60 tbc
> > (default)
> > ...
> > [hevc @ 0x385de80] Skipping NAL unit 62
> > [hevc @ 0x386e700] Skipping NAL unit 62
> > [hevc @ 0x38d8940] Skipping NAL unit 62
> > …
>
> But is it simply skipping or does it know what that signals? Also I’m not as 
> familiar with mkv, but is H264 as the codec normal instead of avc? Can it 
> handle the enhancement layer info?
>
> As far as “correctness” goes, the color probably is correct, as in it was 
> decoded and interpolated  the way it is supposed to be, but obviously it’s 
> not going to have the full range that you get from the output from a licensed 
> hardware decoder after you transcode from the minimal/compatibility hevc main 
> 10 to h264 42.

The colour (and luminance) which has been decoded, mapped between
colour-spaces, and and re-encoded is not correct. If you have a Dolby
Vision compatible TV you can see the difference very clearly. Do you
need me to point a camera at my TV to demonstrate :-)
___
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".

Re: [FFmpeg-user] Dolby Vision

2019-12-10 Thread Carl Eugen Hoyos
Am Sa., 7. Dez. 2019 um 15:43 Uhr schrieb Mark Himsley :

> There are some 4K Dolby Vision files around, like the one linked to
> directly from this page of this site, which are not decoded with the
> correct colours using git master head FFmpeg (compiled last weekend).
>
> https://4kmedia.org/lg-amaze-dolby-vision-uhd-4k-demo/

https://trac.ffmpeg.org/ticket/7624
There is a patch discussed on the FFmpeg development mailing list
that can fix the issue on Intel (?) cpus.

Carl Eugen
___
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".