View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002466 | ardour | features | public | 2008-11-24 14:36 | 2020-04-19 20:13 |
| Reporter | Ethel the Frog | Assigned To | paul | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Product Version | 2.3 | ||||
| Summary | 0002466: cannot connect Alesis Multimix 16 usb2.0 to Ardour | ||||
| Description | Hi. This is likely down to my inexperience. I have a pc with Foxconn m/b and Sempron 3000+, USB2 pci card etc. Running Ubuntu 8.04 Ardour 2.3 (that's what downloaded...) I have an Alesis mixer as above. Works perfectly on XP with Cubase, and as a stand-alone. I am trying to get it to connect to Ardour and/or to Audacity via usb. I think the manual section 10.5.1 about config'ing Linux to connect to another desk is very close to what I need to do, but being not exactly experienced with these matters, would appreciate someone holds my hand... | ||||
| Tags | No tags attached. | ||||
|
|
As you surmised, this issue isn't really related to Ardour. You have to get the desk working with Linux first. In your case isn't the Alesis MultiMix a firewire based product, not USB? In which case your best bet is to try FFADO to see if you can get it running with that, which looking at their site that particular interface is not supported. Not saying that it couldn't work, but saying don't be surprised if it doesn't. If there is a USB version I don't know about, wouldn't be to surprising, you might try using the ALSA usb-audio driver. Namely once you get the device working with Linux, you can probably get it working with Jack, and then it will be available with Ardour. Seablade |
|
|
Seablade, thanks for your time in responding. I do like the OSS community! the mixer is definitely usb2.0 - see http://www.alesis.com/multimix16usb20 for more details. being somewhat "noob" to this I am not at all sure how to get the alsa thing working. I tried googling alsa + alesis + usb a few days back and got nowhere fast. I'll have a try tonight and see how I get on with the usb drivers, but if you have any hints or can give more explicit guidance, it would be much appreciated. btw alesis tech support responded that they have no plans to release drivers for linux so I asked if there was any available data on the form of the data stream from the desk to the usb - I don't know if this is a very dumb question because I haven't worked at this level in a computer for over 20 years and it may be that the world has changed a bit in that time! thx again br Simon (aka Ethel for no very good reason) |
|
|
Simon/Ethel- What you are going to want can be found here. http://alsa-project.org/main/index.php/Matrix:Module-usb-audio#Setting_up_modprobe_and_kmod_support You will want to start just a little above where I linked to the anchor, where there is a box that has the following in it... modprobe snd-usb-audio ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; modprobe snd-seq-oss That is the command to actually load the drivers for USB audio, provided that the device is a class compliant device, which most (But not all) are. Reading from there on should walk you through how to load it, and ensure it is loaded automatically. I would load it once first, and then check to make sure that it is working by typing the following... cat /proc/asound/devices Where you SHOULD see another device, or possibly multiple, in this list for the Alesis now. Once you confirm that, you can follow through with the rest of that document to cause that to be loaded on a regular basis. You should also at this point be able to select the device to use with Jack, which will in turn automatically be used by Ardour since it uses Jack itself. Seablade |
|
|
ok, here's where we are - told you I was inexperienced... First. I entered this in terminal to get a baseline. simon@simon-desktop:~$ cat /proc/asound/devices 0: [ 0] : control 1: : sequencer 16: [ 0- 0]: digital audio playback 17: [ 0- 1]: digital audio playback 18: [ 0- 2]: digital audio playback 24: [ 0- 0]: digital audio capture 27: [ 0- 3]: digital audio capture 33: : timer I then went to the page and copied the commands modprobe snd-usb-audio ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; modprobe snd-seq-oss into terminal, and it said I was not authorised... so I typed sudo, then pasted the commands again, and it asked for my password several times - I'm not sure this worked. I then tried the cat /proc etc command and I got the same answer. So I tried plugging the mixer in just to see... nothing. then I tried the Alsamixer command as suggested and it shows the pci soundcard as it did before. so then I tried to create a file in the /etc/?modutils/ directory (eg. /etc/?modutils/?alsa) (only I called my file alsascript) but I don't have permissions to write to my own system. So I created the file in my home folder, and made it executable, but it still won't let me copy it to the right directory, so I am now trying to learn about file permissions. and so I haven't run the update-modules command yet, and, not surprisingly (at least to me) not working! questions a) am I on the right track b) have I done something dumb? c) what do I do next? all guidance welcome. I knew it would be a steep learning curve! br Simon |
|
|
i may be missing something, but i am fairly certain that there is no audio support for any USB 2.0 devices on linux at this time. don't take my word for it - search around. but i do recall this being an issue at some point in the not too recent past. drivers for devices on linux generally do not come from manufacturers. all USB1.0 audio devices are supported by a single class driver that works for all class compliant hardware. OS X works this way as well. If i am correct, nobody has written a USB2.0 class driver yet. i don't know if one is underway. |
|
|
actually, at this point in time, it appears there is no such thing as a class compliant USB2.0 device. every such device is a proprietary design and requires a dedicated driver. this in turn requires that the manufacturer either provide it or that they make available information so that the linux community can create a driver. you would need to ask alesis if they would be willing to do this. I would suggest that they read this: https://www.linuxfoundation.org/en/Linux_Device_Driver_Model for more information on how this process works. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-11-24 14:36 | Ethel the Frog | New Issue | |
| 2008-11-24 18:07 | seablade | Note Added: 0005349 | |
| 2008-11-24 18:07 | seablade | Status | new => feedback |
| 2008-11-25 14:30 | Ethel the Frog | Note Added: 0005368 | |
| 2008-11-25 16:20 | seablade | Note Added: 0005369 | |
| 2008-11-27 15:46 | Ethel the Frog | Note Added: 0005387 | |
| 2008-11-28 08:28 | paul | Note Added: 0005389 | |
| 2008-11-28 08:48 | paul | Note Added: 0005390 | |
| 2008-11-28 08:48 | paul | cost | => 0.00 |
| 2008-11-28 08:48 | paul | Status | feedback => resolved |
| 2008-11-28 08:48 | paul | Resolution | open => not fixable |
| 2008-11-28 08:48 | paul | Assigned To | => paul |
| 2009-07-10 05:29 | mitshko | Tag Attached: Hi | |
| 2009-07-10 05:29 | mitshko | Tag Detached: Hi | |
| 2020-04-19 20:13 | system | Note Added: 0021825 | |
| 2020-04-19 20:13 | system | Status | resolved => closed |
