Mixxx

Bug #1172299
Comment #8

Comment 8 for bug 1172299

Revision history for this message

RJ Skerry-Ryan (rryan) wrote on 2013-04-26: Re: [Bug 1172299] Re: Jack Audio Connection Kit Implementation Does not Follow Normal Behaviour

#8

On Fri, Apr 26, 2013 at 5:52 PM, Daniel Schürmann <
<email address hidden>> wrote:

> Hi Barney,
>
> the Mixxx ports in Jack are instant ports created as counterparts to the
> connected ports. It is not intended to reconnect them by external Jack
> connection tools. So I am afraid your ideas are misleading.
>
> If you have programming experience and bored from the TV programm ;-).
> I can give you a hand writing a SoundDeviceJack class. This is the best
> way to solve this issue.
>

Yet again the Mixxx codebase goes in circles :). We used to have a sound
device for every API but PortAudio allowed us to rid ourselves of the
maintenance work of managing each individual one.

I really don't want to be back in the business of writing Sound
API-specific code (We were also talking about a PulseAudio SoundDevice to
get rid of pasuspender on Ubuntu!). Sure, each individual API seems simple
enough but when you add it all up it is way too much code to maintain. We
should check with PortAudio to make sure they won't support what we want
(the ability to create a device / endpoint in the case the API supports
it).

Also, I think there still may be some lingering assumptions about PortAudio
in SoundManager (other than the giant sections of ifdef's specific to
portaudio). We'll need to make sure it is truly generic.

> The config GUI will just have a additional SondDevice selector:
> 1. Portaudio:
> like it is.
> 2. Jack:
>

I think there's no reason to expose this detail to the user -- they surely
don't care. We could just make the API list of strings internally
represented by a (sound-device, API) tuple, so the intenral state of hte
API dropdown on linux would look like:

(PA, ALSA), (PA, OSS), (JACK, JACK)

and we would disable or blacklist JACK in PortAudio.

> nothing else except status infos, since everything is set by the jack
> server.
> All mix channels are exposed to jack with proper names.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1172299
>
> Title:
> Jack Audio Connection Kit Implementation Does not Follow Normal
> Behaviour
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1172299/+subscriptions
>

On Fri, Apr 26, 2013 at 5:52 PM, Daniel Schürmann <
1172299@bugs.launchpad.net> wrote:

> Hi Barney,
>
> the Mixxx ports in Jack are instant ports created as counterparts to the
> connected ports. It is not intended to reconnect them by external Jack
> connection tools. So I am afraid your ideas are misleading.
>
> If you have programming experience and bored from the TV programm ;-).
> I can give you a hand writing a SoundDeviceJack class. This is the best
> way to solve this issue.
>

Yet again the Mixxx codebase goes in circles :). We used to have a sound
device for every API but PortAudio allowed us to rid ourselves of the
maintenance work of managing each individual one.

I really don't want to be back in the business of writing Sound
API-specific code (We were also talking about a PulseAudio SoundDevice to
get rid of pasuspender on Ubuntu!). Sure, each individual API seems simple
enough but when you add it all up it is way too much code to maintain. We
should check with PortAudio to make sure they won't support what we want
(the ability to create a device / endpoint in the case the API supports
it).

Also, I think there still may be some lingering assumptions about PortAudio
in SoundManager (other than the giant sections of ifdef's specific to
portaudio). We'll need to make sure it is truly generic.

> The config GUI will just have a additional SondDevice selector:
> 1. Portaudio:
>   like it is.
> 2. Jack:
>

I think there's no reason to expose this detail to the user -- they surely
don't care. We could just make the API list of strings internally
represented by a (sound-device, API) tuple, so the intenral state of hte
API dropdown on linux would look like:

(PA, ALSA), (PA, OSS), (JACK, JACK)

and we would disable or blacklist JACK in PortAudio.

> nothing else except status infos, since everything is set by the jack
> server.
> All mix channels are exposed to jack with proper names.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1172299
>
> Title:
>   Jack Audio Connection Kit Implementation Does not Follow Normal
>   Behaviour
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1172299/+subscriptions
>