Thanks Stephane! Interestingly, it turns out that if I started the faust audio program first, then I could start the sensor scanner afterwards at max scan rate, taking 100% of one cpu. Just not the other way around.
I put your change in and did a make, with results below. Its not obvious to me that it actually compiled, but it seems like it was successful, since now I can start the two programs in either order and they work. Nice! make -C compiler -f Makefile.unix prefix=/usr/local make[1]: Entering directory '/home/pi/faust/compiler' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/pi/faust/compiler' make -C architecture/osclib make[1]: Entering directory '/home/pi/faust/architecture/osclib' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/pi/faust/architecture/osclib' I don't know if this is a change that you want for the main branch, but I may include it in a future pull request. I've also added an check for armv7 in faust2alsaconsole, and the corresponding gcc flags. That seems to work on bananapi and raspberry pi 2, although I don't know if the compiler flags are ideal. Thanks again for the help, Ben On 09/06/2015 01:44 AM, Stéphane Letz wrote: > 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 <[email protected]> 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 >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/faudiostream-users ------------------------------------------------------------------------------ _______________________________________________ Faudiostream-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-users
