Nick Thompson wrote: > OK so I figured out the error of my ways, but I have to say this list is > pretty unresponsive in helping the community so I have to ask myself "is > pulse is a sensible choice for audio development today"? Particularly > since there is little in the way of useful setup documentation for > actually using the library on a programatic way, the error messages from > the library and utilities are not particularly helpful and so on. I disagree that this community is unresponsive. You just have to be patient. Lennart is the main developer but he does not sit slavishly reading the mailing list and responding immediately. He'll usually have a big purge every couple weeks, but generally does respond to almost everyone who asks something, unless someone else has jumped in already. >From what I can tell you've posted a couple questions but answered them yourself within a day! It's not really fair of you to answer your questions yourself so quickly without giving anyone a chance to try and be helpful :p The docs for the API from a coding perspective could do with some TLC I agree. I'm just jumping in to the coding now and it's a bit of an uphill struggle but Lennart typically gives good advice on IRC if he's around. I firmly believe that pulse is the most sensible choice for audio development :) Col
