[openob-users] Re: OpenOb receiver CPU maxing out 100%

Might this be a hardware issue? Have you tried running something else on that PI for an hour or longer and see if it heats up the same way? Lorne Tyndale Hi I installed OpenOb on a RasPi3 B+ using 'Stretch lite' OS, with a UCA222 USB audio interface connected at both ends. After about one hour, the receive end CPU shot to 100%, temp went up to 65 C and the audio stopped, though network lights on the Pi's still flashing. Stopped the receiver, let it cool, then restarted and audio started streaming again. Ran for about 1 hour, then audio dropped out again, CPU at 102%. I re-formatted the SD card and reloaded OpenOb, same problem (also tried with Buster lite, same problem). The prerequisites I used: apt install gstreamer1.0-plugins-base gir1.2-gstreamer1.0 gstreamer1.0-plugins-ugly gstreamer1.0-tools gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-alsa apt install python-setuptools python-gst-1.0 python-gi python-redis python-pip apt install redis-server (Receive end) pip install openob Has anyone come across this problem before ?, am I missing something with the prerequisites ? Any suggestions would be appreciated. Evan _______________________________________________ openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk To unsubscribe send an email to openob-users-leave(a)lists.talkunafraid.co.uk