Re: [FFmpeg-user] encoding H264 from pictures, encoding values manipulation

[Carl Eugen Hoyos]

Am Do., 21. Nov. 2019 um 11:03 Uhr schrieb Carl Eugen Hoyos
:
>
> Am Do., 21. Nov. 2019 um 10:55 Uhr schrieb Jorge Mas :
>
> > i changed the profile to Main
> >
> > the profile_idc change to 77, i need it to be 66 which it is
> > profile = baseline
>
> There is neither a known encoder nor a known decoder that

> supports the "baseline" profile, 77 is "constrained baseline"

Sorry, "constrained baseline" is a large number (66 plus
a constant), 77 is "main":

> which is supported by all encoders and decoders.
> (constrained baseline is a strict subset of baseline, so 66
> is not a wrong value, just a useless one. You can patch
> x264 if you need 66, short googling did not reveal an
> option to force this value.)

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 cuvid not transcoding properly

[Carl Eugen Hoyos]

Am Do., 21. Nov. 2019 um 10:17 Uhr schrieb Ted Park :

> > [AVHWFramesContext @ 0x3a36600] [IMGUTILS @ 0x7ffc3bcc6230] Picture
> > size 0x0 is invalid
> > [mpeg2_cuvid @ 0x3098a40] Error initializing a CUDA frame pool
> > cuvid hwaccel requested for input stream #0:0, but cannot be initialized.
> > [mpeg2_cuvid @ 0x3098a40] ff_get_format failed: -1
>
> It seems you have to specify frame size at the very least.

You cannot specify a frame size for mpeg video...

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] encoding H264 from pictures, encoding values manipulation

[Jorge Mas]

Hello Moritz.

i changed the profile to Main

the profile_idc change to 77, i need it to be 66 which it is profile =
baseline


this is the difference using ffmpeg -i

original video
  libavutil  56. 25.100 / 56. 25.100
  libavcodec 58. 43.100 / 58. 43.100
  libavformat58. 25.100 / 58. 25.100
  libavdevice58.  6.101 / 58.  6.101
  libavfilter 7. 46.101 /  7. 46.101
  libswscale  5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc55.  4.100 / 55.  4.100
[h264 @ 01c19ceda580] Stream #0: not enough frames to estimate rate;
consider increasing probesize
Input #0, h264, from 'original.h264':
  Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive),
1344x968, 25 fps, 25 tbr, 1200k tbn, 50.01 tbc

created:

  libavutil  56. 25.100 / 56. 25.100
  libavcodec 58. 43.100 / 58. 43.100
  libavformat58. 25.100 / 58. 25.100
  libavdevice58.  6.101 / 58.  6.101
  libavfilter 7. 46.101 /  7. 46.101
  libswscale  5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc55.  4.100 / 55.  4.100
[h264 @ 0118abc6a680] Stream #0: not enough frames to estimate rate;
consider increasing probesize
Input #0, h264, from
'McLaren-P16-ExtrinsicCalibration-Front_AT102A_1344x968.jpg.mp4.h264no_head':
  Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive),
1344x968 [SAR 1:1 DAR 168:121], 25 fps, 25 tbr, 1200k tbn, 50 tbc


This is the output of the conversion:
ffmpeg version N-92899-g1dcb5b7dca Copyright (c) 2000-2019 the FFmpeg
developers
  built with gcc 8.2.1 (GCC) 20181201
  configuration: --enable-gpl --enable-version3 --enable-sdl2
--enable-fontconfig --enable-gnutls --enable-iconv --enable-libass
--enable-libbluray --enable-libfreetype --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg
--enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr
--enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack
--enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2
--enable-libzimg --enable-lzma --enable-zlib --enable-gmp
--enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc
--enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom
--enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid
--enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2
--enable-avisynth --enable-libopenmpt
  libavutil  56. 25.100 / 56. 25.100
  libavcodec 58. 43.100 / 58. 43.100
  libavformat58. 25.100 / 58. 25.100
  libavdevice58.  6.101 / 58.  6.101
  libavfilter 7. 46.101 /  7. 46.101
  libswscale  5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc55.  4.100 / 55.  4.100
Input #0, image2, from '1344x968.jpg%04d.jpg':
  Duration: 00:00:05.00, start: 0.00, bitrate: N/A
Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc,
bt470bg/unknown/unknown), 1344x968 [SAR 120:120 DAR 168:121], 25 fps, 25
tbr, 25 tbn, 25 tbc
File '1344x968.jpg.mp4' already exists. Overwrite ? [y/N] y
Stream mapping:
  Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
