Making your own Remote Codec files in Reason with logging

I go over right from start up to adding your controls from your midi controller. I also go over 2 ways to do logging.. 00:00 Intro 02:12 Get the Remote Codec SDK and other documentation 07:06 What Editors I use 10:02 Lets start creating the Codec and mappings files. 12:32 Contents of the LuaCodec file 17:17 The main LUA file 22:34 Basic Mapping file 24:42 When mistakes are made how to fix them 27:56 Getting basic info out (logging). 37:40 Live Logging (Sendlog).. 51:15 Examples of Sendlog 1:02:53 Midi-ox monitoring script 1:06:54 Quick recap. 1:09:38 The Event of Remote_Process_Midi(event) 1:12:22 Adding controls.. 1:24:29 Talking to the midi controller 1:29:19 Tracking when a parameter has changed on a device in Reason 1:40:00 Modes.. Link to the Reason Remote SDK https://developer.reasonstudios.com/d... Lua Crash Course    • Lua Crash Course - Less than 15mins   Midi-OX (PC) http://www.midiox.com/ Midi Monitor for the Mac. https://www.snoize.com/midimonitor/ Dropbox to my files, under remote\codec Note these files are from where this video ends however I have renamed them PoohBear Video.luacodec PoohBear Video.lua PoohBear Video.png PoohBear Video.remotemap MonitorSysExFromReasonRelease.vbs https://www.dropbox.com/scl/fo/q97o95... Notepad++ to edit mapping files. https://notepad-plus-plus.org/ Visual Studio Code https://code.visualstudio.com/ Your Remote files can be found here. Windows: C:\ProgramData\Propellerhead Software\ OSX: //Library/Application Support/Propellerhead Software/ Note: On some Windows machines if you don't have C:\ProgramData\Propellerhead Software\Remote then check %appdata%\Propellerhead Software and see if the remote directory is populated there. Note %appdata%\Propellerhead Software also equals c:\users\YOUR USERNAME\AppData\Roaming\Propellerhead Software