I have a layer with a few quartz patches with an iterator an another layer on top of it with some effects clips. Both layers have audio on their clips too. Somehow, when I trigger a specific clip from the effects layer, this instantly sets the value for the iterator (which incidentally is not a published parameter) in the quartz patches to 1. Triggering any other clip from the same layer resets the iterator's value to what it was originally.
I've tested to see if the triggering clip was associated with its position on the layer where it sits but it's not. The behaviour follows the clip wherever you locate it, even on different layers.
By the way, this whole thing started happening suddenly, everything was working as expected and out of the blue this started happening.
In the past I've experienced similar problems with the iterator but not with such "control". Basically I've had iterators switching themselves to a value of 1 but randomly and once there, the only way to reset them to their original value was to restart Resolume.
I'm extremely puzzled, to say the least, as to what might be the cause of this behaviour as I can't think of anything that might be sending the commands to quartz.
more quartz weirdness
Re: more quartz weirdness
After further testing it appears that it's the fact the clip has audio that it's causing this!
I've reconstructed the clip and it appears that a combination of audio with the "fragment" video effect causes quartz's patches iterator values to be set to 1.
I'm going to carry on investigating but I'm finding this truly bizarre
I've reconstructed the clip and it appears that a combination of audio with the "fragment" video effect causes quartz's patches iterator values to be set to 1.
I'm going to carry on investigating but I'm finding this truly bizarre
Re: more quartz weirdness
and suddenly as I'm testing it's stopped happening...
ahhh computers!
ahhh computers!
Re: more quartz weirdness
Oh mannnnnNN! Ok, it's happening again but now when triggering a different clip.
Re: more quartz weirdness
As you've experienced, anything can happen in the land of computers. Especially when you start tinkering with low level tools like QC and mixing and matching them with other OpenGL calls, crazy things can happen.
It would be great if you could narrow things down to a repeatable set of steps that result in the weird behaviour, or at least like 2 times out of 10.
Otherwise your guess is as good as mine as to why it's happening. There's just too many variables involved to say anything meaningful, simply by reading about it on a forum.
It would be great if you could narrow things down to a repeatable set of steps that result in the weird behaviour, or at least like 2 times out of 10.
Otherwise your guess is as good as mine as to why it's happening. There's just too many variables involved to say anything meaningful, simply by reading about it on a forum.