Bug 520495 - M-Audio Fast Track Pro needs special profiles
Summary: M-Audio Fast Track Pro needs special profiles
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 656998
TreeView+ depends on / blocked
 
Reported: 2009-08-31 19:11 UTC by Dave Maley
Modified: 2010-11-24 16:50 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
: 656998 (view as bug list)
Environment:
Last Closed: 2010-01-06 18:29:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
'pacmd ls' output (15.17 KB, text/plain)
2009-09-04 21:23 UTC, Dave Maley
no flags Details
pacmd ls output (21.15 KB, text/plain)
2009-09-16 16:18 UTC, Dave Maley
no flags Details
alsa-info output (26.97 KB, text/plain)
2009-09-16 16:54 UTC, Dave Maley
no flags Details

Description Dave Maley 2009-08-31 19:11:57 UTC
Description of problem:
I'm unable to set my FastTrack Pro as the record device used by PulseAudio.  When I go to Sound Preferences (gnome-volume-control) the FastTrack isn't listed as an available input device.  It does appear under output devices.

For apps which use alsa directly (eg. audacity) the FastTrack is available to select as a recording device, and likely more important works properly when used to record.


Version-Release number of selected component (if applicable):
gnome-media-2.26.0-6.fc11.x86_64


How reproducible:
100%


Steps to Reproduce:
1. connect FastTrack Pro
2. System -> Preferences -> Sound -> Input

  
Actual results:
FastTrack Pro not available to select as input device


Expected results:
FastTrack Pro be listed as available record device


Additional info:
- According to the unofficial alsa wiki the FastTrack pro should should support recording using usb-audio module:
http://alsa.opensrc.org/index.php/M-Audio_FastTrack_Pro

- this isn't a fundamental problem w/ PA and snd_usb_audio, it's specific to the FT Pro.  My M-Audio USB Pre does appear as a input device when connected.

Comment 1 Bastien Nocera 2009-09-03 09:31:01 UTC
What's the output of "pacmd ls" on your system?

Comment 2 Dave Maley 2009-09-04 21:23:42 UTC
Created attachment 359850 [details]
'pacmd ls' output

Comment 3 Bastien Nocera 2009-09-16 15:52:32 UTC
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.

Comment 4 Dave Maley 2009-09-16 16:18:13 UTC
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.

Comment 5 Bastien Nocera 2009-09-16 16:38:29 UTC
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?

Comment 6 Dave Maley 2009-09-16 16:54:22 UTC
Created attachment 361324 [details]
alsa-info output

Comment 7 Lennart Poettering 2009-09-16 18:48:47 UTC
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.

Comment 8 Dave Maley 2009-09-16 19:09:37 UTC
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.

Comment 9 Lennart Poettering 2009-09-16 21:35:38 UTC
sorry, i am an idiot. Wanted to write "arecord" not "aplay" there. Sorry for the confusion

Comment 10 Dave Maley 2009-09-16 22:22:38 UTC
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

Comment 11 Lennart Poettering 2009-09-17 02:49:56 UTC
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?

Comment 12 Dave Maley 2009-09-17 19:30:08 UTC
> 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

Comment 13 Lennart Poettering 2009-09-29 04:40:37 UTC
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.

Comment 14 Dave Maley 2009-10-05 20:16:10 UTC
[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.

Comment 15 Lennart Poettering 2009-10-06 12:50:01 UTC
Uh, I was talking of Rawhide. This file does not exist on F11. 

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

Comment 16 Dave Maley 2009-10-06 15:32:59 UTC
I'll be moving this system to F12 shortly so I'll try your suggestion from comment 13 once upgraded.

Comment 17 Dave Maley 2009-10-30 19:31:10 UTC
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.

Comment 18 Bug Zapper 2009-11-16 11:52:27 UTC
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

Comment 19 Anonymous account 2009-12-23 18:47:57 UTC
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.

Comment 20 Lennart Poettering 2010-01-06 18:29:40 UTC
Upstream PA now has a profile that specifically covers this sound card.


Note You need to log in before you can comment on or make changes to this bug.