Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transmit custom messages #6

Open
jpcima opened this issue Jan 6, 2019 · 0 comments
Open

Transmit custom messages #6

jpcima opened this issue Jan 6, 2019 · 0 comments

Comments

@jpcima
Copy link
Member

jpcima commented Jan 6, 2019

(23:55:23) at0m: jpcima: can it sollicit dumps, too? ie. many devices have some sysex command that makes them dump
(23:57:07) at0m: reading the docs at http://linuxmao.org/Sysexxer-NG now, seems it cannot. doesn't matter much, long as it can save the .syx
(23:57:34) jpcima: there isn't protocol knowledge about any particular device right now
(23:58:00) jpcima: but I thought we can put together a kind of database
(23:58:28) at0m: yea that would be lot of work, to collect all that into a database. however, given the option, i would find out for my devices..
(23:59:31) at0m: i don't expect you or anyone else to research 1000s of devices sysex dump request codes
(07/01/2019 00:00:19) jpcima: request me a particular device, and I will add it
(00:00:41) at0m: but sending a sollicitation sysex code could be implemented as a trigger, combining that with saving the sysex could be nice
(00:01:10) at0m: then let the users enter their own sollicitation strings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant