Re: Rawmidi bug or missed feature?

[Peter Enderborg <pme@ufh.se>]

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

Paul Davis wrote:

> >How do you solve the problem with sharing hardware then?
>
> I don't. I intend to wait for (and contribute too, if I can) what I
> consider the correct solution:
>
>   a) sequencer genuinely split into:
>
>           1) a router/multiplexer
>           2) a scheduler
>
>   b) sequencer moves into user space
>
> As I've said before, I don't consider the current kernel-side
> implementation of the sequencer, nor its merging of two completely
> different functions, to be in anyone's interest. I think that Frank
> was (like myself and everyone else) somewhat "blinded" by the fact
> that OSS put the sequencer in the kernel, and we did not know that it
> was possible to get similar performance in user space.

How can we get the same performance i userspace? For me it is the
processor/OS schedule that gives the limit for that, and in kernel we
get
the hardware as the limit.

>
>
> For the time being, I have hardware solutions that work for me when I
> need to do complex MIDI routing (i.e. dedicated h/w MIDI patchbays),
> and I never run multiple apps using the same port.
>
> --p

--
foo!



[-- Attachment #2: Type: text/html, Size: 1415 bytes --]