Buffering input commands can't keep up

[ChampAction]

We noticed that when we rapidfire diffent stills on a single deck that resolume can't keep up if the frequency is less than 250ms. When triggering through OSC we send a series of triggers (like a drumriff). But when we stop sending them Resolume keeps finishing all the commands still in buffer. And this can last several seconds.
Same with MIDI, but a tad less.
With an OSC monitor all seems fiune, so it must be that Resolume somehjow internally buffers all incoming commands?
Is there a way to decrease the size?
So it processes one at a time?
MTA, East1

[Zoltán]

Which resolume version is this?
How big is your deck?
How do you send the OSC launches?

[ChampAction]

1) Version: 5.1.14 (the latest)
2) 3 layers of 30 stills each (1000x1000px, uncompressed PNG) comp = 1024x768 (nothing too big...)
Just a bit of layer scaling. The output shows approx. 30fps.
3) OSC: We send "/layerX/clipX/connect 1" messages. If we send these fatser then 5 psec it starts to backup...
MIDI: Same effect, but a bit less.
MTA,

[Zoltán]

3 layers @30 fps doesn't sound like a powerful machine.
What are the specs of your machine?

[ChampAction]

Specs: PC I7 16Gbram; Win 10pro
GTX 1080; 16graph mem;

[Zoltán]

Do you run your main display from the 1080?
If you enable show display info in Output menu and enable output to your secondary display you should see the Renderer line which should say GTX 1080.

[ChampAction]

Thats right.

I disabled the internal graphics. Work screen and 1 beamer are both on GTX.
I noticed also that on a previous production it showed like 60fps.
This seems somewhat slow?
Grts & thnx

[Zoltán]

I assume you run your content form an SSD.
What you could try to see if it improves performance is to convert those images to a few frames DXV video clips, and set them to paused in the composition.

[ChampAction]

Ok. Stay tuned...