You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
amidi (unless -a is used) ignores 0xFE (Active Sensing) messages, This is good. But for the same reason it should also ignore 0xF8 (Timing Clock). Because it doesn't I can't properly fetch a SysEx dump from my Yamaha Reface DX, or from a Yamaha V50 or YS200 for example. These synths not only send streams of 0xFE but also 0xF8 continuously. amidi doesn't correctly detect the end of a sysex dump from my synth, because it still detects 0xF8 bytes coming out of the synth.
Instead of filtering only 0xFE, all bytes from 0xF8 to 0xFF should be filtered out. Or at least 0xFE and 0xF8.
The text was updated successfully, but these errors were encountered:
That is not good and maybe a simple fix if the author is aware of the problem and can get some feedback from your hardware. Please sign up to the alsa-users mailing-list and resubmit your observation to the list and see if one of the main alsa developers will look into it. Thanks for reporting it.
amidi (unless -a is used) ignores 0xFE (Active Sensing) messages, This is good. But for the same reason it should also ignore 0xF8 (Timing Clock). Because it doesn't I can't properly fetch a SysEx dump from my Yamaha Reface DX, or from a Yamaha V50 or YS200 for example. These synths not only send streams of 0xFE but also 0xF8 continuously. amidi doesn't correctly detect the end of a sysex dump from my synth, because it still detects 0xF8 bytes coming out of the synth.
Instead of filtering only 0xFE, all bytes from 0xF8 to 0xFF should be filtered out. Or at least 0xFE and 0xF8.
The text was updated successfully, but these errors were encountered: