hi
Is it possible to get the average luminance of the camera input using GEM?
I am exploring pix_data but as far as I can see it only works with
individual pixels. If I could average or reduce the color information
from the camera to a single color, then I think I could just take the
pix_data
did you try [pix_resize 1 1] ?
cheers
Le 04/02/2020 à 14:17, enrike a écrit :
hi
Is it possible to get the average luminance of the camera input using GEM?
I am exploring pix_data but as far as I can see it only works with individual
pixels. If I could average or reduce the color information
On 2/4/20 2:17 PM, enrike wrote:
> hi
>
> Is it possible to get the average luminance of the camera input using GEM?
>
> I am exploring pix_data but as far as I can see it only works with
> individual pixels. If I could average or reduce the color information
> from the camera to a single color,
sorry I did not see that. I was reading here the descriptions but I guess
it is outdated
https://puredata.info/downloads/gem/documentation/manual/manual/list-of-gem-objects
.
thanks!
On Tue, 4 Feb 2020 at 14:55, IOhannes m zmölnig wrote:
> On 2/4/20 2:17 PM, enrike wrote:
> > hi
> >
> > Is it p
On Sun, Feb 2, 2020 at 1:46 PM ffdd cchh wrote:
>
> Ok, I did Christof's step c) and copied those dummy functions (and basically
> commented out anything but a debug_post() inside "hidio_devices()" and
> "hidio_elements()", and indeed got a binary. But, it's no use.
>
> I try to get some data on
You just have to replace it with #include . I also compiled it
with Msys2.
Christof
On 04.02.2020 23:13, Martin Peach wrote:
On Sun, Feb 2, 2020 at 1:46 PM ffdd cchh wrote:
Ok, I did Christof's step c) and copied those dummy functions (and basically commented out anything
but a debug_post()
As I said before, I could make a binary with Christof's steps, but I dont know
how to debug an external on windows. If you can give me some basic guidelines I
can continue with that.
In the meantime, we got joyosc working on Windows so that's looking good!
Best,
f
fdch.github.io
> On Feb 4
Hi,
I usually run Pd in a debugger like this:
gdb --args pd
> run
Wait for the segfault. The following will print a stack trace, showing
you the function where the segfault occurs:
> bt
(you might need to hit enter to show additional lines of the stacktrace)
From there you can either set
Thanks a lot, Christof!
This is indeed very helpful. I will let you know what I can find!
Cheers,
f
fdch.github.io
> On Feb 4, 2020, at 7:02 PM, Christof Ressi wrote:
>
> Hi,
>
> I usually run Pd in a debugger like this:
>
> gdb --args pd
>
> > run
>
> Wait for the segfault. The follo