Am Di., 19. Nov. 2019 um 03:44 Uhr schrieb Philippe Sudre-Rouffaux
:
> I have a problem during an installation using a bash file.
> (mediaspip_install.sh from https://github.com/kent1D/mediaspip_scripts)
>
> At the beegining all is ok but when the file install ffmpeg, there is
> always problem
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
Hello,
I have a Debian 8 server.
I have a problem during an installation using a bash file.
(mediaspip_install.sh from https://github.com/kent1D/mediaspip_scripts)
At the beegining all is ok but when the file install ffmpeg, there is
always problem with x264.
Here is .log file.
Hi,
Is it possible to record camera to an AES-128-CENC encrypted mp4 file and
open it during the recording session?
I have a detailed explanation about my problem here:
https://gist.github.com/docoprusta/c294ebaaa68fdc8502b6caa641a75d7f
Thanks in advance,
Soma Györe
Hello All,
ffprobe does not seem to be able to retrieve all the metadata entries within a
container.
I am using ffmpeg version 4.1 for MS Windows (build 20181017).
My purpose was to give names to the 2 subtitle streams (mov_text) of my movie.
Therefore, I did it like this :
ffmpeg -i
On Mon, Nov 18, 2019 at 1:08 PM Ted Park wrote:
>
> > I am not sure what you mean? I thought I was doing a simple encoding:
> >
> > - One input video only, one output for video.
> > - One audio input plus a finalized video input for the audio output.
> Yes, but you have separate (raw) input
> I am not sure what you mean? I thought I was doing a simple encoding:
>
> - One input video only, one output for video.
> - One audio input plus a finalized video input for the audio output.
Yes, but you have separate (raw) input sources.
I think by alignment you are referring to the
On Mon, Nov 18, 2019 at 12:37 PM Ted Park wrote:
> The target duration randomly being changed to 7 is weird, but why are you
> doing this at all? Can’t you just do a simple encoding to a ts file for the
> video first with the right gop settings then have that be the reference for
> creating the
The target duration randomly being changed to 7 is weird, but why are you doing
this at all? Can’t you just do a simple encoding to a ts file for the video
first with the right gop settings then have that be the reference for creating
the hls playlist? Or even just create the ts file from both
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 Mon, Nov 18, 2019 at 10:54 AM Dennis Mungai wrote:
> On Mon, 18 Nov 2019, 18:44 Dennis Mungai, wrote:
>
> >
> >
> > On Mon, 18 Nov 2019, 18:38 gordon, wrote:
> >
> >> Okay, thank you. I will give that a go.
> >>
> >> -- aside --
> >>
> >> I thought that the "-force_key_frames
On Mon, Nov 18, 2019 at 10:37 AM gordon wrote:
> Okay, thank you. I will give that a go.
>
> -- aside --
>
> I thought that the "-force_key_frames expr:gte(t,n_forced*2)" was placing
> the key frames for segment boundaries and still allowing the encoder to
> place other keyframes where they
On Mon, 18 Nov 2019, 18:38 gordon, wrote:
> Okay, thank you. I will give that a go.
>
> -- aside --
>
> I thought that the "-force_key_frames expr:gte(t,n_forced*2)" was placing
> the key frames for segment boundaries and still allowing the encoder to
> place other keyframes where they wanted?
Okay, thank you. I will give that a go.
-- aside --
I thought that the "-force_key_frames expr:gte(t,n_forced*2)" was placing
the key frames for segment boundaries and still allowing the encoder to
place other keyframes where they wanted? I am trying to use h264, h265,
and vp9 so I figured the
On Mon, 18 Nov 2019 at 17:31, gordon wrote:
> Why are the segments for my stream not aligned? The first command outputs
> video segment. The second command outputs an audio segment with the
> previous video output copied in.
>
> Ffmpeg commands are pasted below with the m3u8 outputs. The same
Thanks Carl Eugen, that worked. I will have a look at the pix_fmt option.
I now have to find how to pipe correctly to gstreamer, as it does not
like what I'm feeding him with.
WARNING: erroneous pipeline: could not link fdsrc0 to mpph264enc0,
mpph264enc0 can't handle caps video/x-raw,
Why are the segments for my stream not aligned? The first command outputs
video segment. The second command outputs an audio segment with the
previous video output copied in.
Ffmpeg commands are pasted below with the m3u8 outputs. The same results
were observed on ffmpeg 4.2.1 and snapshot
Am Mo., 18. Nov. 2019 um 14:41 Uhr schrieb James E. Baird :
>
> >This issue was fixed over the weekend.
> I am assuming I just need to recompile then?
No, you have to update to current FFmpeg git head.
> CONFIDENTIALITY NOTICE: This e-mail including attachments is covered by the
> Electronic
>This issue was fixed over the weekend.
>
>Carl Eugen
I am assuming I just need to recompile then?
Thanks Carl
CONFIDENTIALITY NOTICE: This e-mail including attachments is covered by the
Electronic Communications Privacy Act, 18 U.S.C. §§2510-2521, is confidential
and may contain
> Am 15.11.2019 um 18:29 schrieb Verachten Bruno :
>
> So far, I have tried ffmpeg -f v4l2 -pix_fmt nv12 -s 1920x1080 -r 30
> -i /dev/video0 -c:v rawvideo -f yuv - >/dev/null
The name of the rawvideo format is not “yuv” (as the console output told you)
but “rawvideo”.
You may also want to
22 matches
Mail list logo
