-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/2011 06:58 PM, Mathieu Bouchard wrote:
> Do you really think that it's a good idea to use a loader in this manner ?
yes.
the idea is to make 3rd party plugins integrate seamlessly into Gem.
>
> What is the possibility of nameclashes here ?
Many video capture devices have multiple physical inputs and some
manufacturers use and input to set things like PAL/NTSC or colorspace or
even resolution. The only way to really figure it out is with the 'dialog'
window. It is kind of a pain to configure certain devices and some of the
pix_video
On Mon, 14 Feb 2011, IOhannes m zmoelnig wrote:
ah, i think i start to understand. what you describe is definitely a
bug, as in this case [pix_blabla] should fail to instantiate. i have
rewritten the entire FreeFrame object a week or so ago, and this might
have slipped in.
Do you really thin
On Mon, 14 Feb 2011, chris clepper wrote:
The messages are different on OSX because devices can and do have
multiple inputs. Selecting a 'device' only is not enough information to
tell the driver of something like a Blackmagic Intensity card so you
need to add an 'input' message as well.
ah
The messages are different on OSX because devices can and do have multiple
inputs. Selecting a 'device' only is not enough information to tell the
driver of something like a Blackmagic Intensity card so you need to add an
'input' message as well.
On Mon, Feb 14, 2011 at 9:47 AM, Mathieu Bouchard
-- Forwarded message --
Date: Mon, 14 Feb 2011 08:43:11 -0500 (EST)
From: Mathieu Bouchard
To: IOhannes m zmoelnig
Subject: [pix_video] osx
Did you know that in gem 92, the "device" method of [pix_video] seems to have
no effect ? I had to use two [pix_video] : one to force ope
OK, thanx. It is working fine now.
++
Jack
Le lundi 14 février 2011 à 13:36 +0100, IOhannes m zmoelnig a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2011-02-14 13:17, cyrille henry wrote:
> >
> >
> > Le 14/02/2011 13:13, IOhannes m zmoelnig a écrit :
> >
> >> ah, i thin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 13:17, cyrille henry wrote:
>
>
> Le 14/02/2011 13:13, IOhannes m zmoelnig a écrit :
>
>> ah, i think i start to understand.
>> what you describe is definitely a bug, as in this case [pix_blabla]
>> should fail to instantiate.
> ok, go
Le 14/02/2011 12:53, cyrille henry a écrit :
right now, i think that only pix_ objects should be affected by the
slow-down; is this correct?
no.
using patch in help folder/02.advanced/22.double-iterative.pd
changing "20" to "100" in both message in order to render lot's more cube.
using Gem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 12:44, cyrille henry wrote:
>> if there is no freeframe plugin, and no abstraction, then what is the
>> pix_blabla object?
>> something that don't do anything?
>> except breaking connection of your patch, since this object have only 1
>>
Le 14/02/2011 12:32, IOhannes m zmoelnig a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 12:06, cyrille henry wrote:
hello
Le 14/02/2011 09:30, IOhannes m zmoelnig a écrit :
some of my patch are more than 2 times slower...
darn.
does that mean "this is a huge prob
Le 14/02/2011 12:36, IOhannes m zmoelnig a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 12:06, cyrille henry wrote:
is it normal that every pix_blablabla object get instancied as a
pix_freeframe object?
yes this is normal.
FreeFrame (and frei0r) also register loader
It is strange to see the object [pix_blabla] created and get in the
console :
error: GemException: couldn't find 'blabla'.''
And a 'help' on this object and i get :
sorry, couldn't find help patch for "pix_freeframe.pd"
++
Jack
Le lundi 14 février 2011 à 12:36 +0100, IOhannes m zmoelnig a écri
On 02/14/2011 12:26 PM, IOhannes m zmoelnig wrote:
if it fail, there is an error in pd log. I think it's ok.
that's why it is not high on my todo list :-)
generally i think it's nicer if you get feedback in the patch as well,
so you can programmatically react on it...
Yes, it is very imp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 12:06, cyrille henry wrote:
>
>
> is it normal that every pix_blablabla object get instancied as a
> pix_freeframe object?
yes this is normal.
FreeFrame (and frei0r) also register loaders, so you can instantiate
these effects as [pix_]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 12:06, cyrille henry wrote:
>
> hello
>
> Le 14/02/2011 09:30, IOhannes m zmoelnig a écrit :
>
>>> some of my patch are more than 2 times slower...
>>
>> darn.
> does that mean "this is a huge problem, i put it on top of my priority".
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-14 12:12, cyrille henry wrote:
>
> caveat: currently only valid shaders are sent; if linking fails, you
> don't know (should be (if needed): 0)
>> if it fail, there is an error in pd log. I think it's ok.
>
that's why it is not high on my
Yep, good new !
++
Jack
Le lundi 14 février 2011 à 12:12 +0100, cyrille henry a écrit :
>
> Le 14/02/2011 10:23, IOhannes m zmoelnig a écrit :
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > i thought it might be a good idea to inform you:
> >
> > glsl_ objects now stopped emittin
Le 14/02/2011 10:23, IOhannes m zmoelnig a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i thought it might be a good idea to inform you:
glsl_ objects now stopped emitting the shader-IDs for each and every frame.
nice
instead, the shaderID is emitted only once, when the shaders are
hello
Le 14/02/2011 09:30, IOhannes m zmoelnig a écrit :
some of my patch are more than 2 times slower...
darn.
does that mean "this is a huge problem, i put it on top of my priority".
or "oups, we're doomed"
?
i also noticed some crash, but did not have something that i can reproduce.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i thought it might be a good idea to inform you:
glsl_ objects now stopped emitting the shader-IDs for each and every frame.
instead, the shaderID is emitted only once, when the shaders are loaded.
thus you won't need the [change] object anymore, to p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i thought it might be a good idea to inform you:
Gem now comes with a simple frei0r wrapper, that allows you to use
frei0r source and effect plugins (though not mixer plugins, atm), just
like FreeFrame effects.
syntax:
[pix_frei0r ]
alternatively:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-02-11 19:31, cyrille henry wrote:
> hello,
>
> i update Gem on my main laptop.
> i notice a very important performance drop.
> rendering multiples primitives (using repeat by example) uses lot's more
> CPU than it use to.
> some of my patch ar
23 matches
Mail list logo
