Since Touch099 doesn’t have a 32bit version, I can’t migrate this project to 099 until this is fixed. The jack setup is 12 i/o setup, and I can’t think of any other way to get audio data into touch with the low latency and quality of data I want for this project other than perhaps trying Dante.
This bug still exists on 2017.35560 , with either 32 or 64 bit Jack. Running on a fully updated version of Windows 10 (creator’s edition came out after the previous bug report).
Hi jmt4zj, We have added this to our bug database but don’t have any timeframe for fixing it. We have been spending a lot of time working on Dante support in 099 and are actively engaged with that, it might be a better/quicker option for you if you are time sensitive.
Unfortunately using Dante for realtime processing of local loopback doesn’t give great results compared to JACK, which guarantees 1 buffer size max delay. Right now I’m running 12 stereo channels, 4 of which are rerouted into Touch, with very little latency when I run JACK at 128 samples.
However, for my current client’s needs I can run touch088 for the JACK real time processing and touch099 for some of the other components needing more asynchronous features and 099 exclusive features, which actually works out better due to the single threaded nature of touch. The Shared memory chops and pipe in/out will do the trick for all the cross thread sync I need to do.
Also, do you recommend using core affinity with Touch? [url]https://en.wikipedia.org/wiki/Processor_affinity[/url] I was considering it to lock the two touch instances to cores, since I’m also running Ableton and Resolume simultaneously to the 2 touch instances.