<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blindly Coding (Posts about Programming)</title><link>http://ahicks.in/</link><description></description><atom:link href="http://ahicks.in/categories/programming.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Tue, 01 Oct 2024 20:37:50 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>The Horror of Audio Output</title><link>http://ahicks.in/posts/december2014/horror-of-audio-output/</link><dc:creator>Austin Hicks</dc:creator><description>&lt;div&gt;&lt;p&gt;Update: I didn't realize there was a clarity issue, but the &lt;a href="https://news.ycombinator.com/item?id=8727312"&gt;Hacker News thread &lt;/a&gt; made it clear that I should provide this clarification.  I knew from the beginning of development that, no matter what I did, I'd need to support multiple backends.  I had already written something like a third of the code that I would have to write by taking this route and, at some point, you just have to do it in the interest of actually moving forward.  I am also developing a commercial library.  To this end, some options that would otherwise be options are closed to me; I cannot use any dependency that my end users may need to purchase nor may I entertain the option of bringing in monolithic app development frameworks.  Anyhow, back to your regularly scheduled blog post...&lt;/p&gt;
&lt;p&gt;I've not been blogging recently because of two factors.  The first of these is that we still do not have an accessible solution by which I can include math equations, save for me instructing you to learn LaTeX and view the source code of my articles; It would be incredibly hypocritical of me to make my blog posts inaccessible.  The second is that the things I have been working on are somewhere between the domain of programming and math textbooks, with a bit of art and a lot of trial and error thrown in, so I simply haven't had anything interesting to say that fits into a blog post.&lt;/p&gt;
&lt;p&gt;the latter of these has fixed itself and I expect I shall actually be posting semi-regularly again.&lt;/p&gt;
&lt;p&gt;Today I want to talk about the horror of the world of audio output and all the wonderful broken promises you run into when you try.  For a very long time, this was the hardest part of Libaudioverse, and I have had to literally give up on software libraries and at least one nice feature.  I'm going to talk about this primarily in the form of  an enumerated list of all the things I've had to try, talking about what's wrong with each one; if you're not interested in a post about various audio libraries and their brokenness, you can stop now.  This is long, but I think it is worth chronicling so that others do not fall into the same pitfalls, something which has both frustrated me greatly and wasted weeks of Libaudioverse development time.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://ahicks.in/posts/december2014/horror-of-audio-output/"&gt;Read more…&lt;/a&gt; (10 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>Libaudioverse</category><category>Programming</category><guid>http://ahicks.in/posts/december2014/horror-of-audio-output/</guid><pubDate>Tue, 09 Dec 2014 20:30:00 GMT</pubDate></item></channel></rss>