I checked how my RMX works in Windows, regarding midi messages for LED-updates. It seem to work as it should there, so I guess it's the ALSA midi issue and/or the RMX driver that is the cause for midi-messages not getting through to the control.
2010/7/20 Anders Gunnarsson <[email protected]>: > 2010/7/20 Sean M. Pappalardo - D.J. Pegasus <[email protected]>: >> >> >> On 07/19/2010 12:35 AM, Anders Gunnarsson wrote: >>> >>> 1. How can I check if a player is currently located on the cue point >>> from a script? I other words how can I in a custom cue handler decide >>> if I should set a cue point or start cue-playing? >> >> Does the regular [ChannelN],cue_default CO not work for you? It handles that >> logic automatically. > > I thought of sticking to this function for now, I think it will work > good enough with the RMX. This give me no chance to know the current > state of the player in my script though, which would be necessary to > implement custom behaviour, custom light behaviour, shift function to > toggle the functions of these buttons etc. > >> >> Otherwise, looking at >> http://mixxx.org/wiki/doku.php/midi_controller_mapping_file_format#ui_midi_controls_and_names >> you could use [ChannelN],cue_point but that gives you samples. You'd have to >> get the sample rate somehow, then divide cue_point by the sample rate to get >> seconds. Then use playposition * duration to get the current position in >> seconds. (Use visual_playposition for more accuracy but higher CPU load.) >> >>> 2. If I send multiple midi-messages in a row from a script like below, >>> only a few seem to reach my Hercules RMX controller. In fact if two >>> messages are sent after another one can almost be sure that the second >>> won't affect the controller. If the second is put on a 20ms timer one >>> can almost be sure that it does. Has this behavior been seen on other >>> controllers as well, or can someone give it a try to verify what >>> happens? >> >> The SCS.3m has this problem when I send commands that it automatically >> writes to flash, and I have to delay each by 10ms according to the >> manufacturer. That's controller-related. But there's also a problem with >> MIDI messages on Linux that we're currently still working around using a 1ns >> scheduler (as seen in the bug report linked earlier.) There seems to be some >> activity on the related ALSA bug so maybe it'll get fixed soon. (We verified >> that Mixxx is indeed sending all the messages it's supposed to.) > > Ok! Good to know! The messages I send are only for changing lights. I > 'll check how it works in windows to see if it's ALSA related. > >> >> Sincerely, >> Sean M. Pappalardo >> "D.J. Pegasus" >> Mixxx Developer - Controller Specialist >> > > //Anders > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
