Skip to contentSkip to conversation

Omnistudio USB

DISCUSSION Rusty Phillips 2 participants 8 messages Jan 12, 2005 – Jan 14, 2005

lore
Share & tools
lore
#0 lore raw

Is anyone working on this, or has anyone gotten it working? I recently purchased one, and have been trying to find out anything I can about getting it to work. So far all I've gotten is playback on two channels at 48Khz with alsa (from the 2.6.10 kernel as well as from alsa CVS).

Anyway, if anyone can point me in the right direction - what to look for, where to go, who to talk to - anything, really - I would really appreciate it. I can provide all the wonderful information that the device produces if it'll help.

Thank you for your replies.

Sincerely,
Rusty Phillips

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

#1 lore raw
Quoted 4 lines · Rusty Phillips

I recently purchased one, and have been trying to find out anything I can about getting it to work. So far all I've gotten is playback on two channels at 48Khz with alsa (from the 2.6.10 kernel as well as from alsa CVS).

What are the contents of /proc/asound/cardX/stream0? Is there a second output device in the output of "aplay -l"?

Clemens

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

#2 lore raw
Quoted 6 lines · Clemens Ladisch
Quoted 4 lines · Rusty Phillips

I recently purchased one, and have been trying to find out anything I can about getting it to work. So far all I've gotten is playback on two channels at 48Khz with alsa (from the 2.6.10 kernel as well as from alsa CVS).

Quoted 6 lines

What are the contents of /proc/asound/cardX/stream0? Is there a second output device in the output of "aplay -l"?

Clemens

Oh...sorry to mislead you there. All four channels "work." The problem is that recording doesn't at all, and neither do higher bitrates.

First, aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 0: USB [OmniStudio USB], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: USB [OmniStudio USB], device 1: USB Audio [USB Audio #1]
Subdevices: 1/1
Subdevice #0: subdevice #0

Quoted 1 line

From my asoundrc:

pcm.omni1 {
type hw
card 0
device 0
}
ctl.omni1 {
type hw
card 0
}
pcm.omni2 {
type hw
card 0
device 1
}
ctl.omni2 {
type hw
card 0
}

So I tested this with this:
arecord -D omni1 -r 48000 -t wav -v out.wav -f S24_3LE -c2 With a microphone plugged into channel 1. The omnistudio shows signal level varying via the LED, so I know I'm getting a signal into the device. However, the result I'm hearing is silence.

Higher recording rates are even worse - I get a strange "beep" followed by static.

Attached is /proc/asound/card0/stream0.

I've found this, which may also refer to the problem in my card (it's about the USB Quattro)...unsure.
http://www.music.columbia.edu/pipermail/linux-audio-user/2004-June/012737.html

Still...I should be getting some kind of signal, shouldn't I? Thoughts?

M-Audio OmniStudio USB at usb-0000:00:07.2-1, full speed : USB Audio

Playback:
Status: Stop
Interface 1

    Altset 4
    Format: S16_LE
    Channels: 2
    Endpoint: 3 OUT (ADAPTIVE)
    Rates: 11025, 22050, 44100
  Interface 4
    Altset 1
    Format: S24_3LE
    Channels: 2
    Endpoint: 3 OUT (ADAPTIVE)
    Rates: 88200, 96000
  Interface 4
    Altset 3
    Format: S24_3LE
    Channels: 2
    Endpoint: 3 OUT (ADAPTIVE)
    Rates: 11025, 22050, 44100, 48000
  Interface 4
    Altset 4
    Format: S16_LE
    Channels: 2
    Endpoint: 3 OUT (ADAPTIVE)
    Rates: 11025, 22050, 44100, 48000

Capture:
Status: Stop
Interface 2

    Altset 4
    Format: S16_LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 11025, 22050, 44100
  Interface 5
    Altset 1
    Format: S24_3LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 88200, 96000
  Interface 5
    Altset 3
    Format: S24_3LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 11025, 22050, 44100, 48000
  Interface 5
    Altset 4
    Format: S16_LE
    Channels: 2
    Endpoint: 5 IN (SYNC)
    Rates: 11025, 22050, 44100, 48000
