On Saturday, 19 August 2017 at 02:50:44 UTC, Johnson Jones wrote:
Trying to get it to work.
You could just try to use/call the ffmeg executable as wrapper.
For sure, not the best, but proabably the easiest solution. Afaik
it also supports pipes.
program with the
debugger attached so I have to run it from the command line. It
was working before, but when I started messing with the ffmpeg
stuff it broke. So at this point the only way I can use ffmpeg is
x64 and running stuff from the command line... This is not the
way I want to go.
On Monday, 21 March 2016 at 17:26:09 UTC, Karabuta wrote:
Will this work
Yes.
and is it the right approach used by video convertor front-ends?
Well, yes, provisionally. When you invoke "ffmpeg" via
spawnProcess, that isolates ffmpeg as its own process, obviously.
From
On Monday, 21 March 2016 at 17:26:09 UTC, Karabuta wrote:
I am new to this kind of multimedia stuff and all this is
currently theoretical. Will this work and is it the right
approach used by video convertor front-ends?
Eh, it is how I did it before, it works and is pretty easy to do.
Hi all,
I'm trying to convert an array of video filenames to another
format using spawnProcess() from std.process. I want to convert
all files in sequence with the command "ffmpeg -i filename.mp4 -o
outputfile.webm" where process will be run one process after the
other.
On Tuesday, 7 July 2015 at 03:05:11 UTC, ketmar wrote:
How stable has the FFMPEG API since beginning 2015?
don't know, but various players stop bundling ffmpeg long time
ago. i assume that API is stable enough to stop worrying about
it.
Ok, thanks.
Have anybody used the FFMPEG bindings at
https://bitbucket.org/sumitraja/ffmpeg-d
?
Specifically do I have to check for a specific version of the
libraries to stay in sync with the version bindings?
How stable has the FFMPEG API since beginning 2015?
What's the policy on future API
On Mon, 06 Jul 2015 16:42:08 +, Per Nordlöw wrote:
How stable has the FFMPEG API since beginning 2015?
don't know, but various players stop bundling ffmpeg long time ago. i
assume that API is stable enough to stop worrying about it.
warning. information deduced, but not checked
p.s. stop bundling means stop bundling their own private versions in
source tree, and started to use system version here.
signature.asc
Description: PGP signature
Am Mon, 07 Jan 2013 03:31:51 +0100
schrieb MrOrdinaire mrordina...@gmail.com:
I agree with you.
One quick question, why do you need a pair of parentheses in
these declarations, ref (ubyte*)[4] and (ubyte*)[4]? The compiler
doesn't complain if I remove it.
I wasn't sure if it's
Am Sun, 06 Jan 2013 12:51:33 +0100
schrieb bearophile bearophileh...@lycos.com:
MrOrdinaire:
I cannot find cint_t nor cint in the d standard modules
(mine are at /usr/include/d/).
I don't remember the correct name.
Are you sure about c_int? I never heard of that before, I only know
Am Sun, 06 Jan 2013 10:48:25 +0100
schrieb MrOrdinaire mrordina...@gmail.com:
Hi,
I am working on D bindings for FFmpeg. I am trying to port the
official examples of FFmpeg to D so that the bindings can be
tested.
My question is how this function declaration is written in D.
int
On Sun, Jan 06, 2013 at 10:48:25AM +0100, MrOrdinaire wrote:
Hi,
I am working on D bindings for FFmpeg. I am trying to port the
official examples of FFmpeg to D so that the bindings can be tested.
My question is how this function declaration is written in D.
int av_image_alloc(uint8_t
On Sunday, 6 January 2013 at 12:46:05 UTC, Johannes Pfau wrote:
Am Sun, 06 Jan 2013 10:48:25 +0100
schrieb MrOrdinaire mrordina...@gmail.com:
Hi,
I am working on D bindings for FFmpeg. I am trying to port the
official examples of FFmpeg to D so that the bindings can be
tested.
My question
Johannes Pfau:
also says C int is the same as D int.
How is this possible?
Bye,
bearophile
On 01/06/2013 01:48 AM, MrOrdinaire wrote:
My question is how this function declaration is written in D.
int av_image_alloc(uint8_t *pointers[4], int linesizes[4],
int w, int h, enum AVPixelFormat pix_fmt, int align);
1) No array is passed to a function as-is in C. Even though there seem
to
(and ffmpeg) documentation suggest that the av_image_alloc
function will always write 4 ubyte* pointers to the pointers parameter.
So you can't use an array smaller than 4 pointers. You can use more, as
it doesn't matter for the ABI, but av_image_alloc will only use 4
pointers.
So I'd argue that ((ubyte
are pointers thing, that might be true. But the
signature (and ffmpeg) documentation suggest that the
av_image_alloc
function will always write 4 ubyte* pointers to the pointers
parameter.
So you can't use an array smaller than 4 pointers. You can use
more, as
it doesn't matter for the ABI
Hi!
I'm trying to get ffmpeg to work with D; I've got some stuff running, but
... well.
av_open_input_file gives me -2 as an error and I can't figure out what
this means (the #defines for the error codes are impossible to understand,
much less translate to D). Anybody ever done
19 matches
Mail list logo
