Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Clemens Ladisch]

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

Colin Fletcher wrote:
> I hope this is the right place for this sort of bug report: if
> there's a better place, please do point me there.

Anything related to the snd-usb-audio driver should go to alsa-devel,
but this bug seems to be in the EHCI driver.

> [2.] I have an Edirol UA-1000 USB 2.0 Audio Capture unit. When
> disconnected (or powered down), it repeatably causes a kernel panic,
> in (I think) linux/drivers/usb/host/ehci-q.c, start_unlink_async(),

You didn't mention that the device was currently playing/recording, so
I assume it wasn't.  In this case, the oops apparently happens when the
MIDI URBs are canceled (the MIDI input URBs are active as long as the
driver is loaded).  Please try the attached patch; it adds two printk()s
around the snd_usbmidi_disconnect() function.  If my theory is correct,
the oops should happen immediately after the "killing MIDI URBs..."
message.


BTW: I never had the opportunity to test my code for the UA-1000.
Does playback/capture/MIDI work?


Regards,
Clemens

[-- Attachment #2: umidi-disconnect.diff.txt --]
[-- Type: text/plain, Size: 539 bytes --]

--- linux/sound/usb/usbmidi.c	27 May 2005 12:10:53 -0000	1.49
+++ linux/sound/usb/usbmidi.c	23 Jun 2005 11:32:57 -0000
@@ -917,6 +917,7 @@
 	snd_usb_midi_t* umidi;
 	int i;
 
+	snd_printk("killing MIDI URBs...\n");
 	umidi = list_entry(p, snd_usb_midi_t, list);
 	for (i = 0; i < MIDI_MAX_ENDPOINTS; ++i) {
 		snd_usb_midi_endpoint_t* ep = &umidi->endpoints[i];
@@ -928,6 +929,7 @@
 		if (ep->in && ep->in->urb)
 			usb_kill_urb(ep->in->urb);
 	}
+	snd_printk("...done\n");
 }
 
 static void snd_usbmidi_rawmidi_free(snd_rawmidi_t* rmidi)

Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Colin Fletcher]

Clemens Ladisch wrote:
> You didn't mention that the device was currently playing/recording, so
> I assume it wasn't.  

Correct. Simply plugging in and unplugging the USB cable (or powering
the UA-1000 on and off) causes the oops every time.

> In this case, the oops apparently happens when the
> MIDI URBs are canceled (the MIDI input URBs are active as long as the
> driver is loaded).  Please try the attached patch; it adds two printk()s
> around the snd_usbmidi_disconnect() function.  If my theory is correct,
> the oops should happen immediately after the "killing MIDI URBs..."
> message.

I don't see the "killing MIDI URBs..." message at all.

> BTW: I never had the opportunity to test my code for the UA-1000.
> Does playback/capture/MIDI work?

jackd will connect to the UA-1000, at which point the 10 output state
LEDs on the front light up, and the output meter shows signals when I
play sound through it, but it's a bit unstable: it will stop working 
after a short while. I haven't investigated any further.


Colin Fletcher.

-- 



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Clemens Ladisch]

Colin Fletcher wrote:
> Clemens Ladisch wrote:
> > In this case, the oops apparently happens when the
> > MIDI URBs are canceled (the MIDI input URBs are active as long as the
> > driver is loaded).  Please try the attached patch; it adds two printk()s
> > around the snd_usbmidi_disconnect() function.  If my theory is correct,
> > the oops should happen immediately after the "killing MIDI URBs..."
> > message.
>
> I don't see the "killing MIDI URBs..." message at all.

OK, the kernel nowadays kills URBs of disconnected devices before it
informs the driver of this.

> > BTW: I never had the opportunity to test my code for the UA-1000.
> > Does playback/capture/MIDI work?
>
> jackd will connect to the UA-1000, at which point the 10 output state
> LEDs on the front light up, and the output meter shows signals when I
> play sound through it, but it's a bit unstable: it will stop working
> after a short while. I haven't investigated any further.

There is a bug in the EHCI driver that will corrupt memory, use this
patch:
http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg35743.html

There seems to be another bug in either the EHCI or the snd-usb-audio
driver; I'm still getting problems with high speed iso transfers.
I'm investigating this.


Regards,
Clemens



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Colin Fletcher]

Clemens Ladisch wrote:
  > There is a bug in the EHCI driver that will corrupt memory, use this
