I am doing better since this morning. Mostly because a bedevilling bug randomly disappeared. Concerning since I don’t know why but less stressful. I realize I may seem overly down on this job but the hardest day is still better than most good days at the last job.
Thinking about team needs first, as a scrum master and leader, this AM is helping with feeling unproductive on my own dev work.
Trying to keep a constructive mind set but struggling. Just want to work away from people the rest of the week.
A problem being mysteriously fixed through no clear action of my own bugs me. A problem this weekend with my mixer is just such a case. After upgrading to the latest version of my operating system, a flavor of Linux that I prefer called Kubuntu, I could not get the software driver I had been using with my mixer working. I could get close but not to the point where my audio workstation would see my mixer. Of course I discovered this right when I sat down to record. Last night, last thing, when there wasn’t time or will left for extensive research and troubleshooting left in the weekend. When else would I discover a problem resulting from upgrading my OS? Not when it would be more convenient to investigate and fix.
The break bugged me so much, especially losing an opportunity to record when I had the will to do so, that I spent some time this morning before work to see if I could get things working again. I installed the latest version of my audio workstation, Ardour 4, because I had been meaning to, anyway. Through some experimentation, I stumbled upon the fact that letting Ardour directly drive my mixer, rather than using an external software controller worked. Doing so only worked using an option I didn’t think had a chance in hell, just using the basic audio stack that comes with Linux.
I was simultaneously relieved to have my mixer back but vexed as to why something that previously did not work, suddenly did. I dislike mysterious fixes almost as much as random breakages. If I don’t understand why something suddenly starts working, I feel helpless to deal with any subsequent breakage. This situation is usually a recipe for cascading frustration.
I did a bit more searching, just now, and I think I found the explanation.
Very current versions of the Linux kernel will support most of the same devices that FFADO can support, directly via the normal ALSA audio device driver layer.
That is from Ardour’s own documentation, specifically on its requirements. FFADO is the separate driver I used to use for my mixer since it is a Firewire mixer, an increasingly less common way to connect peripherals to a computer but one still very well suited to the demands of audio. ALSA is basically the core sound handling component of Linux. As a consequence of my operating system upgrade, I indeed do have a very new kernel.
Mystery solved. Of course, I have only done several seconds worth of testing. In past versions of ALSA, it hasn’t done well with the demands of high quality audio, such as working with a prosumer mixer. It is entirely likely there are frustrations still yet ahead but at least they won’t be entirely mysterious. And I will hopefully get some new recording in soon, regardless.
I couldn’t leave well enough alone. I hate having an unsolved tech puzzle. I was up early anyway, this morning, so tinkered a bit more with my mixer, installing Ardour4. Turns out everything works when allowing Ardour4 to direct drive and configuring to just use ALSA. I had no idea ALSA supported firewire but apparently it now does, all channels seem to be present and working. Long story short, I will be recording again no later than this coming weekend.
Wanted to record. Got mixer half working. Maybe next weekend.
Just realized upgrading to latest Kubuntu upgraded jack, now can’t get mixer working. Wanted to record, now yet another project.
Finished a bunch of writing, including next essay which is out for review, and some material for my other site.
In a couple of weeks, I will be heading to JSConf US 2015. I was going to talk about this, I will still talk about this more, in my next podcast. Given the quickly dwindling time remaining before the conference comes up, I wanted to share a quick heads up. Any reader or listener who will also be there, please feel free to shoot me a quick note if you’d like to meet.
I have one other possible work related conference, AWS re:Invent, that I have tentatively agreed to attend later this year, in October. Again, if you are going to be there and want to hang out, let me know.
I am enjoying being at a gig that is well resourced. While I got to travel at times for my last job, it was feast or famine. Either I was traveling a lot, too much really, or not at all. Now I have some discretion. If you know of any conferences you think I might be interested in, let me know about those too. I can always ask and I think within reason can expect to go to some of the more interesting and relevant tech conferences for the foreseeable future.
So you know, and I’ll unpack these more in a future podcast and/or essay, the technologies I am currently using, learning or interested in include React/Reflux, Node, Scala, microservices, reactive/concurrent programming, Docker, continuous delivery, and automated testing. I can probably make a case for less tech specific but still work relevant conferences like ones that bear strongly on agile as I am currently a scrum master for my day job. Anything else, while it may be of interest to me, I’ll have to foot on my own dime.
Now compiling Node on a Raspberry Pi. Next step: Inception.