Less CPU Load

digitalgigalow's picture

This what i was looking to do. I have a Cube that has a slideshow hooked to up on all 6 sides. I would like to make this into a macro/patch that has a on/off (Enable) plug just for the slideshow.

the reasoning for this setup is that i could turn off the slideshows that i am not using and have more object running allowing for less load on the CPU.

Any help would be greatly appreciated.

The Digital Gigalow

PreviewAttachmentSize
CUBE.qtz5.33 KB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

cybero's picture
Re: Less CPU Load

LIke this?

Or did you mean creating a virtual macro?

Instead of using the simple keyboard trigger in this redraft of your example, you could have a set of demultiplexers to Boolean switch your slide and other macros on and off, different keys or notes or values or whatever.

:-)

cybero

PreviewAttachmentSize
CUBE_SLIDES_KEYBOARD_TRIGGERED.qtz6.98 KB

digitalgigalow's picture
Re: Less CPU Load

not exactly, but i can use this. it will work. maybe a little more info. take just the slideshow make into a patch like you uploaded that can be linked to a cube on all side.

i do not know how the multiplexer works. say i have 4 images hooked to it, when i switch between images, are the 3 images not being viewed still running or are they turned off. i guess what i am asking does it act like on off switch.

i want to be able to hook up multiple slideshows to one cube via multiplexer with the option to turn off slideshows that are not being used.

gtoledo3's picture
Re: Less CPU Load

When you have multiple sources hooked to a multiplexer, and the output of the multiplexer is attached to something that renders somewhere down the line, when you run the composition, only the chain that is dictated by the current index value of the multiplexer evaluates.

When you flip off of that value though, there is info about the state of input ports that have been altered that is stored. This is reflected by the input ports themselves, the fact that tooltip info is stored, and that resources that have been loaded stay available without having to "reload"(for the most part...there seem to be some exceptions). It's not "running" but some info about it's state is now being stored.

digitalgigalow's picture
Re: Less CPU Load

GOTCHA!!! question, to control this i need to make input splitter, and set to numbers to make fader to switch, Right?

gtoledo3's picture
Re: Less CPU Load

Yeah, you can make it a "number splitter", or go into settings and make an "index splitter". Either way, what you need to do to make it a slider in the interface is to give it a maximum range if it's an index (err, sorta oversimplifying - it has to be less than the default max), or max and min if it's a number splitter.

The actual input port of a multiplexer that changes input source is an index though. It's probably better to keep it that way, but it's not horrible if it's a number splitter - it's just that the floating point values won't "do anything" and stuff will round (I'm pretty sure), which might be counterintuitive.

digitalgigalow's picture
Re: Less CPU Load

any way to keep cube and turn off just the slide show?

cybero's picture
Re: Less CPU Load

currently you are connecting your downloaded image to your cube faces directly and instead you could put a Billboard or Sprite in an RII , input the image to that RII Billboard or Sprite, with a clear patch at root, then you can switch that RII on and off as you so wish. Cube still runs. Cube is outside of RII.

digitalgigalow's picture
Re: Less CPU Load

which way is best, billboard or sprite. do i have to create billboard for each side? got the idea down but still a little lost

gtoledo3's picture
Re: Less CPU Load

Have one input on the multiplexer be not connected to anything (index 0 is a good idea). Anytime you want to stop slideshows from evaluating, flip the multiplexer to index 0. If you want it to default to a color, you could use a constant color patch and a crop connected to your non-slideshow multiplexer input.

digitalgigalow's picture
Re: Less CPU Load

stupid me. that makes since. sometimes the simplest things are the hardest top find.