Re: [FFmpeg-user] List members behaviour

2019-04-14 Thread Carl Eugen Hoyos
2019-04-14 16:07 GMT+02:00, Ulf Zibis :

> I don't know what to do right to fulfil his expectations.

You could read my mails...

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-user] scratch start ffmpeg > mpeg-dash multi encode

2019-04-14 Thread dan
I originally posted a script I was trying to use but I'm just not able
to get it to work.  Some politics on this mailing list that I can't
give any useful input too caused me to delay follow ups

Here's what I need to do :

I have a stream, it's either an http stream from an hdhomerun, or it's
an rtsp stream from a security camera.  I need to transcode that
stream for mpeg-dash, probably into 3 streams.  I have an nvidia
jetson nano on it's way and plan to use nvenc for h264 or h265.   It's
a maxwell gen2 with hardward support for 4 1080p h.264/5 encodes.
Unfortunately no VP9 encoding.

I can't seem to wrap my head around the maps and demuxing audio etc in
a single command and pushing output to a .hdr header file and .chk
chunk files.

Would someone be able to give me a very basic command to take this
input, encode it to 2 video and 1 audio stream?  If I have a
functional version I think I can reverse engineer it and understand
better.

Thanks.
___
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] Need info on ATSC3 stream capture going wrong

2019-04-14 Thread Carl Zwanzig

On 4/14/2019 7:14 AM, Deron wrote:
What appears to happen is some audio timestamp drift error is noticed, 
compensation is applied that perhaps has a math sign error, a whole lot of 
silence is inserted, the incoming data is ignored because of that silence, 
and the input buffer is overflowed.


I wonder, and this is just a WAG, if that stream has enough uncorrected bit 
errors spread around that the demux/decoder can't figure out where the data 
blocks start and then picks a likely spot that's wrong. Can you pick out the 
error stats for different channels and compare them?


z!

___
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] Need info on ATSC3 stream capture going wrong

2019-04-14 Thread Deron
Hello, this is a really strange one for me that is way outside my 
understanding. I've been using ffmpeg to stream tv shows and I've run 
across a TV station I can not capture! The symptoms are after 12:55 or 
so minutes the audio goes silent in the output, and shortly after that 
ffmpeg quits. This works with some 40 other tv channels!


I had to bump up the loglevel to 90(!) to see something that might 
explain this. Obviously 13 minutes of loglevel 90 is a huge amount of 
output, so I'm hoping I have identified the important part and make it 
obviously enough that someone might have some guidance on what is wrong. 
What appears to happen is some audio timestamp drift error is noticed, 
compensation is applied that perhaps has a math sign error, a whole lot 
of silence is inserted, the incoming data is ignored because of that 
silence, and the input buffer is overflowed.


Happy to provide complete uncut console data, but it is 50mb! Hopefully 
this is enough that someone can guide me to a solution!


Thanks,

Deron


Command (without proper shell quoting because it is not issued from the 
shell):


ffmpeg -loglevel 90 -f lavfi -i 
movie=/dev/dvb/adapter0/dvr0:f=mpegts:s=dv+da[out0+subcc][out1] 
-force_key_frames expr:gte(t,n_forced*2) -c:v libx264 -profile:v high 
-level:v 4.0 -vf scale=1280:720 -s 1280x720 -aspect 1280:720 -pix_fmt 
yuv420p -r 30 -preset veryfast -b:v 1200k -c:a libfdk_aac -cutoff 18000 
-b:a 128k -ar 48000 -ac 2 -async 2 -flags:a -global_header -af 
volume=volume=10.000dB:precision=float -f hls -hls_time 2 -hls_list_size 
10 -hls_wrap 99 -hls_flags delete_segments -hls_segment_filename 
/var/www/html/stream/v.mid.%06d.ts -y /var/www/html/stream/v.mid.m3u8 
-sn -force_key_frames expr:gte(t,n_forced*2) -c:v libx264 -profile:v 
high -level:v 4.0 -vf scale=640:360 -s 640x360 -aspect 640:360 -pix_fmt 
yuv420p -r 30 -preset veryfast -b:v 200k -c:a libfdk_aac -profile:a 
aac_he -cutoff 18000 -b:a 96k -ar 44100 -ac 1 -flags:a -global_header 
-af volume=volume=10.000dB:precision=float -f hls -hls_time 2 
-hls_list_size 10 -hls_wrap 99 -hls_flags delete_segments 
-hls_segment_filename /var/www/html/stream/v.portrait.%06d.ts -y 
/var/www/html/stream/v.portrait.m3u8 -sn -vn -c:a libfdk_aac -profile:a 
aac_he -cutoff 18000 -b:a 96k -ar 44100 -ac 2 -flags:a -global_header 
-af volume=volume=10.000dB:precision=float -f hls -hls_time 2 
-hls_list_size 10 -hls_wrap 99 -hls_flags delete_segments 
-hls_segment_filename /var/www/html/stream/a.hi.%06d.ts -y 
/var/www/html/stream/a.hi.m3u8 -sn -vn -c:a libfdk_aac -profile:a aac_he 
-cutoff 18000 -b:a 60k -ar 32000 -ac 1 -flags:a -global_header -af 
volume=volume=10.000dB:precision=float -f hls -hls_time 2 -hls_list_size 
10 -hls_wrap 99 -hls_flags delete_segments -hls_segment_filename 
/var/www/html/stream/a.low.%06d.ts -y /var/www/html/stream/a.low.m3u8 
-vf scale=426:240 -s 426x240 -aspect 426:240 -f image2 -vf fps=fps=2 -y 
/var/www/html/stream/t.%06d.jpg -vn -map a:0 -c:a pcm_s16le -ar 48000 
-ac 2 -f stream_segment -segment_time 2 -segment_format s16le -y 
/var/www/html/stream/a.loudness.%06d.pcm



ffmpeg version N-93562-g3e10223385 Copyright (c) 2000-2019 the FFmpeg 
developers

  built with gcc 7 (Ubuntu 7.2.0-8ubuntu3)
  configuration: --enable-shared --enable-gpl --enable-nonfree 
--enable-libxvid --enable-libx264 --enable-libmp3lame --enable-libvorbis 
--enable-libfdk-aac --disable-stripping

  libavutil  56. 26.100 / 56. 26.100
  libavcodec 58. 50.100 / 58. 50.100
  libavformat    58. 27.102 / 58. 27.102
  libavdevice    58.  7.100 / 58.  7.100
  libavfilter 7. 48.100 /  7. 48.100
  libswscale  5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc    55.  4.100 / 55.  4.100

< ... snip ...>

[graph_1_aresample_in_0_1 @ 0x56452dc9ad00] [SWR @ 0x56452dc9b600] 
compensating audio timestamp drift:-0.001021 compensation:-2 in:48000
[graph_1_aresample_in_0_1 @ 0x56452dc9ad00] [SWR @ 0x56452dc9b600] Using 
fltp internally between filters
[graph_3_aresample_in_0_1 @ 0x56452dc5e480] [SWR @ 0x56452ddb9600] 
compensating audio timestamp drift:-0.001021 compensation:-2 in:48000
[graph_3_aresample_in_0_1 @ 0x56452dc5e480] [SWR @ 0x56452ddb9600] Using 
fltp internally between filters
[graph_4_aresample_in_0_1 @ 0x56452dda0380] [SWR @ 0x56452dda1080] 
compensating audio timestamp drift:-0.001021 compensation:-2 in:48000
[graph_4_aresample_in_0_1 @ 0x56452dda0380] [SWR @ 0x56452dda1080] Using 
fltp internally between filters
[graph_5_aresample_in_0_1 @ 0x56452f0c9200] [SWR @ 0x56452f0c9c40] 
compensating audio timestamp drift:-0.001021 compensation:-2 in:48000
[graph_5_aresample_in_0_1 @ 0x56452f0c9200] [SWR @ 0x56452f0c9c40] Using 
fltp internally between filters
[graph_7_aresample_in_0_1 @ 0x56452f18a740] [SWR @ 0x56452f18b180] 
compensating audio timestamp drift:-0.001021 compensation:-2 in:48000
[graph_7_aresample_in_0_1 @ 0x56452f18a740] [SWR @ 0x56452f18b180] Using 
fltp internally between filters


