Output Names

[AMarsh]

Relatively new to WO programming, I've got several different outputs I'm using and have named them all in the Output window. However, when I drag any of them to the timeline, they all read as LED 4 (one of the names). I've labeled them all again in the timeline, but it still shows up with the incorret name on top. They function properly, but it would be nice if they looked right in case someone other than me uses the program. Thoughts?

[Mike Fahl]

Please send a small example show that exhibits this behavior to support@dataton.com, as I don't quite follow what you're doing here.

 

Mike

[jfk]

So few people use the string output device feature that it took me a minute to grasp your description.

I get what you are saying, and what you are observing appears to be perfectly normal.

the cue name is not displayed on the timeline cue, the string output device name is displayed.

i.e When you drag an output device from the output window to a timeline,

it creates a cue. First time I did it,  like you, the displayed name of that cue was not what I expected.

 i.e. it is not the cue name, it is the associated device name.

When the cues are running, watch the display in the Output Device window,

and you will see the cue name appear there,

I suspect that is what you are expecting for the name on the timeline.

 

Now as for all of them being "LED 4", two things to consider. Is the displayed name truncated?

Or face the possibility that are all really String output "LED 4" and 

revisit the process of dragging string output devices to the timeline.

[cowboyclint]

I typically put the output strings in a short AUX timeline, and name that something that makes more sense. Then trigger the AUX through the main timeline. It keeps me more organized.

[jfk]

I typically put the output strings in a short AUX timeline, and name that something that makes more sense. Then trigger the AUX through the main timeline. It keeps me more organized.

 

Yes, I do as well, as I often use the same command in multiple places.

By referencing an aux timeline with a control cue, any edits / corrections made on the aux timeline

are implemented in all the places I use the same cue.

 

Just be aware of the time needed for an

aux timeline to transition from dormant / dead to active / alive

and manage that accordingly in your programming.

 

But that is unrelated to OP's confusion.

The same confusion AMarsh describes will occur on a main timeline or an aux timeline. 

[Walter]

Though if you expand the size of the timeline and you name the cue, you have a clear reference of what the cue is about to perform. (resulting in a cue stating first the outputname and then the actual action).

Would be nice if either you have output + action in one line i.s.o. two, or first the action and then the outputname (once completed in it's box.)

Though indeed, the way to go is make an aux (loopable) for shut on and one for shut off. Put it under a midi-keyboards note and with one push of the button (or a reference in the used timeline for your sequence) you're good to go time after time.

[jfk]

BTW OP. Even though the output window will let you select multiple string outputs,

you must drag a string output one at a time to the timeline to create a cue for it.

If you drag multiples, you still only get just one cue, and it will always be the same 

string output out of the selected group.

 

Though if you expand the size of the timeline and you name the cue, you have a clear reference of what the cue is about to perform. (resulting in a cue stating first the outputname and then the actual action).

 

Say what? "The cue"? Meaning the string output cue or something else? Is this a feature suggestion?

 

Would be nice if either you have output + action in one line i.s.o. two, or first the action and then the outputname (once completed in it's box.)

 

That sure sounds like a feature suggestion too. Possibly should be posted in the topic: Feature requests? - POST here ?

 

Though indeed, the way to go is make an aux

 

And the Control Cue calling the aux timeline

can be named to provide a good description of the action to be performed. 

In a way, this works around the behavuor of the string output cue name display OP describes.  

 

(loopable) for shut on and one for shut off.

 

Depends on how you define loopable I guess.

I trim the timelines down to about 1 or 2 seconds

and then have them die (stop) with an explicit Control Cue - Stop

which implicitly resets them to the beginning for the next use.

That is not really a loop, but I guess the result is similar.

 

Put it under a midi-keyboards note and with one push of the button (or a reference in the used timeline for your sequence) you're good to go time after time.

 

 

 

[Walter]

Hi there, first "feature request" isn't a feature request, as it is a current feature actually. (One can name the string output cue which shows in the second line of the cue).

Second one is a feature request but as I don't need it, won't be posting it in the famous post. (Very curious about future release of wo6 though, anxious to see which requests are taken in).

 

And yes, with "loopable" I mean exactly what you state, a stop cue right after the action cue.

;-)