Jump to content
Dataton Forum

WATCHOUT / Medialon - quick question


Recommended Posts

I am being told second hand that Medialon can not run or kill WATCHOUT auxiliary timelines in cluster mode. Can that be true?

I am hoping something is ‘lost in the translation’.

It is very important that auxiliary timeline control is available. The main timeline is used exclusively for re-mapping since it can not be killed. Much safer to keep the main timeline closed and show programming placed in auxiliary timelines so that there is little chance the mapping is accidentally disturbed.

Link to post
Share on other sites

No, Medialon Manager was always able to control auxiliary timelines.

What might have changed here is auxiliary timelines in folders which in fact might not work since Dataton changed the API.

I would also place the remapping (virtual screens) in the main timeline and make sure that I have a loop back command somewhere inside the cue to make sure that the timeline can't be moved out of the relevant part by accident. The main timeline can't be killed. It is always on.

Link to post
Share on other sites

Thanks for the help Rainer.

No task window folders in this show, will be sure to avoid them. While i do place loopback cues, i also trim the timeline duration to march the cue duration. ;)

Link to post
Share on other sites

You're welcome Jim.

That's another way to do it. I ususally just place a locate to time or cue point somewhere in the middle of the cue, jumpnig back and pausing at either a time within the cue or the cue to jump to. Have been hitting the space bar too often when I wanted to run an aux timeline and instead ran the main timeline 😉.

Link to post
Share on other sites
4 hours ago, RBeddig said:

You're welcome Jim.

That's another way to do it. I ususally just place a locate to time or cue point somewhere in the middle of the cue, jumpnig back and pausing at either a time within the cue or the cue to jump to. Have been hitting the space bar too often when I wanted to run an aux timeline and instead ran the main timeline 😉.

;)

Link to post
Share on other sites

If the error only affects aux timelines in folders, then it may be that Manager hasn't been updated to work with those. The control protocol syntax is a bit weird in this area. This works fine in PIXILAB Blocks of course, with the only caveat being that timelines in folders can not be named the same as top level aux timelines, or aux timelines in other folders.

Mike

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...