openframeworks / openframeworks/openFrameworks
imageSequenceExample should use a vector of ofPixels not ofImages
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
imageSequenceExample
Beginners trying to build off of this example will run into problems because each frame will have its own texture reference and will rapidly eat gfx memory.
See this thread for an example of someone trying to extend it and getting stuck.
The imageSequenceExample should use a vector of ofPixels objects and an ofTexture to display the pixels when they are needed.
ofImage should only be used for loading in this case. actually ofLoadImage() can load directly into an ofPixels object so ofImage really isn't needed at all.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with examples/graphics/imageSequenceExample/src/testApp.cpp and inspect how frames are loaded and displayed. Run the imageSequenceExample to confirm its current behavior, then verify that frames use ofPixels with an ofTexture for display rather than retaining per-frame texture references. Done means the example still displays the sequence without rapidly consuming graphics memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100