Re: [FFmpeg-user] List members behaviour

2019-04-14 Thread Ulf Zibis

Am 13.04.19 um 21:01 schrieb CherylJosie via ffmpeg-user:
>>> this sort of bad behaviour."/
>> If anyone has an idea, how to deal with that, please write.
>> -Ulf
> 
> I’ll take a stab at it.
> We cannot control the behavior of others. We can only control our own 
> behavior.
> We might all first look within for solutions that work for us as individuals 
> rather than trying to impose our solutions on others through the list. Angry 
> outbursts backfire.
> Humility can solve this issue. Failing that, I’m sure list moderation will if 
> it hasn’t already done so. A public spat is not a FOSS existential crisis. We 
> are free to choose hope. Let’s do that.
> If anyone is feeling angry, I’d say diagnose your anger and put out that fire 
> before trying to extinguish it in others. (In my calmer moments anyway that’s 
> how I think)
> Remember that the objective here is sharing knowledge. That’s not what has 
> been shared between Reindl and others on this particular matter. It’s off 
> topic. I’m not sure anyone profits from an addictive group adrenaline binge, 
> or from the cortisol that eats away at us all from the inside out long after 
> the rush fades.
> The spark only ignited all the gasoline fumes lingering in the air. It’s not 
> the root cause of the flame war, it’s just the trigger. Removing the trigger 
> is far less effective than venting the fumes. Then a spark without fumes is 
> an amusing and harmless flash instead of a disaster.
> We are all under stress. I’m sure Reindl’s frustration plus all those 
> frustrated responses to him have their roots deep in the personal lives of 
> those making posts. That’s where the solutions are too, deep inside. Look 
> there.
> Give yourself a break. Vent the fumes elsewhere and stay on topic. That’s the 
> best way IMO. I know it’s difficult to control one’s anger in the face of 
> provocation, but ego doesn’t write FOSS software. Anger is a distraction. 
> Keep that in mind and this problem solves itself.
> IMHO, offered in the spirit of the FOSS authors who brought me so many 
> amazing benefits that I feel truly blessed by all your generosity.

Thanks, CherylJosie, for your words.

Referring
> Remember that the objective here is sharing knowledge.
I'm now stuck with these 1-line comments from Paul B Mahol:

> - Patches are big mess.
> - You showed very little skills.
> - You obviously lack git skills.

I don't know what to do right to fulfil his expectations.

-Ulf


>
> On Saturday, April 13, 2019, 4:35 AM, Ulf Zibis  wrote:
>
>
> Am 11.04.19 um 18:57 schrieb Nicolas George:
>> Ulf Zibis (12019-04-11):
>>> Even "staff members" in this project seem to do so, see posts in
>> One "staff member", please. His behaviour is unacceptable and you are
>> welcome to report him to the list administrator.
>>
>>> It is good to mention, then accept it and then take a big breathe!
>> No, it is not good to accept it. Reindl Harald is being extremely rude,
>> he does the exact opposite than he wants other people to do.
>>
>> Regards,
> Hi,
>
> I'm not sure, if you misunderstood me. I did not bear on Harald.
> I don't know, if he is actively supporting FFmpeg or just using it. But
> as I have no cause to communicate with him, I just watch, what happens
> without participation.
>
> I beard on one who is actively supporting FFmpeg, i.e. the 2nd most busy
> committer to FFmpeg. I'm really interested in cooperation.
>
> So I see me in the category of potential contributors, Phil has written
> about:
> /"This holds back open source software in all its forms. It serves to
> put off new users who might become useful contributors in time. It
> alienates people with useful expertise who are not software engineers.
> The problems caused by all of this are highly visible in open source
> software in general, and ffmpeg in particular.//
> //I don't know what the solution is, but it must necessarily involve
> everyone being nicer to each other, and not trying to jusify
> unprofessional, discourteous behaviour.//
> //I've been saying it for years and I'm going to keep saying it: FOSS
> could do so much better than it does, almost solely because of exactly
> this sort of bad behaviour."/
>
> If anyone has an idea, how to deal with that, please write.
>
> -Ulf
>
> ___
> 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 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 mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email