Press [q] to stop, [?] for help
[swscaler @ 029263bb8340] deprecated pixel format used, make sure you
did set range correctly
[libx264 @ 029263673800] using SAR=1/1
[libx264 @ 029263673800] using cpu capabilities: MMX2 SSE2Fast SSSE3
SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 029263673800] profile Constrained Baseline, level 4.0,
4:2:0, 8-bit
[libx264 @ 029263673800] 264 - core 157 r2935 545de2f - H.264/MPEG-4
AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html -
options: cabac=0 ref=1 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1
psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=1 8x8dct=0
cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6
lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=1
keyint_min=1 scenecut=40 intra_refresh=0 rc=crf mbtree=0 crf=20.0
qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to '1344x968.jpg.mp4':
  Metadata:
encoder : Lavf58.25.100
Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p,
1344x968 [SAR 1:1 DAR 168:121], q=-1--1, 2 kb/s, 25 fps, 12800 tbn, 25
tbc
Metadata:
  encoder : Lavc58.43.100 libx264
Side data:
  cpb: bitrate max/min/avg: 0/0/2000 buffer size: 0 vbv_delay: -1
frame=  125 fps= 60 q=-1.0 Lsize=6028kB time=00:00:04.96
bitrate=9955.0kbits/s speed= 2.4x
video:6026kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
muxing overhead: 0.021828%
[libx264 @ 029263673800] frame I:125   Avg QP:15.53  size: 49362
[libx264 @ 029263673800] mb I  I16..4: 59.3%  0.0% 40.7%
[libx264 @ 029263673800] coded y,uvDC,uvAC intra: 40.2% 38.9% 21.1%
[libx264 @ 029263673800] i16 

Re: [FFmpeg-user] ffmpeg cuvid not transcoding properly

[Ted Park]

> Error while opening decoder for input stream #0:0 : Operation not permitted


Is 0.0.0.0 is the actual value you used the command? The operation not 
permitted error could be referring to the tcp socket you’re opening… Though 
trying to connect to 0.0.0.0 leads to inconsistent behavior on different 
platforms, so I’m not sure. If that’s the actual address you used, I would 
change that first.

> ffmpeg -threads 1 -vsync 1 -hwaccel cuvid -c:v mpeg2_cuvid -deint 1
> -drop_second_field 1 -i 'http://0.0.0.0:46007’……


Also, you’re still getting the input via http so I would have thought you’d 
have to specify just about all of the codec parameters, but I guess on your 
first one, ffmpeg was able to figure it out through some kind of heuristic 
methods? Or from the http header indicating mpeg ts stream made it easier? What 
is the server, can you post the reply headers you get?

> [AVHWFramesContext @ 0x3a36600] [IMGUTILS @ 0x7ffc3bcc6230] Picture
> size 0x0 is invalid
> [mpeg2_cuvid @ 0x3098a40] Error initializing a CUDA frame pool
> cuvid hwaccel requested for input stream #0:0, but cannot be initialized.
> [mpeg2_cuvid @ 0x3098a40] ff_get_format failed: -1

It seems you have to specify frame size at the very least.

Also, Dennis mentioned threading issues, which reminded me that I needed to 
mess with the number of cuda surfaces based filters I was using, if you’re 
deinterlacing and encoding using nvenc I would try 8 as a starting point.

I don’t think you should have to specify -threads 1, since the decoder doesn’t 
support any threading, it’s not going to make any, but the cuda api might be 
crippled with that option so I would just leave it out and keep it at auto.

Basically you need to know beforehand what the codec parameters are before, or 
accept there is going to be latency even if you are able to get it to detect 
the format. One last thing, keeping vsync 0 and setting output frame rate is a 
better idea imho.

___
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] encoding H264 from pictures, encoding values manipulation

[Moritz Barsnick]

On Thu, Nov 21, 2019 at 10:54:49 +0100, Jorge Mas wrote:
> i changed the profile to Main
>
> the profile_idc change to 77, i need it to be 66 which it is profile =
> baseline

What are you actually trying to achieve? Do you really need everything
to be identical? Even if you achieve that, the video may still be
different regarding some characteristics, as it's (likely) a different
encoder.

You are going in to quite deep details, so it might be necessary for
you to get an understanding of these values, and what you need them
for.

> This is the output of the conversion:
> Input #0, image2, from '1344x968.jpg%04d.jpg':
>   Duration: 00:00:05.00, start: 0.00, bitrate: N/A
> Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, 
> bt470bg/unknown/unknown), 1344x968 [SAR 120:120 DAR 168:121], 25 fps, 25

Ah, so you're trying to create a similar video from JPEG files?

> [libx264 @ 029263673800] profile Constrained Baseline, level 4.0, 4:2:0, 
> 8-bit

I don't see why libx264 would create a "Constrained Baseline" profile
video if you tell it to use "-profile Main".

> [libx264 @ 029263673800] 264 - core 157 r2935 545de2f - H.264/MPEG-4
> AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html -
> options: cabac=0 ref=1 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1
> psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=1 8x8dct=0
> cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6
> lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
> bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=1
> keyint_min=1 scenecut=40 intra_refresh=0 rc=crf mbtree=0 crf=20.0
> qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00

BTW, these are some of the parameters which may differ from the
original encoder. (Some affect the encoding strategies, some affect the
resulting video.) Do you really understand them all? Do you know which
you want to reproduce?

That said, I don't see how your "original" video has
constraint_set0_flag = 0 while being "Contrained Baseline". As far as
x264 is concerned, this seems like a contradiction.

Cheers,
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] encoding H264 from pictures, encoding values manipulation

[Carl Eugen Hoyos]

Am Do., 21. Nov. 2019 um 10:55 Uhr schrieb Jorge Mas :

> i changed the profile to Main
>
> the profile_idc change to 77, i need it to be 66 which it is
> profile = baseline

There is neither a known encoder nor a known decoder that
supports the "baseline" profile, 77 is "constrained baseline"
which is supported by all encoders and decoders.
(constrained baseline is a strict subset of baseline, so 66
is not a wrong value, just a useless one. You can patch
x264 if you need 66, short googling did not reveal an
option to force this value.)

This is what I tried to explain yesterday.

Please find out what top-posting means and avoid it here,
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 cuvid not transcoding properly

[Dennis Mungai]

On Thu, 21 Nov 2019 at 06:34, Andy  wrote:
>
> It seems like again I hit the wall. While one mpeg2 source works with
> the mpeg2_cuvid option, the other gives me troubles.
>
> ffmpeg -threads 1 -vsync 1 -hwaccel cuvid -c:v mpeg2_cuvid -deint 1
> -drop_second_field 1 -i 'http://0.0.0.0:46007' -c:v h264_nvenc -vb
> 1000k -preset:v medium -c:a aac -ac 2 -ar 48k -ab 96k -map 0:0 -map
> 0:1 -f flv rtmp://0.0.0.0:1940/live/1
> ffmpeg version N-95728-g1354c39 Copyright (c) 2000-2019 the FFmpeg developers
>   built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.12) 20160609
>   configuration: --enable-cuda --enable-cuvid --enable-nvenc
> --enable-nonfree --enable-libnpp
> --extra-cflags=-I/usr/local/cuda/include
> --extra-ldflags=-L/usr/local/cuda/lib64 --enable-libx264
> --enable-libfdk-aac --enable-gpl
>   libavutil  56. 35.101 / 56. 35.101
>   libavcodec 58. 62.100 / 58. 62.100
>   libavformat58. 35.100 / 58. 35.100
>   libavdevice58.  9.100 / 58.  9.100
>   libavfilter 7. 66.100 /  7. 66.100
>   libswscale  5.  6.100 /  5.  6.100
>   libswresample   3.  6.100 /  3.  6.100
>   libpostproc55.  6.100 / 55.  6.100
> [mpegts @ 0x3092a40] Could not find codec parameters for stream 0
> (Video: mpeg2video ([27][0][0][0] / 0x001B), none(tv)): unspecified
> size
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> Input #0, mpegts, from 'http://0.0.0.0:46007':
>   Duration: N/A, start: 67033.565011, bitrate: 192 kb/s
>   Program 107
> Metadata:
>   service_name: NTV
>   service_provider: NTV BD
> Stream #0:0[0x327]: Video: mpeg2video ([27][0][0][0] / 0x001B),
> none(tv), 90k tbr, 90k tbn, 90k tbc
> Stream #0:1[0x2c3]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz,
> stereo, fltp, 192 kb/s
> [AVHWFramesContext @ 0x3a36600] [IMGUTILS @ 0x7ffc3bcc6230] Picture
> size 0x0 is invalid
> [mpeg2_cuvid @ 0x3098a40] Error initializing a CUDA frame pool
> cuvid hwaccel requested for input stream #0:0, but cannot be initialized.
> [mpeg2_cuvid @ 0x3098a40] ff_get_format failed: -1
> Stream mapping:
>   Stream #0:0 -> #0:0 (mpeg2video (mpeg2_cuvid) -> h264 (h264_nvenc))
>   Stream #0:1 -> #0:1 (mp2 (native) -> aac (native))
> Error while opening decoder for input stream #0:0 : Operation not permitted


Show us the output of:

ffprobe -i 'http://0.0.0.0:46007'

Secondly, are you on a Turing (TU10x-) series GPU, the RTX series?
If that's the case, then use -deint 2 in place of -deint 1.
Turing explicitly disabled interlaced encoding *but* this might not be
the case here as we don't see the nvenc encoder quit on you.

Another observation: In your ffmpeg build options, I see
--enable-cuda. If you can, rebuild that package and pass
--enable-cuda-nvcc, that previous option is deprecated. The other
option --enable-cuda-llvm can be used if you don't need scale_npp, but
it requires a working installation of clang.
___
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 cuvid not transcoding properly

[Carl Eugen Hoyos]

Am Do., 21. Nov. 2019 um 10:01 Uhr schrieb Dennis Mungai :
>
> On Thu, 21 Nov 2019 at 06:34, Andy  wrote:
> >
> > It seems like again I hit the wall. While one mpeg2 source works with
> > the mpeg2_cuvid option, the other gives me troubles.
> >
> > ffmpeg -threads 1 -vsync 1 -hwaccel cuvid -c:v mpeg2_cuvid -deint 1
> > -drop_second_field 1 -i 'http://0.0.0.0:46007' -c:v h264_nvenc -vb
> > 1000k -preset:v medium -c:a aac -ac 2 -ar 48k -ab 96k -map 0:0 -map
> > 0:1 -f flv rtmp://0.0.0.0:1940/live/1
> > ffmpeg version N-95728-g1354c39 Copyright (c) 2000-2019 the FFmpeg 
> > developers
> >   built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.12) 20160609
> >   configuration: --enable-cuda --enable-cuvid --enable-nvenc
> > --enable-nonfree --enable-libnpp
> > --extra-cflags=-I/usr/local/cuda/include
> > --extra-ldflags=-L/usr/local/cuda/lib64 --enable-libx264
> > --enable-libfdk-aac --enable-gpl
> >   libavutil  56. 35.101 / 56. 35.101
> >   libavcodec 58. 62.100 / 58. 62.100
> >   libavformat58. 35.100 / 58. 35.100
> >   libavdevice58.  9.100 / 58.  9.100
> >   libavfilter 7. 66.100 /  7. 66.100
> >   libswscale  5.  6.100 /  5.  6.100
> >   libswresample   3.  6.100 /  3.  6.100
> >   libpostproc55.  6.100 / 55.  6.100
> > [mpegts @ 0x3092a40] Could not find codec parameters for stream 0
> > (Video: mpeg2video ([27][0][0][0] / 0x001B), none(tv)): unspecified
> > size
> > Consider increasing the value for the 'analyzeduration' and 'probesize' 
> > options
> > Input #0, mpegts, from 'http://0.0.0.0:46007':
> >   Duration: N/A, start: 67033.565011, bitrate: 192 kb/s
> >   Program 107
> > Metadata:
> >   service_name: NTV
> >   service_provider: NTV BD
> > Stream #0:0[0x327]: Video: mpeg2video ([27][0][0][0] / 0x001B),
> > none(tv), 90k tbr, 90k tbn, 90k tbc
> > Stream #0:1[0x2c3]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz,
> > stereo, fltp, 192 kb/s
> > [AVHWFramesContext @ 0x3a36600] [IMGUTILS @ 0x7ffc3bcc6230] Picture
> > size 0x0 is invalid
> > [mpeg2_cuvid @ 0x3098a40] Error initializing a CUDA frame pool
> > cuvid hwaccel requested for input stream #0:0, but cannot be initialized.
> > [mpeg2_cuvid @ 0x3098a40] ff_get_format failed: -1
> > Stream mapping:
> >   Stream #0:0 -> #0:0 (mpeg2video (mpeg2_cuvid) -> h264 (h264_nvenc))
> >   Stream #0:1 -> #0:1 (mp2 (native) -> aac (native))
> > Error while opening decoder for input stream #0:0 : Operation not permitted
>
>
> Show us the output of:
>
> ffprobe -i 'http://0.0.0.0:46007'

Don't we already see that above?

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 cuvid not transcoding properly

[Carl Eugen Hoyos]

