Stingy Sphere drives comp to 1.45fps
Posted: Tue Feb 27, 2018 01:15
I was working on a comp last week for an LED sculpture made of 16 bars (120px each) fanning out into a semi-circle, controlled by a PixLite16 MkII. Comp was generative content (Lines, Rings, PolarKaleido, Shaper, etc.) at 300x300 pixels.
Advanced Output had one screen output to Syphon, going into Madmapper for Artnet mapping. This screen had 1 active slice with the entire comp, and 16 inactive (de-selected) slices, each with its own layer (containing a single clip of a static white line) to be triggered in Chaser.
I wanted to use Stingy Sphere for a 3D illusion This worked fine (60fps) during all testing: with Chaser and all those slices, and with Syphon into Madmapper. BUT with the PixLite connected, Stingy Sphere drove the comp to 1.45fps every time.
It appears that an active ArtNet connection was the factor preventing Stingy Sphere from running smoothly, but it baffles me because everything except the PixLite is running on the GPU.
Can anyone find or explain this bottleneck? Should the 16 Chaser slices be on a Virtual Device? Should I finally figure out how to use Resolume's ArtNet output?
Put simply:
Arena + Stingy Sphere = GOOD
Arena + Chaser + Stingy Sphere = GOOD
Arena + Chaser + Stingy Sphere -> Syphon -> Madmapper = GOOD
Arena 6 + Chaser + Stingy Sphere -> Syphon -> Madmapper -> ArtNet output = 1.45fps
Arena 6 (No Chaser) + Stingy Sphere -> Syphon -> Madmapper -> ArtNet output = 1.45fps
Arena 6 + Chaser (no Stingy Sphere) -> Syphon -> Madmapper -> ArtNet output = GOOD
The slices are active here just to make them visible.
Arena 6.0.5: 1 Screen (17 Slices, only 1 active), Syphon output to Madmapper
Chaser
Macbook Pro Retina, Mid-2015
AMD Radeon R9 M370X 2GB
2.8 GHz Intel i7
16GB RAM
Advanced Output had one screen output to Syphon, going into Madmapper for Artnet mapping. This screen had 1 active slice with the entire comp, and 16 inactive (de-selected) slices, each with its own layer (containing a single clip of a static white line) to be triggered in Chaser.
I wanted to use Stingy Sphere for a 3D illusion This worked fine (60fps) during all testing: with Chaser and all those slices, and with Syphon into Madmapper. BUT with the PixLite connected, Stingy Sphere drove the comp to 1.45fps every time.
It appears that an active ArtNet connection was the factor preventing Stingy Sphere from running smoothly, but it baffles me because everything except the PixLite is running on the GPU.
Can anyone find or explain this bottleneck? Should the 16 Chaser slices be on a Virtual Device? Should I finally figure out how to use Resolume's ArtNet output?
Put simply:
Arena + Stingy Sphere = GOOD
Arena + Chaser + Stingy Sphere = GOOD
Arena + Chaser + Stingy Sphere -> Syphon -> Madmapper = GOOD
Arena 6 + Chaser + Stingy Sphere -> Syphon -> Madmapper -> ArtNet output = 1.45fps
Arena 6 (No Chaser) + Stingy Sphere -> Syphon -> Madmapper -> ArtNet output = 1.45fps
Arena 6 + Chaser (no Stingy Sphere) -> Syphon -> Madmapper -> ArtNet output = GOOD
The slices are active here just to make them visible.
Arena 6.0.5: 1 Screen (17 Slices, only 1 active), Syphon output to Madmapper
Chaser
Macbook Pro Retina, Mid-2015
AMD Radeon R9 M370X 2GB
2.8 GHz Intel i7
16GB RAM