Image sequencer of large images has slow framerate

@mitnosirrag wrote:

First time poster, thanks to everyone who contributes.

My machine specs:

• 4ghz i7 with 4 cores (can get a 6 core unit if needed)
• Samsung 850 Pro SSD
• 32gb RAM (can get 64gb if needed)
• (2) nVidia Quadro M5000, 8gb memory each (running Mosaic)
• nVidia Sync Card
• (8) 55" 1080p displays, side by side in portrait mode for a resolution of 8682x1920 (42px are bezel correction)
• Windows 7 Pro (can go Windows 10 if it helps)

The gist of my project is an image sequence that has 720 images that circle around a center point, as if you were walking around it looking at the center point. Two images for every degree. At the next phase, this will be controlled with a rotary encoder, but for now I just need to get it working in a continuous cycle at 60fps.

Where this goes from a very simple task to more complicated is that each image is 8682x1920, compressed JPG. I have determined that each image decompresses to about 50mb, so the total is around 36gb. I plan to have this lazy load files and swap textures in and out of the graphics card as needed, but for now I just need a solid proof of concept at full resolution. Here is my workflow:

Loading in a much smaller set of images, maybe 180 images (3 seconds of footage), which should fit nicely in both RAM and the two Quadro's 16gb combined memory. When I do this, the playback peaks at 60fps for a few seconds, then will throttle down to ~20-24fps. If I toggle the direction of the playback (it goes forward and backward) it will speed back up for a few seconds, then drop again. I'm storing all of the images in a vector <ofImage> and not deleting or modifying anything after they are in there. I've also tried storing them all in a map <int, ofImage> and that didn't change anything, good or bad.

If I can get it working with enough images that should clearly fit inside of memory, I will incorporate setUseTexture and swap in and out as needed (I'm assuming that's how that works), but for now I just need it working at its most basic. I have working versions at smaller file dimensions in both OF and an HTML5/canvas version, so I know the code is at least decent.

I can post code samples if necessary, but they aren't really anything complicated. Honestly, it's the complicated stuff that I don't know. My experience with C++ is very intermediate, a notch above beginner.

Thanks again.

Posts: 3

Participants: 2

Read full topic