Bug 520495

What's the output of "pacmd ls" on your system?

Created attachment 359850 [details]
'pacmd ls' output

That's really not useful, your "FastTrack Pro" device wasn't plugged in when you ran the command.

Please test again with the latest gnome-media-2.27.91, and attach the output of "pacmd ls" with the device plugged in if you can reproduce.

Created attachment 361315 [details]
pacmd ls output

Apologies for the confusion .....

I updated my system to the 2.27.91-1 gnome-media pkgs from updates-testing and was still able to reproduce.  Attaching updated 'pacmd ls' output.

PulseAudio says it doesn't have any inputs:
	profiles:
		output-analog-stereo: Output Analog Stereo (priority 51000)
		output-iec958-stereo: Output Digital Stereo (IEC958) (priority 50500)
		off: Off (priority 0)
	active profile: <output-analog-stereo>
	sinks:
		alsa_output.usb_device_763_2012_noserial_if0_sound_card_0/#1: FastTrack_Pro
	sources:
		alsa_output.usb_device_763_2012_noserial_if0_sound_card_0.monitor/#2: Monitor of FastTrack_Pro

Can you please launch alsa-info and upload the output?

Created attachment 361324 [details]
alsa-info output

Most likely the driver lacks a high level device string for recording stereo or mono.

Does the following work?

aplay -D front:0 -f S16_LE -r 44100 -c2 > /dev/null

(try replacing the rate by 48000, and play around with the number of channels, i.e. -c2)

PA requires that those high-level device strings are defined. If they aren't for your device and the device is not mono, or stereo but multichannel PA cannot make use of this since we wouldn't know the channel map to use.

When I select the FastTrack Pro as the output device in gnome-volume-control and use:

  aplay $wavfile

..it plays properly via the FastTrack outputs.

When I use the cmd from comment 7 it plays the audio via my laptops internal speakers.  However if I change the cmd to front:1

  aplay -D front:1 -f S16_LE -r 44100 -c2 > /dev/null $wavfile

..it plays properly via the FastTrack outputs.  This behavior doesn't change based on which output I have selected in gnome-volume-control.

sorry, i am an idiot. Wanted to write "arecord" not "aplay" there. Sorry for the confusion

OK that doesn't work.  When I run:

  arecord -D front:0 -f S16_LE -r 44100 -c2 foo.wav

..it records properly via the laptop's internal mic.  When I run:

  arecord -D front:1 -f S16_LE -r 44100 -c2 foo.wav

..I get the following error:

  arecord: main:608: audio open error: No such file or directory

Same error regardless of the # of channels and/or rate.

When I run the same cmd w/ my MobilePRE USB connected it does record properly.  So it seems you're right in that the driver is missing some definition(s) for the FastTrack Pro.

/me wonders what kind of alsa-magic-foo audacity uses to be able to record from the FT Pro

So yepp, PA doesn't know how to open the device, because hw:1 cannot be opened for 1 or 2 channels (where the channel map is clear), front:1 cannot either, and the multichannel device strings probably not either.

What is missing here is some kind of definition which would allow PA to open the device with some kind of sane channel map.

How many channels does your device have, and how are they labelled?

Also, is this one of those ice1712 beasts?

> How many channels does your device have, and how are they labelled?

According to the M-Audio site[1] it's 4x4, plus spdif i/o and midi i/o.  Here's a breakdown of what it has for inputs/output and their associated labels ...

On the front there's 2 combined XLR/TRS inputs:
- Mic/Inst 1
- Mic/Inst 2

..plus a headphone jack.

On the back there's:
- Midi In/Out
- S/PDIF In/Out (2 RCA/coax jacks)
- Output 1-4 (4 RCA jacks)
- TRS Output 1-2 (2 1/4" jacks)
- Inserts 1-2 (2 1/4" jacks)

According to the M-Audio site[1] the "Inserts" jacks are for outboard effects.  


> Also, is this one of those ice1712 beasts?

I don't believe so.  It's not listed on the alsa wiki ice1712 page, and it uses the snd_usb_audio module, so I afaict it's not ice1712.



[1] http://www.m-audio.com/products/en_us/FastTrackPro.html

Hmmm, could you please try this:

Edit /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf and coment all "direction = output" lines you can find, then restart PA. Does that change anything?

Currently, as a simple optimization we only look for mono or stereo recording and don't bother with multichannel recording. Since you card seems to be a semi-pro card of some kind it might make sense to check this.

[dave@ ~]$ ls /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf
ls: cannot access /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf: No such file or directory
[dave@ ~]$ ls /usr/share/pulseaudio/
ls: cannot access /usr/share/pulseaudio/: No such file or directory


Am I missing something?  I checked w/ yum to see whatprovides the default.conf but didn't find anything.

Uh, I was talking of Rawhide. This file does not exist on F11. 

Sorry, but your problem can not be fixed on F11.

I'll be moving this system to F12 shortly so I'll try your suggestion from comment 13 once upgraded.

I've had a chance to test this under (pre-)F12.  Commenting out all of the "direction = output" lines does change the behavior slightly, but it still doesn't appear as an available input device.

After making the suggested changes and restarting PA the FastTrack now lists an additional profile under Sound Preferences -> Hardware.  Prior to making the change the only option under the profile drop-down was "Analog Stereo Output" and the device section showed "1 output".  After the change "Digital Stereo Duplex (IEC958)" now appears in the drop-down.  When it's selected it still shows as only "1 output" under the devices section.  And it's still not listed under the Input tab.

So the analog inputs still aren't being recognized at all, and even now that the digital inputs are being seen in some capacity they're still not available to use for recording.

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I experience the same problems with the M-audio Fasttrack pro interface. Has there been any progress on this? I'd be happy to provide more information.

Upstream PA now has a profile that specifically covers this sound card.