Differences

This shows you the differences between two versions of the page.

--- webapi:examples:miditoweb [2020/04/19 15:21] – ↷ Page moved from web_api:examples:miditoweb to webapi:examples:miditoweb icke_siegen
+++ webapi:examples:miditoweb [2024/08/24 08:56] (current) – icke_siegen
@@ Line 8: / Line 8: @@
 ^ published               | https://www.avolites.de/support-downloads/midi-to-web                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 ^ prog. lang./ framework  | C, C++ (sources and instructions to compile it with GCC/MinGW are provided)                                                                                                                                                                                                                                                                                                                                                                                                                    |
-^ description             | The result is a simple exe file which can run on Windows computers. It listens to class-compliant MIDI devices. Upon incoming MIDI messages Web API requests are being sent.\\ \\ Configuation - which request being triggered by which MIDI message - is done by editing a simple text file. Extensive examples are provided.\\ \\ Also includes [[web_api:examples:titanIds|]] to retrieve the [[macros:identifier:titanid|Titan IDs]] and [[macros:identifier:location|location strings]].  |
+^ description             | The result is a simple exe file which can run on Windows computers. It listens to class-compliant MIDI devices. Upon incoming MIDI messages Web API requests are being sent.\\ \\ Configuation - which request being triggered by which MIDI message - is done by editing a simple text file. Extensive examples are provided.\\ \\ Also includes [[webapi:examples:titanids]] to retrieve the [[macros:identifier:titanid|Titan IDs]] and [[macros:identifier:location|location strings]].  |
-^ other requirements      | none (for using [[web_api:examples:titanIds]] a web browser is required)                                                                                                                                                                                                                                                                                                                                                                                                                       |
+^ other requirements      | none (for using [[webapi:examples:titanids]] a web browser is required)                                                                                                                                                                                                                                                                                                                                                                                                                       |
 ===== Screenshots =====
-|{{:web_api:examples:midi2web_1.png?323|MidiToWeb (console program)}}|{{:web_api:examples:midi2web_2.png?394|MidiToWeb's cinfig file}}|{{:web_api:examples:titan_ids_1.png?198|TitanIDs}}|
+|{{:webapi:examples:midi2web_1.png?323|MidiToWeb (console program)}}|{{:webapi:examples:midi2web_2.png?394|MidiToWeb's config file}}|{{:webapi:examples:titan_ids_1.png?198|TitanIDs}}|
@@ Line 23: / Line 23: @@
 //MIDI To Web uses a modular system to allow for defining requests and parameters separately. This is explained in length in the manual, and briefly in the config file itself. This system allows to add more WebAPI requests if needed just by editing the config file. Here, just the requests are listed which are included as examples.//
-  * [[:web_api:requests:Playbacks/FirePlaybackAtLevel]]
+  * [[webapi:requests:playbacks_fireplaybackatlevel]]
-  * [[:web_api:requests:Playbacks/SwopPlayback]]
+  * [[webapi:requests:playbacks_swopplayback]]
-  * [[:web_api:requests:Playbacks/ClearSwopPlayback]]
+  * [[webapi:requests:playbacks_clearswopplayback]]
-  * [[:web_api:requests:Playbacks/FlashPlayback]]
+  * [[webapi:requests:playbacks_flashplayback]]
-  * [[:web_api:requests:Playbacks/ClearFlashPlayback]]
+  * [[webapi:requests:playbacks_clearflashplayback]]
-  * [[:web_api:requests:Masters/SetMaster]]
+  * [[webapi:requests:masters_setmaster]]
-  * [[:web_api:requests:Masters/Flash]]
+  * [[webapi:requests:masters_flash]]
-  * [[:web_api:requests:Masters/DeadBlackOut]]
+  * [[webapi:requests:masters_deadblackout]]
-  * [[:web_api:requests:Masters/ClearFlash]]
+  * [[webapi:requests:masters_clearflash]]
-  * [[:web_api:requests:Group/SetGroupFaderLevel]]
+  * [[webapi:requests:group_setgroupfaderlevel]]
-  * [[:web_api:requests:Palette/ApplyPalette]]
+  * [[webapi:requests:palette_applypalette]]
-  * [[:web_api:requests:Masters/SetSpeed]]
+  * [[webapi:requests:masters_setspeed]]