Patch not refreshing

We're having frequent problems with the patch not refreshing.  About 10% of the time the display will not show the new info for a second or two.  Sometimes it will show up when you arrow to the next field, other times you have to retype the info to get it to show up.  Occasionally the info will show up but the lamp won't respond when you bring the channel up.  Closing the patch window usually helps but sometimes we have to reopen it and type the new info again.

Could this problem be related to "RND 0001903 Changing patch data with multiple patch views open does not refresh data in those other tabs.

We are running both a client and a file server on the network.  We notice these problems more often when patching from the client but I suspect that is only because we do more single channel patching from the client than the console.  We use the client as a remote during focus calls and as a designer display during tech rehearsals.  The initial patch is generated from Lightwright 4 and corrected through a series of find and replace commands in MS Word to make the ASCII file compatible with Congo.

We are on version 6.0.3.

Thanks,
Mat

Parents Reply Children
  • I have a few more details.  Yesterday I patched an output to a new channel using the universe 1 output list.  I hit escape to close the output list, went to live and brought up the new channel.  The lamp stayed off.  I reopened the output list and retyped the channel into the appropriate output, the info was already displayed, and the lamp came on.  I hit escape to exit the output list and the lamp went out.  I opened the output list again and a moment later the lamp came back on.  Close the output list the lamp goes out.  Bringing the channel out and back to full had no effect.  I then opened the channel list and re-entered the output there.  That got things working again.

    Thanks,
    Mat

  • If you mostly see this on the client, it might be related to the refresh problem of the Main Playback that you also reported.

    Is the client connected directly to the switch or through the wireless network when you see this?

  • We see this problem on both the client and the main console.

Related