Changeset - 91bcc6c76934
[Not reviewed]
default
0 2 0
Drew Perttula - 6 years ago 2019-06-01 23:46:06
drewp@bigasterisk.com
sequencer can use zmq, it seems, but KC should not
Ignore-this: 79346c5e99e957c2f4fa3e7a5155b8c5
2 files changed with 12 insertions and 2 deletions:
0 comments (0 inline, 0 general)
bin/effectsequencer
Show inline comments
 
@@ -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, {
light9/subclient.py
Show inline comments
 
@@ -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)
0 comments (0 inline, 0 general)