Hi Jason, On Thu, 2007-12-06 at 19:13 -0700, Jason Schaefer wrote: > I am now using gutsy and built rev 1636. I am experiencing these same > issues. When I have jack running i cannot select any sound device and > mixxx does not show up in qjackctrl. If jack is not running everything > works as expected. I am using portaudio19-dev 19+svn20070125-1ubuntu2 > > Thanks for everyones help! > > Jason
Can you please try compiling and installing the latest development snapshot of PortAudio-v19 from here: http://www.portaudio.com/archives/pa_snapshot_v19.tar.gz If you compile it with --prefix=/usr, it should overwrite your stock Ubuntu portaudio package (which is what we want). If it's still not working once you've upgraded PortAudio, then see if you can follow Arve's instructions given here for enabling extra debugging info in PortAudio: http://www.nabble.com/forum/ViewPost.jtp?post=13978273&framed=y If you need help with this, send me an email and I'll do what I can. Thanks, Albert > > > > > On Nov 25, 2007 7:27 PM, Poor Yorick <[EMAIL PROTECTED]> wrote: > > > I think that was the longest sentence ever posted to mixxx-devel, so > > > forgive me for not quite being able to follow it. :P > > > > I'm famous for it. : ) > > > > > It sounds like you've got a bunch of different problems: > > > > > > 1) JACK is still not getting detected...? My guy feeling is telling me > > > this is definitely related to bug 1835494. Did you manage to try another > > > PortAudio-v19 application and see if JACK shows up in that? (Remember we > > > found out Audacity doesn't use PA-v19 on Gutsy...) > > > > I don't know any other PortAudio-v19 applications. What says the > > gallery? Know anyone else using PortAudio v19? I agree that it's > > related to 1835494, seems to be the same thing in action. > > > > > 1.5) r1612 was a one-line change, and I don't think it should cause any > > > "Audio device could not be opened" errors since it's related to closing > > > PA streams (see #2 below) > > > > The bugs didn't show up patching 1611->1612, it was more like > > 1580->1612. If SVN keeps logs of its patch revisions (and I bet it > > does) I can probably track down the version that worked. > > > > > 2) The thought just occurred to me that if I try locking the mutex before > > > calling Pa_AbortStream(), we can probably terminate the stream AND avoid > > > any deadlocks. (I've encountered this sluggish behaviour with > > > Pa_StopStream before too and it's pretty annoying, I agree.) > > > > I don't really know what you're talking about but I'll smile and nod > > because it sounds good. > > > > ~Yorick > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Mixxx-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
