On Saturday 22 November 2008 09:34:17 Albert Santoni wrote: > I have no idea about this, you're going to have to poke at the MIDI > code to find out what's going on here. Perhaps our new MIDI mapping > spec should include a scriptable section for what MIDI commands to > send when closing a particular device. I agree that we shouldn't be > sending anything crazy like this at exit though.
I don't think that is needed at this stage, although could be something to consider further down the track. I imagine that just iterating through all the LEDs and sending them 'off' would be sufficient. > The MIDI baud rate is 38400 bps, and if each MIDI LED command is 16- > bits, and is being sent 1000 times/second (1ms latency), then that > uses up about half of the MIDI bandwidth we have. If we're sending > multiple MIDI commands to trigger the LEDs at 1ms latency, we can > easily push past the available MIDI bandwidth and probably cause all > sorts of problems. Each MIDI LED is 3 bytes, I think, and on the current mapping for the herc there are 10 of them that are changed. This could easily start to use significant chunks of bandwidth. > So yes, you shouldn't be able to push more data than the MIDI spec > says, regardless of your latency. Patches welcome. :) I'll start looking at it some time soonish I hope. Robin.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
