News, tours, venues, and more!
Stay up to date with Meyer Sound.
Sign Up for Newsletters

Meyer Sound Forum

Welcome to the Meyer Sound Forum!
While our customer support team moderates this forum and participates in some discussions, this is not an ingress point for our internal support staff. To submit a feature request or bug report, please use the button below.

Submit Feature Request or Bug Report

Code of Conduct
This forum for is for audio professionals and Meyer Sound users to exchange advice, ask questions, meet with other members of the audio community and Meyer Sound Customer Support personnel. Please keep discussions relevant to Meyer Sound products.
Be Kind and Courteous
We’re all in this together to create a welcoming environment. Let’s treat everyone with respect. Healthy debates are natural, but kindness is required.
No Promotions or Spam
Give more than you take to this forum. Self-promotion, spam and irrelevant links aren’t allowed. Please keep discussions relevant to Meyer Sound products. Do not post product ads or “For Sale” ads. Do not post inappropriate images or ads, you will be banned immediately.
Respect Everyone’s Privacy
Being part of this group requires mutual trust. Authentic, expressive discussions make forums great, but may also be sensitive and private. What’s shared in the forums should stay in the forums.
Keep it Legal
Be mindful of security, copyright, and intellectual property concerns when sharing venue drawings, project files, Spacemaps and other file types.
File Posting
File uploads are allowed up to 10MB for the following types: jpg, jpeg, gif, png, bmp, pdf, mapp, spacemaps, coreproject. For larger files, please use a file sharing service and post a link.
Specific Software Support Issues
Visit our Contact Form select Software Support, and enter the requested information to create a feature request or bug report.
Consult a Professional
Absolutely no advice for rigging/electrical/life safety is allowed beyond “Consult a professional.”
Contact
For requests and issues related to this forum, please email forums@meyersound.com.
Disclaimer
Meyer Sound is not liable or responsible for content posted in these forums.
Forum Navigation
You need to log in to create posts and topics.

Monitoring Cue Recalls using TCP/IP

richardb@msli.com@richardbmsli-com
6 Posts
#1 · June 23, 2023, 6:59 AM
20230623

jaf

You can use TCP/ASCII to be notified whenever a Cue has been recalled (by anyone) by just watching the CueStation log for “Recalled Cue #XXX” messages.Specifically:
  1. Connect to port 18034 of any D-Mitri processor module in the system.
  2. Send the ASCII command “watch log/* quietly” (the “quietly" keyword is so that you won’t receive the current contents of the log, rather only future additions to it)
  3. Whenever a line of text comes back over the TCP connection, scan it for the substring “sourceName=[dcasld@“ and also the substring “name=[Recalled Cue #”; if both are present, then a cue has been recalled and the Cue ID is the number immediately after that # symbol.
Jeremy
Uploaded files:
Click for thumbs down.0Click for thumbs up.0
Last edited on June 23, 2023, 12:26 PM by richardb@msli.com