> patch:
> http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg35743.html

After applying this, I can start jackd, record a couple of minutes worth 
of eight tracks in ardour, and stop jackd again with no problems.

For the record, without the patch, as soon as I start jackd I get:
ehci_hcd 0000:00:03.3: fatal command 010010 (park)=0 ithresh=1 Periodic 
period=1024 HALT
ehci_hcd 0000:00:03.3: fatal status 4008 Periodic FLR
and my computer freezes, so that's definite progress. Thank you!

> There seems to be another bug in either the EHCI or the snd-usb-audio
> driver; I'm still getting problems with high speed iso transfers.
> I'm investigating this.

Do let me know if there's anything else you'd like me to test.

Colin Fletcher

-- 




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Clemens Ladisch]

Colin Fletcher wrote:
> Clemens Ladisch wrote:
> > There seems to be another bug in either the EHCI or the snd-usb-audio
> > driver; I'm still getting problems with high speed iso transfers.

That was a bug in snd-usb-audio; it didn't correctly handle high speed
endpoints with bInterval > 1.  Now fixed in the ALSA CVS.

> Do let me know if there's anything else you'd like me to test.

I'd like to know if playback and/or MIDI work.  It may be possible
that the driver doesn't send playback PCM data at exactly the correct
rate because the playback stream should have been synchronized to the
capture stream.


Regards,
Clemens



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Colin Fletcher]

Clemens Ladisch wrote:

> I'd like to know if playback and/or MIDI work.  It may be possible
> that the driver doesn't send playback PCM data at exactly the correct
> rate because the playback stream should have been synchronized to the
> capture stream.

I don't have any MIDI hardware to hand at the moment: I can try to dig 
out my old Roland drum machine next week if that will help.

Meanwhile, I've tried playback (with jack 0.100.1, ardour, & 
realtime_lsm loaded).

With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in 
itd_patch()"), using jackd in realtime mode at 44.1kHz with 64 
frames/period and 4 periods/buffer, I get a stream of xruns of about 
0.020 ms, several per second.

Using the same kernel and jackd settings, but with the sound/ and 
include/sound directories from ALSA CVS of about 7:30 this evening, it 
seems to work fine, at least for a couple of minutes of stereo playback.

At 128 frames/period, both kernels have a crackling background noise: I 
haven't experimented with any other settings yet.

I hope this is useful: I'm afraid I'm not going to have time to try much 
more until next week now.

Colin Fletcher

-- 




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[david-b]

> With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in 
> itd_patch()"), using jackd in realtime mode at 44.1kHz with 64 
> frames/period and 4 periods/buffer, I get a stream of xruns of about 
> 0.020 ms, several per second.

In USB, one frame == 1 msec.  Most EHCI silicon using the 2.6.12 code
will get unhappy with 256 msec per ISO URB, so I hope you're using
"frame" without a necessary adjective ... ;)


> Using the same kernel and jackd settings, but with the sound/ and 
> include/sound directories from ALSA CVS of about 7:30 this evening, it 
> seems to work fine, at least for a couple of minutes of stereo playback.
>
> At 128 frames/period, both kernels have a crackling background noise: I 
> haven't experimented with any other settings yet.

I discourage drivers from using more than 64 msec per ISO URB.

Thanks for the status info ... it's seeming that ISO-OUT through
EHCI is probably usable now.  ISO-IN is a different story.  :)

- Dave



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Lee Revell]

On Mon, 2005-06-27 at 19:03 -0700, david-b@pacbell.net wrote:
> > With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in 
> > itd_patch()"), using jackd in realtime mode at 44.1kHz with 64 
> > frames/period and 4 periods/buffer, I get a stream of xruns of about 
> > 0.020 ms, several per second.
> 
> In USB, one frame == 1 msec.  Most EHCI silicon using the 2.6.12 code
> will get unhappy with 256 msec per ISO URB, so I hope you're using
> "frame" without a necessary adjective ... ;)
> 

"frame" = audio frame (4 bytes with S16LE).

"USB frame" = 1 msec

> 
> > Using the same kernel and jackd settings, but with the sound/ and 
> > include/sound directories from ALSA CVS of about 7:30 this evening, it 
> > seems to work fine, at least for a couple of minutes of stereo playback.
> >
> > At 128 frames/period, both kernels have a crackling background noise: I 
> > haven't experimented with any other settings yet.
> 
> I discourage drivers from using more than 64 msec per ISO URB.
> 

