Having trouble getting an M-Audio Transit working

synthead · 2007-09-04 06:30:43

I plug it in, lsusb recognizes it as Midiman. Normal, but when I sudo alsaconf, it doesn't detect the card. It's making that classic faint static sound that means that drivers for it hasn't been loaded yet.

What can I do to get it to work?

newgargamel · 2007-09-04 15:17:04

create or edit the following files:

.asoundrc

pcm.!default {
  type hw
  card 1
 }
ctl.!default {
  type hw
  card 1
}

modprobe.conf

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-hda-intel
options snd-hda-intel index=0
alias sound-slot-0 snd-hda-intel
alias snd-card-1 snd-usb-audio
options snd-usb-audio index=1
alias sound-slot-1 snd-usb-audio

Last edited by newgargamel (2007-09-04 17:33:18)

synthead · 2007-09-10 07:05:12

Hmm ... turns out that some M-Audio cards need to have proprietary firmware uploaded to them on every hotplug. Soooooo ... I made a package for it and put it in the AUR

http://aur.archlinux.org/packages.php?d … s=0&SeB=nd

redbit · 2008-05-26 17:51:20

Hi there,

my M-Audio Transit stopped working. I think it has to do with the kernel upgrade to 2.6.25. Can anybody confirm this and has a solution for this? I wan't my Transit back *crying*

Greetings,
redbit

Army · 2008-11-22 11:54:36

Do you guys have your m-audio transit working? I gut that for my birthday and I really like it, but would love to use it with Archlinux! The package in the AUR doesn't work for me, already left a comment.

redbit · 2008-11-22 13:00:40

That package doesn't work for me, too. So I always load the firmware by hand.

Army · 2008-11-22 17:11:13

Stupid question maybe, but how to do that? I never had to do such stuff. Could you give me a step by step explanation, what needs to be done, to make (Arch)Linux use the Transit?

redbit · 2008-11-22 17:45:09

just plug in the transit device. Then note the Bus ID und Device ID by using the command lsusb.
Now you can flash the firmware to the device with the following command as root:
madfuload -3 -f path/to/firmware -D /dev/bus/usb/BusID/DeviceID

Unfortunately, i cannot remember where i got the firmware from?!? ... .... Ah, now i can remember. You can get it from your driver CD. The file as called ma006100.bin .

The next step is to redirect the sound output to the transit device. In KDE4, you can simply choose the order of the sound devices in system controls. Don't know which desktop environment you use.

By the way, happy birthday

[Edit] ok, i've forgotten something: how to get the madfuload executable without this package. I only found the source code of madfuload on sourceforge. So, you will have to compile it yourself.

Or if you like, i can upload the madfuload executable to my webspace.

Last edited by redbit (2008-11-22 18:19:06)

Army · 2008-11-22 19:38:38

Thanks man, I would kiss you if I were 1. gay and 2. in your area But at this moment I don't have the CD by hand, so I'll try it tomorrow. But seems like it is gonna work

I didn't have my birthday yet, it was just a present of my uncle, who goes to America on Monday and he wanted to see my face himself, when I open the present

You don't need to upload it, now I simply changed the configure script, so it doesn't check the version number of udev. But still, where has udevinfo gone?! I guess the package works

If there are problems left, like autoload of modules (I guess that won't work here, also doesn't with my brother's Edirol UA25, which works out of the box, but snd-usb-audio isn't loaded automatically)

Ah, one question left, sorry: Do you need the stuff in asoundrc and modprobe.conf which newgargamel posted here?

edit:

Oh, I found something:

$  pacman -Ql madfuload 
madfuload /etc/
madfuload /etc/udev/
madfuload /etc/udev/rules.d/
madfuload /etc/udev/rules.d/42-madfuload.rules
madfuload /usr/
madfuload /usr/sbin/
madfuload /usr/sbin/madfuload
madfuload /usr/share/
madfuload /usr/share/usb/
madfuload /usr/share/usb/maudio/
madfuload /usr/share/usb/maudio/ma003101.bin
madfuload /usr/share/usb/maudio/ma004103.bin
madfuload /usr/share/usb/maudio/ma005101.bin
madfuload /usr/share/usb/maudio/ma006100.bin
madfuload /usr/share/usb/maudio/ma008100.bin

Are these the right firmwares?! Well, I just tried it out:

$  lsusb
Bus 003 Device 001: ID 1d6b:0002  
Bus 004 Device 002: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Bus 004 Device 001: ID 1d6b:0001  
Bus 002 Device 006: ID 0763:2806 Midiman 
Bus 002 Device 002: ID 0bc7:0006 X10 Wireless Technology, Inc. 
Bus 002 Device 001: ID 1d6b:0001  
Bus 001 Device 001: ID 1d6b:0001

$  sudo madfuload -3 -f /usr/share/usb/maudio/ma006100.bin -D /dev/bus/usb/002/006 
cannot reset device: (19) No such device

Argh, damn!

Last edited by Army (2008-11-22 19:49:59)

redbit · 2008-11-22 20:33:23

Yes the firmware is included in this package. The correct file is m006100.bin.

I didn't change anything in asoundrc or modprobe.conf.

It was quite a while ago, when i used the transit the last time. Strangely i get this error too when loading the firmware. It didn't appear before. Nevertheless the usb device works. You can test it by catting the file /proc/asound/cards.

If it looks similiar to this it should work:

[root@m67n madfuload]# cat /proc/asound/cards
 0 [I82801DBICH4   ]: ICH4 - Intel 82801DB-ICH4
                      Intel 82801DB-ICH4 with STAC9750,51 at irq 4
 1 [Modem          ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
                      Intel 82801DB-ICH4 Modem at irq 4
 2 [pcsp           ]: PC-Speaker - pcsp
                      Internal PC-Speaker at port 0x61
 3 [USB            ]: USB-Audio - Transit USB
                      M-Audio Transit USB at usb-0000:00:1d.0-2, full speed

PS: point 2 nearly fulfilled. Living in Bavaria ;-)

Last edited by redbit (2008-11-22 20:38:18)

Army · 2008-11-22 21:52:44

$  cat /proc/asound/cards
 0 [I82801DBICH4   ]: ICH4 - Intel 82801DB-ICH4
                      Intel 82801DB-ICH4 with ALC655 at irq 10
 1 [USB            ]: USB-Audio - Transit USB
                      M-Audio Transit USB at usb-0000:00:1d.1-1, full speed

