Hi, I will take a look at this in the future. At this moment I'm busy with starting a new project on my daytime job. However maybe after few weeks.
Best regards, Hannu --- 18.9.2011 5.56, Sebastian Parborg wrote: > Hmm... > After some debugging of the code in oss_envy24ht, it seems like the > driver code is working. > I added some more cmn_err outputs in the midi code and it seems like > it can read the input events that is sent to it from my midi keyboard. > The received events seem sane (when I print the RX queue and the input > read) but it seems like the output gets lost somewhere on the way to > the midi in device in /dev (midi00 in this case). > > For example this is what I get in dmesg: > Checking for input, status is 13 > Trying to read midi, input is 80 > /dev/midi01: Input buffer overflow > > As you can see here the RX queue (status) is 0x13 and the input is 0x80. > However it seems like this trying to pass the information to the > midi01 device (output/MIDI out) and not my input device! > > I think this explains why midi00 is always silent. But I have no idea > why it tries to use midi01 instead of midi00 as it will only listen to > input if i open the input device for reading. > An other thing I noticed is it seems like I can't send and receive > MIDI events at the same time. > If I connect the MIDI in jack to the MIDI out jack and run the midiout > and midiin examples from the OSS4 manual the output transmits put the > input seems to get put on hold till the output is done. > Is this a limitation of the current midi implementation in OSS4 or is > it perhaps my soundcard? It seems quite dumb to have two MIDI jacks if > you can only use one at a time... > The software based midi loopback device seems to be able to. But i > guess it differs somewhat from the MIDI implementation on the > soundcards. > > Anyhow, it seems to me like I need to find out where and why it tries > to output to the wrong device and I should be able to use my MIDI in > jack. > I would be really grateful if someone would try to help me out with > this. Not necessarily with coding but just with a few pointers of hint > on where the problem could reside. > > Regards, > Sebastian Parborg > _______________________________________________ > oss-devel mailing list > oss-devel@mailman.opensound.com > http://mailman.opensound.com/mailman/listinfo/oss-devel _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
