Re: jack problems 'portable, cross-platform' apps (was qjackctl patchbay)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



schoappied wrote:
> Fons Adriaensen wrote:
>   
>> On Fri, Apr 18, 2008 at 04:43:19AM -0700, Justin Smith wrote:
>>
>>   
>>     
>>> I think this is because, when your app is using oss or alsa, the friendly
>>> thing to do is to stop using the sound card (since using the sound card
>>> blocks other applications that would like to use it), and it is easier to
>>> plug in your calls to the jack api in the same place as the oss or alsa api
>>> calls, than it is to change your connection/disconnection policy based on
>>> api.
>>>     
>>>       
>> Probably true, but it's a weak argument IMHO. It would just
>> take a couple of ifs to get this right.
>>
>> A real problem are the 'portable, cross-platform' audio APIs
>> and tools that usually fail to understand the rather special
>> nature of JACK, or have been designed in such a way that they
>> can't handle it.
>>
>> Ciao,
>>
>>     

If it just takes a couple of ifs, than things has to improve in my 
opinion....

I don't know if there are devs of audacity and rezound on this list, but 
I'd like to see those apps have a constant connection with jack... so 
you can connect is to jack_mixer for example...

Or should 'we' mail those guys or make a bug report? Or does Fons want 
to make contact with the devs of these apps...? What's the best way to 
solve this problem?

Regards,

Dirk



_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux