Re: [Alsa-devel] HDSP 9652 MIDI IN - stuck notes
Takashi-san, Was this of any use? Are you looking into this, or do you need more data? Thanks, Mark On Fri, 2003-02-28 at 05:09, Mark Knecht wrote: > On Fri, 2003-02-28 at 04:56, Mark Knecht wrote: > > > at least, we need to check whether the interrupts for MIDI are > > > generated properly. > > > please try the following. > > > > > > 1. connect HDSP MIDI1 input to HDSP MIDI1 output via aconnect. > > > 2. trigger a note from MIDI1 input. > > >check whether the IRQ count in /proc/interrupts (for HDSP) > > >increases. > > >during this test, don't use HDSP audio. > > > > > > > [EMAIL PROTECTED] card1]$ more /proc/interrupts > >CPU0 > > 0: 62488 XT-PIC timer > > 1:816 XT-PIC keyboard > > 2: 0 XT-PIC cascade > > 5:749 XT-PIC usb-uhci, usb-uhci, usb-uhci, eth0 > > 8: 1 XT-PIC rtc > > 10: 94 XT-PIC hdsp > > 11: 5 XT-PIC ohci1394 > > 12: 7033 XT-PIC PS/2 Mouse > > 14: 8556 XT-PIC ide2 > > 15: 9005 XT-PIC ide3 > > NMI: 0 > > ERR: 0 > > [EMAIL PROTECTED] card1]$ > > BTW - The HDSP interrupts above do not represent a failure. All I did is > what you asked me to do. If you asked me to wait for a failure, we'd > have 1000's on interrupts at least, I'm sure, and I don't know how we > would identify that one did not happen. > > Also, if I wasn't clear earlier, the failure is ONE stuck note. The MIDI > input keeps working, and subsequent notes work properly. (both on and > off) It's just that a single note gets stuck every 1-2 minutes. > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 MIDI IN - stuck notes
On Fri, 2003-02-28 at 04:56, Mark Knecht wrote: > > at least, we need to check whether the interrupts for MIDI are > > generated properly. > > please try the following. > > > > 1. connect HDSP MIDI1 input to HDSP MIDI1 output via aconnect. > > 2. trigger a note from MIDI1 input. > >check whether the IRQ count in /proc/interrupts (for HDSP) > >increases. > >during this test, don't use HDSP audio. > > > > [EMAIL PROTECTED] card1]$ more /proc/interrupts >CPU0 > 0: 62488 XT-PIC timer > 1:816 XT-PIC keyboard > 2: 0 XT-PIC cascade > 5:749 XT-PIC usb-uhci, usb-uhci, usb-uhci, eth0 > 8: 1 XT-PIC rtc > 10: 94 XT-PIC hdsp > 11: 5 XT-PIC ohci1394 > 12: 7033 XT-PIC PS/2 Mouse > 14: 8556 XT-PIC ide2 > 15: 9005 XT-PIC ide3 > NMI: 0 > ERR: 0 > [EMAIL PROTECTED] card1]$ BTW - The HDSP interrupts above do not represent a failure. All I did is what you asked me to do. If you asked me to wait for a failure, we'd have 1000's on interrupts at least, I'm sure, and I don't know how we would identify that one did not happen. Also, if I wasn't clear earlier, the failure is ONE stuck note. The MIDI input keeps working, and subsequent notes work properly. (both on and off) It's just that a single note gets stuck every 1-2 minutes. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 MIDI IN - stuck notes
On Fri, 2003-02-28 at 04:14, Takashi Iwai wrote: > At 26 Feb 2003 20:47:41 -0800, > Mark Knecht wrote: > > > >If I then change my keyboard to drive the HDSP 9652 input 1 (Alsa > > 64:0) and change the connections internally to drive all of outputs, I > > get stuck notes pretty much immediately. It seems a bit worse with the > > sustain pedal, but does not seem to be effected at all by controllers. > > It is heavily effected by the MIDI note density. If I hit only one or > > two notes, I'm not likely to get it, but using the sustain pedal I can > > create the problem in under a minute. > > > >To be sure it's the input and not the outputs (as much as I can be) I > > have external synths attached to the Alsa outputs on 64:0, 72:0 and > > 72:1. When I get a stuck note, I seem to get it on both internal soft > > synths and all three external hardware synths at the same time. For this > > reason I deduce that it is the HDSP input that is not clearing out > > whatever event queue that holds this stuff and somehow the note never > > shuts off. > > to be sure, the configuration which doesn't work is like below, ok? > > HDSP MIDI1 input -> softsynth > > and/or > > HDSP MIDI1 input -> HDSP MIDI1 output -> external device Both don't work, and when they fail, they both fail at the same time in the same way, with a note stuck on. That's why I titled the thread HDSP MIDI In - stuck notes. (I'm actually using MIDI 0, not MIDI 1) -> softsynth | HDSP MIDI 0 -- | -> HDSP MIDI 0 output -> external synth Using the USB MIDI in does not fail: -> softsynth | MidiSport 0 -- | -> HDSP MIDI 0 output -> external synth > > at least, we need to check whether the interrupts for MIDI are > generated properly. > please try the following. > > 1. connect HDSP MIDI1 input to HDSP MIDI1 output via aconnect. > 2. trigger a note from MIDI1 input. >check whether the IRQ count in /proc/interrupts (for HDSP) >increases. >during this test, don't use HDSP audio. > [EMAIL PROTECTED] card1]$ more /proc/interrupts CPU0 0: 62488 XT-PIC timer 1:816 XT-PIC keyboard 2: 0 XT-PIC cascade 5:749 XT-PIC usb-uhci, usb-uhci, usb-uhci, eth0 8: 1 XT-PIC rtc 10: 94 XT-PIC hdsp 11: 5 XT-PIC ohci1394 12: 7033 XT-PIC PS/2 Mouse 14: 8556 XT-PIC ide2 15: 9005 XT-PIC ide3 NMI: 0 ERR: 0 [EMAIL PROTECTED] card1]$ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] HDSP 9652 MIDI IN - stuck notes
At 26 Feb 2003 20:47:41 -0800, Mark Knecht wrote: > >If I then change my keyboard to drive the HDSP 9652 input 1 (Alsa > 64:0) and change the connections internally to drive all of outputs, I > get stuck notes pretty much immediately. It seems a bit worse with the > sustain pedal, but does not seem to be effected at all by controllers. > It is heavily effected by the MIDI note density. If I hit only one or > two notes, I'm not likely to get it, but using the sustain pedal I can > create the problem in under a minute. > >To be sure it's the input and not the outputs (as much as I can be) I > have external synths attached to the Alsa outputs on 64:0, 72:0 and > 72:1. When I get a stuck note, I seem to get it on both internal soft > synths and all three external hardware synths at the same time. For this > reason I deduce that it is the HDSP input that is not clearing out > whatever event queue that holds this stuff and somehow the note never > shuts off. to be sure, the configuration which doesn't work is like below, ok? HDSP MIDI1 input -> softsynth and/or HDSP MIDI1 input -> HDSP MIDI1 output -> external device at least, we need to check whether the interrupts for MIDI are generated properly. please try the following. 1. connect HDSP MIDI1 input to HDSP MIDI1 output via aconnect. 2. trigger a note from MIDI1 input. check whether the IRQ count in /proc/interrupts (for HDSP) increases. during this test, don't use HDSP audio. Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] HDSP 9652 MIDI IN - stuck notes
Hi, I've had a miserable stuck note problem with Alsa MIDI for a while, so I finally sat down this evening to try and determine where the problem was coming from, and it appears to be the HDSP 9652 MIDI input. My system has two 2-port MIDI interfaces, the HDSP 9652 (Alsa MIDI 64:0 & 64:32) and a MidiSport 2x2 (Alsa MIDI 72:0 & 72:1) I am using three external hardware synths on different ports (Alsa 64:0, 72:0 and 72:1) and additionally I ran a copy each of the Linux synths ZynAddSubFx (Alsa 130:0) and amSynth (Alsa 128:0) at the same time. (I.e. - 5 synths in parallel, all being driven by a single MIDI input.) To do the tests, I use kaconnect and aconnect to build routing in the MIDI stack to connect a single input to all outputs, which looks like the attachment when I attach all outputs to the MidiSport Port A input. In this configuration I can play continually, basically overdriving the whole system with lots of MIDI events, including controllers and sustain pedal, and I have no problems. I can do this for at least 15 minutes with no problem on any of the synths. If I then change my keyboard to drive the HDSP 9652 input 1 (Alsa 64:0) and change the connections internally to drive all of outputs, I get stuck notes pretty much immediately. It seems a bit worse with the sustain pedal, but does not seem to be effected at all by controllers. It is heavily effected by the MIDI note density. If I hit only one or two notes, I'm not likely to get it, but using the sustain pedal I can create the problem in under a minute. To be sure it's the input and not the outputs (as much as I can be) I have external synths attached to the Alsa outputs on 64:0, 72:0 and 72:1. When I get a stuck note, I seem to get it on both internal soft synths and all three external hardware synths at the same time. For this reason I deduce that it is the HDSP input that is not clearing out whatever event queue that holds this stuff and somehow the note never shuts off. I'll be happy to try any other tests anyone wants me to look into. I'd be curious to know if this is a problem on any of the other RME products that have MIDI or whether it's specifically a HDSP 9652 issue. Also, have any other HDSP 9652 owners seen this? Please let me know what I might be able to do to help further get this solved. Knowing now that the MidiSport doesn't have a problem, I can just use it and for me that's fine. However, for others that might be depending on the HDSP 9652 as a primary interface this would not be acceptable. Thanks, Mark <>
