Mixer on Rane Serato Live does not work

Bug #179966 reported by LCID Fire
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Wishlist
Unassigned

Bug Description

On my USB-Audio device I can both record and play music - but the mixer is not working. When I attemt to open amixer oder alsamixer I get the output:
snd_mixer_load: Invalid argument
So it seems like something about the mixer does not suit alsa. Is there a way to get a more decent error message?

Revision history for this message
LCID Fire (lcid-fire) wrote :
Revision history for this message
LCID Fire (lcid-fire) wrote :
Revision history for this message
LCID Fire (lcid-fire) wrote :
Revision history for this message
LCID Fire (lcid-fire) wrote :

Seems to be related to this -5 error

Revision history for this message
LCID Fire (lcid-fire) wrote :
Revision history for this message
Murat Gunes (mgunes) wrote :

Thanks for your report. Are you sure that your device has an internal mixer? Some audio interfaces only have inputs and outputs, but no way to mix the signals internally, so mixing can only be done in software.

Changed in alsa-driver:
status: New → Incomplete
Revision history for this message
LCID Fire (lcid-fire) wrote :

Did you have a look at the amixer output? It has a mixer - but it seems like alsa has some kind of problem with it.
I got just told that it might work with oss wrapper so I'll try this next.

Revision history for this message
LCID Fire (lcid-fire) wrote :

Oss wrapper doesn't work either - but at least the oss mixer is accessible. It has a pcm channel - which doesn't seem to be modifieable.

Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha 6?

The necessary information also includes the output from `lsusb -v'

Revision history for this message
LCID Fire (lcid-fire) wrote :

The point is:
1. I have a alsa patch pending which implements a device specific switch for the device.
2. I'm not sure whether the device has a mixer. I'd need some help from a usb/alsa developer to sort this out.
3. Regardless whether a real mixer is present - I need the mixer instance for the switch (see 1).

For all I'd need some alsa developer - but it seems like nobody cares *grrr*

Revision history for this message
Daniel T Chen (crimsun) wrote :

It's not that "nobody cares" - Clemens is fairly busy, and I personally am very busy, so I have extremely limited resources (i.e., time - until early December) to address this issue. That said, I do follow alsa-devel, so I'll take a look over the coming veterans' holiday.

Changed in alsa-driver:
assignee: nobody → ubuntu-audio
importance: Undecided → Wishlist
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
assignee: Ubuntu Audio Team (ubuntu-audio) → nobody
Revision history for this message
penalvch (penalvch) wrote :

LCID Fire, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? With your USB device plugged in, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.