# HG changeset patch
# User Drew Perttula <drewp@bigasterisk.com>
# Date 2019-06-01 23:46:06
# Node ID 91bcc6c7693456849273060a2c3ae39189fd9a47
# Parent  feafbe49ca0b410fcee30835f9528a5612344265

sequencer can use zmq, it seems, but KC should not
Ignore-this: 79346c5e99e957c2f4fa3e7a5155b8c5

diff --git a/bin/effectsequencer b/bin/effectsequencer
--- a/bin/effectsequencer
+++ b/bin/effectsequencer
@@ -39,7 +39,11 @@ class App(object):
     def launch(self, *args):
         self.seq = Sequencer(
             self.graph, lambda settings: sendToCollector(
-                'effectSequencer', self.session, settings))
+                'effectSequencer', self.session, settings,
+                # This seems to be safe here (and lets us get from
+                # 20fpx to 40fpx), even though it leads to big stalls
+                # if I use it on KC.
+                useZmq=True))
 
         self.cycloneApp = cyclone.web.Application(handlers=[
             (r'/()', cyclone.web.StaticFileHandler, {
diff --git a/light9/subclient.py b/light9/subclient.py
--- a/light9/subclient.py
+++ b/light9/subclient.py
@@ -41,4 +41,10 @@ class SubClient:
         except Exception:
             traceback.print_exc()
             return
-        return sendToCollector('subclient', self.session, outputSettings)
+        return sendToCollector('subclient', self.session, outputSettings,
+                               # when KC uses zmq, we get message
+                               # pileups and delays on collector (even
+                               # at 20fps). When sequencer uses zmp,
+                               # it runs great at 40fps. Not sure the
+                               # difference- maybe Tk main loop?
+                               useZmq=False)