Damn, we almost have the same soundcards (I don't allow the pcsp and modem to be loaded)

Now it only has to work! I tried to play a soundfile over this soundcard, but didn't hear anything. But I guess I have to do a little more research

edit: Bayern?!? Oh, joa, ich Ulm Trotzdem, Punkt 1 ist nicht erfüllbar, ätsch

Last edited by Army (2008-11-22 21:53:54)

redbit · 2008-11-22 22:18:07

Damn, we almost have the same soundcards smile (I don't allow the pcsp and modem to be loaded)

May be, that's why we both had the wish for a new soundcard ;-)

The output volume levels, right after loading the firmware, are so low, that you can't hear anything. You have to adjust it by alsamixer -c 1. Try pushing it nearly to the top.
And you have to somehow redirect the sound to the usb sound card, but that depends on what desktop environment you are using (you were using KDEmod??? if I remember correctly).
Otherwise there was a command to redirect all sound output to an given sound card, but i can't remember. May be it comes to my mind again :-)

PS: Bestätige, Punkt 1 trifft hier ebenfalls nicht zu! :-)

Last edited by redbit (2008-11-22 22:18:53)

Army · 2008-11-22 23:00:52

I already used alsamixer -c 1 and pushed them to the top, they were down on the floor as you said. When I start playback, I hear a short pulse (nen Knackser halt) and afterwards just silence.

Right now I'm on XFCE, KDE isn't mine any more, v3 isn't maintained any more and my machine is too weak for v4.

Well, now it's midnight here, I guess I'll stop this now and do some research tomorrow.

Does anybody know, if this device works with oss4? Would love to use it with that, because I hate alsa Although I depend on it, damn ..

Army · 2008-11-23 01:41:59

Well ... I couldn't sleep because of this and had to give another try Always the same with this linux thing, when you discover something new ...

Now I think I got it working perfectly, it works as normal ALSA device, I'm listening to music via mpd right now with the Transit and Jack also seems to work quite well, did some test recordings. I also installed oss4 for a short moment and it's also being autodetected. ossinfo shows the device, osstest plays the testsound in the right order and .. well, in the end it didn't work anymore, don't know what I've done wrong, but as I told before, using linux means to be dependend on alsa in some way, really sad. But still, I'm pretty satisfied with this little device I'm really thinking about completely deactivating my internal card now.. We'll see

redbit, I dank dir no recht gschmoideg, dass d ma ghoifn host (das verstehn bestimmt nichtmal alle Deutschen hier )

Would be cool to have a package to make it work simply by plugin it in. But as long as there is no windows or apple guy behind me watching me hacking the bash and laughing, it's ok for me

redbit · 2008-11-23 08:54:52

Glad to hear that it works now partly.

Koa Problem, gfrei mi ja wenn i hoifa ko.

redbit

Last edited by redbit (2008-11-23 08:55:16)

redbit · 2008-12-07 07:44:40

Hey Army,
did you get it working with oss already?

Army · 2008-12-07 09:23:26

It works out of the box, but there is a strong clipping in the sound, which is very dangerous for speakers. Do you have an idea what the reason for that could be and how I could fix this? Seems like the input gain is a little bit too high...

redbit · 2008-12-07 09:55:55

hmm that's strange. osstest gives me some error when testing the transit device.

sorry, i've no solution for the clipping problem. But we will see, if i have this problem too, when i manage to get it working with oss. ;-)

Last edited by redbit (2008-12-07 09:58:45)

synthead · 2008-12-30 19:36:11

Hey, I own the madfuload package and want to fix it. Recently though, when I plug my Transit into my computer, nothing at all shows up. lsusb doesn't report anything, and nothing new appears in /dev. What is the deal? :S

redbit · 2008-12-30 21:04:52

That sounds strange.
lsusb is showing me the Transit correctly as always before.

Army · 2008-12-30 22:11:39

Same here, still everything works as it should, except of automatic loading of the firmware via HAL, but that really doesn't matter at all Would be cool if you could fix it ... Do you have a chance to try our transit on another pc? Maybe it's broken?!

synthead · 2008-12-31 12:49:51

So lsusb reported the transit on my laptop, but I'm in a real hairball. I'm fighting udev to the death ... I made a thread about it

http://bbs.archlinux.org/viewtopic.php?id=62072

It SUCKS. It's 5AM and I have been trying to get this to work for FIVE HOURS. I'm going to bed for now ...

Army · 2009-01-03 14:05:00

Your command cannot work here! The line I needed a few moments ago to make it run was

madfuload -3 -f /usr/share/usb/maudio/ma006100.bin -D /dev/bus/usb/002/003

and your solution with awk etc is

madfuload -3 -f /usr/share/usb/maudio/ma006100.bin -D /dev/bus/usb/001/$(lsusb | awk -F':| ' '/763:2806/{print $4}')

See? I have .../usb/002/... and your command has .../usb/001/... fix, so it only works on special usb ports, but not on all of them.
I hope the solution is that simple!!!

edit: My output of lsusb is

Bus 004 Device 001: ID 1d6b:0002  
Bus 003 Device 003: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Bus 003 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
Bus 003 Device 001: ID 1d6b:0001  
Bus 002 Device 004: ID 0763:2006 Midiman 
Bus 002 Device 002: ID 0bc7:0006 X10 Wireless Technology, Inc. 
Bus 002 Device 001: ID 1d6b:0001  
Bus 001 Device 001: ID 1d6b:0001

just for info

Last edited by Army (2009-01-03 14:08:16)

synthead · 2009-01-27 11:35:41

Yeah ... I realized that, sorry. BUT! I figured it out and made a new package for madfuload that works 100%! That means that the new udev rules work, so just plug it in and it comes to life. Go try it, it's in the AUR.

http://aur.archlinux.org/packages.php?ID=12812

Last edited by synthead (2009-01-27 11:37:14)

greenfish · 2009-08-25 20:00:13

synthead wrote:

Yeah ... I realized that, sorry. BUT! I figured it out and made a new package for madfuload that works 100%! That means that the new udev rules work, so just plug it in and it comes to life. Go try it, it's in the AUR.
http://aur.archlinux.org/packages.php?ID=12812

First of all thanks for your contribution sir!

I bought the transit as my first and last m-audio product. The player barely works at all in vista/windows7 and sometimes the system disables the firmware so i have to manually load it in windows. Their forum/site is beyond pathetic in terms of support, they've been promising to fix all the 64 bit driver errors since 2007 (not sure about the date).

Anyways i compiled madfu from source (aur) plugged in the audio transit only to be greeted with:

hub 7-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 7-1: USB disconnect, address 4
usb 7-1: new full speed USB device using uhci_hcd and address 5
usb 7-1: device descriptor read/64, error -71
hub 7-0:1.0: unable to enumerate USB device on port 1
CE: hpet increasing min_delta_ns to 22500 nsec
usb 7-1: new full speed USB device using uhci_hcd and address 6
usb 7-1: configuration #1 chosen from 1 choice
madfuload[2456]: segfault at d4f1347a ip 00007fbdd4e41461 sp 00007fffe9b7bff0 error 4 in libc-2.10.1.so[7fbdd4dfc000+149000]

lsusb
Bus 007 Device 006: ID 0763:2806 Midiman M-Audio Transit DFU
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05ca:183d Ricoh Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 002: ID 044e:3017 Alps Electric Co., Ltd
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Repository     : core
Name           : glibc
Version        : 2.10.1-4
URL            : http://www.gnu.org/software/libc
Licenses       : GPL  LGPL
Groups         : base
Provides       : None
Depends On     : kernel-headers>=2.6.30.5  tzdata
Optional Deps  : None
Conflicts With : None
Replaces       : glibc-xen
Download Size  : 12559.29 K
Installed Size : 35776.00 K
Packager       : Jan de Groot <jgc@archlinux.org>
Architecture   : x86_64
Build Date     : Sun 23 Aug 2009 04:24:37 PM CEST
MD5 Sum        : c9ab969684213e48b8d0b80ae18a89cd
Description    : GNU C Library

Just updated arch with pacman -Syu (still the same errors)

Running alsamixer -c 2 sure enough shows my audio device, but only 1 audio bar and there's no sound from my headphones except for the weird noise which tells me the firmware isn't loaded.

Any ideas?

Thank You

EDIT: been reading your aur entry, manually loading the firmware with madfu also results in a segmentation fault

Last edited by greenfish (2009-08-25 20:05:51)

Arch Linux

#1 2007-09-04 06:30:43

Having trouble getting an M-Audio Transit working

#2 2007-09-04 15:17:04

Re: Having trouble getting an M-Audio Transit working

#3 2007-09-10 07:05:12

Re: Having trouble getting an M-Audio Transit working

#4 2008-05-26 17:51:20

Re: Having trouble getting an M-Audio Transit working

#5 2008-11-22 11:54:36

Re: Having trouble getting an M-Audio Transit working

#6 2008-11-22 13:00:40

Re: Having trouble getting an M-Audio Transit working

#7 2008-11-22 17:11:13

Re: Having trouble getting an M-Audio Transit working

#8 2008-11-22 17:45:09

Re: Having trouble getting an M-Audio Transit working

#9 2008-11-22 19:38:38

Re: Having trouble getting an M-Audio Transit working

#10 2008-11-22 20:33:23

Re: Having trouble getting an M-Audio Transit working

#11 2008-11-22 21:52:44

Re: Having trouble getting an M-Audio Transit working

#12 2008-11-22 22:18:07

Re: Having trouble getting an M-Audio Transit working

#13 2008-11-22 23:00:52

Re: Having trouble getting an M-Audio Transit working

#14 2008-11-23 01:41:59

Re: Having trouble getting an M-Audio Transit working

#15 2008-11-23 08:54:52

Re: Having trouble getting an M-Audio Transit working

#16 2008-12-07 07:44:40

Re: Having trouble getting an M-Audio Transit working

#17 2008-12-07 09:23:26

Re: Having trouble getting an M-Audio Transit working

#18 2008-12-07 09:55:55

Re: Having trouble getting an M-Audio Transit working

#19 2008-12-30 19:36:11

Re: Having trouble getting an M-Audio Transit working

#20 2008-12-30 21:04:52

Re: Having trouble getting an M-Audio Transit working

#21 2008-12-30 22:11:39

Re: Having trouble getting an M-Audio Transit working

#22 2008-12-31 12:49:51

Re: Having trouble getting an M-Audio Transit working

#23 2009-01-03 14:05:00

Re: Having trouble getting an M-Audio Transit working

#24 2009-01-27 11:35:41

Re: Having trouble getting an M-Audio Transit working

#25 2009-08-25 20:00:13

Re: Having trouble getting an M-Audio Transit working

Board footer