15 Jul
2011
15 Jul
'11
8:30 a.m.
Hi everyone,
I want to give hdsp mixer OSC support for fader-, pan, mute and presetcontrol in both
directions and input metering.
the OSC client shall be another hdsp mixer instance on the remote machine.
I wanted to know, where i can find the sources?
And if someone has some hints to do that...
Bye Ck
15 Jul
15 Jul
10:05 a.m.
On Fri, Jul 15, 2011 at 08:29:23AM +0200, Christoph Kuhr wrote:
Hi everyone,
Hi!
I want to give hdsp mixer OSC support for fader-, pan,
mute and
presetcontrol in both directions and input metering.
the OSC client shall be another hdsp mixer instance on
the remote machine.
Eh? And why do you need OSC for this? You can use plain socket()
communication if you're using two HDSP mixer instances anyway. This
said, you can resort to X-Forwarding, VNC or the lot and forget about
even hacking on it.
I wanted to know, where i can find the sources?
hdspmixer is part of alsa-tools:
git://git.alsa-project.org/alsa-tools.git
And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.
Good luck. ;)
--
mail: adi(a)thur.de http://adi.thur.de PGP/GPG: key via keyserver
10:44 a.m.
Hi,
Osc because i want to use some puredata patches with it, which would also be possible with
sockets, but i like the structure and functionality of osc and i think its more
flexible... if i control ardour/jack via osc i would like to have the same for alsa...
I wanted to make a menu item: osc client mode
The recording machine run hdsp mixer with osc server daemon and the remote machine runs
hdsp mixer, but with osc not alsa...
But rewriting the whole thing doesnt fit for me now... this is a little side need...
At the moment im mainly writing on an avb module...
Bye
Ck
Adrian Knoth <adi(a)drcomp.erfurt.thur.de> schrieb:
On Fri, Jul 15, 2011 at 08:29:23AM +0200, Christoph Kuhr wrote:
Hi everyone,
Hi!
I want to give hdsp mixer OSC support for fader-, pan,
mute and
presetcontrol in both directions and input metering.
the OSC client shall be another hdsp mixer instance on
the remote machine.
Eh? And why do you need OSC for this? You can use plain socket()
communication if you're using two HDSP mixer instances anyway. This
said, you can resort to X-Forwarding, VNC or the lot and forget about
even hacking on it.
I wanted to know, where i can find the sources?
hdspmixer is part of alsa-tools:
git://git.alsa-project.org/alsa-tools.git
And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.
Good luck. ;)
--
mail: adi(a)thur.de http://adi.thur.de PGP/GPG: key via keyserver
_____________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
16 Jul
16 Jul
1:33 p.m.
Is there the possibility to run a hdsp card dummy?
im programming on another machine without hdsp card...
On 15.07.2011 10:05, Adrian Knoth wrote:
On Fri, Jul 15, 2011 at 08:29:23AM +0200, Christoph
Kuhr wrote:
Hi everyone,
Hi!
I want to give hdsp mixer OSC support for fader-,
pan, mute and
presetcontrol in both directions and input metering.
the OSC client shall be another hdsp mixer instance on the remote machine.
Eh? And
why do you need OSC for this? You can use plain socket()
communication if you're using two HDSP mixer instances anyway. This
said, you can resort to X-Forwarding, VNC or the lot and forget about
even hacking on it.
I wanted to know, where i can find the sources?
hdspmixer is part of alsa-tools:
git://git.alsa-project.org/alsa-tools.git
And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.
Good luck. ;)
4:01 a.m.
On Friday, July 15, 2011 10:05:24 AM Adrian Knoth wrote:
On Fri, Jul 15, 2011 at 08:29:23AM +0200, Christoph
Kuhr wrote:
This is something I've never understood: Why is there no generic interface in the ALSA
API for a matrix mixer? For every pro-audio card that comes out the wheel has to be
completely re-
invented just to control the thing. Are the devices with matrix mixers that different that
it prevents them from being wrapped by a common API that any ALSA compliant mixer can
hook into?
-Reuben
And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.
18 Jul
18 Jul
4:23 a.m.
On Sat, Jul 16, 2011 at 10:02 PM, Reuben Martin <reuben.m(a)gmail.com> wrote:
On Friday, July 15, 2011 10:05:24 AM Adrian Knoth
wrote:
what i recall (from years and years and years ago) was that the ALSA
control API can handle 3-argument calls (input,output,gain - for
example), which is why amixer and aset can be used to control the hdsp
matrix mixer, but there is no general representation that could be
feasibly used by generic tools. put differently, there is no "concept"
of a matrix mixer anywhere in the ALSA API.
On Fri, Jul 15, 2011 at 08:29:23AM +0200,
Christoph Kuhr wrote:
This is something I've never understood: Why is there no generic interface in the
ALSA API for a matrix mixer? For every pro-audio card that comes out the wheel has to be
completely re-
invented just to control the thing. Are the devices with matrix mixers that different
that it prevents them from being wrapped by a common API that any ALSA compliant mixer
can
hook into? And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.
19 Jul
19 Jul
9:40 a.m.
well as you guys said, its horrible code...
so i cam to the conclusion that modifing takes to much time and pain...
i think i will write a new one, using osc communication by default...
but that will take some time...
bye
Ck
On 18.07.2011 04:23, Paul Davis wrote:
On Sat, Jul 16, 2011 at 10:02 PM, Reuben
Martin<reuben.m(a)gmail.com> wrote:
On Friday, July 15, 2011 10:05:24 AM Adrian Knoth
wrote:
what i recall (from years and years and years ago) was that the ALSA
control API can handle 3-argument calls (input,output,gain - for
example), which is why amixer and aset can be used to control the hdsp
matrix mixer, but there is no general representation that could be
feasibly used by generic tools. put differently, there is no "concept"
of a matrix mixer anywhere in the ALSA API.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev On Fri, Jul 15, 2011 at 08:29:23AM +0200,
Christoph Kuhr wrote:
This is something I've never understood: Why is there no generic interface in
the ALSA API for a matrix mixer? For every pro-audio card that comes out the wheel has to
be completely re-
invented just to control the thing. Are the devices with matrix mixers that different
that it prevents them from being wrapped by a common API that any ALSA compliant mixer
can
hook into? And if someone has some hints to do that...
Rewrite hdspmixer, first. It's a horrible mess at the moment, but I'm
sure you'll see in a second. ;) We could use some clean abstraction of
cards, a matrix mixer and especially a rewrite from scratch in GTK/Qt.
4811
days inactive
4815
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Adrian Knoth -
Christoph Kuhr -
Clemens Ladisch -
Paul Davis -
Reuben Martin