Please clarify.  64msec of what?

Lee



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[david-b]

> From: Lee Revell <rlrevell@joe-job.com>
> Date: Mon, 27 Jun 2005 22:30:11 -0400
>
> On Mon, 2005-06-27 at 19:03 -0700, david-b@pacbell.net wrote:
> > > With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in 
> > > itd_patch()"), using jackd in realtime mode at 44.1kHz with 64 
> > > frames/period and 4 periods/buffer, I get a stream of xruns of about 
> > > 0.020 ms, several per second.
> > 
> > In USB, one frame == 1 msec.  Most EHCI silicon using the 2.6.12 code
> > will get unhappy with 256 msec per ISO URB, so I hope you're using
> > "frame" without a necessary adjective ... ;)
> > 
>
> "frame" = audio frame (4 bytes with S16LE).
> "USB frame" = 1 msec

No.  "frame" == ambiguous.  This message is on a USB list, where the
no-adjective version means "USB frame".  It's also cross-posted to
a list where the no-adjective version means something very different.

The only solution that removes ambiguity for _everyone_ is to ensure
that such words never appear without an adjective.


> > > Using the same kernel and jackd settings, but with the sound/ and 
> > > include/sound directories from ALSA CVS of about 7:30 this evening, it 
> > > seems to work fine, at least for a couple of minutes of stereo playback.
> > >
> > > At 128 frames/period, both kernels have a crackling background noise: I 
> > > haven't experimented with any other settings yet.
> > 
> > I discourage drivers from using more than 64 msec per ISO URB.
> > 
>
> Please clarify.  64msec of what?

128 frames/period == 128 msec between transfers, probably not what he
meant to say ... but not clear what he _did_ mean to say either.

An ISO URB has one buffer that's split into N transfers, performed
one transfer per period.  If (N * P) < 64 msec it will hit the fewest
number of scheduling issues ... usually two or three can be scheduled
with no gaps (such gaps will cause noise).  At 128 msec, most hosts
can't double-buffer ... gaps are almost ensured.

- Dave



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Lee Revell]

On Mon, 2005-06-27 at 20:31 -0700, david-b@pacbell.net wrote:
> > From: Lee Revell <rlrevell@joe-job.com>
> > Date: Mon, 27 Jun 2005 22:30:11 -0400
> >
> > On Mon, 2005-06-27 at 19:03 -0700, david-b@pacbell.net wrote:
> > > > With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in 
> > > > itd_patch()"), using jackd in realtime mode at 44.1kHz with 64 
> > > > frames/period and 4 periods/buffer, I get a stream of xruns of about 
> > > > 0.020 ms, several per second.
> > > 
> > > In USB, one frame == 1 msec.  Most EHCI silicon using the 2.6.12 code
> > > will get unhappy with 256 msec per ISO URB, so I hope you're using
> > > "frame" without a necessary adjective ... ;)
> > > 
> >
> > "frame" = audio frame (4 bytes with S16LE).
> > "USB frame" = 1 msec
> 
> No.  "frame" == ambiguous.  This message is on a USB list, where the
> no-adjective version means "USB frame".  It's also cross-posted to
> a list where the no-adjective version means something very different.
> 
> The only solution that removes ambiguity for _everyone_ is to ensure
> that such words never appear without an adjective.
> 

OK, makes sense.

So what the poster was saying was that if he uses 64 audio frames per
period, which at 44.1KHz requires the audio interface to deliver a chink
of data every ~1.4ms, he gets periodic xruns, IOW the audio interface is
not able to do that.  If he uses 128, he gets no xruns, so he's getting
a chunk of data every 2.8ms, but it's corrupted, hence the crackling.

Lee



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Clemens Ladisch]

Colin Fletcher wrote:
> Clemens Ladisch wrote:
> > I'd like to know if playback and/or MIDI work.
>
> I don't have any MIDI hardware to hand at the moment: I can try to dig
> out my old Roland drum machine next week if that will help.

You could just use a MIDI cable for loopback.

> > It may be possible
> > that the driver doesn't send playback PCM data at exactly the correct
> > rate because the playback stream should have been synchronized to the
> > capture stream.
>
> At 128 frames/period, both kernels have a crackling background noise: I
> haven't experimented with any other settings yet.

