Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.fan.sailor-moon    |    Weird fetishistic shit from Japan    |    8,273 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,245 of 8,273    |
|    Darci Carlton to All    |
|    Moog Matriarch 101 The Video Manual TUTO    |
|    04 Dec 23 17:11:19    |
      From: carltondarci07@gmail.com              MIDI scripting allows native support for any MIDI controller. Scripts are       written in 'Python' code, stored in a plain text file, that FL Studio uses to       translate commands between the controller and FL Studio. MIDI communication       can go in both directions;        The controller can access features in the FL Studio code (as listed below),       and FL Studio can send data back to the controller (such as lighting pads or       showing track names).FL Studio MIDI scripts are based on Python. You do not       need to install anything,        FL Studio will handle scripts directly. When scripts are created in the       folders shown below, the scripted device will display in the Controller type       menu under the MIDI Settings tab. From there, select the controller and use it       as normal.NOTES:Script        hierarchy - As FL Studio natively handles many MIDI functions and messages,       this allows you to write simple scripts to handle specific cases or inputs and       leave the rest to FL Studio's generic MIDI support. For example, you do not       need to tell FL Studio        what to do with MIDI notes. If the script doesn't specifically make changes to       default behavior, FL Studio will handle them as normal.Scripts are complex -       With power and flexibility comes complexity. MIDI scripting is intended for       hardware manufacturers        and advanced users to create custom support for MIDI controllers. If you are       new to programming, MIDI scripting will be confronting and confusing at first.       This is normal, but patience and persistence will be rewarded! There are some       simple examples to        get started on our user forum listed below.Support ForumFL Studio customers       can access the MIDI Controller Scripting forum to discuss scripting, share       scripts, make feature requests and report issues.Script Locations and File       NamesFL Studio will check        the following locations for MIDI Scripts and related files:Script files -       Scripted device files are located in the User data folder under ...       Documents\Image-Line\FL Studio\Settings\Hardware\devicename\devi       e_devicename.py.Script folder naming - The sub        folder 'devicename' is arbitrary and can be anything you like. Normally you       would use the name of the MIDI hardware you are scripting for.Script file       naming - The 'device_devicename' (bold part) can be anything you like to       identify the MIDI script file.        NOTE: 'device_devicename.py' is mandatory for the device to be processed by FL       Studio. You can use spaces and capitals for devicename e.g. 'device_My PHAT       Controller.py'.The controller name - Shown in the MIDI Settings > Controller       type menu is defined        on first line of 'device_devicename.py' script file, e.g. #name=AKAI FL Studio       Fire. This will appear in the device list as 'AKAI FL Studio Fire (user)'. The       (user) suffix is to distinguish your device scripts from installed factory       scripts.              [continued in next message]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca