openframeworks / openframeworks/openFrameworks

ofTexture on pi4

Open
#6,757 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.4k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
9

Description

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 https://github.com/openframeworks/openFrameworks/issues/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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior with two ofTexture instances refreshed from camera arrays on a Raspberry Pi 4 running Debian Buster and openFrameworks 0.11.2. Compare the results with ofImage and with issue 6596, then identify whether the complete texture replacement is reproducible and document a verified fix or a narrowed cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, raspberry-pi
Domain
computer-graphics, embedded-iot, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.