This seems to be this synchronization issue.

To be able to handle this correctly, the driver would need to be
extended to always capture data so that it can determine the exact
rate for playback.


Regards,
Clemens



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Colin Fletcher]

Lee Revell wrote:
> On Mon, 2005-06-27 at 20:31 -0700, david-b@pacbell.net wrote:

>>No.  "frame" == ambiguous.  This message is on a USB list, where the
>>no-adjective version means "USB frame".  It's also cross-posted to
>>a list where the no-adjective version means something very different.
>>
>>The only solution that removes ambiguity for _everyone_ is to ensure
>>that such words never appear without an adjective.
>>

I'm sorry for being the originator of such confusion. I'll try to be 
less ambiguous from now on :-)

> So what the poster was saying was that if he uses 64 audio frames per
> period, which at 44.1KHz requires the audio interface to deliver a chink
> of data every ~1.4ms, he gets periodic xruns, IOW the audio interface is
> not able to do that.  If he uses 128, he gets no xruns, so he's getting
> a chunk of data every 2.8ms, but it's corrupted, hence the crackling.


That's exactly right, though yesterday's ALSA CVS almost completely 
cures the xruns (only four in > 25 minutes so far today).

Colin Fletcher

-- 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Colin Fletcher]

Clemens Ladisch wrote:

> You could just use a MIDI cable for loopback.

OK, I'll give this a try when I get a chance.

Colin Fletcher

-- 




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Clemens Ladisch]

david-b@pacbell.net wrote:
> > With kernel 2.6.12 + "[PATCH] ehci-hcd - fix page pointer allocation in
> > itd_patch()"), using jackd in realtime mode at 44.1kHz with 64
> > frames/period and 4 periods/buffer, I get a stream of xruns of about
> > 0.020 ms, several per second.
>
> In USB, one frame == 1 msec.  Most EHCI silicon using the 2.6.12 code
> will get unhappy with 256 msec per ISO URB, so I hope you're using
> "frame" without a necessary adjective ... ;)
> ...
> I discourage drivers from using more than 64 msec per ISO URB.

The URBs used by the snd-usb-audio driver are mostly independent of
ALSA's period size, and use between 1 and 20 ms.

> Thanks for the status info ... it's seeming that ISO-OUT through
> EHCI is probably usable now.  ISO-IN is a different story.  :)

Recording on both Edirol UA-1000 and Audigy 2 NX seems to work, and
frequency feedback for the async out endpoints, too.


Regards,
Clemens



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Colin Fletcher]

Clemens Ladisch wrote:
>>>I'd like to know if playback and/or MIDI work.
>>
>>I don't have any MIDI hardware to hand at the moment: I can try to dig
>>out my old Roland drum machine next week if that will help.
> 
> 
> You could just use a MIDI cable for loopback.

I'm sorry it took me so long to find a MIDI cable... I've now tried 
this, and it seems to work (kernel 2.6.12.2 + the ALSA CVS from 
27/06/2005 that I was using before). I haven't stressed it: I just sent 
a few note on/note off events and continuous controllers to the "UA-1000 
MIDI" out, and saw that they came back in again. Is there anything more 
elaborate I should try?

Colin Fletcher

-- 




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface

[Clemens Ladisch]

Colin Fletcher wrote:
> Clemens Ladisch wrote:
> >>>I'd like to know if playback and/or MIDI work.
>
> I've now tried this, and it seems to work (kernel 2.6.12.2 + the
> ALSA CVS from 27/06/2005 that I was using before). I haven't
> stressed it: I just sent a few note on/note off events and
> continuous controllers to the "UA-1000 MIDI" out, and saw that
> they came back in again. Is there anything more elaborate I should
> try?

You could try a SysEx, but it seems to work just fine.

Do you (or the manual) know what the control port is good for?


Regards,
Clemens



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

UA-1000 MIDI control port (was - Re: [linux-usb-devel] [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface)

[Colin Fletcher]

Clemens Ladisch wrote:
> Do you (or the manual) know what the control port is good for?

No, I was wondering that myself. I assume it's for controlling the 
internal patchbay, monitoring and so forth by sending it magic SysExes, 
but there's no mention of how to do this in the Owner's Manual.

I posted a message on the edirol.co.uk web site asking if they can send 
me some documentation: if they come back with anything useful I'll let 
you know.

Colin Fletcher

-- 








This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar