Production Computer Protocol - setInput command 3rd parameter Help

[ahaghshenas]

I am trying to get an input to fade to a value I set.

 

In the user guide pg 256, for the setInput command there is a 3rd parameter which is a fade rate in mS.

 

I cannot get this to work can anyone help.

 

 

Example

 

Generic Input - Label used Volume - limit set to 100 - fade rate 20000mS

 

Command used

 

setInput Volume 100 20000

 

Using this command, I get the value instantly.

[jfk]

I am trying to get an input to fade to a value I set.

 

In the user guide pg 256, for the setInput command there is a 3rd parameter which is a fade rate in mS.

 

I cannot get this to work can anyone help.

 

Out of curiousity, are you using Production Computer Protocol or Display Cluster Protocol?

The command is the same for both,

For command details, the Display Cluster Protocol references the section in Production Computer Protocol,

so the page reference could be either one.

 

Example

 

Generic Input - Label used Volume - limit set to 100 - fade rate 20000mS

 

Command used

 

setInput Volume 100 20000

 

Using this command, I get the value instantly.

 

That is odd,  Clearly it does not matter since you are achieving the target value, but shouldn't the string value be in quotes?

 

Also, of more importance, did you use the Limit setting of the Generic Input to redefine your range?

 

 

The default range is 0 - 1.0 , for the defaults, your target value is out of range and should be 1.0 for 100%

 

Have you checked the local error log after sending this command?

 

with default limit, try

setInput "Volume" 1.0 20000

 

I have seen the fade rate parameter used succesfully in both targets forms (absolute and relative)

in Cluster mode. Albeit not at such a long duration, but I doubt that is the issue.

[ahaghshenas]

Out of curiousity, are you using Production Computer Protocol or Display Cluster Protocol?

The command is the same for both,

For command details, the Display Cluster Protocol references the section in Production Computer Protocol,

so the page reference could be either one.

 

 

That is odd,  Clearly it does not matter since you are achieving the target value, but shouldn't the string value be in quotes?

 

Also, of more importance, did you use the Limit setting of the Generic Input to redefine your range?

 

 

The default range is 0 - 1.0 , for the defaults, your target value is out of range and should be 1.0 for 100%

 

Have you checked the local error log after sending this command?

 

with default limit, try

setInput "Volume" 1.0 20000

 

I have seen the fade rate parameter used succesfully in both targets forms (absolute and relative)

in Cluster mode. Albeit not at such a long duration, but I doubt that is the issue.

Thanks for your reply, I am in fact using production computer protocol.

 

I have changed the range to 100 and I am not getting any errors as I execute the command, just an instant jump to the value and no fade to value.

 

I have tried what you suggested with the same results as before, an instant jump to value.

 

the reason for the long fade rate is because I was testing over the top durations as I am always getting an instant change.

 

 

This has been puzzling me for a while, as the documentation is very clear and don't understand why its not working

[Mike Fahl]

Normally, the value used is in the range 0…1. It appears you're controlling volume of something. Try fading the value to 0 and 1 instead, as Jim suggests, to see if this gets you the result you want:

 

   setInput "Volume" 1.0 20000

 

and

 

   setInput "Volume" 0 20000

 

should fade the Volume input to those extremes over 20 seconds.

 

Mike

[ahaghshenas]

I have used default values and realistic fade rates but no matter what I try I get no fade and an instant change.

 

Using

 

setInput "Volume" 1.0 20000

and

setInput "Volume" 0 20000

 

I have tried carrage return, line feed and both together.

 

 

Here is the show file I made to test it.

https://www.dropbox.com/s/ud7zebcnh3e2e03/cool.watch

 

This doesn't make sense, where am I going wrong?

[jfk]

 

...Here is the show file I made to test it.

https://www.dropbox.com/s/ud7zebcnh3e2e03/cool.watch

 

This doesn't make sense, where am I going wrong?

 

That show file has no media, no stage objects and no cues ????

 

If you are expecting to see the Value field of the Input window animate the fade in its indicator,

ain't gonna happen. That does not mean it is not fading in actual use.

Yes, the value indicator jumps between 0 and 1 when the appropriate commands are received,

but the actual result (sound output) does fade as expected.

 

I just added a sound file (a sample file supplied with Win 7 called "Maid with the Flaxen Hair.mp3")

and added a display to your sample show,

attached the volume input to the volume tween formula of the sound file,

connected and typed the setInput commands in MacOS's terminal program (after establishing a telnet connection),

and the fades via production protocol work just fine. 

 

I even tried the 20 second fade and it worked as expected.

 

Here are the commands that I tried, all worked as expected ...

 

setInput "Volume" 0 2000

setInput "Volume" 1 2000

setInput "Volume" 0 2000

setInput "Volume" 1 6000

setInput "Volume" 0 20000

 

I would post the modified files for you if you would like, but I am running 5.5 and you are running 5.3.1,

so you could no use them at this point anyway.

[ahaghshenas]

Haha works a charm.

 

Really thought I would see it animate in the input window.

 

Thanks for your help

[jfk]

Haha works a charm.

 

Really thought I would see it animate in the input window.

 

Thanks for your help

 

I'll let you off the hook on that one, its an easy assumption to make, albeit incorrect.

The input window value indicators work the same for all input types.

i.e. the indicator always snaps to the new target value as soon as it is received.

MIDI and ArtNet/DMX inputs execute fades by sending a rapid stream of new targets,

and as such the indicator animates the fade since there is no fade rate data,

just a rapidly updating set of new targets.

But MIDI and ArtNet/DMX inputs send discrete target, while the setInput command has the option of sending a vector (target and rate),

and the indicator does not reflect the fade rate, only the target value