Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Owen Williams <owilliams@mixxx.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Regression in Traktor Audio10 driver (snd-usb-audio) mixer flags
Date: Sun, 10 Jan 2016 15:20:17 -0500	[thread overview]
Message-ID: <1452457217.18937.9.camel@mixxx.org> (raw)
In-Reply-To: <s5h37u78ah9.wl-tiwai@suse.de>

Unfortunately I can't narrow the problem down more specifically than
the changes from Ubuntu-3.18.0-14.14 to Ubuntu-3.19.0-1.1.  If I try to
git bisect between those, I end up with commits that don't have the
proper debian packaging information so I can't build packages.  Any
ideas?  I see a bunch of merges for the sound subsystem in the 3.19
branch so if can figure out how to build debs I bet the problem is in
there.

On Sat, 2016-01-09 at 08:42 +0100, Takashi Iwai wrote:
> On Fri, 08 Jan 2016 15:18:58 +0100,
> Owen Williams wrote:
> > 
> > Sorry to bump my own thread, but I don't know how else to report
> > bugs to
> > ALSA (I think the bug tracker was abandoned a while back?).  I'm
> > willing
> > to do work to diagnose and fix this problem (I'm comfortable
> > building
> > kernels, doing git bisect, using gdb, etc) but I need some guidance
> > about how to start.
> 
> If the problem is easily reproducible, could you try bisection?
> This is the best way to spot out the cause.
> 
> 
> thanks,
> 
> Takashi
> 
> > On Thu, 2015-12-31 at 13:26 -0500, Owen Williams wrote:
> > > Sometime between kernels 3.13 (ubuntu 14.04) and 3.19 (15.04)
> > > there was
> > > a regression that caused the mixer elements of the Traktor
> > > Audio10
> > > driver to stop responding to changes to True.  I have an older
> > > machine
> > > still running 14.04, and if I open alsamixer I can see and
> > > interact
> > > with the 8 basic boolean switches:
> > > 
> > > numid=3,iface=MIXER,name='Direct Thru Channel A'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=4,iface=MIXER,name='Direct Thru Channel B'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=5,iface=MIXER,name='Direct Thru Channel C'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=6,iface=MIXER,name='Direct Thru Channel D'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=7,iface=MIXER,name='Phono Input Channel A'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=8,iface=MIXER,name='Phono Input Channel B'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=9,iface=MIXER,name='Phono Input Channel C'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > numid=10,iface=MIXER,name='Phono Input Channel D'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > 
> > > 
> > > or I can use amixer:
> > > amixer -c T10 cset numid=8 on
> > > 
> > > 
> > > however on my newer machine, with ubuntu 15.04 and 15.10, I am
> > > unable
> > > to change the values to true.  I am a member of the audio group
> > > and I
> > > have also tried with sudo, but when I try to set the value on
> > > nothing
> > > happens:
> > > 
> > > $ amixer -c T10 cset numid=8 on
> > > numid=8,iface=MIXER,name='Phono Input Channel B'
> > >   ; type=BOOLEAN,access=rw------,values=1
> > >   : values=off
> > > 
> > > The fun part is, if I connect the card to my mac I can set
> > > startup
> > > conditions for these flags.  I can set them to true, and when I
> > > connect
> > > to my linux machines the flags start up as true.  And then, even
> > > on the
> > > newer kernel, I can turn them off!  But I can't turn them back on
> > > again.
> > > 
> > > This sound card is the one I'd like to recommend officially for
> > > the
> > > Mixxx DJ project so I'd really like to get to the bottom of this
> > > issue.
> > > 
> > > 
> > > thanks,
> > > Owen Williams
> > > 
> > > A Lead Developer, Mixxx.org
> > 
> > 
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > 
> 
> 

  reply	other threads:[~2016-01-10 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 18:26 Regression in Traktor Audio10 driver (snd-usb-audio) mixer flags Owen Williams
2016-01-08 14:18 ` Owen Williams
2016-01-09  7:42   ` Takashi Iwai
2016-01-10 20:20     ` Owen Williams [this message]
2016-01-12  6:22       ` Takashi Iwai
2016-01-12 21:24         ` Owen Williams
2016-01-12 22:17           ` Takashi Iwai
2016-01-13  4:23             ` Owen Williams
2016-01-13  6:39               ` Takashi Iwai
2016-01-13 14:58                 ` Owen Williams
2016-01-13 15:03                   ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1452457217.18937.9.camel@mixxx.org \
    --to=owilliams@mixxx.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox