Mercurial > code > home > repos > light9
changeset 1924:91bcc6c76934
sequencer can use zmq, it seems, but KC should not
Ignore-this: 79346c5e99e957c2f4fa3e7a5155b8c5
author | Drew Perttula <drewp@bigasterisk.com> |
---|---|
date | Sat, 01 Jun 2019 23:46:06 +0000 |
parents | feafbe49ca0b |
children | f8ab10f4c80b |
files | bin/effectsequencer light9/subclient.py |
diffstat | 2 files changed, 12 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/bin/effectsequencer Sat Jun 01 23:45:25 2019 +0000 +++ b/bin/effectsequencer Sat Jun 01 23:46:06 2019 +0000 @@ -39,7 +39,11 @@ 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, {
--- a/light9/subclient.py Sat Jun 01 23:45:25 2019 +0000 +++ b/light9/subclient.py Sat Jun 01 23:46:06 2019 +0000 @@ -41,4 +41,10 @@ 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)