You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pi4 debian buster with of 0.11.2 im getting a extrange behaviour, i have a app that grabs an array from a camera and i have two cameras so have two textures that refresh on display.
Sometimes the textures mixes, i mean texture 1 get data from texture 2 or reverse, is not a tearing is the complete replacement of the texture.
Sorry if i can not explain it better, i can test anything as im currently working with that
Note that is similar to #6596 where i also commented but im posting here because i think the problem is not from GST but from the texture itself
If helps is very easy to reproduce with a pair of textures that refresh on display.
Also if i use a ofImage seems to happen with less frecuecy but still happens, and once it starts it will not stop.
Is like the identification for each texture gets mixed....
Any clue on what i need to look for?
Thanks
The text was updated successfully, but these errors were encountered:
Hello
In pi4 debian buster with of 0.11.2 im getting a extrange behaviour, i have a app that grabs an array from a camera and i have two cameras so have two textures that refresh on display.
Sometimes the textures mixes, i mean texture 1 get data from texture 2 or reverse, is not a tearing is the complete replacement of the texture.
Sorry if i can not explain it better, i can test anything as im currently working with that
Note that is similar to #6596 where i also commented but im posting here because i think the problem is not from GST but from the texture itself
If helps is very easy to reproduce with a pair of textures that refresh on display.
Also if i use a ofImage seems to happen with less frecuecy but still happens, and once it starts it will not stop.
Is like the identification for each texture gets mixed....
Any clue on what i need to look for?
Thanks
The text was updated successfully, but these errors were encountered: