>Same previously said machine configuration, LL RTC 2.4.17 kernel, using >latest (ALSA 0.9.10a) drivers and pmidi 1.5.4 (both compiled and >installed by hand here). >Every MIDI played with pmidi has "eaten" notes, even a very simple MIDI >file I wrote to test (one channel, max 3 notes playing simultaneously, >long notes). The file scatman.mid has lots of eaten notes. Invoking MusE >0.4.14 without options gives the same behavior. With the -RL things get
i suspect that you had the ALSA sequencer set up with the default timing source, which has a resolution of 10msec. since MusE uses the RTC to provide finer-grain resolution, i would expect it to do better. the ALSA sequencer can be configured to use the RTC as well. >I get no xruns with MusE -RL. I don't know about MusE's internals, but >it seems to do a better job than the ALSA sequencer's scheduler when the >device is EMU10K. If ALSA sequencer is at kernel level, it should be >able to change its priority ro RT, or access the RTC directly, without >depending on one's permission to. it doesn't have a priority per se. its a set of kernel routines that are executed by a handler for the timing source (e.g the system "tick" or the RTC or a PCM clock or whatever). >Well, shots in the dark, anyway. But >it's still too complicated to play MIDI files with EMU10K. the EMU10K is not a hardware MIDI synth. it requires a device driver to translate MIDI into register manipulations to produce sound. as such, the performance of the "synth" is *highly* dependent on the state of the device driver. --p _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
