Been having some stability issues with serialosc. I frequently see 2 or 3 instances of serialoscd running in Activity Monitor. This morning I woke to my MBP fan wooshing loudly. Checked the console and found:
11/29/15 7:26:36.266 AM ReportCrash: Saved crash report for serialoscd version ??? to /Users/jasonwehmhoener/Library/Logs/DiagnosticReports/serialoscd_2015-11-29-072636_Jasons-MacBook-Pro.crash
11/29/15 7:28:05.000 AM kernel: process serialoscd thread 5681 caught burning CPU!; EXC_RESOURCE supressed due to audio playback
Here’s what the system profiler has to say about my USB environment. usb.rtf (54.4 KB)
That list makes it look complicated, but it’s just the internal keyboard/trackpad, the internal bluetooth host, and the two internal USB hubs, to which are attached a monitor which has an internal hub and media reader. Attached to the monitor is a KVM switch which has a mouse and keyboard attached. There is also a new Anker USB hub attached directly to the Macbook. This has the Monome, Scarlett 18i8 attached. Finally, my silly large Manhattan hub is also attached to the Anker hub, but since I’m only using that to charge things at the moment, I’ll remove that to simplify things.
Here’s what it looks like with the Manhattan hub removed: usb_v2.rtf (12.8 KB)
Since I never heard an answer about how to determine which version of serialosc I’m using, I went to look at dates in Github. It looks like the monome installer v1.1 was released in June 2014. It looks like serialosc 1.2 was released in October 2012 and 1.4 was released in August 2015. So I guess I probably have serialosc 1.2 installed.
I’m assuming it makes sense to download and install serialosc 1.4? Do I need to uninstall 1.2 first?
Edit: just noticed that the serialosc 1.3 release date makes it a candidate for what I already have installed as well. Which version was included with the monome 1.1 installer? That Github repository doesn’t appear to have any files in it, so I can’t verify for myself.
I learned that a restart is required before the new version will start.
I also learned that while serialosc 1.2 just has three indistinguishable serialoscd processes visible in activity monitor, 1.4 shows serialoscd, serialosc-devic, and serialosc-detector. So that’s one way to tell the difference.
Feature request for version 1.5: a version flag that would be visible in crash reports and from the command line.
Anyway (and aside), since this comes up somewhat often maybe another community effort could be maintenance of an FAQ for serialosc. For example, I noticed that there’s a stale link on the OSC docs and filed a bug but I’m not sure where that source lives or I’d just submit a PR!
Aside: I opened an issue to track the idea of a serialosc FAQ on the serialosc repo (#25). I wonder though if this wouldn’t be better hosted more centrally and encourage community input. Maybe a new repo in monome-community to host user maintained docs?