#3 lore raw
In reply to Clemens Ladisch

Okay, I've been trying most of my testing with the first two channels.

However, I just figured out that recording and playback works on channels #3 and #4 at 96000.

The first two are the best ones to get, though, because those are the ones with built-in preamps and XLR inputs. Note that even bypassing the preamps by going directly through the line-ins doesn't work, though.

Clues?

Quoted 6 lines · Clemens Ladisch
Quoted 4 lines · Rusty Phillips

I recently purchased one, and have been trying to find out anything I can about getting it to work. So far all I've gotten is playback on two channels at 48Khz with alsa (from the 2.6.10 kernel as well as from alsa CVS).

Quoted 6 lines

What are the contents of /proc/asound/cardX/stream0? Is there a second output device in the output of "aplay -l"?

Clemens

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

#4 lore raw
Quoted 4 lines · Rusty Phillips

Okay, I've been trying most of my testing with the first two channels.

However, I just figured out that recording and playback works on channels #3 and #4 at 96000.

The first two channels use an additional 16-bit interface, probably for compatibility with the Windows USB Audio driver.

Please try the patch below.

HTH
Clemens

Signature · 150 lines
Index: alsa-kernel/usb/usbaudio.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbaudio.c,v
retrieving revision 1.113
diff -u -r1.113 usbaudio.c
--- alsa-kernel/usb/usbaudio.c	16 Dec 2004 16:12:51 -0000	1.113
+++ alsa-kernel/usb/usbaudio.c	14 Jan 2005 10:16:31 -0000
@@ -2977,6 +2977,8 @@
 		return create_ua700_ua25_quirk(chip, iface);
 	case QUIRK_AUDIO_EDIROL_UA1000:
 		return create_ua1000_quirk(chip, iface);
+	case QUIRK_IGNORE_INTERFACE:
+		return 0;
 	default:
 		snd_printd(KERN_ERR "invalid quirk type %d\n", quirk->type);
 		return -ENXIO;
Index: alsa-kernel/usb/usbaudio.h
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbaudio.h,v
retrieving revision 1.35
diff -u -r1.35 usbaudio.h
--- alsa-kernel/usb/usbaudio.h	30 Sep 2004 10:11:25 -0000	1.35
+++ alsa-kernel/usb/usbaudio.h	14 Jan 2005 10:16:31 -0000
@@ -157,6 +157,7 @@
 #define QUIRK_MIDI_STANDARD_INTERFACE	6
 #define QUIRK_AUDIO_EDIROL_UA700_UA25	7
 #define QUIRK_AUDIO_EDIROL_UA1000	8
+#define QUIRK_IGNORE_INTERFACE		9

 typedef struct snd_usb_audio_quirk snd_usb_audio_quirk_t;
 typedef struct snd_usb_midi_endpoint_info snd_usb_midi_endpoint_info_t;
@@ -190,6 +191,8 @@

 /* for QUIRK_AUDIO_EDIROL_UA700_UA25/UA1000, data is NULL */

+/* for QUIRK_IGNORE_INTERFACE, data is null */
+
 /*
  */

Index: alsa-kernel/usb/usbquirks.h
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbquirks.h,v
retrieving revision 1.38
diff -u -r1.38 usbquirks.h
--- alsa-kernel/usb/usbquirks.h	30 Sep 2004 10:11:25 -0000	1.38
+++ alsa-kernel/usb/usbquirks.h	14 Jan 2005 10:16:31 -0000
@@ -876,6 +876,22 @@
 			 * but captured samples are big-endian (see usbaudio.c).
 			 */
 			{
+				.ifnum = 0,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 1,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 2,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 3,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
 				.ifnum = 4,
 				.type = QUIRK_AUDIO_STANDARD_INTERFACE
 			},
