I there.

I use a sound analyse to track a dmx light in a data array. (time in value one, dmx data in value 2) 

I record a first sound name the patch "caidadata" and a second one naming the path "extandida", erase, and re record. 

My goal is next to playback the 2 different .txt file

On my harddrive, i have both this 2 txt file create. 

But : I made a firt cue to play song + array data with "caidadata" path : i'ts work great

A second replacing the path by "extandida" : but it read "caidadata" array ! 

Do i missed something in the process ? 

Thanks for any helps :)

Cheers

@dusx said:

@tgk I believe you are having range problems. Here you have an output with a defined range of [int] 0 thru 127, and an input that is setup as [int] 1 thru 4. Now because a range is defined on each end of the connection Isadora does a value scaling

 @tgk 

This tutorial video on value scaling may be helpful.

@tgk

I believe you are having range problems. Here you have an output with a defined range of [int] 0 thru 127, and an input that is setup as [int] 1 thru 4. Now because a range is defined on each end of the connection Isadora does a value scaling. If you have a prog. num output of 22, you will see the select input switch to 2.

The easiest fix here is to place some actor between these 2. I would probably use an Absolute Value actor. Since the range on both the input and output of the Absolute value actor are set to Min and Max, no scaling will occur on either end, and you should see your Midi values received arrive unchanged to the select input of the Router actor.

Hi,

Attached is a very simple scene which contains a Program Change Watcher, set up on port 1 channel 1, which sends the program number it receives to a router. I have a MIDI footswitch which outputs PCs 1 through 4 and I see them appear correctly in the PC Watcher in the scene.

The output of this PC Watcher is connected to the Select input on a Router, with 4 outputs. I see the line flash green when the MIDI PC messages are received but the Router "Select" input never changes.

I can work around this by inserting a Trigger Value actor between them but this does seem like it may be a bug?

Thanks

Simple test scene

@woland It worked! Thank you so much, that saved me a ton of time!

@dusx I did now, 

thanks for your support in this 

Have you opened a support ticket yet?
If not, please do so we can follow up with you and try to determine why this isn't working.

Support link in my signature below.

@tease said:

@DusX : this is what I pasted in Isadora GLSL Actor (just took out the first line): (just took out the first line):

 Are you 100% sure you cleared the default code fully before pasting?
I was able to select and paste the code above into Isadora and it worked.

@danielpineiro said:

I checked that my computer is getting the OSC stream correctly (whit Protocol software:)Protokol screenshot

 It looks like the W/ address really should be 51 versions, eg: W/INT/
The way this software is sending this data is very non-standard, I don't think you can get access to this data in any better way unless you are able to change the way it is packaged and sent.

@gpeddino

I've changed the link. Try now.