Hi,
I have two questions about the dshow input device.
Question 1:
On the wiki page https://trac.ffmpeg.org/wiki/DirectShow can be found
this example:
ffmpeg -f dshow -video_size 1280x720 -framerate 15 -vcodec mjpeg -i
video="Integrated Camera" out.avi
Is -vcodec in this case an
Thank's a lot Moritz for your kindly help.
It works !!!
I am an ffmpeg user since november 2018 and I didn't pay attention to this
warning message that was in green color. It's the first time I use vidstab*
filters.
I will continue doing tests because the video I received from a friend is a
On Fri, Aug 07, 2020 at 22:47:10 +0300, scrutinizer wrote:
> Yes, I was talking about macOS 10.7, and even the source code needs
> to be compatible.
ffmpeg's source code is extremely compatible, honestly. They go to long
efforts not to depend on modern compiler or system features.
> Every link I
Hello All,
I don't understand how ffmpeg/ffprobe manage some metadata of audio streams.
Let's take a simple example :
ffmpeg -i INPUT.mp4 -c copy -metadata:s:a:0 "title=5.1" OUTPUT.mp4
The result is :
1- ffprobe is not able to retrieve the audio title of the resulting file,
whatever are the
On Sat, Aug 08, 2020 at 11:23:28 +0200, Michael Koch wrote:
> ffmpeg -f dshow -video_size 1280x720 -framerate 15 -vcodec mjpeg -i
> video="Integrated Camera" out.avi
>
> Is -vcodec in this case an undocumented option of the dshow input
> device? I ask because it's written before -i.
> Or is it an
have you read first this page : https://ffmpeg.org/legal.html
Maybe you will find yous answers
Le mer. 5 août 2020 à 22:26, Don Fotheringham a
écrit :
> Hello,
>
> We have developed software that requires the distribution of FFmpeg
> (included in the download). Our intention is to sell the
On 8/08/2020 8:47 pm, PPRJ01 wrote:
> I am an ffmpeg user since november 2018 and I didn't pay attention to this
> warning message that was in green color. It's the first time I use vidstab*
> filters.
>
> I will continue doing tests because the video I received from a friend is a
> very very
On 07/08/2020 13:25, Moritz Barsnick wrote:
On Thu, Aug 06, 2020 at 15:00:55 +0200, Alfred E. Heggestad wrote:
I am wondering if DASH muxer supports variable framerate.
[...]
What I have seen is that DASH and HLS behaves differently
regarding variable framerate input.
muxer:
Hi,
> Is -vcodec in this case an undocumented option of the dshow input device? I
> ask because it's written before -i.
> Or is it an option for the output, and could (or should?) be written before
> the output file?
I think it's not documented because it's deprecated, ultimately it's
Is there a way to convert WavPack format to PCM using ffmpeg?
Kirk Calabrese, MA,CMT, Network+ Certified Professional
IT Consultant
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On 08/08/2020 13:21, PPRJ01 wrote:
> Hello All,
>
> I don't understand how ffmpeg/ffprobe manage some metadata of audio streams.
>
> Let's take a simple example :
>
> ffmpeg -i INPUT.mp4 -c copy -metadata:s:a:0 "title=5.1" OUTPUT.mp4
>
> The result is :
> 1- ffprobe is not able to retrieve the
Thank you Peter, but (in my understanding) the following syntax is right (at
least under Windows) :
ffmpeg -i INPUT.mp4 -c copy -metadata:s:a:0 "title=5.1" OUTPUT.mp4
For 3 reasons :
1- the ffmpeg stderr output displays "title : 5.1", with no warning, because it
parsed it correctly and wrote
Hi,
> Is there a way to convert WavPack format to PCM using ffmpeg?
If you just re-save as wav, I think the default is pcm 16bit.
i.e.
ffmpeg -i input.wav output.wav
Regards,
Ted Park
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Hi,
> We have developed software that requires the distribution of FFmpeg
> (included in the download). Our intention is to sell the software.
> Who do I contact to inquire further about how to proceed regarding
> permission, royalties, fees etc.?
Run ffmpeg -L to see which license is
On 08/08/2020 17:35, PPRJ01 wrote:
> Thank you Peter, but (in my understanding) the following syntax is right (at
> least under Windows) :
>
> ffmpeg -i INPUT.mp4 -c copy -metadata:s:a:0 "title=5.1" OUTPUT.mp4
>
> For 3 reasons :
> 1- the ffmpeg stderr output displays "title : 5.1", with no
Am 08.08.2020 um 13:41 schrieb Moritz Barsnick:
On Sat, Aug 08, 2020 at 11:23:28 +0200, Michael Koch wrote:
ffmpeg -f dshow -video_size 1280x720 -framerate 15 -vcodec mjpeg -i
video="Integrated Camera" out.avi
Is -vcodec in this case an undocumented option of the dshow input
device? I ask
16 matches
Mail list logo