@@ -884,6 +900,10 @@
 				.type = QUIRK_AUDIO_STANDARD_INTERFACE
 			},
 			{
+				.ifnum = 6,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
 				.ifnum = 7,
 				.type = QUIRK_AUDIO_STANDARD_INTERFACE
 			},
@@ -936,11 +956,56 @@
 	.driver_info = (unsigned long) & (const snd_usb_audio_quirk_t) {
 		.vendor_name = "M-Audio",
 		.product_name = "OmniStudio",
-		.ifnum = 9,
-		.type = QUIRK_MIDI_MIDIMAN,
-		.data = & (const snd_usb_midi_endpoint_info_t) {
-			.out_cables = 0x0001,
-			.in_cables  = 0x0001
+		.ifnum = QUIRK_ANY_INTERFACE,
+		.type = QUIRK_COMPOSITE,
+		.data = & (const snd_usb_audio_quirk_t[]) {
+			{
+				.ifnum = 0,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 1,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 2,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 3,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 4,
+				.type = QUIRK_AUDIO_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = 5,
+				.type = QUIRK_AUDIO_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = 6,
+				.type = QUIRK_IGNORE_INTERFACE
+			},
+			{
+				.ifnum = 7,
+				.type = QUIRK_AUDIO_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = 8,
+				.type = QUIRK_AUDIO_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = 9,
+				.type = QUIRK_MIDI_MIDIMAN,
+				.data = & (const snd_usb_midi_endpoint_info_t) {
+					.out_cables = 0x0001,
+					.in_cables  = 0x0001
+				}
+			},
+			{
+				.ifnum = -1
+			}
 		}
 	}
 },



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
#5 lore raw

Using the current CVS I can apply most of that patch at fuzziness level 3 (which could still cause problems), but not the last hunk. I can probably figure it out and patch manually.

But if it's easy for you to do, could you tell me what you're actually patching if not the current CVS (at cvs.alsa-project.org)?

Thanks!

Rusty Phillips

Quoted 6 lines · Clemens Ladisch
Quoted 4 lines · Rusty Phillips

Okay, I've been trying most of my testing with the first two channels.

However, I just figured out that recording and playback works on channels #3 and #4 at 96000.

Quoted 9 lines

The first two channels use an additional 16-bit interface, probably for compatibility with the Windows USB Audio driver.

Please try the patch below.

HTH
Clemens

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

#6 lore raw
Quoted 6 lines · Rusty Phillips

Using the current CVS I can apply most of that patch at fuzziness level 3 (which could still cause problems), but not the last hunk. I can probably figure it out and patch manually.

But if it's easy for you to do, could you tell me what you're actually patching if not the current CVS (at cvs.alsa-project.org)?

This patch was against the current CVS.

Are the revision numbers of the original files in the patch the same that you see?

Anyway, I've put the three patches files here:
<http://www.informatik.uni-halle.de/~ladischc/usbomnistudio.tar.gz>

Clemens

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

#7 lore raw
In reply to Clemens Ladisch

Excellent work, and great turnaround! Not only did that fix the problem I was having with the first two channels, but now that part of the card works in full duplex mode!

This means that I have now gotten all the functionality that the card offers - I can do 4x2 or 2x4 capture/send with Jack.

The only claimed functionality that is missing is sending on 3 and 4 while capturing on 1-4 (in other words, using channels 3 and 4 in full duplex mode. I couldn't even get this to work in windows...it could be a physical limitation (does the Quattro have this problem?)

Strangely, each input channel is returning a different gain even with the same settings. Also, the preamps are absolutely horrible. If anyone is thinking of purchasing this thing because it of the built-in mixer functionality, don't.

Quoted 15 lines · Clemens Ladisch
Quoted 4 lines · Rusty Phillips

Okay, I've been trying most of my testing with the first two channels.

However, I just figured out that recording and playback works on channels #3 and #4 at 96000.

The first two channels use an additional 16-bit interface, probably for compatibility with the Windows USB Audio driver.

Please try the patch below.

HTH
Clemens

Signature · 4 lines
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt