Resolume Forum

I'm getting very random behaviours with some fairly basic quartz patches.
Basically I have quartz patch with a grid made out of cubes using the iterator, several parameters are published to be controlled from resolume. Initially everything works as expected but after a little while random things happen.

• the cube grid suddenly appears as a single row (originally the number of x and y rows was published to resolume but after this issue I edited the quartz patch to have fixed numbers to no avail)
• I have cube rotation controlled from resolume synched to BPM but after a while the rotation of the cubes stops although the relevant slider within the parameters carries on moving
• sometimes the whole thing disappears and only quitting resolume and reopening brings it back.

Much head scratching going on, any help appreciated.

I have similar problems, mostly when the "iterator"-module is in play in the QuartzComposer-patch. I mostly got "init-bugs", like no iterator-distribution parameters are available, or they are wrong, or all iteration-objects just init and follow on the very first iteration-object (resulting in visually just one instance).

I haven't found a way to work around that problem yet (I experienced that in CoGe as well btw...). Currently I'm looking at "replicate in space", that essentially is really not that flexible as the iterator - but allows me to play with more instances of objects at once.

When I want to add a .qtz file to my set arena 4.1.7 freezes. But i can shut down it wit cmd + q and enter. Tested it with the default arena setup. when i chose the "quartz Composer Deck"- nothing. need to restart Arena... My mistake or a bug?

Myself I generally use a syphon output patch and then bring that back into Resolume. I find that I get a better fps and I'm not concerned in QC crashes as it separate and can't crash Resolume. This also lets you use kineme network patches this way.

Kineme is very nice! but it would be awesome to control some parameter on the resolume panel. (thats the reason, why i moved from modul8 to resolume/vdmx )

Nodepond wrote:I have similar problems, mostly when the "iterator"-module is in play in the QuartzComposer-patch. I mostly got "init-bugs", like no iterator-distribution parameters are available, or they are wrong, or all iteration-objects just init and follow on the very first iteration-object (resulting in visually just one instance).

I haven't found a way to work around that problem yet (I experienced that in CoGe as well btw...). Currently I'm looking at "replicate in space", that essentially is really not that flexible as the iterator - but allows me to play with more instances of objects at once.

Very interesting. Drop me out the problematic composition so I could take a look into. If the problem persists in both Resolume and CoGe there is a good chance it is a QC bug, but cannot say anything helpful without looking into that composition.

Guys, if you publish out number types inputs from QC, make sure you are defined the min and max values - use input splitters to do that