Hello everyone, this day will We have prepared an interesting update on the user interface of the robot.
As mentioned in previous posts, the Orcobot will perform musical pieces previously "loaded" in his memory. However, this process is much more complex than it seems. Try to be very clear to explain.
First, a MIDI file is loaded into the user interface, the interface is responsible for decoding and interpreting MIDI messages (see MIDI input nude 1). Once done, the values \u200b\u200bextracted from each message (statement, note, velocity, etc.) Are sent serially to the microcontroller master, which stores them in its FLASH memory.
El programa del maestro va a ejecutar las instrucciones almacenadas en memoria y buála!! Let’s Rock!!
¿Pero como diablos le vamos a hacer para entender y descifrar un archivo MIDI?
Afortunadamente, existe bastante documentación sobre este estándar y hemos trabajado mucho en comprenderlo. Además, encontramos en la red varios códigos de prueba que nos permiten hacer la decodificación e interpretación del protocolo (Ver entrada MIDI al desnudo 2 ).
Impresión de pantalla de la interfaz de usuario.
Hicimos nuestra interfaz de usuario utilizando dos de estos ejemplos basis (DumpReceiver.java and DumpSequence.java). As you can see in the picture, the decoded data are displayed in the interface, ie, we already have the notes of the song and the speed to be executed.
serial data for another entry.
Finally, we thank a very special PiKoS_NaN . Valuable help in the design process and software development made possible this interface.
As mentioned in previous posts, the Orcobot will perform musical pieces previously "loaded" in his memory. However, this process is much more complex than it seems. Try to be very clear to explain.
First, a MIDI file is loaded into the user interface, the interface is responsible for decoding and interpreting MIDI messages (see MIDI input nude 1). Once done, the values \u200b\u200bextracted from each message (statement, note, velocity, etc.) Are sent serially to the microcontroller master, which stores them in its FLASH memory.
El programa del maestro va a ejecutar las instrucciones almacenadas en memoria y buála!! Let’s Rock!!
¿Pero como diablos le vamos a hacer para entender y descifrar un archivo MIDI?
Afortunadamente, existe bastante documentación sobre este estándar y hemos trabajado mucho en comprenderlo. Además, encontramos en la red varios códigos de prueba que nos permiten hacer la decodificación e interpretación del protocolo (Ver entrada MIDI al desnudo 2 ).
Impresión de pantalla de la interfaz de usuario. Hicimos nuestra interfaz de usuario utilizando dos de estos ejemplos basis (DumpReceiver.java and DumpSequence.java). As you can see in the picture, the decoded data are displayed in the interface, ie, we already have the notes of the song and the speed to be executed.
based programs to interface:
DumpSequence.java
DumpReceiver.java
displays the contents of a MIDI file decoded
Usage: java dumpSequence midifile
We leave pending the transmission DumpSequence.java
DumpReceiver.java
displays the contents of a MIDI file decoded
Usage: java dumpSequence
serial data for another entry.
Finally, we thank a very special PiKoS_NaN . Valuable help in the design process and software development made possible this interface.
0 comments:
Post a Comment