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
> 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
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.
>
> 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
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
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
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
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
Thanks
Le mar. 19 nov. 2019 à 04:07, Andy a écrit :
> On Mon, Nov 18, 2019 at 12:35 PM Ted Park wrote:
> >
> > I just noticed this but it some examples it seems you are specifying h264
> decoder for an input that (apparently) is mpeg? I’m not sure which is
> which, but I think cuvid and nvdec
This finally fixed it:
-hwaccel cuvid -c:v mpeg2_cuvid
Indeed, you need to specify the input type before transcoding!
Thank you
On Mon, Nov 18, 2019 at 12:35 PM Ted Park wrote:
>
> I just noticed this but it some examples it seems you are specifying h264
> decoder for an input that
Unfortunately lowering threads did not help and resulted in the same error.
I noticed that all inputs that im having issues with are mpegts...
On Sun, Nov 17, 2019 at 12:33 AM Dennis Mungai wrote:
> Hey there,
>
> Lower your decoder threads and retest:
>
> ffmpeg -threads 1 -vsync 1 -hwaccel
On Mon, Nov 18, 2019 at 12:35 PM Ted Park wrote:
>
> I just noticed this but it some examples it seems you are specifying h264
decoder for an input that (apparently) is mpeg? I’m not sure which is
which, but I think cuvid and nvdec differ in the way they map or copy to
graphics memory thought
I just noticed this but it some examples it seems you are specifying h264
decoder for an input that (apparently) is mpeg? I’m not sure which is which,
but I think cuvid and nvdec differ in the way they map or copy to graphics
memory thought maybe that might be the difference between the logs
On Sun, Nov 17, 2019 at 12:33 AM Dennis Mungai wrote:
>
> Hey there,
>
> Lower your decoder threads and retest:
>
> ffmpeg -threads 1 -vsync 1 -hwaccel cuvid -c:v h264_cuvid -deint 1
> -drop_second_field 1 -i 'http://0.0.0.0:4603' -c:v h264_nvenc -vb
> 1000k -preset:v medium -c:a aac -ac 2 -ar
Hey there,
Lower your decoder threads and retest:
ffmpeg -threads 1 -vsync 1 -hwaccel cuvid -c:v h264_cuvid -deint 1
-drop_second_field 1 -i 'http://0.0.0.0:4603' -c:v h264_nvenc -vb
1000k -preset:v medium -c:a aac -ac 2 -ar 48k -ab 96k test.mp4
Now with the yadif_cuda filter:
ffmpeg -threads
How is the stream being served over http? Does it make any difference if you
save a file wget for example first?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or
No luck with -vf yadif_cuda=0:-1:0
___
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".
Try using yadif_cuda to deinterlace instead
___
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".
18 matches
Mail list logo
