problem with two consecutive glshader elements with preset in pipeline

[Hamdi Rakkez]

Hi,

Yes it is a bug actually, but I get the same behavior with the *vars*
property.

Is there a chance for this element to be fixed before any other release ?

Best,
Hamdi

On Tue, Oct 27, 2015 at 5:35 AM, Matthew Waters <ystreet00 at gmail.com> wrote:

> There probably was a bug in the preset handling code that relied on static
> variables somewhere.  The glshader element has since been redesigned in
> master and is very unlikely to receive any updates in 1.6.
>
> Cheers
> -Matt
>
>
> On 26/10/15 21:39, Hamdi Rakkez wrote:
>
> Revive thread
>
> On Wed, Oct 21, 2015 at 5:25 PM, Hamdi Rakkez <
> hamdi.rakez.selotec at gmail.com> wrote:
>
>> Hi list,
>>
>> I'm using gstreamer-1.5.90 on ubuntu 14.04LTS.
>>
>> Here is the problem :
>>
>> When using two consecutive *glshader* element in a pipeline and one of
>> them have a *preset* property(uniform variable file path), that preset
>> is not taken into consideration (as if it does not exist, and all the
>> uniform variable into the fragment shader take the value 0.0)
>>
>> pipeLine :
>> gst-launch-1.0 videotestsrc ! glupload ! glshader location=fragment1.frag
>> ! glshader location=fragment2.frag
>> preset=fragment2_uniform_variables.preset ! gldownload ! glimagesink
>>
>> when removing the first *glshader* element from the pipeline, *preset*
>> property works fine.
>>
>> Does anyone knows if this is a bug or I'm missing something here ?
>>
>> PS: Some behavior if I replace *preset* with *vars* and declare uniform
>> variables withing the pipeline.
>>
>> Thanks in advance.
>>
>> Best regards,
>> Hamdi
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20151027/eaba02b2/attachment.html>