https://www.reaperaccessibility.com/api.php?action=feedcontributions&feedformat=atom&user=ChesselReaper Accessibility Wiki - User contributions [en]2026-04-24T08:22:03ZUser contributionsMediaWiki 1.44.5https://www.reaperaccessibility.com/index.php?title=Useful_Links_and_Resources&diff=628Useful Links and Resources2023-11-28T18:01:27Z<p>Chessel: /* Toni barth's reaPack Repository */</p>
<hr />
<div>= Useful Links and Resources =<br />
<br />
== Other Reaper Specific Resources ==<br />
<br />
In addition to the already mentioned sws extensions, there are some more packs and sites (usually created by users) that further extend the functionality and knowledge of reaper. A (hopefully) comprehensive list of these follows. Please note that the accessibility of some of those is not thoroughly tested and cannot be guaranteed. However, you might find something fun or useful here, Who knows?<br />
*mentioned in the manual and elsewhere, there is the [http://stash.reaper.fm reaper stash,] where you can download presets, scripts, instrument banks, themes, language packs and so on.<br />
*The cockos wiki has documentation available for [http://wiki.cockos.com/wiki/index.php/Jesusonic_Effects_Documentation many of the other supplied effects] that are not in the [[ReaEffects guide]]<br />
* [https://reapack.com/ ReaPack] is a freeware utility which manages and installs user created scripts for a really vast number of tricks and functions. Its interface is accessible.<br />
* [https://www.helgoboss.org/projects/playtime/ playtime] is a paid vst especially designed for Reaper which claims to add Ableton Live like features and functionality. Currently not an accessible utility.<br />
*For some nice free sampled acoustic drums there are several versions of [https://smmdrums.wordpress.com this kit,] which was originally and especially designed to use reaper's only stock plug-ins. And [https://groovemonkee.com/blogs/blog/megareaper-sm-drums-freebie a few complementary professionally designed free grooves from groovemonkee] to go with it.<br />
* [http://vordio.net/ Vordio] is a free audio post production workflow tool that converts XML exported from an NLE video project from programs like Final cut Pro, Premiere Pro, or DaVinci Resolve, into a REAPER audio project for audio post production.<br />
*[https://reaperblog.net/ the reaper blog] provides paid one on one support, lots of free learning materials for reaper, plug-in reviews, tips, tutorials and more.<br />
* [http://www.ambisonictoolkit.net/ The Ambisonic Toolkit] "brings together a number of classic and novel tools for the artist working with Ambisonic surround sound." A set of reaper js effects scripts are available from their site.<br />
* [http://www.aatranslator.com.au/ AA translator] is a paid utility that aims to convert sessions or projects files from different DAWS.<br />
*Last but not least, there are [https://www.tb-software.com/TBProAudio/accessiblemeter.html accessible spectrum (frequency) analysis, phase analysis and peak meter vst tools] you can use in reaper.<br />
<br />
This wiki also has been [https://drive.google.com/uc?export=download&id=17MaD9YjSEguxWzKVO3-0XTQ-cxev-FiS archived offline in wikiSyntax form only, for now].<br />
<br />
== User Groups, Community Support and Resources focused on accessibility ==<br />
<br />
=== Reapers Without Peepers (an email list hosted on groups.io) ===<br />
<br />
The RWP (Reapers Without Peepers) mailing list, is a very helpful place for those learning or using Reaper. Discussion of Reaper's accessibility via any means on either the Windows or Mac platforms is welcome. You can [https://groups.io/g/rwp join RWP here.]<br />
<br />
=== Reaper Access (a friendly, active group on WhatsApp) ===<br />
<br />
This WhatsApp group is another source of assistance for people who are interested in learning or indeed already using Reaper. It tends to be higher traffic than RWP. It's a fairly loose, friendly hang, and has proven to be a great place to collaborate and/or get critique. Most of the messages being exchanged day-to-day are voice notes, but people who prefer to text are equally welcome.<br />
<br />
To minimize spam, we've unfortunately had to pull down the direct link. Instead, we're going to give you an easy-to-follow description of how you can join. This measure keeps the group readily available to humans, whilst slamming the door firmly in the face of spam bots.<br />
<br />
To join the group, you'll need a device with WhatsApp installed (iPhone, Android etc).<br />
<br />
Open the browser on your device, and assemble the shortened link described below in your address bar.<br />
<br />
*The link starts with www and a dot, as usual.<br />
*Then you'll want to type the word tiny, another dot, and the letters cc.<br />
*Next comes a forward slash.<br />
*After the forward slash, type the word ReaperAccess exactly as it is written here.<br />
*Notice that there are no spaces anywhere in the link, and you'll want to make sure that the first letter of Reaper and the first letter of Access are both uppercase.<br />
<br />
If you get stuck following those instructions, just subscribe to RWP and let them know that you'd like to be added to the WhatsApp group. Someone will get you hooked up.<br />
<br />
=== REAPER Dropbox ===<br />
<br />
This is a community-maintained, accessibility-focused Dropbox folder that's choc full of useful content, including custom actions, audio and text tutorials, templates, preset libraries and free instruments that can all be used to some extent with screen reader software. Some of the content is mirrored on this here site, but new stuff tends to hit the Dropbox first. If you'd like to subscribe, just ask for an invitation on RWP or WhatsApp.<br />
<br />
Right now, the resource is a bit bigger than Dropbox's space allowance on their free plan. Migration to a different service will be completed soon. In the meantime, if you're on the free plan, you can [https://seafile.mur.org.uk/f/2a9546217f304002b89d/?dl=1 download November's Dropbox snapshot] instead of subscribing.<br />
<br />
=== Reaper Accessible Archive ===<br />
<br />
Lee Julien, along with others, compiles a growing archive of useful resources. It includes:<br />
* Excellent tutorials in French language<br />
* An alternative to the default OSARA keymap<br />
* [http://reaperaccessible.fr/archives/LBL%20Add-On%20For%20NVDA.zip LBL, a free NVDA add-on which provides bolt-on accessibility support for a growing number of software instruments (also includes overlays from the SIBIAC add-on)]<br />
* Steven Slate Drums Accessibility bundle for NVDA<br />
* SessionDrummer3 accessibility info <br />
* The free instrument and plugins library, ReaLibrary<br />
* Audio and MIDI loops <br />
And much more.<br />
*<br />
<br />
[https://en.reaperaccessible.fr Here is the English list of resources shared by reaperaccessible.fr]<br />
<br />
[https://reaperaccessible.fr Go to reaperaccessible.fr home page for French content]<br />
<br />
== Tutorials and Presentations ==<br />
<br />
=== Reaper Made Easy: free training from The Global Voice ===<br />
<br />
This is the most recently recorded series of free screen reader focused tutorial content that we know of. The first batch of lessons starts right at the beginning, covering concepts and installation of everything you'll need on Windows and Mac. There's plenty more to come over time, you'd be wise to bookmark the [https://theglobalvoice.info/reaper Reaper Made Easy landing page.]<br />
<br />
=== Ten Typical Tasks with Scott ===<br />
<br />
These are bite-size tutorials covering the basics of editing, recording and using effects. Reaper on Windows is what you'll hear being demoed, but keystrokes and notes for Mac folk are also included all the way through.<br />
<br />
You can either [https://nextcloud.danielwproductions.com/index.php/s/aLPkZka2Yk2Pk9H/download grab a zip file containing the whole series], or [https://nextcloud.danielwproductions.com/index.php/s/aLPkZka2Yk2Pk9H browse and download individual files as required.]<br />
<br />
Shout out to Daniel Wolak for hosting the content.<br />
<br />
This series took a considerable amount of time and effort to make. If it proves to be useful to you, and you're in a position to be able to support its author, [https://paypal.me/ScottChesworth donations sent here will reach Scott, its presenter.] Any amount will be massively appreciated, but rest assured that donation is completely optional.<br />
<br />
=== ReaProducer Podcast ===<br />
<br />
This free set of audio tutorials by Garth Humphreys and occasional guests can be found at [http://reaproducer.com The ReaProducer Standalone Site]. If you'd prefer to subscribe, [https://itunes.apple.com/podcast/id1170942901?mt=2&ls=1 here's the ReaProducer Podcast feed for Apple Podcasts], or [http://reaproducer.com/index.php/feed/ here's the RSS feed for other podcast catchers.] Most of these episodes have been produced on the Mac, however Garth has always been mindful to make sure that his content is applicable to both platforms.<br />
<br />
If you're new to Reaper, it is recommended that you work through the first few tutorials in order. They start with installation, and move through important concepts, such as importing media, recording, and editing with both time selections and items. How to Save and Render projects is also covered, along with side-chaining and an introduction to automation. There really is a ton of useful info contained within these bite-sized tutorials.<br />
<br />
===Audio Access Youtube Videos===<br />
<br />
Mohomed Rashad, has made many videos on how to use Reaper with a screen reader some with thousands of views. He covers a wide range of topics which start from the very beginning of how to get set up.<br />
[https://www.youtube.com/channel/UCRGSnf4c1Wps8_dAm-s5x-w Audio Access channel home page.]<br />
<br />
=== Recordings of Live Streams and Presentations ===<br />
<br />
==== Sound Design With Justin Macleod ====<br />
<br />
Justin Macleod (a Reaper power user from the UK with serious sound design chops) has taken to live streaming deep dives into various topics. These sessions are part presentation, part exploration, part Q&A. Here's a folder containing [https://nextcloud.danielwproductions.com/index.php/s/BwcC2mdPPtNjfiz recordings of previous live streams] (shout out to Daniel Wolak for hosting).<br />
<br />
The topics covered are loosely voted on by members of RWP. Keep a lookout for emails with #Demo in the subject line to find out when the next stream will be.<br />
<br />
Justin streams on TeamTalk. If you're new to that platform and need help getting hooked up, just ask.<br />
<br />
If you appreciate his efforts, [http://www.paypal.me/jmacleod Justin massively appreciates donations via PayPal.]<br />
<br />
==== Toni Barth Music ==== <br />
<br />
[https://www.youtube.com/channel/UCY9gmULHVuRSMsymsrMmwdw/videos The Toni barth Music Youtube channel] is a series of posts with each one focusing on a specific topic. Many are about Reaper accessibility and include the stock EQ plug-in, the media explorer, the peak watcher and many more.<br />
<br />
==== CAVI Courses (aging, but still useful resources)====<br />
<br />
For a few years, CAVI (Cisco Academy for the Vision Impaired) ran popular courses designed for people who were getting started with Audio Production and more specifically, Reaper.<br />
<br />
In March 2018, all of the previously available audio related course materials were released for free. The links to the actual audio content have since been pulled, but Daniel Wolak has once again saved the day. Use the following links to browse and download the audio content from his server:<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/jX94eGtoJJ5Neqo Audio Essentials (2017, Semester 1]<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/m9ZG46GyMEjsAQw Reaper Beginners]<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/mNkpX9AimyAAAR6 Reaper Advanced]<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/RLff77YRjjNB7p9 Reaper MIDI]<br />
<br />
The wiki content from previous courses can still be found [http://wiki.cucat.org/index.php/Main/AudioInsAndOuts here.]<br />
<br />
Nowadays the materials therein are getting a little long in the tooth, but there's still plenty to be learned, so grab 'em while you can. We'll only be linking to them until they're superseded by free content that's more current.<br />
<br />
==== Chris Belle's Tutorials ====<br />
<br />
Reaper user Chris Belle has very generously offered a set of free tutorials, which can be downloaded from these two mirrors [https://drive.google.com/uc?export=download&id=1RCHImJg6WQMPjcjArR1JxxUCrhPJNzhl (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/reaper+free.zip (mirror link 2)]<br />
They contain the following: <br />
*About the actions list<br />
*making custom actions<br />
*Editing basics, and an explanation of the [[chapter 7: Editing Tracks and Items#7.31 Ripple Editing|reaper ripple editing modes]]<br />
*[[ReaEffects guide#6.6 Subtract Mode|noise reduction]] with reaper<br />
<br />
*Using [[Chapter 10: Pitch and Time Manipulation#10.8 Stretch Markers|stretch markers]]<br />
* [[Sidechaining_with_ReaComp|Side-chaining with ReaComp]]<br />
<br />
==== Patrick Perdue's Tutorials ====<br />
<br />
Patrick Perdue recorded a tutorial on using vocoders with reaper. The stock ReaVocode plugin is explained first, then Patrick demonstrates other third-party vocoders.<br />
Download: [https://drive.google.com/uc?export=download&id=1nx7LXb5Q5UQikbGKEKPugyna1OP4tcyZ (mirror 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/UsingVocodersWithReaper.mp3 (mirror 2)]<br />
<br />
==== Podcasts on CoolBlindTech.com ====<br />
<br />
A growing set of podcasts have been done by members of the CoolBlindTech.com team, mostly by Alex Hiironen. They cover many things, from basics to using some effects and virtual instruments. <br />
They are somewhat scattered, but the first of them are presented in a (hopefully) organized manner. <br />
Note: they seem to be applicable to windows only.<br />
<br />
<br />
<br />
* [https://coolblindtech.com/reaper-on-windows-episode-1-general-introduction-why-reaper-is-awesome/ part 1, why is reaper awesome]<br />
* [https://coolblindtech.com/reaper-part-2-rudimentary-recording-for-windows/ part 2, rudimentary recording]<br />
* [https://coolblindtech.com/reaper-windows-part-3-configure-play/ part 3, recommended configurations] <br />
* [https://coolblindtech.com/reaper-windows-part-4-tracking-next-single/ part 4 tracking your next single] <br />
* [https://coolblindtech.com/?s=reaper and so on and so on]<br />
<br />
== Accessibility Enhancing Scripts ==<br />
<br />
Now follows a large collection of utilities and scripts created mostly by blind reaper users. Most of these are windows based, though you might find useful reaper presets and tricks as well.<br />
<br />
=== Access4Music Scripts and Utilities ===<br />
<br />
This is a collection of links that point to scripts that allow the user to access [http://access4music.com/en/script various third-party software instruments] and [http://access4music.com/en/script/utilities as well as enhancing the accessibility of Reaper's MIDI Event List]. Access4Music is a small Italian team of visually impaired programmers.<br />
<br />
=== Free NumPad and Applications Key Emulation Scripts ===<br />
<br />
If you're using a laptop that doesn't have an embedded numeric keypad but you'd still like to use those keys in Reaper, here is a [https://www.sendspace.com/pro/dl/yffgb7 numpad key emulator script by Andrew Downie] <br />
[https://drive.google.com/uc?export=download&id=1e52FT7Qf2EKtcBvujKohgaHx86BPyaXQ (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/andrew's+numpad-keys-v22.exe (mirror link 2)]along with its corresponding [https://www.sendspace.com/pro/dl/s7dl6n auto hotkey source code] [https://drive.google.com/uc?export=download&id=1N4NH8mm5SpGsGzWoe9H6dk2SEAD4yLJS (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/andrews+sourceCode+numpad-keys-v22.ahk (mirror link 2)]. This nifty script reminds you if you've accidentally left the NumPad emulation turned on by a series of beeps, and you can configure how often you get reminded. The script activates the NumPad emulation by default as soon as it is opened. It also displays a dialog box with configuration options and a list of the hotkeys used. Quite self-explanatory by design, but if you get stuck, Andrew has been known to haunt RWP from time to time.<br />
<br />
On Windows, Shift+F10 doesn't always work as a substitute for the Applications key inside Reaper. If you're stuck on a keyboard without an Applications key, here is an [https://www.dropbox.com/s/rnzv0abmf7cqu7b/AppsKey4Reaper.exe?dl=1 Applications key emulation script] [https://drive.google.com/uc?export=download&id=1b6hIV-V_emIouVuRpAdPL2KbdodlQCJl (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/Matej+Golians+AppsKey4Reaper.exe (mirror link 2)] available (written by Matej Golian). launch it every time you want to work in REAPER. You can<br />
then use the right CTRL key instead of the applications key. So for<br />
example the shortcut alt+applications will become alt+right CTRL.<br />
<br />
The Access4Music team also has [http://www.access4music.com/en/script/utilities their own version of an Applications key script] along with another handy utility which makes it possible to read columns in Reaper's MIDI Event List individually.<br />
<br />
Last but by no means least, [https://www.sendspace.com/pro/dl/3ut3tk here is Andrew Downie's version of an Applications key emulation script] [https://drive.google.com/uc?export=download&id=1DhAb6ljrgu9t_gohBqubxQAD3dj2_98h (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/Andrew+Downie's+appskey.exe (mirror link 2)]<br />
<br />
=== Sibiac NVDA Add-on ===<br />
<br />
A sighted programmer from Germany, known as [http://azslow.com/ Az,] (Alexey Zhelezov) has very generously created the [[SIBIAC add-on for NVDA]] which aims to make a growing list of third-party fx or instrument plugins accessible. These include addictive drums 2, toontrack EzMix 2, and the worldwide renowned Melodyne, among many others.<br />
<br />
=== accessibility bundle (Sonorous Arts Group) ===<br />
<br />
Accessibility Bundle is a set of screen reader independent, easy to<br />
use helpers packed into one application which aims at making different<br />
pieces of software more accessible for the blind and visually<br />
impaired.<br />
This set was created with integrity and portability in mind; No<br />
installers and no launching a bunch of scripts to get your software<br />
working (Run once, Use anywhere).<br />
It currently supports Xfer Serum, Tone2 Icarus (version 1.x), Native<br />
Instruments Kontakt 6 and Native Instruments Kontakt 7 (Only partially<br />
supported).<br />
For more information, Refer to the readme file present in the<br />
compressed archive.<br />
You may always [https://sonorousarts.com/product-manager/products/download/3/ download the latest version of the accessibility bundle here].<br />
<br />
===Toni barth's reaPack Repository===<br />
There are a bunch of useful scripts and plugins available from Toni barth's reaPack repository. Add the following URL to your reaPack:<br />
https://github.com/Timtam/reapack/raw/master/index.xml<br />
<br />
== a list of third party accessible instruments and effects ==<br />
<br />
Note: this probably needs its own page if it grows too much? (see or start a discussion on this topic)<br />
<br />
Even though most virtual instruments and effects are highly visually oriented, some of those are being successfully controlled and used by blind and visually impaired people via a combination of automation parameters, OCR and various bolt-on scripted solutions. The choices mentioned on this page are a loosely organized, non-exhaustive list of feedback compiled from all corners of the Reaper accessibility community. Discussing automation parameters from the ground up is certainly beyond the scope of this page, instead, you're more likely to find hints on which parameters of an instrument or plugin can be manipulated using OSARA's Parameters dialog, or tips on parameters that are misleadingly labelled, to take a few examples at random. It is recommended, but not always necessary that plugins are opened in bridged mode with dedicated process per plugin (most often the case if you're attempting to access a plugin with an AutoHotkey script from the likes of Access4Music). Brace yourselves, there are MANY of them. User reports follow:<br />
<br />
<br />
=== Waves Accessibility ===<br />
<br />
The presets for most Waves plugins are accessible when loaded in VST3 mode. Parameters are labeled correctly and most will provide real-world values. Notable (but likely not the only) exceptions are Waves Tune LT, GTR3 Stomps and GTR3 Tool Rack (where the stomp box parameters are not labeled because they are interchangeable). Sibiac provides some accessibility to the GTR3 Tool Rack plugin.<br />
<br />
* All of the reverbs, including renaissance, trueVerb, echo. Built in Presets are selectable from the slider as well, but cannot be edited from the text box. Also, when setting parameters like frequency ranges (in hertz) or room sizes for the reverbs the editable field shows values that do not correspond at all with the reported parameters so its better to just stick to the slider when manipulating those effects.<br />
* RVox (a vocal compressor) and C6 (a multi-band compressor/equalizer) can be used without any problems as well.<br />
*GTR3: The accessibility isn’t quite as good as some of their other plugs (not all the parameters show formatted values) The only labeled parameter is the on/off switch for each box, so that will help you find out which box is which. The GTR3 Tool Rack requires a golden cursor location to load presets properly, but is doable with no problems, which when loaded will prompt an accessible context menu. It’s also very modular, so you can access just stomps, just amps/cabs etc as separate plugs and use the fx chain to switch around the order of those boxes if you want. Reaper user Gerad Deuvall has created [https://www.youtube.com/watch?v=Ez490lJaFX8 a youtube video demonstrating its use]<br />
<br />
=== PianoTeq 6 ===<br />
<br />
All of the presets for pianos, harps ETC are now visible to reaper. Just go to the FX window by hitting F on the track that has PianoTeq instantiated on it, tab to the Presets combo box and use your ArrowUp and ArrowDown keys to navigate the choices.<br />
<br />
Since version 6.1, automatable parameters are accessible in the OSARA Parameters dialog.<br />
However, changing between the different pianos is a bit tricky. Here's a suggested way of doing it:<br />
Press F on the relevant track to open the FX window, make sure PianoTeq is selected in the FX chain list box, then tab until you find an unlabelled check box. Using NVDA's object navigation, go to the next object (note that you need to use object nav, you can't tab to this area of the screen). It's reported as "unknown" by NVDA. Using NVDA+Shift+NumPadMinus, set focus to that "unknown" object. That object is the PianoTeq GUI itself, and it isn't accessible, but once focused, it does react to some key presses. Control+N switches between categories of instruments, and N switches from instrument to instrument. Your controller will continue working while you are interacting with the inaccessible GUI, so you can play a few notes, hit N, play some more, and so on until you've found a preset you like. Performing OCR may even tell you which preset that was.<br />
<br />
=== Omnisphere 2 ===<br />
<br />
Omnisphere is partially accessible if you're comfortable with concepts like review cursor in screen mode, object navigation with the use of the number pad, simulated clicking and relocating cursor. This also means that expansions like Keyscape, Trilion, ETC. will work too. You can change preset banks, select visible lists and some other settings. To navigate more presets, you will have to scroll with a mouse wheel.<br />
<br />
After the plugin is instantiated in REAPER’s FX Window, use Shift+Tab to move to the “Add” button, then press UpArrow to get into Omnisphere’s GUI.<br />
Use NVDA’s screen review to navigate to the area where NVDA will report “software version x.x, or sound sources version x.x" (where x is the version you’re using). Move the mouse pointer to this information with NVDA+NumPad+Slash, and press the NumPad+Slash to click. You’ll be taken to the library tab of the plugin GUI.<br />
Using screen review, you’ll find some category filters such as type of sound, (for example, bells and vibs, ARP+BPM, etc). Filter the sounds as needed by selecting the appropriate filter using the above commands. Once again, they're NVDA+NumPad+Slash to move the mouse pointer to the desired item, and NumPad+Slash to click. The list of sounds in the category you've chosen will appear on the right of the screen, after where NVDA says: “normal”.<br />
Still using screen review, select your first sound and play your keyboard to see whether you like it. Once the first sound has been clicked, you'll be able to navigate through other sounds in that category using UpArrow and DownArrow. Note that the sound list wraps; that means if you have reached the last sound on the list, when you press DownArrow again, you’ll be at the very first sound.<br />
<br />
Hint: if you need to open another instance of Omnisphere during your session, from that instance of the plugin onward, you’ll be taken directly to the Library tab. It's recommended to save any sounds you like as user presets by hitting Shift+Space on the Plus button in REAPER's FX window. This will enable you to recall them quickly without having to muck about in the plugin GUI as described above every time.<br />
<br />
=== Addictive Drums 2 ===<br />
<br />
You can make some changes and preset selections with OCR. You can also change kit pieces and presets, but it's limited.<br />
<br />
For NVDA, the [[SIBIAC add on for NVDA|Sibiac framework]] allows almost complete operation (except for MIDI groove selection). You can [http://www.azslow.com/index.php?topic=372.0 get more info on Sibiac here]<br />
<br />
=== iZotope Plugins ===<br />
<br />
* Nectar 2 and Neutron 2: once you find the Presets menu with OCR, you can browse the subcategories with NVDA speech, using the arrow keys, however, the main category title is not announced. It behaves like a folder tree though. <br />
* Nectar elements: in addition to parameters being reported correctly, there is a user created rpl (reaper presets library) file which allows these to be selected just like any other preset from the regular effects dialog. It contains all presets of Nectar Elements, plus two special packs: Styles 1 and Utility pack. Many thanks to Alan Escola. The file can be found [https://www.dropbox.com/s/6wm7uodb2euigrl/NectarElements%20RPL%20Pack.zip?dl=1 via this dropbox link] [https://drive.google.com/uc?export=download&id=18cmrukS_JvN8vm0xMQ_NccaTWCHhmBHB (mirror 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/NectarElements+RPL+Pack.zip (mirror 2)] <br />
* iZotope OZone 8: Once you find the preset menu with OCR, a dialog box will pop up and you can arrow through the presets with speech.<br />
*The iZotope DDLY Dynamic Delay and iZotope Vinyl plugins are all properly labeled from the parameter list. The DDLY plugin allows two different delays to be applied to the same track, and can be downloaded as a trial if you want to see it for yourself. The Vinyl plugin is free, and adds a vinyl noise effect to the track which you apply it to.<br />
<br />
=== Cakewalk Dimension Pro ===<br />
<br />
Use OCR to find the preset selection, and when you hit enter, an accessible dialog box will pop up. Scripts are also available at the [http://access4music.com/en/script music access site].<br />
<br />
=== Superior Drummer 2 ===<br />
<br />
OCR works okay with this in Classic Mode since all kit pieces are stationary, no matter the expansion selected. Problem is, you have to use OCR to go to some menus to select classic mode, then from there, you have to find some text, move your cursor slightly above, and right click and you will be able to read the context menus with speech for kit selection pieces. The Learn button is also somewhat visible, making this extremely tricky but can be done. Probably not worth the headaches though.<br />
<br />
Scripts are also available at the [http://access4music.com/en/script music access site].<br />
<br />
=== SoniVox VSTs ===<br />
<br />
I've noticed that SoniVox VSTs are accessible. You can just tab down to the presets menus, and it lists all the different instruments there. I have SoniVox Orchestra companion Strings, Brass, and woodwinds, and they all work in that exact same way. I also have SoniVox's Harpsichord, session drummer, classic bass, big band percussion, and singles taylor acoustic guitar and they all work perfectly accessibility wise.<br />
Also The classic series of plugs work well, the free ones you can download from Mixcraft - classic delay, reverb, eq, chorus, that entire set of plugs.<br />
<br />
=== Sugar Bytes ===<br />
<br />
The Sugar Bytes Unique virtual synthesizer is a virtual synth that specializes in vowel sounds. The parameters are visible in the list but are not labeled, but the preset list is accessible from the dropdown list that is found in the FX chain window. It can be downloaded as a trial as well.<br />
<br />
=== Versilian Studios ===<br />
<br />
Versilian Studios makes a ton of free and extremely affordable plugins that all seem to be fully accessible. I've purchased a couple and have all the free ones, and have had no issues with the standalone versions, and I believe there are Kontakt versions of many of the plugins as well. However, note that the VSCO instruments are strictly Kontakt instruments, except for the community edition which is a free library of raw wave files from the Kontakt versions.<br />
http://vis.versilstudios.net/products.html<br />
<br />
=== Korg Virtual Instruments ===<br />
<br />
* KORG Legacy: when I modify some parameters they do not cause any effect. Example, with KORG MS-20. It is a monophonic (or polyphonic) analog synthesizer from the 70s. There are some presets that are polyphonic, when I modify the parameter that is used to change the polyphony, I can not do it even though I used the slide bar in the corresponding parameter. It is something strange. The same happens with other parameters. Almost all parameters have a name, but some do not. Not only happens with the MS-20, it also happens with MonoPoly and Polysix. they are all from KORG Legacy.<br />
* WaveStation and M1, there are no problems. WaveStation parameters are accessible through the GUI, while some can be accessed in the FX parameters box.<br />
<br />
== Using Yamaha SYXG 50 on Modern Machines ==<br />
<br />
For those wanting a gm compatible synth, [http://veg.by/en/projects/syxg50/ there is a recently updated version of this once popular Yamaha soft synth] [https://drive.google.com/uc?export=download&id=1Sl0n74XtxzDgxHIYSkzq1d_zOQmjB2Hk (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/yamaha_syxg50_vsti.7z (mirror link 2)]. Since newer windows systems do not have the ability to allow a particular midi device to be selected as the system default (older windows versions did), you must install [http://coolsoft.altervista.org/en/forum/post/2052/attachment?fid=473 this midi mapper] [https://drive.google.com/uc?export=download&id=1elnFGAFZdcCzUYI4QXO1I7_v_gVCuyBL (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/CoolSoft_MIDIMapper_0.9.0-beta5.exe (mirror link 2)] (you can log in with a google account or create one to be able to download it or just use the mirror links). After installing the [https://kode54.net/vstmididrv.exe VST midi system synth driver] first according to the procedure described on the first link, you should be ready to go. It basically acts as a midi mapper just like it did on the older windows installations so that you can select the VST midi system synth as the system default. <br />
The response of this VST is just as good. It tends to stutter a little especially when some new patches come in, but no major issues have been reported. <br />
If you plan to make music or do music production with it, then you should instantiate this by choosing the "Virtual instrument on new track" option from Reaper's Insert top menu.</div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Useful_Links_and_Resources&diff=627Useful Links and Resources2023-11-28T17:58:44Z<p>Chessel: /* accessibility bundle (Sonorous Arts Group) */</p>
<hr />
<div>= Useful Links and Resources =<br />
<br />
== Other Reaper Specific Resources ==<br />
<br />
In addition to the already mentioned sws extensions, there are some more packs and sites (usually created by users) that further extend the functionality and knowledge of reaper. A (hopefully) comprehensive list of these follows. Please note that the accessibility of some of those is not thoroughly tested and cannot be guaranteed. However, you might find something fun or useful here, Who knows?<br />
*mentioned in the manual and elsewhere, there is the [http://stash.reaper.fm reaper stash,] where you can download presets, scripts, instrument banks, themes, language packs and so on.<br />
*The cockos wiki has documentation available for [http://wiki.cockos.com/wiki/index.php/Jesusonic_Effects_Documentation many of the other supplied effects] that are not in the [[ReaEffects guide]]<br />
* [https://reapack.com/ ReaPack] is a freeware utility which manages and installs user created scripts for a really vast number of tricks and functions. Its interface is accessible.<br />
* [https://www.helgoboss.org/projects/playtime/ playtime] is a paid vst especially designed for Reaper which claims to add Ableton Live like features and functionality. Currently not an accessible utility.<br />
*For some nice free sampled acoustic drums there are several versions of [https://smmdrums.wordpress.com this kit,] which was originally and especially designed to use reaper's only stock plug-ins. And [https://groovemonkee.com/blogs/blog/megareaper-sm-drums-freebie a few complementary professionally designed free grooves from groovemonkee] to go with it.<br />
* [http://vordio.net/ Vordio] is a free audio post production workflow tool that converts XML exported from an NLE video project from programs like Final cut Pro, Premiere Pro, or DaVinci Resolve, into a REAPER audio project for audio post production.<br />
*[https://reaperblog.net/ the reaper blog] provides paid one on one support, lots of free learning materials for reaper, plug-in reviews, tips, tutorials and more.<br />
* [http://www.ambisonictoolkit.net/ The Ambisonic Toolkit] "brings together a number of classic and novel tools for the artist working with Ambisonic surround sound." A set of reaper js effects scripts are available from their site.<br />
* [http://www.aatranslator.com.au/ AA translator] is a paid utility that aims to convert sessions or projects files from different DAWS.<br />
*Last but not least, there are [https://www.tb-software.com/TBProAudio/accessiblemeter.html accessible spectrum (frequency) analysis, phase analysis and peak meter vst tools] you can use in reaper.<br />
<br />
This wiki also has been [https://drive.google.com/uc?export=download&id=17MaD9YjSEguxWzKVO3-0XTQ-cxev-FiS archived offline in wikiSyntax form only, for now].<br />
<br />
== User Groups, Community Support and Resources focused on accessibility ==<br />
<br />
=== Reapers Without Peepers (an email list hosted on groups.io) ===<br />
<br />
The RWP (Reapers Without Peepers) mailing list, is a very helpful place for those learning or using Reaper. Discussion of Reaper's accessibility via any means on either the Windows or Mac platforms is welcome. You can [https://groups.io/g/rwp join RWP here.]<br />
<br />
=== Reaper Access (a friendly, active group on WhatsApp) ===<br />
<br />
This WhatsApp group is another source of assistance for people who are interested in learning or indeed already using Reaper. It tends to be higher traffic than RWP. It's a fairly loose, friendly hang, and has proven to be a great place to collaborate and/or get critique. Most of the messages being exchanged day-to-day are voice notes, but people who prefer to text are equally welcome.<br />
<br />
To minimize spam, we've unfortunately had to pull down the direct link. Instead, we're going to give you an easy-to-follow description of how you can join. This measure keeps the group readily available to humans, whilst slamming the door firmly in the face of spam bots.<br />
<br />
To join the group, you'll need a device with WhatsApp installed (iPhone, Android etc).<br />
<br />
Open the browser on your device, and assemble the shortened link described below in your address bar.<br />
<br />
*The link starts with www and a dot, as usual.<br />
*Then you'll want to type the word tiny, another dot, and the letters cc.<br />
*Next comes a forward slash.<br />
*After the forward slash, type the word ReaperAccess exactly as it is written here.<br />
*Notice that there are no spaces anywhere in the link, and you'll want to make sure that the first letter of Reaper and the first letter of Access are both uppercase.<br />
<br />
If you get stuck following those instructions, just subscribe to RWP and let them know that you'd like to be added to the WhatsApp group. Someone will get you hooked up.<br />
<br />
=== REAPER Dropbox ===<br />
<br />
This is a community-maintained, accessibility-focused Dropbox folder that's choc full of useful content, including custom actions, audio and text tutorials, templates, preset libraries and free instruments that can all be used to some extent with screen reader software. Some of the content is mirrored on this here site, but new stuff tends to hit the Dropbox first. If you'd like to subscribe, just ask for an invitation on RWP or WhatsApp.<br />
<br />
Right now, the resource is a bit bigger than Dropbox's space allowance on their free plan. Migration to a different service will be completed soon. In the meantime, if you're on the free plan, you can [https://seafile.mur.org.uk/f/2a9546217f304002b89d/?dl=1 download November's Dropbox snapshot] instead of subscribing.<br />
<br />
=== Reaper Accessible Archive ===<br />
<br />
Lee Julien, along with others, compiles a growing archive of useful resources. It includes:<br />
* Excellent tutorials in French language<br />
* An alternative to the default OSARA keymap<br />
* [http://reaperaccessible.fr/archives/LBL%20Add-On%20For%20NVDA.zip LBL, a free NVDA add-on which provides bolt-on accessibility support for a growing number of software instruments (also includes overlays from the SIBIAC add-on)]<br />
* Steven Slate Drums Accessibility bundle for NVDA<br />
* SessionDrummer3 accessibility info <br />
* The free instrument and plugins library, ReaLibrary<br />
* Audio and MIDI loops <br />
And much more.<br />
*<br />
<br />
[https://en.reaperaccessible.fr Here is the English list of resources shared by reaperaccessible.fr]<br />
<br />
[https://reaperaccessible.fr Go to reaperaccessible.fr home page for French content]<br />
<br />
== Tutorials and Presentations ==<br />
<br />
=== Reaper Made Easy: free training from The Global Voice ===<br />
<br />
This is the most recently recorded series of free screen reader focused tutorial content that we know of. The first batch of lessons starts right at the beginning, covering concepts and installation of everything you'll need on Windows and Mac. There's plenty more to come over time, you'd be wise to bookmark the [https://theglobalvoice.info/reaper Reaper Made Easy landing page.]<br />
<br />
=== Ten Typical Tasks with Scott ===<br />
<br />
These are bite-size tutorials covering the basics of editing, recording and using effects. Reaper on Windows is what you'll hear being demoed, but keystrokes and notes for Mac folk are also included all the way through.<br />
<br />
You can either [https://nextcloud.danielwproductions.com/index.php/s/aLPkZka2Yk2Pk9H/download grab a zip file containing the whole series], or [https://nextcloud.danielwproductions.com/index.php/s/aLPkZka2Yk2Pk9H browse and download individual files as required.]<br />
<br />
Shout out to Daniel Wolak for hosting the content.<br />
<br />
This series took a considerable amount of time and effort to make. If it proves to be useful to you, and you're in a position to be able to support its author, [https://paypal.me/ScottChesworth donations sent here will reach Scott, its presenter.] Any amount will be massively appreciated, but rest assured that donation is completely optional.<br />
<br />
=== ReaProducer Podcast ===<br />
<br />
This free set of audio tutorials by Garth Humphreys and occasional guests can be found at [http://reaproducer.com The ReaProducer Standalone Site]. If you'd prefer to subscribe, [https://itunes.apple.com/podcast/id1170942901?mt=2&ls=1 here's the ReaProducer Podcast feed for Apple Podcasts], or [http://reaproducer.com/index.php/feed/ here's the RSS feed for other podcast catchers.] Most of these episodes have been produced on the Mac, however Garth has always been mindful to make sure that his content is applicable to both platforms.<br />
<br />
If you're new to Reaper, it is recommended that you work through the first few tutorials in order. They start with installation, and move through important concepts, such as importing media, recording, and editing with both time selections and items. How to Save and Render projects is also covered, along with side-chaining and an introduction to automation. There really is a ton of useful info contained within these bite-sized tutorials.<br />
<br />
===Audio Access Youtube Videos===<br />
<br />
Mohomed Rashad, has made many videos on how to use Reaper with a screen reader some with thousands of views. He covers a wide range of topics which start from the very beginning of how to get set up.<br />
[https://www.youtube.com/channel/UCRGSnf4c1Wps8_dAm-s5x-w Audio Access channel home page.]<br />
<br />
=== Recordings of Live Streams and Presentations ===<br />
<br />
==== Sound Design With Justin Macleod ====<br />
<br />
Justin Macleod (a Reaper power user from the UK with serious sound design chops) has taken to live streaming deep dives into various topics. These sessions are part presentation, part exploration, part Q&A. Here's a folder containing [https://nextcloud.danielwproductions.com/index.php/s/BwcC2mdPPtNjfiz recordings of previous live streams] (shout out to Daniel Wolak for hosting).<br />
<br />
The topics covered are loosely voted on by members of RWP. Keep a lookout for emails with #Demo in the subject line to find out when the next stream will be.<br />
<br />
Justin streams on TeamTalk. If you're new to that platform and need help getting hooked up, just ask.<br />
<br />
If you appreciate his efforts, [http://www.paypal.me/jmacleod Justin massively appreciates donations via PayPal.]<br />
<br />
==== Toni Barth Music ==== <br />
<br />
[https://www.youtube.com/channel/UCY9gmULHVuRSMsymsrMmwdw/videos The Toni barth Music Youtube channel] is a series of posts with each one focusing on a specific topic. Many are about Reaper accessibility and include the stock EQ plug-in, the media explorer, the peak watcher and many more.<br />
<br />
==== CAVI Courses (aging, but still useful resources)====<br />
<br />
For a few years, CAVI (Cisco Academy for the Vision Impaired) ran popular courses designed for people who were getting started with Audio Production and more specifically, Reaper.<br />
<br />
In March 2018, all of the previously available audio related course materials were released for free. The links to the actual audio content have since been pulled, but Daniel Wolak has once again saved the day. Use the following links to browse and download the audio content from his server:<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/jX94eGtoJJ5Neqo Audio Essentials (2017, Semester 1]<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/m9ZG46GyMEjsAQw Reaper Beginners]<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/mNkpX9AimyAAAR6 Reaper Advanced]<br />
<br />
[https://nextcloud.danielwproductions.com/index.php/s/RLff77YRjjNB7p9 Reaper MIDI]<br />
<br />
The wiki content from previous courses can still be found [http://wiki.cucat.org/index.php/Main/AudioInsAndOuts here.]<br />
<br />
Nowadays the materials therein are getting a little long in the tooth, but there's still plenty to be learned, so grab 'em while you can. We'll only be linking to them until they're superseded by free content that's more current.<br />
<br />
==== Chris Belle's Tutorials ====<br />
<br />
Reaper user Chris Belle has very generously offered a set of free tutorials, which can be downloaded from these two mirrors [https://drive.google.com/uc?export=download&id=1RCHImJg6WQMPjcjArR1JxxUCrhPJNzhl (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/reaper+free.zip (mirror link 2)]<br />
They contain the following: <br />
*About the actions list<br />
*making custom actions<br />
*Editing basics, and an explanation of the [[chapter 7: Editing Tracks and Items#7.31 Ripple Editing|reaper ripple editing modes]]<br />
*[[ReaEffects guide#6.6 Subtract Mode|noise reduction]] with reaper<br />
<br />
*Using [[Chapter 10: Pitch and Time Manipulation#10.8 Stretch Markers|stretch markers]]<br />
* [[Sidechaining_with_ReaComp|Side-chaining with ReaComp]]<br />
<br />
==== Patrick Perdue's Tutorials ====<br />
<br />
Patrick Perdue recorded a tutorial on using vocoders with reaper. The stock ReaVocode plugin is explained first, then Patrick demonstrates other third-party vocoders.<br />
Download: [https://drive.google.com/uc?export=download&id=1nx7LXb5Q5UQikbGKEKPugyna1OP4tcyZ (mirror 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/UsingVocodersWithReaper.mp3 (mirror 2)]<br />
<br />
==== Podcasts on CoolBlindTech.com ====<br />
<br />
A growing set of podcasts have been done by members of the CoolBlindTech.com team, mostly by Alex Hiironen. They cover many things, from basics to using some effects and virtual instruments. <br />
They are somewhat scattered, but the first of them are presented in a (hopefully) organized manner. <br />
Note: they seem to be applicable to windows only.<br />
<br />
<br />
<br />
* [https://coolblindtech.com/reaper-on-windows-episode-1-general-introduction-why-reaper-is-awesome/ part 1, why is reaper awesome]<br />
* [https://coolblindtech.com/reaper-part-2-rudimentary-recording-for-windows/ part 2, rudimentary recording]<br />
* [https://coolblindtech.com/reaper-windows-part-3-configure-play/ part 3, recommended configurations] <br />
* [https://coolblindtech.com/reaper-windows-part-4-tracking-next-single/ part 4 tracking your next single] <br />
* [https://coolblindtech.com/?s=reaper and so on and so on]<br />
<br />
== Accessibility Enhancing Scripts ==<br />
<br />
Now follows a large collection of utilities and scripts created mostly by blind reaper users. Most of these are windows based, though you might find useful reaper presets and tricks as well.<br />
<br />
=== Access4Music Scripts and Utilities ===<br />
<br />
This is a collection of links that point to scripts that allow the user to access [http://access4music.com/en/script various third-party software instruments] and [http://access4music.com/en/script/utilities as well as enhancing the accessibility of Reaper's MIDI Event List]. Access4Music is a small Italian team of visually impaired programmers.<br />
<br />
=== Free NumPad and Applications Key Emulation Scripts ===<br />
<br />
If you're using a laptop that doesn't have an embedded numeric keypad but you'd still like to use those keys in Reaper, here is a [https://www.sendspace.com/pro/dl/yffgb7 numpad key emulator script by Andrew Downie] <br />
[https://drive.google.com/uc?export=download&id=1e52FT7Qf2EKtcBvujKohgaHx86BPyaXQ (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/andrew's+numpad-keys-v22.exe (mirror link 2)]along with its corresponding [https://www.sendspace.com/pro/dl/s7dl6n auto hotkey source code] [https://drive.google.com/uc?export=download&id=1N4NH8mm5SpGsGzWoe9H6dk2SEAD4yLJS (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/andrews+sourceCode+numpad-keys-v22.ahk (mirror link 2)]. This nifty script reminds you if you've accidentally left the NumPad emulation turned on by a series of beeps, and you can configure how often you get reminded. The script activates the NumPad emulation by default as soon as it is opened. It also displays a dialog box with configuration options and a list of the hotkeys used. Quite self-explanatory by design, but if you get stuck, Andrew has been known to haunt RWP from time to time.<br />
<br />
On Windows, Shift+F10 doesn't always work as a substitute for the Applications key inside Reaper. If you're stuck on a keyboard without an Applications key, here is an [https://www.dropbox.com/s/rnzv0abmf7cqu7b/AppsKey4Reaper.exe?dl=1 Applications key emulation script] [https://drive.google.com/uc?export=download&id=1b6hIV-V_emIouVuRpAdPL2KbdodlQCJl (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/Matej+Golians+AppsKey4Reaper.exe (mirror link 2)] available (written by Matej Golian). launch it every time you want to work in REAPER. You can<br />
then use the right CTRL key instead of the applications key. So for<br />
example the shortcut alt+applications will become alt+right CTRL.<br />
<br />
The Access4Music team also has [http://www.access4music.com/en/script/utilities their own version of an Applications key script] along with another handy utility which makes it possible to read columns in Reaper's MIDI Event List individually.<br />
<br />
Last but by no means least, [https://www.sendspace.com/pro/dl/3ut3tk here is Andrew Downie's version of an Applications key emulation script] [https://drive.google.com/uc?export=download&id=1DhAb6ljrgu9t_gohBqubxQAD3dj2_98h (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/Andrew+Downie's+appskey.exe (mirror link 2)]<br />
<br />
=== Sibiac NVDA Add-on ===<br />
<br />
A sighted programmer from Germany, known as [http://azslow.com/ Az,] (Alexey Zhelezov) has very generously created the [[SIBIAC add-on for NVDA]] which aims to make a growing list of third-party fx or instrument plugins accessible. These include addictive drums 2, toontrack EzMix 2, and the worldwide renowned Melodyne, among many others.<br />
<br />
=== accessibility bundle (Sonorous Arts Group) ===<br />
<br />
Accessibility Bundle is a set of screen reader independent, easy to<br />
use helpers packed into one application which aims at making different<br />
pieces of software more accessible for the blind and visually<br />
impaired.<br />
This set was created with integrity and portability in mind; No<br />
installers and no launching a bunch of scripts to get your software<br />
working (Run once, Use anywhere).<br />
It currently supports Xfer Serum, Tone2 Icarus (version 1.x), Native<br />
Instruments Kontakt 6 and Native Instruments Kontakt 7 (Only partially<br />
supported).<br />
For more information, Refer to the readme file present in the<br />
compressed archive.<br />
You may always [https://sonorousarts.com/product-manager/products/download/3/ download the latest version of the accessibility bundle here].<br />
<br />
===Toni barth's reaPack Repository===<br />
There are a bunch of useful scripts and plugins available from Toni barth's reaPack repository. Add the following URL to your reaPack:<br />
\\https://github.com/Timtam/reapack/raw/master/index.xml<br />
<br />
== a list of third party accessible instruments and effects ==<br />
<br />
Note: this probably needs its own page if it grows too much? (see or start a discussion on this topic)<br />
<br />
Even though most virtual instruments and effects are highly visually oriented, some of those are being successfully controlled and used by blind and visually impaired people via a combination of automation parameters, OCR and various bolt-on scripted solutions. The choices mentioned on this page are a loosely organized, non-exhaustive list of feedback compiled from all corners of the Reaper accessibility community. Discussing automation parameters from the ground up is certainly beyond the scope of this page, instead, you're more likely to find hints on which parameters of an instrument or plugin can be manipulated using OSARA's Parameters dialog, or tips on parameters that are misleadingly labelled, to take a few examples at random. It is recommended, but not always necessary that plugins are opened in bridged mode with dedicated process per plugin (most often the case if you're attempting to access a plugin with an AutoHotkey script from the likes of Access4Music). Brace yourselves, there are MANY of them. User reports follow:<br />
<br />
<br />
=== Waves Accessibility ===<br />
<br />
The presets for most Waves plugins are accessible when loaded in VST3 mode. Parameters are labeled correctly and most will provide real-world values. Notable (but likely not the only) exceptions are Waves Tune LT, GTR3 Stomps and GTR3 Tool Rack (where the stomp box parameters are not labeled because they are interchangeable). Sibiac provides some accessibility to the GTR3 Tool Rack plugin.<br />
<br />
* All of the reverbs, including renaissance, trueVerb, echo. Built in Presets are selectable from the slider as well, but cannot be edited from the text box. Also, when setting parameters like frequency ranges (in hertz) or room sizes for the reverbs the editable field shows values that do not correspond at all with the reported parameters so its better to just stick to the slider when manipulating those effects.<br />
* RVox (a vocal compressor) and C6 (a multi-band compressor/equalizer) can be used without any problems as well.<br />
*GTR3: The accessibility isn’t quite as good as some of their other plugs (not all the parameters show formatted values) The only labeled parameter is the on/off switch for each box, so that will help you find out which box is which. The GTR3 Tool Rack requires a golden cursor location to load presets properly, but is doable with no problems, which when loaded will prompt an accessible context menu. It’s also very modular, so you can access just stomps, just amps/cabs etc as separate plugs and use the fx chain to switch around the order of those boxes if you want. Reaper user Gerad Deuvall has created [https://www.youtube.com/watch?v=Ez490lJaFX8 a youtube video demonstrating its use]<br />
<br />
=== PianoTeq 6 ===<br />
<br />
All of the presets for pianos, harps ETC are now visible to reaper. Just go to the FX window by hitting F on the track that has PianoTeq instantiated on it, tab to the Presets combo box and use your ArrowUp and ArrowDown keys to navigate the choices.<br />
<br />
Since version 6.1, automatable parameters are accessible in the OSARA Parameters dialog.<br />
However, changing between the different pianos is a bit tricky. Here's a suggested way of doing it:<br />
Press F on the relevant track to open the FX window, make sure PianoTeq is selected in the FX chain list box, then tab until you find an unlabelled check box. Using NVDA's object navigation, go to the next object (note that you need to use object nav, you can't tab to this area of the screen). It's reported as "unknown" by NVDA. Using NVDA+Shift+NumPadMinus, set focus to that "unknown" object. That object is the PianoTeq GUI itself, and it isn't accessible, but once focused, it does react to some key presses. Control+N switches between categories of instruments, and N switches from instrument to instrument. Your controller will continue working while you are interacting with the inaccessible GUI, so you can play a few notes, hit N, play some more, and so on until you've found a preset you like. Performing OCR may even tell you which preset that was.<br />
<br />
=== Omnisphere 2 ===<br />
<br />
Omnisphere is partially accessible if you're comfortable with concepts like review cursor in screen mode, object navigation with the use of the number pad, simulated clicking and relocating cursor. This also means that expansions like Keyscape, Trilion, ETC. will work too. You can change preset banks, select visible lists and some other settings. To navigate more presets, you will have to scroll with a mouse wheel.<br />
<br />
After the plugin is instantiated in REAPER’s FX Window, use Shift+Tab to move to the “Add” button, then press UpArrow to get into Omnisphere’s GUI.<br />
Use NVDA’s screen review to navigate to the area where NVDA will report “software version x.x, or sound sources version x.x" (where x is the version you’re using). Move the mouse pointer to this information with NVDA+NumPad+Slash, and press the NumPad+Slash to click. You’ll be taken to the library tab of the plugin GUI.<br />
Using screen review, you’ll find some category filters such as type of sound, (for example, bells and vibs, ARP+BPM, etc). Filter the sounds as needed by selecting the appropriate filter using the above commands. Once again, they're NVDA+NumPad+Slash to move the mouse pointer to the desired item, and NumPad+Slash to click. The list of sounds in the category you've chosen will appear on the right of the screen, after where NVDA says: “normal”.<br />
Still using screen review, select your first sound and play your keyboard to see whether you like it. Once the first sound has been clicked, you'll be able to navigate through other sounds in that category using UpArrow and DownArrow. Note that the sound list wraps; that means if you have reached the last sound on the list, when you press DownArrow again, you’ll be at the very first sound.<br />
<br />
Hint: if you need to open another instance of Omnisphere during your session, from that instance of the plugin onward, you’ll be taken directly to the Library tab. It's recommended to save any sounds you like as user presets by hitting Shift+Space on the Plus button in REAPER's FX window. This will enable you to recall them quickly without having to muck about in the plugin GUI as described above every time.<br />
<br />
=== Addictive Drums 2 ===<br />
<br />
You can make some changes and preset selections with OCR. You can also change kit pieces and presets, but it's limited.<br />
<br />
For NVDA, the [[SIBIAC add on for NVDA|Sibiac framework]] allows almost complete operation (except for MIDI groove selection). You can [http://www.azslow.com/index.php?topic=372.0 get more info on Sibiac here]<br />
<br />
=== iZotope Plugins ===<br />
<br />
* Nectar 2 and Neutron 2: once you find the Presets menu with OCR, you can browse the subcategories with NVDA speech, using the arrow keys, however, the main category title is not announced. It behaves like a folder tree though. <br />
* Nectar elements: in addition to parameters being reported correctly, there is a user created rpl (reaper presets library) file which allows these to be selected just like any other preset from the regular effects dialog. It contains all presets of Nectar Elements, plus two special packs: Styles 1 and Utility pack. Many thanks to Alan Escola. The file can be found [https://www.dropbox.com/s/6wm7uodb2euigrl/NectarElements%20RPL%20Pack.zip?dl=1 via this dropbox link] [https://drive.google.com/uc?export=download&id=18cmrukS_JvN8vm0xMQ_NccaTWCHhmBHB (mirror 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/NectarElements+RPL+Pack.zip (mirror 2)] <br />
* iZotope OZone 8: Once you find the preset menu with OCR, a dialog box will pop up and you can arrow through the presets with speech.<br />
*The iZotope DDLY Dynamic Delay and iZotope Vinyl plugins are all properly labeled from the parameter list. The DDLY plugin allows two different delays to be applied to the same track, and can be downloaded as a trial if you want to see it for yourself. The Vinyl plugin is free, and adds a vinyl noise effect to the track which you apply it to.<br />
<br />
=== Cakewalk Dimension Pro ===<br />
<br />
Use OCR to find the preset selection, and when you hit enter, an accessible dialog box will pop up. Scripts are also available at the [http://access4music.com/en/script music access site].<br />
<br />
=== Superior Drummer 2 ===<br />
<br />
OCR works okay with this in Classic Mode since all kit pieces are stationary, no matter the expansion selected. Problem is, you have to use OCR to go to some menus to select classic mode, then from there, you have to find some text, move your cursor slightly above, and right click and you will be able to read the context menus with speech for kit selection pieces. The Learn button is also somewhat visible, making this extremely tricky but can be done. Probably not worth the headaches though.<br />
<br />
Scripts are also available at the [http://access4music.com/en/script music access site].<br />
<br />
=== SoniVox VSTs ===<br />
<br />
I've noticed that SoniVox VSTs are accessible. You can just tab down to the presets menus, and it lists all the different instruments there. I have SoniVox Orchestra companion Strings, Brass, and woodwinds, and they all work in that exact same way. I also have SoniVox's Harpsichord, session drummer, classic bass, big band percussion, and singles taylor acoustic guitar and they all work perfectly accessibility wise.<br />
Also The classic series of plugs work well, the free ones you can download from Mixcraft - classic delay, reverb, eq, chorus, that entire set of plugs.<br />
<br />
=== Sugar Bytes ===<br />
<br />
The Sugar Bytes Unique virtual synthesizer is a virtual synth that specializes in vowel sounds. The parameters are visible in the list but are not labeled, but the preset list is accessible from the dropdown list that is found in the FX chain window. It can be downloaded as a trial as well.<br />
<br />
=== Versilian Studios ===<br />
<br />
Versilian Studios makes a ton of free and extremely affordable plugins that all seem to be fully accessible. I've purchased a couple and have all the free ones, and have had no issues with the standalone versions, and I believe there are Kontakt versions of many of the plugins as well. However, note that the VSCO instruments are strictly Kontakt instruments, except for the community edition which is a free library of raw wave files from the Kontakt versions.<br />
http://vis.versilstudios.net/products.html<br />
<br />
=== Korg Virtual Instruments ===<br />
<br />
* KORG Legacy: when I modify some parameters they do not cause any effect. Example, with KORG MS-20. It is a monophonic (or polyphonic) analog synthesizer from the 70s. There are some presets that are polyphonic, when I modify the parameter that is used to change the polyphony, I can not do it even though I used the slide bar in the corresponding parameter. It is something strange. The same happens with other parameters. Almost all parameters have a name, but some do not. Not only happens with the MS-20, it also happens with MonoPoly and Polysix. they are all from KORG Legacy.<br />
* WaveStation and M1, there are no problems. WaveStation parameters are accessible through the GUI, while some can be accessed in the FX parameters box.<br />
<br />
== Using Yamaha SYXG 50 on Modern Machines ==<br />
<br />
For those wanting a gm compatible synth, [http://veg.by/en/projects/syxg50/ there is a recently updated version of this once popular Yamaha soft synth] [https://drive.google.com/uc?export=download&id=1Sl0n74XtxzDgxHIYSkzq1d_zOQmjB2Hk (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/yamaha_syxg50_vsti.7z (mirror link 2)]. Since newer windows systems do not have the ability to allow a particular midi device to be selected as the system default (older windows versions did), you must install [http://coolsoft.altervista.org/en/forum/post/2052/attachment?fid=473 this midi mapper] [https://drive.google.com/uc?export=download&id=1elnFGAFZdcCzUYI4QXO1I7_v_gVCuyBL (mirror link 1)] [https://f001.backblazeb2.com/file/rwp-resources/useful+resourcesFiles/CoolSoft_MIDIMapper_0.9.0-beta5.exe (mirror link 2)] (you can log in with a google account or create one to be able to download it or just use the mirror links). After installing the [https://kode54.net/vstmididrv.exe VST midi system synth driver] first according to the procedure described on the first link, you should be ready to go. It basically acts as a midi mapper just like it did on the older windows installations so that you can select the VST midi system synth as the system default. <br />
The response of this VST is just as good. It tends to stutter a little especially when some new patches come in, but no major issues have been reported. <br />
If you plan to make music or do music production with it, then you should instantiate this by choosing the "Virtual instrument on new track" option from Reaper's Insert top menu.</div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=626Js programming2023-11-20T21:18:09Z<p>Chessel: /* JSFX Programming */ General read through and tidy up.</p>
<hr />
<div>=JSFX Programming=<br />
<br />
== Introduction ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. <br />
<br />
== View Existing JSFX Plugins ==<br />
JSFX plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a JSFX plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.(What is VoiceOver equivalent?)<br />
<br />
== Structure of a plugin ==<br />
A JSFX plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
Note the @slider section runs even when a slider gains focus - i.e. when you tab to it. Thus, it is often helpful to copy slider contents into variables and then in the @slider section, compare the variable with the slider's current value to see if it has changed. If it has then update the variable and run any additional code necessary. For instance:<br />
<br />
//code start<br />
// we define a slider called s_lowpassCutoff, with initial value of 50, min and max of 20 and 100, and label "lowpass cutoff"<br />
slider1:s_lowpassCutoff=50 <20, 100, 1>lowpass cutoff<br />
<br />
<br />
@init<br />
lowpassCutoff = s_lowpassCutoff; // store the initial slider value to compare with later<br />
// do other initialization like initialize your filter, etc<br />
<br />
@slider<br />
<br />
// if slider has changed<br />
lowpassCutoff != s_lowpassCutoff ? (<br />
lowpassCutoff = s_lowpassCutoff; // update the variable<br />
// set filter cutoff etc<br />
//...<br />
);<br />
<br />
This will set the filter cutoff only if the user actually changed the slider.<br />
<br />
Importantly the case of variable names are ignored. So the variable myfrequency (all lower case) and the variable MyFrequency (first letter capitalised) are processed as the same variable. Using mixed case to improve pronunciation is a good idea.<br />
<br />
<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many samples This is. It is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed here. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin <br />
<br />
slider1:100<0,100,1>Volume <br />
<br />
@slider <br />
<br />
scaler = slider1/100; <br />
<br />
@sample <br />
<br />
spl0 *= scaler; <br />
<br />
spl1 *= scaler; <br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
A slider is defined at the top of the file which ranges from 0 to 100 with step sizes of 1 and an initial value of 100.<br />
Whenever the slider is moved the variable scaler is calculated based on the slider value. The slider ranges from 0 to 100 but scaler ranges from 0 to 1.<br />
Every time a sample is about to be played, the left and right channels get multiplied by the scaler variable.<br />
You can try playing around with this. What happens if you comment out the calculation for spl0? Add a double forward slash to that line. Save the file and reload the plugin on your track. You don't need to rescan, just press control R when the plugin is selected in the FX chain.<br />
Could you add another slider called Pan that ranges from -100 to +100 and changes the balance of the audio?<br />
<br />
== First MIDI Plugin ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
<br />
desc:My first Midi <br />
<br />
slider1:0<-24,24,1>Offset<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 == 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
: msg1 & 0xF0 == 0x80 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
: midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
== Tools to help write plugins ==<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbuilt editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press control R on your plugin and replace the plugin with a new instance of itself to for the changes take effect. Or have a project saved and reload it using alt F, R for recent projects.<br />
<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Go down one and you can then review each variable. Using NVDA num pad enter to activate this window also gives you first letter navigation. On each line the name of the variable is given, then its value and then the number of times the variable is used in the code.<br />
<br />
Reviewing the list of variables is particularly useful to check if there is a typo in the code. A screen reader will not pronounce the two variables ChekX and CheckX differently but if you notice two variables in the list where you would expect only one then there is probably a typo in one of the variable names. Or sometimes you might call a variable NoteOn and somewhere else call it OnNote.<br />
<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
It is possible to write debug messages to the screen as the program runs. This might help in determining if a certain bit of code was executed for instance. Unfortunately, because you only see the last mesage written, it isn't as useful as it could be.<br />
<br />
Use a statement like the following:<br />
<br />
sprintf(#dbg_desc, "a message, which may include values of integers %d, or floats %f", integerVar, floatVar);<br />
<br />
However, monitoring the list of variables as described above does reflect the value real-time so it can be useful particularly on slowly changing variables or those driven by user activity.<br />
<br />
Another trick is to have a slider which is written to when a particular bit of code is executed and perhaps only once:<br />
<br />
condition == 1 && !done ?<br />
<br />
(<br />
<br />
done = 1;<br />
<br />
slider64 = TestVariable;<br />
<br />
); <br />
<br />
==Resources ==<br />
<br />
Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
There is a good tutorial made by [https://www.admiralbumblebee.com/music/2018/02/08/Write-a-Reaper-MIDI-JSFX-from-scratch.html Admiral Bumblebeee] which goes through a modestly complex project to write a MIDI plugin. There is also other useful content on this web site.<br />
<br />
[https://www.reaper.fm/sdk/js/basiccode.php#js_basic The JSFX Programming Reference - Language Essentials] is on Reaper's web site. It is a reference manual though and not a tutorial but if you get into JSFX programming you will come to appreciate this resource.<br />
<br />
The Reaper community are a helpful bunch. [https://forum.cockos.com/forumdisplay.php?f=3 The JSFX forum]. Use the search feature or search with something like Google putting reaper jsfx forum in as part of your search. Sign up to post a question. </div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=625Js programming2023-11-20T20:46:09Z<p>Chessel: /* First MIDI Plugin */ Corrected code for My First MIDI so it runs though not sure about formatting on wiki page.</p>
<hr />
<div>=JSFX Programming=<br />
<br />
== Introduction ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. Disadvantages are around limited to non-existent file handling.<br />
<br />
== View and existing js plugin ==<br />
js plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a js plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.<br />
<br />
== Structure of a plugin ==<br />
A js plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
One thing I've noticed is that the @slider section runs even when a slider gains focus - i.e. when you tab to it. Thus, it is often helpful to copy slider contents into variables and then in the @slider section, compare the variable with the slider's current value to see if it has changed. If it has then update the variable and run any additional code necessary. For instance:<br />
<br />
//code start<br />
// we define a slider called s_lowpassCutoff, with initial value of 50, min and max of 20 and 100, and label "lowpass cutoff"<br />
slider1:s_lowpassCutoff=50 <20, 100, 1>lowpass cutoff<br />
<br />
<br />
@init<br />
lowpassCutoff = s_lowpassCutoff; // store the initial slider value to compare with later<br />
// do other initialization like initialize your filter, etc<br />
<br />
@slider<br />
<br />
// if slider has changed<br />
lowpassCutoff != s_lowpassCutoff ? (<br />
lowpassCutoff = s_lowpassCutoff; // update the variable<br />
// set filter cutoff etc<br />
//...<br />
);<br />
<br />
This will set the filter cutoff only if the user actually changed the slider.<br />
<br />
Note that variable names can be mixed case, but they are case folded by the compiler. This means that MyVariable is the same as myvariable however screen reader pronounciation is better with mixed case, so that's what I tend to use. Underscores can also be used in variable names, i.e. my_variable is valid.<br />
<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many sampless. This is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed and action taken accordingly. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin <br />
<br />
slider1:100<0,100,1>Volume <br />
<br />
@slider <br />
<br />
scaler = slider1/100; <br />
<br />
@sample <br />
<br />
spl0 *= scaler; <br />
<br />
spl1 *= scaler; <br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
A slider is defined at the top of the file which ranges from 0 to 100 with step sizes of 1 and an initial value of 100.<br />
Whenever the slider is moved the variable scaler is calculated based on the slider value. The slider ranges from 0 to 100 but scaler ranges from 0 to 1.<br />
Every time a sample is about to be played, the left and right channels get multiplied by the scaler variable.<br />
You can try playing around with this. What happens if you comment out the calculation for spl0? Add a double forward slash to that line. Save the file and reload the plugin on your track. You don't need to rescan, just press control R when the plugin is selected in the FX chain.<br />
Could you add another slider called Pan that ranges from -100 to +100 and changes the balance of the audio?<br />
<br />
== First MIDI Plugin ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
<br />
desc:My first Midi <br />
<br />
slider1:0<-24,24,1>Offset<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 == 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
: msg1 & 0xF0 == 0x80 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
: midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
== Tools to help write plugins ==<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbult editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press control R on your plugin and replace the plugin with a new instance of itself to for the changes take effect.<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Gone down and you can then review each variable.<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
It is possible to write debug messages to the screen as the program runs. THis might help in determining if a certain bit of code was executed for instance. Unfortunately, because you only see the last mesage written, it isn't as useful as it could be.<br />
<br />
Use a statement like the following:<br />
<br />
sprintf(#dbg_desc, "a message, which may include values of integers %d, or floats %f", integerVar, floatVar);<br />
<br />
<br />
<br />
==Resources ==<br />
<br />
There are not a whole bunch of great resources for writing js plugins. Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
There is a good tutorial made by [https://www.admiralbumblebee.com/music/2018/02/08/Write-a-Reaper-MIDI-JSFX-from-scratch.html Admiral Bumblebeee] which goes through a modestly complex project to write a MIDI plugin. There is also other useful content on this web site.<br />
<br />
[https://www.reaper.fm/sdk/js/basiccode.php#js_basic The JSFX Programming Reference - Language Essentials] is on Reaper's web site. It is a reference manual though and not a tutorial but if you get into JSFX programming you will come to appreciate this resource.<br />
<br />
The Reaper community are a helpful bunch. [https://forum.cockos.com/forumdisplay.php?f=3 The JSFX forum]. Use the search feature or search with something like Google putting reaper jsfx forum in as part of your search. Sign up to post a question. </div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Main_Page&diff=624Main Page2023-11-20T20:13:46Z<p>Chessel: /* The Reaper Accessibility Wiki */ Changed title of link for JSFX programming</p>
<hr />
<div><languages/><br />
<translate><br />
= The Reaper Accessibility Wiki = <!--T:15--><br />
<br />
<!--T:16--><br />
REAPER is a complete digital audio production application for Windows and Mac OS X, offering a full multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset. This wiki provides information for blind Reaper users. Whether you're a musician, songwriter, podcaster or audio/video editor, Reaper can more than serve your needs.<br />
<br />
<!--T:17--><br />
To start, you may wish to [[Special:MyLanguage/Getting_Started|read how to download and install Reaper, Osara and SWS.]] You can also [[Special:MyLanguage/Useful_Links_and_Resources|checkout these useful links and resources]] and the [[:Category:ArchivedSites|archived sites]].<br />
<br />
<!--T:18--><br />
Also, we are starting to make accessible and adapt the following official documents, found on the reaper website and some others:<br />
*official reaper user guide. Thanks to the author of the users guide, Geoffrey Francis' abundant generosity and patience the document is now properly tagged and can be read using your preferred screen reader and pdf reader. [http://reaper.fm/userguide.php download from reaper's official site]<br />
* [[Special:MyLanguage/ReaEffects guide|ReaEffects guide]]<br />
*the [[Special:MyLanguage/Reaper plus! the power of sws extensions|Reaper plus! the power of sws extensions]]<br />
<br />
<!--T:19--><br />
Below you will find a contents section that lists every Reaper Accessibility article on this site written for users, by users of the reaper accessibility community.<br />
<br />
<br />
== Contents (user written articles) == <!--T:20--><br />
<br />
<!--T:21--><br />
*[[Special:MyLanguage/Getting_Started|Getting Started (Downloading and Installing Reaper With accessibility]]<br />
*[[Special:MyLanguage/Keyboard_Shortcuts|Keyboard Shortcuts]]<br />
**[[Special:MyLanguage/Reaper shortcut key list by headings|Reaper shortcut key list by headings]]<br />
*[[Special:MyLanguage/Making_Your_First_Recording|Making Your First Recording In Reaper]]<br />
*[[Special:MyLanguage/Basic_editing|basic editing tasks in reaper]]<br />
*[[Special:MyLanguage/Enabling_Midi_Devices|Enabling Midi Devices]]<br />
*some ideas for [[Special:MyLanguage/editing midi in reaper using osara|editing midi in reaper using osara]]<br />
*[[Special:MyLanguage/Using_Reaper_Under_MacOs|tips for mac users]]<br />
*[[Special:MyLanguage/Monitoring levels when you can't see the meters|Monitoring levels when you can't see the meters]]<br />
*[[Special:MyLanguage/Tracks_and_Track_Folders|Tracks And Track Folders]]<br />
*[[Special:MyLanguage/Track_Templates|Track Templates]]<br />
*[[Special:MyLanguage/Project_Templates|Project Templates]]<br />
*[[Special:MyLanguage/The fast and easy way to understand compression and reaComp accessibility|The fast and easy way to understand compression and reaComp accessibility]]<br />
*[[Special:MyLanguage/Sidechaining_with_ReaComp|Setting Up a Side Chain with Reacomp]]<br />
*[[Special:MyLanguage/tapeStop effect using stretch markers|tapeStop effect using stretch markers]]<br />
*[[Special:MyLanguage/Implementing accessible automation|Implementing accessible automation]]<br />
*[[Special:MyLanguage/The_render_and_Consolidate/Export_Tracks_Dialogs|Rendering and Exporting Tracks and Projects]]<br />
*[[Special:MyLanguage/Reaper_Preferences_to_save_Disc_Space|Reaper Preferences To Save Disc Space]]<br />
*[[Special:MyLanguage/Reaper_Preferences_General|overview of Reaper Preferences (General)]]<br />
*[[Special:MyLanguage/Loop or beat slicing using reaSamploMatic|Loop or beat slicing using reaSamploMatic]]<br />
*[[Special:MyLanguage/Ideas_for_video_editing|Ideas for video editing]]<br />
*[[Special:MyLanguage/SIBIAC add on for NVDA|SIBIAC add on for NVDA]] an addon which aims to make third party fx or instrument plug-ins accessible<br />
*[[Special:MyLanguage/Reaper_and_Osara_Cookbook|Reaper and Osara Cookbook]] A problem and solution style guide to many tasks using Reaper with the Osara extension.<br />
*[[Special:MyLanguage/js_programming|JSFX Programming]]<br />
*[[Special:MyLanguage/Useful_Links_and_Resources|Useful Links and resources]]<br />
</translate></div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=621Js programming2023-11-18T08:06:37Z<p>Chessel: /* js Programming */ Changed title and looked at formatting on first example.</p>
<hr />
<div>=JSFX Programming=<br />
<br />
== Introduction ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. Disadvantages are around limited to non-existent file handling.<br />
<br />
== View and existing js plugin ==<br />
js plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a js plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.<br />
<br />
== Structure of a plugin ==<br />
A js plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
One thing I've noticed is that the @slider section runs even when a slider gains focus - i.e. when you tab to it. Thus, it is often helpful to copy slider contents into variables and then in the @slider section, compare the variable with the slider's current value to see if it has changed. If it has then update the variable and run any additional code necessary. For instance:<br />
<br />
//code start<br />
// we define a slider called s_lowpassCutoff, with initial value of 50, min and max of 20 and 100, and label "lowpass cutoff"<br />
slider1:s_lowpassCutoff=50 <20, 100, 1>lowpass cutoff<br />
<br />
<br />
@init<br />
lowpassCutoff = s_lowpassCutoff; // store the initial slider value to compare with later<br />
// do other initialization like initialize your filter, etc<br />
<br />
@slider<br />
<br />
// if slider has changed<br />
lowpassCutoff != s_lowpassCutoff ? (<br />
lowpassCutoff = s_lowpassCutoff; // update the variable<br />
// set filter cutoff etc<br />
//...<br />
);<br />
<br />
This will set the filter cutoff only if the user actually changed the slider.<br />
<br />
Note that variable names can be mixed case, but they are case folded by the compiler. This means that MyVariable is the same as myvariable however screen reader pronounciation is better with mixed case, so that's what I tend to use. Underscores can also be used in variable names, i.e. my_variable is valid.<br />
<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many sampless. This is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed and action taken accordingly. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin <br />
<br />
slider1:100<0,100,1>Volume <br />
<br />
@slider <br />
<br />
scaler = slider1/100; <br />
<br />
@sample <br />
<br />
spl0 *= scaler; <br />
<br />
spl1 *= scaler; <br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
A slider is defined at the top of the file which ranges from 0 to 100 with step sizes of 1 and an initial value of 100.<br />
Whenever the slider is moved the variable scaler is calculated based on the slider value. The slider ranges from 0 to 100 but scaler ranges from 0 to 1.<br />
Every time a sample is about to be played, the left and right channels get multiplied by the scaler variable.<br />
You can try playing around with this. What happens if you comment out the calculation for spl0? Add a double forward slash to that line. Save the file and reload the plugin on your track. You don't need to rescan, just press control R when the plugin is selected in the FX chain.<br />
Could you add another slider called Pan that ranges from -100 to +100 and changes the balance of the audio?<br />
<br />
== First MIDI Plugin ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
Desc: My first MIDI js plugin<br />
<br />
<br />
slider:0<-24,24,1>Semitone shift<br />
<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 = 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
:<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
== Tools to help write plugins ==<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbult editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press control R on your plugin and replace the plugin with a new instance of itself to for the changes take effect.<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Gone down and you can then review each variable.<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
It is possible to write debug messages to the screen as the program runs. THis might help in determining if a certain bit of code was executed for instance. Unfortunately, because you only see the last mesage written, it isn't as useful as it could be.<br />
<br />
Use a statement like the following:<br />
<br />
sprintf(#dbg_desc, "a message, which may include values of integers %d, or floats %f", integerVar, floatVar);<br />
<br />
<br />
<br />
==Resources ==<br />
<br />
There are not a whole bunch of great resources for writing js plugins. Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
There is a good tutorial made by [https://www.admiralbumblebee.com/music/2018/02/08/Write-a-Reaper-MIDI-JSFX-from-scratch.html Admiral Bumblebeee] which goes through a modestly complex project to write a MIDI plugin. There is also other useful content on this web site.<br />
<br />
[https://www.reaper.fm/sdk/js/basiccode.php#js_basic The JSFX Programming Reference - Language Essentials] is on Reaper's web site. It is a reference manual though and not a tutorial but if you get into JSFX programming you will come to appreciate this resource.<br />
<br />
The Reaper community are a helpful bunch. [https://forum.cockos.com/forumdisplay.php?f=3 The JSFX forum]. Use the search feature or search with something like Google putting reaper jsfx forum in as part of your search. Sign up to post a question. </div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=620Js programming2023-11-11T09:38:27Z<p>Chessel: /* First Audio Plugin */</p>
<hr />
<div>=js Programming=<br />
<br />
== Introduction ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. Disadvantages are around limited to non-existent file handling.<br />
<br />
== View and existing js plugin ==<br />
js plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a js plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.<br />
<br />
== Structure of a plugin ==<br />
A js plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
One thing I've noticed is that the @slider section runs even when a slider gains focus - i.e. when you tab to it. Thus, it is often helpful to copy slider contents into variables and then in the @slider section, compare the variable with the slider's current value to see if it has changed. If it has then update the variable and run any additional code necessary. For instance:<br />
<br />
//code start<br />
// we define a slider called s_lowpassCutoff, with initial value of 50, min and max of 20 and 100, and label "lowpass cutoff"<br />
slider1:s_lowpassCutoff=50 <20, 100, 1>lowpass cutoff<br />
<br />
<br />
@init<br />
lowpassCutoff = s_lowpassCutoff; // store the initial slider value to compare with later<br />
// do other initialization like initialize your filter, etc<br />
<br />
@slider<br />
<br />
// if slider has changed<br />
lowpassCutoff != s_lowpassCutoff ? (<br />
lowpassCutoff = s_lowpassCutoff; // update the variable<br />
// set filter cutoff etc<br />
//...<br />
);<br />
<br />
This will set the filter cutoff only if the user actually changed the slider.<br />
<br />
Note that variable names can be mixed case, but they are case folded by the compiler. This means that MyVariable is the same as myvariable however screen reader pronounciation is better with mixed case, so that's what I tend to use. Underscores can also be used in variable names, i.e. my_variable is valid.<br />
<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many sampless. This is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed and action taken accordingly. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin <br />
<br />
slider1:100<0,100,1>Volume <br />
<br />
@slider <br />
scaler = slider1/100; <br />
<br />
@sample <br />
spl0 *= scaler; <br />
spl1 *= scaler; <br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
A slider is defined at the top of the file which ranges from 0 to 100 with step sizes of 1 and an initial value of 100.<br />
Whenever the slider is moved the variable scaler is calculated based on the slider value. The slider ranges from 0 to 100 but scaler ranges from 0 to 1.<br />
Every time a sample is about to be played, the left and right channels get multiplied by the scaler variable.<br />
You can try playing around with this. What happens if you comment out the calculation for spl0? Add a double forward slash to that line. Save the file and reload the plugin on your track. You don't need to rescan, just press control R when the plugin is selected in the FX chain.<br />
Could you add another slider called Pan that ranges from -100 to +100 and changes the balance of the audio?<br />
<br />
== First MIDI Plugin ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
Desc: My first MIDI js plugin<br />
<br />
<br />
slider:0<-24,24,1>Semitone shift<br />
<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 = 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
:<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
== Tools to help write plugins ==<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbult editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press control R on your plugin and replace the plugin with a new instance of itself to for the changes take effect.<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Gone down and you can then review each variable.<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
It is possible to write debug messages to the screen as the program runs. THis might help in determining if a certain bit of code was executed for instance. Unfortunately, because you only see the last mesage written, it isn't as useful as it could be.<br />
<br />
Use a statement like the following:<br />
<br />
sprintf(#dbg_desc, "a message, which may include values of integers %d, or floats %f", integerVar, floatVar);<br />
<br />
<br />
<br />
==Resources ==<br />
<br />
There are not a whole bunch of great resources for writing js plugins. Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
There is a good tutorial made by [https://www.admiralbumblebee.com/music/2018/02/08/Write-a-Reaper-MIDI-JSFX-from-scratch.html Admiral Bumblebeee] which goes through a modestly complex project to write a MIDI plugin. There is also other useful content on this web site.<br />
<br />
[https://www.reaper.fm/sdk/js/basiccode.php#js_basic The JSFX Programming Reference - Language Essentials] is on Reaper's web site. It is a reference manual though and not a tutorial but if you get into JSFX programming you will come to appreciate this resource.<br />
<br />
The Reaper community are a helpful bunch. [https://forum.cockos.com/forumdisplay.php?f=3 The JSFX forum]. Use the search feature or search with something like Google putting reaper jsfx forum in as part of your search. Sign up to post a question. </div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=618Js programming2023-11-07T19:45:46Z<p>Chessel: /* Tools to help write plugins */</p>
<hr />
<div>=js Programming=<br />
<br />
== Introduction ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. Disadvantages are around limited to non-existent file handling.<br />
<br />
== View and existing js plugin ==<br />
js plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a js plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.<br />
<br />
== Structure of a plugin ==<br />
A js plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many sampless. This is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed and action taken accordingly. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin<br />
<br />
<br />
slider:100<0,100,1>Volume<br />
<br />
<br />
@slider<br />
<br />
scaler = slider1/100;<br />
<br />
<br />
@sample<br />
<br />
spl0 *= scaler;<br />
<br />
spl1 *= scaler;<br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
== First MIDI Plugin ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
Desc: My first MIDI js plugin<br />
<br />
<br />
slider:0<-24,24,1>Semitone shift<br />
<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 = 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
:<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
== Tools to help write plugins ==<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbult editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press contrl R on your plugin and replace the plugin with a new instance of itself to for the changes take effect.<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Gone down and you can then review each variable.<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
==Resources ==<br />
<br />
There are not a whole bunch of great resources for writing js plugins. Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
There is a good tutorial made by [https://www.admiralbumblebee.com/music/2018/02/08/Write-a-Reaper-MIDI-JSFX-from-scratch.html Admiral Bumblebeee] which goes through a modestly complex project to write a MIDI plugin. There is also other useful content on this web site.<br />
<br />
[https://www.reaper.fm/sdk/js/basiccode.php#js_basic The JSFX Programming Reference - Language Essentials] is on Reaper's web site. It is a reference manual though and not a tutorial but if you get into JSFX programming you will come to appreciate this resource.<br />
<br />
The Reaper community are a helpful bunch. [https://forum.cockos.com/forumdisplay.php?f=3 The JSFX forum]. Use the search feature or search with something like Google putting reaper jsfx forum in as part of your search. Sign up to post a question. </div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=617Js programming2023-11-02T22:38:10Z<p>Chessel: /* js Programming */ Corrected headings.</p>
<hr />
<div>=js Programming=<br />
<br />
== Introduction ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. Disadvantages are around limited to non-existent file handling.<br />
<br />
== View and existing js plugin ==<br />
js plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a js plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.<br />
<br />
== Structure of a plugin ==<br />
A js plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many sampless. This is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed and action taken accordingly. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin<br />
<br />
<br />
slider:100<0,100,1>Volume<br />
<br />
<br />
@slider<br />
<br />
scaler = slider1/100;<br />
<br />
<br />
@sample<br />
<br />
spl0 *= scaler;<br />
<br />
spl1 *= scaler;<br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
== First MIDI Plugin ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
Desc: My first MIDI js plugin<br />
<br />
<br />
slider:0<-24,24,1>Semitone shift<br />
<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 = 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
:<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
== Tools to help write plugins ==<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbult editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press contrl R on your plugin and replace the plugin with a new instance of itself to for the changes take effect.<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Gone down and you can then review each variable.<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
Resources<br />
<br />
<br />
There are not a whole bunch of great resources for writing js plugins. Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
<br />
There is a good tutorial made by Admirable Bumble Bee which goes through a modestly complex project to write a MIDI plugin. There is also other content on this web site.<br />
<br />
<br />
The user manual for the js plugin language is on Reaper's web site. It is a reference manual though and not a tutorial.<br />
<br />
The Reaper community are a helpful bunch. Click on the Forum link from the Reaper homepage and sign up. There is a js plugin and reaScript forum where you can ask questions and see other questions and answers. There is a search option for each forum or include "Reaper js plugin forum" in a search engine query.</div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=616Js programming2023-11-02T22:32:50Z<p>Chessel: /* js Programming */ First draft of majority of initial content</p>
<hr />
<div>=js Programming=<br />
<br />
== Introduction == ==<br />
js plugins are Reaper's own plugin format similar in many ways to VST plugins. A js plugin can process and generate audio and midi data and expose parameters to the user which can be automated.<br />
<br />
js plugins have a number of advantages such as easy to start writing, all parameters are exposed and these parameters are easy to interact with via a keyboard either directly in the user interface or by the OSARA parameter dialogue. They also support graphics making them good for sighted users and it is also possible to add keyboard support though this is almost vanishingly rare. Disadvantages are around limited to non-existent file handling.<br />
<br />
== View and existing js plugin== ==<br />
js plugins are written in plain text files and there are plenty to take a look at. From the Reaper Help Options menu select Resource path. In here is a folder called "Effects" in which are all the js plugins that come with Reaper.<br />
<br />
Typically a js plugin either has no file extension or an extension of jsfx. Use your favourite plain text editor to open up any of the files to see what they look like.<br />
<br />
It is useful to turn the vebosity of your screen reader so it speaks all characters. It is important to capture all the code when programming. For example, a semicolon is required at the end of each command and most people dont set their screen reader to announce these.<br />
<br />
In NVDA, the verbosity can be cycled with NVDA+P.<br />
<br />
== Structure of a plugin== ==<br />
A js plugin is made up of a header and then a series of sections which have a predefined named and purpose.<br />
<br />
<br />
The header can be as short as a declaration of the name of the plugin but can also hold much more information such as the author, date, version, release notes, instructions on usage and other information that helps with reaPack integration.<br />
<br />
<br />
The header is followed by definition of the plugin parameters which is done by defining a slider for each parameter. A slider has a min value, a max value, an increment value and a default value. These are seen by the user in the plugin user interface as a slider and edit box for each parameter.<br />
<br />
<br />
The @init block is run when the plugin first starts which is typically when it is first loaded onto an FX chain and when play starts. It is used to initialise variables to default values. Note that the js plugin language does not require variables to be declared before they are used so this section does not need to include initialisation of all variables if this is done elsewhere. Also, the default initialisation of a variable is to set it to zero.<br />
<br />
<br />
The @slider block is run whenever a parameter is changed either through automation or by the user. For example, a parameter might be presented to the user as a percentage from 0 to 100 but the code needs this rescaling from -1 to 1.<br />
<br />
<br />
The @block code is run as a new block of samples arrives. The block size as defined in Reaper preferences in the devices section dictates how many sampless. This is an area of code commonly used to process MIDI as all the MIDI notes and events coming up in the next block of samples can be processed and action taken accordingly. Also, MIDI notes and events can be inserted so they are played once the block enters Reaper's play buffer.<br />
<br />
<br />
The@sample block is run every sample. So yes, many thousands of times a second. Commonly used to process audio as there is easy access to the value of the audio in each channel.<br />
<br />
<br />
The @gfx block is used to draw graphics and process keyboard input. I'm not sure when it is run.<br />
<br />
== First Audio Plugin== ==<br />
Let's dive in with a very simple js plugin that includes a volume control for audio. Open up a plain text editor and copy and paste the following code into it.<br />
<br />
<br />
Desc: My first audio plugin<br />
<br />
<br />
slider:100<0,100,1>Volume<br />
<br />
<br />
@slider<br />
<br />
scaler = slider1/100;<br />
<br />
<br />
@sample<br />
<br />
spl0 *= scaler;<br />
<br />
spl1 *= scaler;<br />
<br />
<br />
Save this in the Reaper resources Effects folder, ideally in a new subfolder to contain all your plugins. Start up Reaper and it should do a rescan and make your new js plugin available to use.<br />
<br />
<br />
Create a track and add some audio to it for example recording yourself speaking, by inserting an audio file or selecting something from media explorer. Hit F on the track to bring up the FX chain dialogue and use the Add button to add your plugin. Type in "first" as this is text included in the first line of the code copied into the plugin and is the name given to the plugin. Arrow down and you should find the plugin. Hit enter and it will get loaded onto the FX chain for the track. Press tab to work your way through the plugin and you will come to the slider and edit controls for the volume parameter.<br />
<br />
<br />
Press space to play the audio and then adjust the volume with either the slider or entering a new value in the edit field. The volume changes. Your first plugin.<br />
<br />
== First MIDI Plugin== ==<br />
Here is a simple plugin that has a slider to change the pitch of any incoming MIDI notes. The minimum code for MIDI is a little more than for audio.<br />
<br />
<br />
Desc: My first MIDI js plugin<br />
<br />
<br />
slider:0<-24,24,1>Semitone shift<br />
<br />
<br />
@slider<br />
<br />
shift = slider1;<br />
<br />
<br />
@block<br />
<br />
while( midirecv( offset, msg1, msg2, msg3 ) )<br />
<br />
(<br />
<br />
msg1 & 0xF0 = 0x90 ?<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2 + shift, msg3 );<br />
<br />
)<br />
<br />
:<br />
<br />
(<br />
<br />
midisend( offset, msg1, msg2, msg3 );<br />
<br />
);<br />
<br />
);<br />
<br />
<br />
In the same way as with the audio plugin, copy this code into a plain text file and save it in the Effects subfolder in the Reaper resource path ideally in your own subfolder holding all your plugins. Start up Reaper so it does a rescan and then insert reaSynth onto a track as as a VSTi. Test you can play notes. Now add your first MIDI plugin onto this track as well. Before it has any effect thugh yu need to move reaSynth so it is below your first MIDI plugin since the plugin needs to update the MIDI data between it being played and it arriving at reaSynth. Do this by either cutting and pasting reaSynth so it is second in the chain, or using the action bound to control-shift alt page down (Windows).<br />
<br />
<br />
Tab to the Semitone shift slider in your new plugin. Play a note and then change the slider. The pitch of notes is shifted.<br />
<br />
<nowiki>==Tools to help write plugins==</nowiki><br />
<br />
The most basic tool is your plain text editor of choice. Reaper does have an inbult editor but it is not easily accessible. So writing code in a plain text editor is the next best thing. If you make a change to your code and save it though, you will need to return to Reaper and the FX chain , press contrl R on your plugin and replace the plugin with a new instance of itself to for the changes take effect.<br />
<br />
<br />
It is possible to view all the variables used in a plugin along with their values. This can be done with NVDA object navigation by tabbing to the edit button in the FX dialogue, hitting enter , and uing object navigation to move right until a list control is reached. Gone down and you can then review each variable.<br />
<br />
<br />
Debugging is difficult though in js plugins. There is no option to display a message box or output diagnostic info to a file. And some variables will change their value with every sample or every block making them impossible to track. You cannot step through the code one line at a time reviewing variable values like you can in more complex IDE's.<br />
<br />
Resources<br />
<br />
<br />
There are not a whole bunch of great resources for writing js plugins. Probably the most comprehensive source of information are all the plugins that come with Reaper and found in the Effects folder. But these can be complex and difficult to work out how they work.<br />
<br />
<br />
There is a good tutorial made by Admirable Bumble Bee which goes through a modestly complex project to write a MIDI plugin. There is also other content on this web site.<br />
<br />
<br />
The user manual for the js plugin language is on Reaper's web site. It is a reference manual though and not a tutorial.<br />
<br />
The Reaper community are a helpful bunch. Click on the Forum link from the Reaper homepage and sign up. There is a js plugin and reaScript forum where you can ask questions and see other questions and answers. There is a search option for each forum or include "Reaper js plugin forum" in a search engine query.</div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=615Js programming2023-11-02T21:59:57Z<p>Chessel: </p>
<hr />
<div>=js Programming=<br />
This page is an introduction to programming js plugins.</div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Js_programming&diff=614Js programming2023-11-02T21:54:14Z<p>Chessel: Created page with "<-js Programming-> This page is an introduction to programming js plugins."</p>
<hr />
<div><-js Programming-><br />
This page is an introduction to programming js plugins.</div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Main_Page&diff=612Main Page2023-10-29T21:53:51Z<p>Chessel: Made js programming a title</p>
<hr />
<div><languages/><br />
<translate><br />
= The Reaper Accessibility Wiki = <!--T:15--><br />
<br />
<!--T:16--><br />
REAPER is a complete digital audio production application for Windows and Mac OS X, offering a full multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset. This wiki provides information for blind Reaper users. Whether you're a musician, songwriter, podcaster or audio/video editor, Reaper can more than serve your needs.<br />
<br />
<!--T:17--><br />
To start, you may wish to [[Special:MyLanguage/Getting_Started|read how to download and install Reaper, Osara and SWS.]] You can also [[Special:MyLanguage/Useful_Links_and_Resources|checkout these useful links and resources]] and the [[:Category:ArchivedSites|archived sites]].<br />
<br />
<!--T:18--><br />
Also, we are starting to make accessible and adapt the following official documents, found on the reaper website and some others:<br />
*official reaper user guide. Thanks to the author of the users guide, Geoffrey Francis' abundant generosity and patience the document is now properly tagged and can be read using your preferred screen reader and pdf reader. [http://reaper.fm/userguide.php download from reaper's official site]<br />
* [[Special:MyLanguage/ReaEffects guide|ReaEffects guide]]<br />
*the [[Special:MyLanguage/Reaper plus! the power of sws extensions|Reaper plus! the power of sws extensions]]<br />
<br />
<!--T:19--><br />
Below you will find a contents section that lists every Reaper Accessibility article on this site written for users, by users of the reaper accessibility community.<br />
<br />
<br />
== Contents (user written articles) == <!--T:20--><br />
<br />
<!--T:21--><br />
*[[Special:MyLanguage/Getting_Started|Getting Started (Downloading and Installing Reaper With accessibility]]<br />
*[[Special:MyLanguage/Keyboard_Shortcuts|Keyboard Shortcuts]]<br />
**[[Special:MyLanguage/Reaper shortcut key list by headings|Reaper shortcut key list by headings]]<br />
*[[Special:MyLanguage/Making_Your_First_Recording|Making Your First Recording In Reaper]]<br />
*[[Special:MyLanguage/Basic_editing|basic editing tasks in reaper]]<br />
*[[Special:MyLanguage/Enabling_Midi_Devices|Enabling Midi Devices]]<br />
*some ideas for [[Special:MyLanguage/editing midi in reaper using osara|editing midi in reaper using osara]]<br />
*[[Special:MyLanguage/Using_Reaper_Under_MacOs|tips for mac users]]<br />
*[[Special:MyLanguage/Monitoring levels when you can't see the meters|Monitoring levels when you can't see the meters]]<br />
*[[Special:MyLanguage/Tracks_and_Track_Folders|Tracks And Track Folders]]<br />
*[[Special:MyLanguage/Track_Templates|Track Templates]]<br />
*[[Special:MyLanguage/Project_Templates|Project Templates]]<br />
*[[Special:MyLanguage/The fast and easy way to understand compression and reaComp accessibility|The fast and easy way to understand compression and reaComp accessibility]]<br />
*[[Special:MyLanguage/Sidechaining_with_ReaComp|Setting Up a Side Chain with Reacomp]]<br />
*[[Special:MyLanguage/tapeStop effect using stretch markers|tapeStop effect using stretch markers]]<br />
*[[Special:MyLanguage/Implementing accessible automation|Implementing accessible automation]]<br />
*[[Special:MyLanguage/The_render_and_Consolidate/Export_Tracks_Dialogs|Rendering and Exporting Tracks and Projects]]<br />
*[[Special:MyLanguage/Reaper_Preferences_to_save_Disc_Space|Reaper Preferences To Save Disc Space]]<br />
*[[Special:MyLanguage/Reaper_Preferences_General|overview of Reaper Preferences (General)]]<br />
*[[Special:MyLanguage/Loop or beat slicing using reaSamploMatic|Loop or beat slicing using reaSamploMatic]]<br />
*[[Special:MyLanguage/Ideas_for_video_editing|Ideas for video editing]]<br />
*[[Special:MyLanguage/SIBIAC add on for NVDA|SIBIAC add on for NVDA]] an addon which aims to make third party fx or instrument plug-ins accessible<br />
*[[Special:MyLanguage/Reaper_and_Osara_Cookbook|Reaper and Osara Cookbook]] A problem and solution style guide to many tasks using Reaper with the Osara extension.<br />
*<nowiki>[[js programming]]</nowiki><br />
*[[Special:MyLanguage/Useful_Links_and_Resources|Useful Links and resources]]<br />
</translate></div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Main_Page&diff=611Main Page2023-10-29T09:26:55Z<p>Chessel: Added js programming bullet point</p>
<hr />
<div><languages/><br />
<translate><br />
= The Reaper Accessibility Wiki = <!--T:15--><br />
<br />
<!--T:16--><br />
REAPER is a complete digital audio production application for Windows and Mac OS X, offering a full multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset. This wiki provides information for blind Reaper users. Whether you're a musician, songwriter, podcaster or audio/video editor, Reaper can more than serve your needs.<br />
<br />
<!--T:17--><br />
To start, you may wish to [[Special:MyLanguage/Getting_Started|read how to download and install Reaper, Osara and SWS.]] You can also [[Special:MyLanguage/Useful_Links_and_Resources|checkout these useful links and resources]] and the [[:Category:ArchivedSites|archived sites]].<br />
<br />
<!--T:18--><br />
Also, we are starting to make accessible and adapt the following official documents, found on the reaper website and some others:<br />
*official reaper user guide. Thanks to the author of the users guide, Geoffrey Francis' abundant generosity and patience the document is now properly tagged and can be read using your preferred screen reader and pdf reader. [http://reaper.fm/userguide.php download from reaper's official site]<br />
* [[Special:MyLanguage/ReaEffects guide|ReaEffects guide]]<br />
*the [[Special:MyLanguage/Reaper plus! the power of sws extensions|Reaper plus! the power of sws extensions]]<br />
<br />
<!--T:19--><br />
Below you will find a contents section that lists every Reaper Accessibility article on this site written for users, by users of the reaper accessibility community.<br />
<br />
<br />
== Contents (user written articles) == <!--T:20--><br />
<br />
<!--T:21--><br />
*[[Special:MyLanguage/Getting_Started|Getting Started (Downloading and Installing Reaper With accessibility]]<br />
*[[Special:MyLanguage/Keyboard_Shortcuts|Keyboard Shortcuts]]<br />
**[[Special:MyLanguage/Reaper shortcut key list by headings|Reaper shortcut key list by headings]]<br />
*[[Special:MyLanguage/Making_Your_First_Recording|Making Your First Recording In Reaper]]<br />
*[[Special:MyLanguage/Basic_editing|basic editing tasks in reaper]]<br />
*[[Special:MyLanguage/Enabling_Midi_Devices|Enabling Midi Devices]]<br />
*some ideas for [[Special:MyLanguage/editing midi in reaper using osara|editing midi in reaper using osara]]<br />
*[[Special:MyLanguage/Using_Reaper_Under_MacOs|tips for mac users]]<br />
*[[Special:MyLanguage/Monitoring levels when you can't see the meters|Monitoring levels when you can't see the meters]]<br />
*[[Special:MyLanguage/Tracks_and_Track_Folders|Tracks And Track Folders]]<br />
*[[Special:MyLanguage/Track_Templates|Track Templates]]<br />
*[[Special:MyLanguage/Project_Templates|Project Templates]]<br />
*[[Special:MyLanguage/The fast and easy way to understand compression and reaComp accessibility|The fast and easy way to understand compression and reaComp accessibility]]<br />
*[[Special:MyLanguage/Sidechaining_with_ReaComp|Setting Up a Side Chain with Reacomp]]<br />
*[[Special:MyLanguage/tapeStop effect using stretch markers|tapeStop effect using stretch markers]]<br />
*[[Special:MyLanguage/Implementing accessible automation|Implementing accessible automation]]<br />
*[[Special:MyLanguage/The_render_and_Consolidate/Export_Tracks_Dialogs|Rendering and Exporting Tracks and Projects]]<br />
*[[Special:MyLanguage/Reaper_Preferences_to_save_Disc_Space|Reaper Preferences To Save Disc Space]]<br />
*[[Special:MyLanguage/Reaper_Preferences_General|overview of Reaper Preferences (General)]]<br />
*[[Special:MyLanguage/Loop or beat slicing using reaSamploMatic|Loop or beat slicing using reaSamploMatic]]<br />
*[[Special:MyLanguage/Ideas_for_video_editing|Ideas for video editing]]<br />
*[[Special:MyLanguage/SIBIAC add on for NVDA|SIBIAC add on for NVDA]] an addon which aims to make third party fx or instrument plug-ins accessible<br />
*[[Special:MyLanguage/Reaper_and_Osara_Cookbook|Reaper and Osara Cookbook]] A problem and solution style guide to many tasks using Reaper with the Osara extension.<br />
*js programming<br />
*[[Special:MyLanguage/Useful_Links_and_Resources|Useful Links and resources]]<br />
</translate></div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Main_Page&diff=610Main Page2023-10-29T09:23:33Z<p>Chessel: /* Contents (user written articles) */ Added bullet point for js programming</p>
<hr />
<div><languages/><br />
<translate><br />
= The Reaper Accessibility Wiki = <!--T:15--><br />
<br />
<!--T:16--><br />
REAPER is a complete digital audio production application for Windows and Mac OS X, offering a full multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset. This wiki provides information for blind Reaper users. Whether you're a musician, songwriter, podcaster or audio/video editor, Reaper can more than serve your needs.<br />
<br />
<!--T:17--><br />
To start, you may wish to [[Special:MyLanguage/Getting_Started|read how to download and install Reaper, Osara and SWS.]] You can also [[Special:MyLanguage/Useful_Links_and_Resources|checkout these useful links and resources]] and the [[:Category:ArchivedSites|archived sites]].<br />
<br />
<!--T:18--><br />
Also, we are starting to make accessible and adapt the following official documents, found on the reaper website and some others:<br />
*official reaper user guide. Thanks to the author of the users guide, Geoffrey Francis' abundant generosity and patience the document is now properly tagged and can be read using your preferred screen reader and pdf reader. [http://reaper.fm/userguide.php download from reaper's official site]<br />
* [[Special:MyLanguage/ReaEffects guide|ReaEffects guide]]<br />
*the [[Special:MyLanguage/Reaper plus! the power of sws extensions|Reaper plus! the power of sws extensions]]<br />
<br />
<!--T:19--><br />
Below you will find a contents section that lists every Reaper Accessibility article on this site written for users, by users of the reaper accessibility community.<br />
<br />
<br />
== Contents (user written articles) == <!--T:20--><br />
<br />
<!--T:21--><br />
*[[Special:MyLanguage/Getting_Started|Getting Started (Downloading and Installing Reaper With accessibility]]<br />
*[[Special:MyLanguage/Keyboard_Shortcuts|Keyboard Shortcuts]]<br />
**[[Special:MyLanguage/Reaper shortcut key list by headings|Reaper shortcut key list by headings]]<br />
*[[Special:MyLanguage/Making_Your_First_Recording|Making Your First Recording In Reaper]]<br />
*[[Special:MyLanguage/Basic_editing|basic editing tasks in reaper]]<br />
*[[Special:MyLanguage/Enabling_Midi_Devices|Enabling Midi Devices]]<br />
*some ideas for [[Special:MyLanguage/editing midi in reaper using osara|editing midi in reaper using osara]]<br />
*[[Special:MyLanguage/Using_Reaper_Under_MacOs|tips for mac users]]<br />
*[[Special:MyLanguage/Monitoring levels when you can't see the meters|Monitoring levels when you can't see the meters]]<br />
*[[Special:MyLanguage/Tracks_and_Track_Folders|Tracks And Track Folders]]<br />
*[[Special:MyLanguage/Track_Templates|Track Templates]]<br />
*[[Special:MyLanguage/Project_Templates|Project Templates]]<br />
*[[Special:MyLanguage/The fast and easy way to understand compression and reaComp accessibility|The fast and easy way to understand compression and reaComp accessibility]]<br />
*[[Special:MyLanguage/Sidechaining_with_ReaComp|Setting Up a Side Chain with Reacomp]]<br />
*[[Special:MyLanguage/tapeStop effect using stretch markers|tapeStop effect using stretch markers]]<br />
*[[Special:MyLanguage/Implementing accessible automation|Implementing accessible automation]]<br />
*[[Special:MyLanguage/The_render_and_Consolidate/Export_Tracks_Dialogs|Rendering and Exporting Tracks and Projects]]<br />
*[[Special:MyLanguage/Reaper_Preferences_to_save_Disc_Space|Reaper Preferences To Save Disc Space]]<br />
*[[Special:MyLanguage/Reaper_Preferences_General|overview of Reaper Preferences (General)]]<br />
*[[Special:MyLanguage/Loop or beat slicing using reaSamploMatic|Loop or beat slicing using reaSamploMatic]]<br />
*[[Special:MyLanguage/Ideas_for_video_editing|Ideas for video editing]]<br />
*[[Special:MyLanguage/SIBIAC add on for NVDA|SIBIAC add on for NVDA]] an addon which aims to make third party fx or instrument plug-ins accessible<br />
*[[Special:MyLanguage/Reaper_and_Osara_Cookbook|Reaper and Osara Cookbook]] A problem and solution style guide to many tasks using Reaper with the Osara extension.<br />
*[[Special:MyLanguage/Project_Templates|js programming]]<br />
* [[Special:MyLanguage/Useful_Links_and_Resources|Useful Links and resources]]<br />
</translate></div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Main_Page&diff=609Main Page2023-10-29T09:09:08Z<p>Chessel: /* Contents (user written articles) */</p>
<hr />
<div><languages/><br />
<translate><br />
= The Reaper Accessibility Wiki = <!--T:15--><br />
<br />
<!--T:16--><br />
REAPER is a complete digital audio production application for Windows and Mac OS X, offering a full multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset. This wiki provides information for blind Reaper users. Whether you're a musician, songwriter, podcaster or audio/video editor, Reaper can more than serve your needs.<br />
<br />
<!--T:17--><br />
To start, you may wish to [[Special:MyLanguage/Getting_Started|read how to download and install Reaper, Osara and SWS.]] You can also [[Special:MyLanguage/Useful_Links_and_Resources|checkout these useful links and resources]] and the [[:Category:ArchivedSites|archived sites]].<br />
<br />
<!--T:18--><br />
Also, we are starting to make accessible and adapt the following official documents, found on the reaper website and some others:<br />
*official reaper user guide. Thanks to the author of the users guide, Geoffrey Francis' abundant generosity and patience the document is now properly tagged and can be read using your preferred screen reader and pdf reader. [http://reaper.fm/userguide.php download from reaper's official site]<br />
* [[Special:MyLanguage/ReaEffects guide|ReaEffects guide]]<br />
*the [[Special:MyLanguage/Reaper plus! the power of sws extensions|Reaper plus! the power of sws extensions]]<br />
<br />
<!--T:19--><br />
Below you will find a contents section that lists every Reaper Accessibility article on this site written for users, by users of the reaper accessibility community.<br />
<br />
<br />
== Contents (user written articles) == <!--T:20--><br />
<br />
<!--T:21--><br />
*[[Special:MyLanguage/Getting_Started|Getting Started (Downloading and Installing Reaper With accessibility]]<br />
*[[Special:MyLanguage/Keyboard_Shortcuts|Keyboard Shortcuts]]<br />
**[[Special:MyLanguage/Reaper shortcut key list by headings|Reaper shortcut key list by headings]]<br />
*[[Special:MyLanguage/Making_Your_First_Recording|Making Your First Recording In Reaper]]<br />
*[[Special:MyLanguage/Basic_editing|basic editing tasks in reaper]]<br />
*[[Special:MyLanguage/Enabling_Midi_Devices|Enabling Midi Devices]]<br />
*some ideas for [[Special:MyLanguage/editing midi in reaper using osara|editing midi in reaper using osara]]<br />
*[[Special:MyLanguage/Using_Reaper_Under_MacOs|tips for mac users]]<br />
*[[Special:MyLanguage/Monitoring levels when you can't see the meters|Monitoring levels when you can't see the meters]]<br />
*[[Special:MyLanguage/Tracks_and_Track_Folders|Tracks And Track Folders]]<br />
*[[Special:MyLanguage/Track_Templates|Track Templates]]<br />
*[[Special:MyLanguage/Project_Templates|Project Templates]]<br />
*[[Special:MyLanguage/The fast and easy way to understand compression and reaComp accessibility|The fast and easy way to understand compression and reaComp accessibility]]<br />
*[[Special:MyLanguage/Sidechaining_with_ReaComp|Setting Up a Side Chain with Reacomp]]<br />
*[[Special:MyLanguage/tapeStop effect using stretch markers|tapeStop effect using stretch markers]]<br />
*[[Special:MyLanguage/Implementing accessible automation|Implementing accessible automation]]<br />
*[[Special:MyLanguage/The_render_and_Consolidate/Export_Tracks_Dialogs|Rendering and Exporting Tracks and Projects]]<br />
*[[Special:MyLanguage/Reaper_Preferences_to_save_Disc_Space|Reaper Preferences To Save Disc Space]]<br />
*[[Special:MyLanguage/Reaper_Preferences_General|overview of Reaper Preferences (General)]]<br />
*[[Special:MyLanguage/Loop or beat slicing using reaSamploMatic|Loop or beat slicing using reaSamploMatic]]<br />
*[[Special:MyLanguage/Ideas_for_video_editing|Ideas for video editing]]<br />
*[[Special:MyLanguage/SIBIAC add on for NVDA|SIBIAC add on for NVDA]] an addon which aims to make third party fx or instrument plug-ins accessible<br />
*[[Special:MyLanguage/Reaper_and_Osara_Cookbook|Reaper and Osara Cookbook]] A problem and solution style guide to many tasks using Reaper with the Osara extension.<br />
*js plugin programming <br />
* [[Special:MyLanguage/Useful_Links_and_Resources|Useful Links and resources]]<br />
</translate></div>Chesselhttps://www.reaperaccessibility.com/index.php?title=Reaper_Preferences_General&diff=39Reaper Preferences General2023-05-30T16:46:06Z<p>Chessel: Testing of ability to edit. Changed stick to are sticky</p>
<hr />
<div>=Preferences=<br />
<br />
Below are some of the options in the preferences dialogue (control + P) which are commonly changed from their default values. Useful to review when learning Reaper or after a reset to factory defaults.<br />
<br />
Note that changes to preferences are sticky from one load of Reaper to another. There are other options in Reaper, such as metronome settings, which are part of the default project settings and only persist once the Save As Default button is used in project settings (alt _+ enter).<br />
<br />
<br />
<br />
*General<br />
** There are tick boxes for what creates an undo item. Untick to shorten the undo history.<br />
** Option to preserve undo history when saving a project.<br />
** Several options on how Reaper behaves when starting up such as load last project, start a new project or prompt. Also can check for new versions of Reaper and an option to allow multiple instances of Reaper to be run.<br />
*Paths<br />
** Option to set a specific folder to store peak files (reapeaks). Can then clear this folder out from time to time.<br />
*Keyboard / multitouch<br />
** Recommend ticking Allow space key to be used for navigation in various windows<br />
*Projects<br />
** Option to define a default project template <br />
** Prompt to save on new project. Tick this if you want to be forced to define a path for all your projects which means you know where your media is going.<br />
** Options to autosave project backups into a defined subfolder. Suggestion is to store to a subfolder called Backups every 10 or 15 minutes. Backup files are generally small.<br />
** Option to save the undo history.<br />
*Media Item defaults<br />
** Default fade in and fade out time is 10ms. Can reduce to 3ms to be less obtrusive. Is If looping and splitting samples may want to reduce this to zero to avoid dips in volume between samples. Alternatively, can raise these values to get modulation effects when splitting an item at grid lines.<br />
*Audio<br />
** Recommended to turn off tiny fade in and fade out on start and stop.<br />
*Devices and MIDI<br />
** Fundamental section specific to equipment set up for input and output of audio and MIDI<br />
*Buffering<br />
** Can reduce Default Media Buffer size from 1200 to around 100 for more responsivness on playback.<br />
*Playback<br />
** Recommend ticking Stop playback at end of loop if repeat is disabled. This links with other settings in Edditing.<br />
*Recording<br />
** Recommend disabling Show preview of recording items while recording <br />
** Options to prompt to save or discard newly recorded material on stop. Often easier to disable this and use control + Z to undo recorded media if new material isn't wanted.<br />
** Option to define the name given to newly recorded items<br />
*Rendering<br />
** Option to override the default buffer size when rendering which can speed up render times e.g. Can set to 1024.<br />
** Options to set a tail duration and when it is applied to capture effects like reverb.<br />
*Editting<br />
** Can set Move edit cursor to start of time selection on time selection change. So when ending a time selection with right bracket edit cursor moves to the start of the time selection.<br />
** Option to set moving edit cursor to end of item when pasting. Useful if pasting multiple copies of an item one after another. Can also cause confusion though as means have to rewind to hear newly pasted content.<br />
** Link loop points to time selection. Set this to on so that option in Playback section works effectively. Can unlink loop points and time selection in the options menu if needed for a particular workflow.<br />
*Envelope display<br />
** Options here to change the range of volume and pitch envelopes.<br />
*Media<br />
** Option on copying media to project directory <br />
** Options for rendering tails on item FX. Defaults are quite short. Values of 5000 to 10,000 more useful.<br />
** Can untick Show status window when generating peaks as this is just annoying.<br />
*MIDI<br />
** Some default options for how to treat MIDI files being imported<br />
*Plugins<br />
** Numerous options on how to display FX windows. Typically do want to auto-resize, uncheck auto-float newly created windows, don't want to dock, and tick display only one window at a time but this last doesn't really work very well.<br />
*Compatibility<br />
** Options in here on how to treat 32-bit plugins by default but can also do this each plugin at a time using the context menu when highlighting a plugin in the FX search dialogue.<br />
*VST<br />
** Fundamental option to define the paths that Reaper uses when searching for and loading VST's.<br />
*External editors<br />
** Define the path of external editors</div>Chessel