Thread: [Alsa-user] State of highspeed usb2 audio?
Brought to you by:
perex
From: alexander <axe...@gm...> - 2011-11-19 10:18:39
|
I recently bought a sound devices usbpre2 wich is both usb1.1 and usb2 class compliant.. It works very well as a usb1 device but not as usb2.. with jackd I can get it to run as record only, but not playback only or duplex.. |
From: Daniel M. <da...@zo...> - 2011-11-19 20:14:06
|
On Nov 19, 2011 11:22 AM, "alexander" <axe...@gm...> wrote: > > I recently bought a sound devices usbpre2 wich is both usb1.1 and usb2 > class compliant.. It works very well as a usb1 device but not as usb2.. > with jackd I can get it to run as record only, but not playback only or > duplex.. Can you send your output of "lsusb -v", please? |
From: alexander <axe...@gm...> - 2011-11-19 22:36:08
|
On 11/19/2011 10:13 PM, Daniel Mack wrote: > > > On Nov 19, 2011 11:22 AM, "alexander" <axe...@gm... > <mailto:axe...@gm...>> wrote: > > > > I recently bought a sound devices usbpre2 wich is both usb1.1 and usb2 > > class compliant.. It works very well as a usb1 device but not as usb2.. > > with jackd I can get it to run as record only, but not playback only or > > duplex.. > > Can you send your output of "lsusb -v", please? > http://pastebin.com/8uCBAkNb it's connected as highspeed usb2 |
From: alexander <axe...@gm...> - 2011-11-25 14:19:56
|
On 11/19/2011 10:13 PM, Daniel Mack wrote: > > > On Nov 19, 2011 11:22 AM, "alexander" <axe...@gm... > <mailto:axe...@gm...>> wrote: > > > > I recently bought a sound devices usbpre2 wich is both usb1.1 and usb2 > > class compliant.. It works very well as a usb1 device but not as usb2.. > > with jackd I can get it to run as record only, but not playback only or > > duplex.. > > Can you send your output of "lsusb -v", please? > Any news on this? here's the "lsusb -v" again http://pastebin.com/8uCBAkNb |
From: Pablo F. <pab...@gm...> - 2011-11-25 23:45:43
|
On Fri, Nov 25, 2011 at 3:14 PM, alexander <axe...@gm...> wrote: > On 11/19/2011 10:13 PM, Daniel Mack wrote: > > > On Nov 19, 2011 11:22 AM, "alexander" <axe...@gm...> wrote: > > > > I recently bought a sound devices usbpre2 wich is both usb1.1 and usb2 > > class compliant.. It works very well as a usb1 device but not as usb2.. > > with jackd I can get it to run as record only, but not playback only or > > duplex.. > > Could this be a similar issue? http://www.mail-archive.com/als...@li.../msg28007.html BTW, I have just read in lkml that Thomas Poussevin's patch is included in linux 3.2 rc3. :) Cheers, Pablo |
From: Bharat R. <me...@gm...> - 2011-11-27 14:55:52
|
Hi , I am replying to this as I had originally posted the issue in the link provided by Pablo. The issue with mine was that it was plugged into a laptop usb port which was on an internal usb hub and hence couldn't handle duplex. I applied the patch on the 3.0.13 kernel and it worked beautifully, but is now causing other problems (my internal laptop web cam that is also plugged in via another internal usb hub does not work. It works with the kernel without the patch). I will be testing this more in detail and filing bug reports if required. My device is a usb 1.1 device and it had problems in duplex mode. I have another usb 1.1. card which worked just fine. Alexander mentions that his device works just fine in usb 1.1 mode and has problems in usb 2 mode, so I don't think that it is not the same thing as my issue. Alexander, just curious, are you plugging your card into a hub or directly into your PCs usb ports? Bharat On Fri, Nov 25, 2011 at 11:45 PM, Pablo Fernandez <pab...@gm...>wrote:p > > > On Fri, Nov 25, 2011 at 3:14 PM, alexander <axe...@gm...> wrote: > >> On 11/19/2011 10:13 PM, Daniel Mack wrote: >> >> >> On Nov 19, 2011 11:22 AM, "alexander" <axe...@gm...> wrote: >> > >> > I recently bought a sound devices usbpre2 wich is both usb1.1 and usb2 >> > class compliant.. It works very well as a usb1 device but not as usb2.. >> > with jackd I can get it to run as record only, but not playback only or >> > duplex.. >> >> Could this be a similar issue? > > http://www.mail-archive.com/als...@li.../msg28007.html > > BTW, I have just read in lkml that Thomas Poussevin's patch is included in > linux 3.2 rc3. :) > > Cheers, Pablo > > > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Alsa-user mailing list > Als...@li... > https://lists.sourceforge.net/lists/listinfo/alsa-user > > |
From: alexander <axe...@gm...> - 2011-11-27 16:06:20
|
On 11/27/2011 04:55 PM, Bharat Rajagopalan wrote: > Hi , > > I am replying to this as I had originally posted the issue in the link > provided by Pablo. > > The issue with mine was that it was plugged into a laptop usb port > which was on an internal usb hub and hence couldn't handle duplex. I > applied the patch on the 3.0.13 kernel and it worked beautifully, but > is now causing other problems (my internal laptop web cam that is also > plugged in via another internal usb hub does not work. It works with > the kernel without the patch). I will be testing this more in detail > and filing bug reports if required. > > My device is a usb 1.1 device and it had problems in duplex mode. I > have another usb 1.1. card which worked just fine. Alexander mentions > that his device works just fine in usb 1.1 mode and has problems in > usb 2 mode, so I don't think that it is not the same thing as my issue. > > Alexander, just curious, are you plugging your card into a hub or > directly into your PCs usb ports? > > Bharat > it's directly connected to the pc's usb ports, I've tried switching it around too withouth luck.. |
From: Clemens L. <cla...@go...> - 2011-11-28 07:33:10
|
Bharat Rajagopalan wrote: > I applied the patch on the 3.0.13 kernel and it worked beautifully, > but is now causing other problems (my internal laptop web cam that is > also plugged in via another internal usb hub does not work. It works > with the kernel without the patch). Matthieu has posted a follow-up patch on linux-usb: diff --git a/drivers/usb/host/ehci-sched.c b/drivers/usb/host/ehci-sched.c index 56a3203..464b451 100644 --- a/drivers/usb/host/ehci-sched.c +++ b/drivers/usb/host/ehci-sched.c @@ -1475,6 +1475,7 @@ iso_stream_schedule ( * jump until after the queue is primed. */ else { + int done = 0; start = SCHEDULE_SLOP + (now & ~0x07); /* NOTE: assumes URB_ISO_ASAP, to limit complexity/bugs */ @@ -1491,19 +1492,23 @@ iso_stream_schedule ( /* check schedule: enough space? */ if (stream->highspeed) { if (itd_slot_ok(ehci, mod, start, - stream->usecs, period)) + stream->usecs, period)) { + done = 1; break; + } } else { if ((start % 8) >= 6) continue; if (sitd_slot_ok(ehci, mod, stream, - start, sched, period)) + start, sched, period)) { + done = 1; break; + } } } while (start > next); /* no room in the schedule */ - if (start == next) { + if (!done) { ehci_dbg(ehci, "iso resched full %p (now %d max %d)\n", urb, now, now + mod); status = -ENOSPC; |
From: alexander <axe...@gm...> - 2012-01-01 01:53:06
|
Here is what dmesg says after I plug the thing in as a usb2 device [ 2384.749399] usb 1-2: USB disconnect, device number 2 [ 2390.729825] usb 1-2: new high speed USB device number 3 using ehci_hcd [ 2390.863654] generic-usb 0003:0926:0202.0003: hiddev0,hidraw0: USB HID v1.01 Device [Sound Devices USBPre2] on usb-0000:00:02.1-2/input3 it does seem to recognize it correctly.... This is dmesg after I try to use it/start jackd or directly with alsa. [ 2418.388135] cannot submit syncpipe for urb 0, error -90: internal error I didn't try the patch as I dont have any experience compiling kernels, but if it's in 3.2 it should be out soon... On 11/28/2011 09:33 AM, Clemens Ladisch wrote: > > Matthieu has posted a follow-up patch on linux-usb: > > diff --git a/drivers/usb/host/ehci-sched.c b/drivers/usb/host/ehci-sched.c > index 56a3203..464b451 100644 > --- a/drivers/usb/host/ehci-sched.c > +++ b/drivers/usb/host/ehci-sched.c > @@ -1475,6 +1475,7 @@ iso_stream_schedule ( > * jump until after the queue is primed. > */ > else { > + int done = 0; > start = SCHEDULE_SLOP + (now& ~0x07); > > /* NOTE: assumes URB_ISO_ASAP, to limit complexity/bugs */ > @@ -1491,19 +1492,23 @@ iso_stream_schedule ( > /* check schedule: enough space? */ > if (stream->highspeed) { > if (itd_slot_ok(ehci, mod, start, > - stream->usecs, period)) > + stream->usecs, period)) { > + done = 1; > break; > + } > } else { > if ((start % 8)>= 6) > continue; > if (sitd_slot_ok(ehci, mod, stream, > - start, sched, period)) > + start, sched, period)) { > + done = 1; > break; > + } > } > } while (start> next); > > /* no room in the schedule */ > - if (start == next) { > + if (!done) { > ehci_dbg(ehci, "iso resched full %p (now %d max %d)\n", > urb, now, now + mod); > status = -ENOSPC; > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Alsa-user mailing list > Als...@li... > https://lists.sourceforge.net/lists/listinfo/alsa-user > |
From: alexander <axe...@gm...> - 2012-01-08 15:14:32
|
So again, exactly what is the state of usb2 audio class compliance? I've asked around in many places now and noone seems to know. I read somewhere that it's spotty at best and other places that it has just been implemented, seems like noone knows for sure.. So another question arises, is it a hard thing to do? It seems to be properly detected, but I get an error when trying to use it. |[ 2384.749399] usb 1-2: USB disconnect, device number 2 [ 2390.729825] usb 1-2: new high speed USB device number 3 using ehci_hcd [ 2390.863654] generic-usb 0003:0926:0202.0003: hiddev0,hidraw0: USB HID v1.01 Device [Sound Devices USBPre2] on usb-0000:00:02.1-2/input3 [ 2418.388135] cannot submit syncpipe for urb 0, error -90: internal error Here are the lsusb -v again, both with the device connected as 1.1 and 2.0. As usb1.1http://pastebin.com/Jj6mXHxJ and here as usb2http://pastebin.com/8uCBAkNb I've looked at them and the only thing that differs is the|bInterval, wich is 1 in usb1.1 and 4 in usb2. Wich I've understood has something to do with how often the device is called or something.. |
From: Daniel M. <zo...@gm...> - 2012-04-12 18:59:43
|
On 08.01.2012 16:07, alexander wrote: > So again, exactly what is the state of usb2 audio class compliance? I've > asked around in many places now and noone seems to know. I read > somewhere that it's spotty at best and other places that it has just > been implemented, seems like noone knows for sure.. So another question > arises, is it a hard thing to do? Sorry for the late response. Support for v2 is fairly complete, with the exception of some clocking features that have not been observed "in the wild". Is you issue already solved? If not, can I ask you to build a 3.4.0 kernel and apply this patch on top? I just submitted a new version of a rework patch that changes a lot things around USB packet handling in the snd-usb driver. https://gist.github.com/1168715 I would be interested wether this changes anything for your card. Daniel > > It seems to be properly detected, but I get an error when trying to use it. > > |[ 2384.749399] usb 1-2: USB disconnect, device number 2 > [ 2390.729825] usb 1-2: new high speed USB device number 3 using ehci_hcd > [ 2390.863654] generic-usb 0003:0926:0202.0003: hiddev0,hidraw0: USB HID v1.01 Device [Sound Devices USBPre2] on usb-0000:00:02.1-2/input3 > [ 2418.388135] cannot submit syncpipe for urb 0, error -90: internal error > > Here are the lsusb -v again, both with the device connected as 1.1 and 2.0. As usb1.1 http://pastebin.com/Jj6mXHxJ and here as usb2 http://pastebin.com/8uCBAkNb > > I've looked at them and the only thing that differs is the |bInterval, wich is 1 in usb1.1 and 4 in usb2. Wich I've understood has something to do with how often the device is called or something.. > > > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > > > > _______________________________________________ > Alsa-user mailing list > Als...@li... > https://lists.sourceforge.net/lists/listinfo/alsa-user |
From: alexander <axe...@gm...> - 2012-04-12 19:26:37
|
On 04/12/2012 09:59 PM, Daniel Mack wrote: > On 08.01.2012 16:07, alexander wrote: >> So again, exactly what is the state of usb2 audio class compliance? I've >> asked around in many places now and noone seems to know. I read >> somewhere that it's spotty at best and other places that it has just >> been implemented, seems like noone knows for sure.. So another question >> arises, is it a hard thing to do? > Sorry for the late response. > > Support for v2 is fairly complete, with the exception of some clocking > features that have not been observed "in the wild". Is you issue already > solved? > > If not, can I ask you to build a 3.4.0 kernel and apply this patch on > top? I just submitted a new version of a rework patch that changes a lot > things around USB packet handling in the snd-usb driver. > > https://gist.github.com/1168715 > > I would be interested wether this changes anything for your card. > > > Daniel > > Hooray! That's a very late response ;D nonetheless, it's a response and I'm very happy! I've never compiled a kernel before but I could give it a try.. Have you seen my alsa bug report? https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5512 I just noticed now as I write that a reporter named bjorn has a hack for it that seems to work. Reporter 'shal' also gets the same dmesg error, but I dont know if it's the same card or not.. He says he has more linux background tho so he might be more effective with the kernel compiling etc. |
From: Daniel M. <zo...@gm...> - 2012-04-12 22:06:51
Attachments:
usbpre2-quirk-3.4.0.diff
|
On 12.04.2012 21:24, alexander wrote: > On 04/12/2012 09:59 PM, Daniel Mack wrote: >> On 08.01.2012 16:07, alexander wrote: >>> So again, exactly what is the state of usb2 audio class compliance? I've >>> asked around in many places now and noone seems to know. I read >>> somewhere that it's spotty at best and other places that it has just >>> been implemented, seems like noone knows for sure.. So another question >>> arises, is it a hard thing to do? >> Sorry for the late response. >> >> Support for v2 is fairly complete, with the exception of some clocking >> features that have not been observed "in the wild". Is you issue already >> solved? >> >> If not, can I ask you to build a 3.4.0 kernel and apply this patch on >> top? I just submitted a new version of a rework patch that changes a lot >> things around USB packet handling in the snd-usb driver. >> >> https://gist.github.com/1168715 >> >> I would be interested wether this changes anything for your card. >> >> >> Daniel >> >> > Hooray! That's a very late response ;D nonetheless, it's a response and > I'm very happy! I've never compiled a kernel before but I could give it > a try.. Have you seen my alsa bug report? > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5512 I just > noticed now as I write that a reporter named bjorn has a hack for it > that seems to work. Reporter 'shal' also gets the same dmesg error, but > I dont know if it's the same card or not.. He says he has more linux > background tho so he might be more effective with the kernel compiling etc. Ah ok. Saw the patch and added a new one that implements the quirk for newer kernels. I also attached the patch here. Once you managed to build the kernel (there are plenty of good HOWTOs out there), let me know the result. You can apply the other patch additionally (from the gist location I pointed you to), but that should be optional. Daniel |
From: Daniel M. <zo...@gm...> - 2012-04-12 22:47:48
Attachments:
usbpre2-quirk-3.4.0.diff
|
On 13.04.2012 00:06, Daniel Mack wrote: > Ah ok. Saw the patch and added a new one that implements the quirk for > newer kernels. I also attached the patch here. > > Once you managed to build the kernel (there are plenty of good HOWTOs > out there), let me know the result. You can apply the other patch > additionally (from the gist location I pointed you to), but that should > be optional. Eh, sorry. My last patch was bogus. Instead, you should try the one attached to this mail, but you need to apply the streaming rework series *before* that: https://gist.github.com/1168715 Let me know if that works. Daniel |
From: alexander <axe...@gm...> - 2012-04-13 16:50:46
|
> Eh, sorry. My last patch was bogus. Instead, you should try the one > attached to this mail, but you need to apply the streaming rework series > *before* that: https://gist.github.com/1168715 > > Let me know if that works. > > > Daniel > I'm pretty shure I got the patching and compiling right, but I don't know cause it wont work even in usb1 mode with this kernel.. this is my dmesg error when I try to start jack:[ 40.126590] 2:1:2 : invalid synch pipe |
From: alexander <axe...@gm...> - 2012-06-15 11:48:24
|
On 04/13/2012 01:47 AM, Daniel Mack wrote: > On 13.04.2012 00:06, Daniel Mack wrote: > >> Ah ok. Saw the patch and added a new one that implements the quirk for >> newer kernels. I also attached the patch here. >> >> Once you managed to build the kernel (there are plenty of good HOWTOs >> out there), let me know the result. You can apply the other patch >> additionally (from the gist location I pointed you to), but that should >> be optional. > Eh, sorry. My last patch was bogus. Instead, you should try the one > attached to this mail, but you need to apply the streaming rework series > *before* that: https://gist.github.com/1168715 > > Let me know if that works. > > > Daniel > Any news on this? The patche's didn't work last time I tried. I could try again with the latest stable kernel, but I doubt that helps :P I still get the same error with the vanilla 3.4.2 kernel. |
From: Daniel M. <zo...@gm...> - 2012-06-18 17:37:40
Attachments:
usbpre2-quirk-3.4.0.diff
|
On 15.06.2012 13:43, alexander wrote: > On 04/13/2012 01:47 AM, Daniel Mack wrote: >> On 13.04.2012 00:06, Daniel Mack wrote: >> >>> Ah ok. Saw the patch and added a new one that implements the quirk for >>> newer kernels. I also attached the patch here. >>> >>> Once you managed to build the kernel (there are plenty of good HOWTOs >>> out there), let me know the result. You can apply the other patch >>> additionally (from the gist location I pointed you to), but that should >>> be optional. >> Eh, sorry. My last patch was bogus. Instead, you should try the one >> attached to this mail, but you need to apply the streaming rework series >> *before* that: https://gist.github.com/1168715 >> >> Let me know if that works. >> >> >> Daniel >> > Any news on this? The patche's didn't work last time I tried. I lost track on this. Was it that the patch didn't apply? > I could > try again with the latest stable kernel, but I doubt that helps :P I > still get the same error with the vanilla 3.4.2 kernel. There have been some final updates on the new streaming logic just recently. Please checkout v3.5-rc3 and apply the patch I sent back then (attached again). I just double-checked that it still applies cleanly. Daniel |