Hi.
I've been thinking a bit about how to simplify the audio interface in
OpenBSD and I thought about sysctl. Personally I find the mixerctl
interface horrible. 88 entries on my system, and I honestly do not
understand what half of it is for ;-)
I'm not trying to undermine the work put into thi
mixerctl inputs.master=[0,255]
mixerctl outputs.master=[0,255]
those two should do what you want. the rest are there for people that
like to poke at their audio bits.
On 2009 Nov 20 (Fri) at 15:39:55 +0100 (+0100), Thomas Pfaff wrote:
:Hi.
:
:I've been thinking a bit about how to simplify the
On Fri, 20 Nov 2009 15:45:31 +0100
Peter Hessler wrote:
> mixerctl inputs.master=[0,255]
> mixerctl outputs.master=[0,255]
>
>
> those two should do what you want. the rest are there for people that
> like to poke at their audio bits.
>
Well, inputs could be a line or a mic so I think we ne
On Fri, 20 Nov 2009 15:45:31 +0100
Peter Hessler wrote:
> mixerctl inputs.master=[0,255]
> mixerctl outputs.master=[0,255]
>
>
> those two should do what you want. the rest are there for people that
> like to poke at their audio bits.
>
Sorry, I misread what you said.
Still, is a simpler s
On Nov 20, 2009, at 8:03 AM, Thomas Pfaff wrote:
On Fri, 20 Nov 2009 15:45:31 +0100
Peter Hessler wrote:
mixerctl inputs.master=[0,255]
mixerctl outputs.master=[0,255]
Still, is a simpler sysctl interface something people want? mixerctl
can be reserved for people wanting to screw around w
On Fri, 20 Nov 2009 08:28:34 -0800
Ted Unangst wrote:
> On Nov 20, 2009, at 8:03 AM, Thomas Pfaff wrote:
>
> > On Fri, 20 Nov 2009 15:45:31 +0100
> > Peter Hessler wrote:
> >
> >> mixerctl inputs.master=[0,255]
> >> mixerctl outputs.master=[0,255]
> >
> > Still, is a simpler sysctl interface s
On Fri, 20 Nov 2009 16:10:26 +0100
Thomas Pfaff wrote:
> On Fri, 20 Nov 2009 15:45:31 +0100
> Peter Hessler wrote:
>
> > mixerctl inputs.master=[0,255]
> > mixerctl outputs.master=[0,255]
> >
> >
> > those two should do what you want. the rest are there for people that
> > like to poke at th
On Fri, Nov 20, 2009 at 03:39:55PM +0100, Thomas Pfaff wrote:
> Hi.
>
> I've been thinking a bit about how to simplify the audio interface in
> OpenBSD and I thought about sysctl. Personally I find the mixerctl
> interface horrible. 88 entries on my system, and I honestly do not
> understand wha
On Nov 20, 2009, at 8:47 AM, Thomas Pfaff wrote:
On Fri, 20 Nov 2009 08:28:34 -0800
Ted Unangst wrote:
On Nov 20, 2009, at 8:03 AM, Thomas Pfaff wrote:
On Fri, 20 Nov 2009 15:45:31 +0100
Peter Hessler wrote:
mixerctl inputs.master=[0,255]
mixerctl outputs.master=[0,255]
Still, is a s
On Fri, 20 Nov 2009 18:01:24 +0100
Alexandre Ratchov wrote:
>
> > I'm not trying to undermine the work put into this; it has been greatly
> > improved over the last 6 months or so, but all I really want to do is
> > simply adjust the input and output volume (and a few other things);
> >
> >sy
On Fri, Nov 20, 2009 at 03:45:31PM +0100, Peter Hessler wrote:
> mixerctl inputs.master=[0,255]
record.volume, actually. historical/consistency reasons.
> mixerctl outputs.master=[0,255]
>
> those two should do what you want. the rest are there for people that
> like to poke at their audio bit
On Fri, Nov 20, 2009 at 04:10:26PM +0100, Thomas Pfaff wrote:
> On Fri, 20 Nov 2009 15:45:31 +0100
> Peter Hessler wrote:
>
> > mixerctl inputs.master=[0,255]
> > mixerctl outputs.master=[0,255]
> >
> >
> > those two should do what you want. the rest are there for people that
> > like to poke
On Fri, Nov 20, 2009 at 08:16:40PM +0100, Atle Kristensen wrote:
> what about audioctl, I think that the defaults could be more sane on USB
> audio's?
> (OpenBSD 4.6
>
> play.rate=32000
> play.channels=1
> play.precision=8
this was recently changed in -current to try to set 44.1 kHz stereo 16-b
On Fri, Nov 20, 2009 at 08:28:34AM -0800, Ted Unangst wrote:
> On Nov 20, 2009, at 8:03 AM, Thomas Pfaff wrote:
>
> >On Fri, 20 Nov 2009 15:45:31 +0100
> >Peter Hessler wrote:
> >
> >>mixerctl inputs.master=[0,255]
> >>mixerctl outputs.master=[0,255]
> >
> >Still, is a simpler sysctl interface s
On Fri, Nov 20, 2009 at 05:47:19PM +0100, Thomas Pfaff wrote:
> On Fri, 20 Nov 2009 08:28:34 -0800
> Ted Unangst wrote:
>
> > On Nov 20, 2009, at 8:03 AM, Thomas Pfaff wrote:
> >
> > > On Fri, 20 Nov 2009 15:45:31 +0100
> > > Peter Hessler wrote:
> > >
> > >> mixerctl inputs.master=[0,255]
> >
On Fri, Nov 20, 2009 at 3:19 PM, Jacob Meuser
wrote:
>> If you don't like mixerctl, there's at least a half dozen mixers in
>> ports.
>
> those don't help at all. cmixer is the only one with a chance of
> ever being really helpful, imo. it's the only one that doesn't use
> libossaudio (where the
On Sat, Nov 21, 2009 at 12:28:38AM -0500, Ted Unangst wrote:
> On Fri, Nov 20, 2009 at 3:19 PM, Jacob Meuser
> wrote:
> >> If you don't like mixerctl, there's at least a half dozen mixers in
> >> ports.
> >
> > those don't help at all. cmixer is the only one with a chance of
> > ever being really
On Sat, Nov 21, 2009 at 05:54:21AM +, Jacob Meuser wrote:
> On Sat, Nov 21, 2009 at 12:28:38AM -0500, Ted Unangst wrote:
> > On Fri, Nov 20, 2009 at 3:19 PM, Jacob Meuser
> > wrote:
> > >> If you don't like mixerctl, there's at least a half dozen mixers in
> > >> ports.
> > >
> > > those don't
On Fri, 20 Nov 2009 20:29:08 +0100
Thomas Pfaff wrote:
>
> OK, I got the feedback I wanted. Thanks all. I'll continue
> hating mixerctl(1) and hope something more sane show up in
> the future ;-)
>
That was a bit harsh. I do actually like mixerctl(1) for simpler
devices, like my uaudio(4) hea
Thomas Pfaff wrote:
> What I wanted was a simpler way of controlling the basic features of the
> device.
Yes, but what you failed to comprehend is that these devices are very
complex, it is not easy to "define" the basic features of the device
because there are many devices in different vendor-im
20 matches
Mail list logo
