[ANSWERED] Why doesn't the Matrix Value Receive actor Receive my values?

Bennnid

it seems the matrix actors are not appropriate to send soundplayer "play" for example as the datas are being interpolated, so broadcast seems the best option to remote control players in an activated scene?

Bennnid

@dusx yes I use it for another show but this team has a nano control 1, I didn't have time to adapt so I took midi learn from the DL page... must do it back again but as the paste over function is not working for me I'm stuck...

Bennnid

I'm still not understanding why datas are not pushed when entering the scene... I need help... MATRIX SQUARED.izz

mark

@bennnid said:

'm still not understanding why datas are not pushed when entering the scene...

I can't look at your patch right at this moment, but this patch proves that the values are being sent when you enter a scene.

1) Open Patch
2) Choose View > Actor/Control Split
3) Press letter 'a' to activate secondary scene and jump to "Values 1"
4) Values change to 99 99 0 50 0 0 0 0 0 99
5) Press space bar to jump to "Values 2"
6) Values change to 75 75 0 25 0 0 0 0 0 75

So I'm not sure what the problem might be.

matrix-value-example.izz

Best Wishes,
Mark

Bennnid

@mark

indeed I see when it works, but I need to understand why it doesn't...

does it come from my float use and texte parser configuration?
thx

mark

@bennnid said:

indeed I see when it works, but I need to understand why it doesn't...

It's because of the order of your actors in the first scene. The Activate Scene actor is below the Matrix Value Send actor. Because Isadora executes the actors from top to bottom, the Matrix Value Send actor is executed *before* the Activate Scene actor. There is no Matrix Value Receive actor "listening" at the time you send the values, so nothing changes.

Usually, where the execution order of the actors is important, you can simply reverse the order. But the Jump, Jump++, and Activate/Deactivate Scene actors are special. For technical reasons, the scenes will not actually be activated or deactivated until the next execution cycle - i.e., the secondary scene will be activated after all actors in this scene are executed.

Instead, the solution is to get your Matrix Value Receive actor running before you ever get to the scene where you need it. I always use something like this to activate secondary scenes: 1) activate the scene, and 2) jump over that scene into the first scene of my show.

The example patch shows the way you did it and the way I've suggested above, and shows that my method works as you might expect. Make sure to show the stage so you can see the output from the Matrix Value Receive and the decoded values from the Javascript actor.

matrix-squared-simplified.izz

Best Wishes,
Mark

Bennnid

@mark

Thanks for your reply I t helps a lot

Though i still have problems when scene fade is set to 0, data’s are not pushed anymore, so I set 0,1 but don t know if it is a normal behavior...

mark

@bennnid said:

Though i still have problems when scene fade is set to 0, data’s are not pushed anymore, so I set 0,1 but don t know if it is a normal behavior...

You're right. I see this. I will investigate.

Best Wishes,
Mark

Bennnid

@mark
I also discovered strange behavior when scene fade interpolates matrix value send,
if same values are used on the next scene, there's a kind of flickering values as you can see on the patch passing from scene 1 to 2,
there seem to be a kind of conflict...

matrix square same values.izz

Bennnid

My bad, finally working fine, I guess I forgot another patch with same matrix send in the background...

Bennnid

Dear @mark, (I know you already noted the 0sec fade time bug but I have another one I guess )
I still have strange behavior with Matrix S/R, in below patch you'll see that you can use scene crossfade,

but if you click on the scene , not using crossfade; the matrix values don't communicate through the patch...

I'm I wrong somewhere? would it require a enter scene trigger?

thanks

test matrix scenes video.izz

Woland

@bennnid

Please report this in a support ticket (link in my signature) so we can get it logged and keep track of it more easily.

Best wishes,

Woland

Bennnid

@woland

Thanks a lot I was becoming nuts;-)