[Audacity-devel] Re: 1.1.3

[Joshua H. <jo...@re...>]

Joshua Haberman writes:
> I really want our next stable release to have a robust audio i/o
> system.  I don't want to delay the next release any more than anyone
> else, but I don't think we should pass off our current audio i/o as
> "stable."

I hope this didn't come off the wrong way.  I don't mean to put down the
first audio i/o rewrite -- moving to a completely new model is a tricky
thing to get right, especially where threads are concerned.  PortAudio
v18 doesn't offer a specific enough API to avoid the problems I was
mentioning.  My rewrite was based on what I learned from reading the
current code; I would not have known the pitfalls of using this model
(and how to avoid them) if I had started from scratch. 

I think our audio i/o is moving in a really good direction, I just want
to prevent exposing users to the instability of a transitional period. 

Josh