On Sun, 2008-07-06 at 22:20 +0200, Arve Knudsen wrote:
> Hi Espen
> Perhaps you could come up with a patch for this?
>
> What do others think of this scheme?
>
> Arve
>
>
> On Mon, 16 Jun 2008 03:51:54 +0200, Esben Stien <
b0ef@...>
> wrote:
>
> > Having the app connect to a JACK device is not what is wanted in most
> > JACK use cases.
> >
> > It would be nice with a virtual device that simply advertised itself
> > with some ports and the JACK sample rate. This would mean that the app
> > would just appear as a normal JACK client that didn't connect to
> > anything and you could use normal JACK connection management
> > applications to connect its ins and outs.
> >
I never understood this, so perhaps you can elaborate more. When I run
Mixxx with jackd running, it connects to the output device
automatically, so the user doesn't have to mess around with another
external application to make Mixxx work. The way PortAudio currently
behaves with JACK right now "just works" - The user will launch an
application, which will then be able to immediately playback audio.
Is the use case where the user wants to do more advanced routing that
begins with no connections really the most common case?
Thanks,
Albert
_______________________________________________
Portaudio mailing list
Portaudio@...
http://techweb.rfa.org/mailman/listinfo/portaudio
