Conor Henry

I'm working on a patch that uses jit.xfade to combine two images, and then changes some other attributes like brightness and contrast below before displaying the image in a pwindow. I'm incredibly frustrated because xfade seems to be behaving incorrectly. I bang xfade repeatedly with a qmetro, but when I change the value it doesn't update. The only way to get it to update seems to be to capture a new image with the webcam. But what's even more strange is that the values for the other attributes for brightness, contrast, etc. all *do* update with the qmetro, even though the qmetro is only attached to xfade. So the bangs are all propagating through xfade to the other objects, but xfade doesn't change. It's getting to the point that I'm wondering if it's just my computer or something. I have no idea what I'm doing wrong. Any help is appreciated. Below is my patch. 

button

number

message

flonum

umenu

qmetro

pattrstorage

autopattr

jit.fastblur

jit.rota

jit.brcosa

jit.hue

toggle

jit.window

jit.xfade

jit.matrix

prepend

comment

dropfile

jit.pwindow

gate

jit.grab

I'm working on a patch that uses jit.xfade to combine two images, and then changes some other attributes like brightness and contrast below before displaying the image in a pwindow. I'm incredibly frustrated because xfade seems to be behaving incorrectly. I bang xfade repeatedly with a qmetro, but when I change the value it doesn't update. The only way to get it to update seems to be to capture a new image with the webcam. But what's even more strange is that the values for the other attributes for brightness, contrast, etc. all *do* update with the qmetro, even though the qmetro is only attached to xfade. So the bangs are all propagating through xfade to the other objects, but xfade doesn't change. It's getting to the point that I'm wondering if it's just my computer or something. I have no idea what I'm doing wrong. Any help is appreciated. Below is my patch. 



I'm working on a patch that uses jit.xfade to combine two images, and then changes some other attributes like brightness and contrast below 

xfade-won't-update-even-when-attached-to-qmetro

That gate was confusing things and I don't think you need it, also if you bang the matrix going into the xfade instead of the xfade itself.

Another possible issue is the internal size of [jit.xfade]. When you first input a matrix in the rightmost input, the internal size is 1 1, so the image is pretty much lost. [jit.xfade]'s internal size will be [1280 720] only after such a matrix inputs its left inlet.

To make your patch work, you'll need to either input the right image after the left one has triggered at least once, or to give [jit.xfade] an initial size like [jit.xfade 4 char 1280 720], or a quick trick would be to bang both your left and right image with your [qmetro] (less elegant, but that would work).

Another possible issue is the internal size of [jit.xfade]. When you first input a matrix in the rightmost input, the internal size is 1 1, so the image is pretty much lost. [jit.xfade]'s internal size will be [1280 720] only after such a matrix inputs its left inlet.
To make your patch work, you'll need to either input the right image after the left one has triggered at least once, or to give [jit.xfade] an initial size like [jit.xfade 4 char 1280 720], or a quick trick would be to bang both your left and right image with your [qmetro] (less elegant, but that would work).

Xfade won't update even when attached to qmetro