You may try to hack the "OSCSetup::start" method in "faust/src/osc/OSCSetup.cpp" and add a "SetPriority" call like:
fOSCThread = new OscThread (mp, port, fErrCallback, fArg); fOSCThread ->SetPriority(80); fOSCThread->start(); recompile/restart and see if it helps. Stéphane Le 6 sept. 2015 à 02:41, Ben Burdette <bburde...@gmail.com> a écrit : > Hey all; > > I'm trying out faust for synthesis on an instrument, which uses a > bananapi ARM computer. On the banana pi there's a c++ program which > continuously scans a number of sensors, and then faust which receives > the osc messages to trigger audio. > > When the key scanner is run full blast it maxes out one of the two > cpus. This causes the osc interface for faust to be unresponsive, even > though it apparently continues with audio synthesis. If I throttle back > on the scanner, the osc stuff starts responding - if I restart the faust > program. > > At certain rates I can start the faust program first, then start the key > scanner and it works. But the other way around doesn't. > > Any ideas re this? Maybe running faust with realtime priority? > > thanks, > > Ben > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Faudiostream-users mailing list > Faudiostream-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/faudiostream-users ------------------------------------------------------------------------------ _______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