Am Do., 21. Nov. 2019 um 04:34 Uhr schrieb Andy :
>
> It seems like again I hit the wall. While one mpeg2 source works with
> the mpeg2_cuvid option, the other gives me troubles.
>
> ffmpeg -threads 1 -vsync 1 -hwaccel cuvid -c:v mpeg2_cuvid -deint 1
> -drop_second_field 1 -i 'http://0.0.0.0:46007' -c:v h264_nvenc -vb
> 1000k -preset:v medium -c:a aac -ac 2 -ar 48k -ab 96k -map 0:0 -map
> 0:1 -f flv rtmp://0.0.0.0:1940/live/1
> ffmpeg version N-95728-g1354c39 Copyright (c) 2000-2019 the FFmpeg developers
>   built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.12) 20160609
>   configuration: --enable-cuda --enable-cuvid --enable-nvenc
> --enable-nonfree --enable-libnpp
> --extra-cflags=-I/usr/local/cuda/include
> --extra-ldflags=-L/usr/local/cuda/lib64 --enable-libx264
> --enable-libfdk-aac --enable-gpl
>   libavutil  56. 35.101 / 56. 35.101
>   libavcodec 58. 62.100 / 58. 62.100
>   libavformat58. 35.100 / 58. 35.100
>   libavdevice58.  9.100 / 58.  9.100
>   libavfilter 7. 66.100 /  7. 66.100
>   libswscale  5.  6.100 /  5.  6.100
>   libswresample   3.  6.100 /  3.  6.100
>   libpostproc55.  6.100 / 55.  6.100
> [mpegts @ 0x3092a40] Could not find codec parameters for stream 0
> (Video: mpeg2video ([27][0][0][0] / 0x001B), none(tv)): unspecified
> size
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> Input #0, mpegts, from 'http://0.0.0.0:46007':
>   Duration: N/A, start: 67033.565011, bitrate: 192 kb/s
>   Program 107
> Metadata:
>   service_name: NTV
>   service_provider: NTV BD
> Stream #0:0[0x327]: Video: mpeg2video ([27][0][0][0] / 0x001B),
> none(tv), 90k tbr, 90k tbn, 90k tbc

Feel free to record such a sample with wget, curl or tcpdump and provide
it if it allows to reproduce the issue.

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 cuvid not transcoding properly

[Ted Park]

> You cannot specify a frame size for mpeg video…

Really? Do you mean the decoder ignores any frame format/doesn't use the info? 
___
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 cuvid not transcoding properly

[Carl Eugen Hoyos]

Am Do., 21. Nov. 2019 um 17:13 Uhr schrieb Ted Park :
>
> > You cannot specify a frame size for mpeg video…
>
> Really? Do you mean the decoder ignores any frame format/doesn't use the info?

I think "ignore" is the wrong word, it's just not how video decoding works
for compressed codecs.

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] Add soft subtitles to YouTube Mouse Stream?

[Steven Kan]

Thank you for finding that! And, a few minutes later, in he goes:

https://youtu.be/gh7bUtECd0Y?t=29460 

Just before he pokes his nose in, you can see a guard bee at the far right of 
the entrance, not doing her job.

Back on-topic, I also have had an issue with these Reolink cameras, in that 
sometimes they get into a weird state that ffmpeg doesn’t like, and ffmpeg 
starts dumping out:

[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq e680 expected=0b49
[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq 93ab expected=0b49
[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq 93ac expected=0b49
[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq e682 expected=0b49

forever.

Has anyone seen this error, and/or know what it means? Stopping and restarting 
ffmpeg doesn’t fix this problem; I need to reboot the camera.

But I’m trying to grok how ffmpeg could put a camera into a bad state, just by 
connecting via rtsp.



> On Nov 21, 2019, at 1:58 AM, Moritz Barsnick  wrote:
> 
> On Wed, Nov 20, 2019 at 14:30:27 -0600, Steven Kan wrote:
>> Danke für deine Hilfe!
> 
> Gerne!
> 
>> Yes, I have mice in my yard :-(
>> 
>> They can actually invade a weak hive and wreak havoc! Do you remember
>> approximately when you saw it? YT automatically archives the footage
>> twice a day, so I’d like to review it and see the mouse!
> 
> I wasn't aware of that. Basically, about five minutes before I wrote my
> email, so around 14:05h CET. Have you considered downloading the
> archived YouTube stream and doing motion detection on it?
> 
> Actually, I found it:
> https://youtu.be/gh7bUtECd0Y?t=29118
> 

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