[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-audio-dev
Subject:    Re: [LAD]  =?utf-8?q?=3F=3D=3D=3Futf-8=3Fq=3F__further_in_on_midi2udp?=
From:       "Ralf Mattes" <rm () mh-freiburg ! de>
Date:       2018-09-11 17:19:19
Message-ID: 61e4-5b97f900-3d3-53d31c00 () 186644223
[Download RAW message or body]

 
Am Dienstag, 11. September 2018 19:13 CEST, Len Ovens <len@ovenwerks.net> schrieb: 
 
> On Tue, 11 Sep 2018, Jonathan E. Brickman wrote:
> 
> > The current software thought is to have both sides have two threads: one thread
> > running callback to JACK, the other handling UDP/TCP, the threads communicating
> > by Python FIFO queues, the UDP/TCP thread being constrained by 31.5kHz wait-state
> 
> Use jack ring buffers for thread communication. They are rt safe. I have 
> used them with a midi to qwerty keyboard bridge. (see: 
> http://www.ovenwerks.net/software/midikb.html )

That's C-code, iirc. The problem with python: the interpreter has a global lock (the
infamous GIL). So, unless you write your jack callback in C/C++ your code might block.

 Cheers, RalfD
 
> 
> 
> --
> Len Ovens
> www.ovenwerks.net
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev@lists.linuxaudio.org
> https://lists.linuxaudio.org/listinfo/linux-audio-dev
 
 
 
 
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev

[prev in list] [next in list] [prev in thread] [next in thread]