First of all, thank you so much for your support. You are awesome! I hope you enjoy this product and make some amazing sounds with it :)
With your purchase of a license, you are entitled to free updates + exceptional support from me directly. This user guide should help with the most common issues, so please look for help here before emailing me.
Your license key will activate up to 3 computers (more activations can be provided at my discretion). Your license key is for your own personal use and may be used for commercial or non-commercial work. If you share your license key with anyone else, it will be revoked and you will not get a refund.
For a site license, just purchase as many copies as you need and activations will be added to the same license key.
All scripts come with a free 14-day trial. In order to start the trial, follow the instructions below to install the script and leave the license key field blank when prompted.
In order to install this script you will need to first install ReaPack. It's an amazing way for people to easily share REAPER scripts with other users and will allow for this script and all other scripts to be easily updated from within REAPER. For more info on how to use ReaPack go here.
ReaPack Repository: https://nvk.tools/index.xml
Note: If you would like to automatically stay up to date with this and other ReaPack Repositories, you can select Extensions-ReaPack-Manage repositories and then Options-Install new packages when synchronizing. Then, when you select Extensions-ReaPack->Synchronize packages it will automatically install all new scripts.
You will also need to install ReaImgui from the ReaTeam Extensions Repository. This repository is included with ReaPack by default so you should have it already. The instructions are the same as installing the main script, just make sure you have the repository enabled, search for 'ReaImgui' in ReaPack and install it.
Download SWS/S&M Extension and follow the instructions to install
Once you have the script installed, load your actions list and search "nvk" to locate the script. Double-click it or assign it to a hotkey and run the script. You will be prompted to input your license key, which you should have recieved immediately after purchasing the script.
This script is only guaranteed to work on the latest version of REAPER and SWS/S&M 64-bit. 32-bit is not supported. Make sure you are up to date before contacting support.
nvk_AUTODOPPLER is a script for REAPER which allows you to automatically write automation for doppler plug-ins based on the RMS peak of the items on the track or folder you have selected. It works with a variety of third-party doppler plug-ins as well as nvk_DOPPLER (included with purchase).
If you have Snap Offsets enabled nvk_AUTODOPPLER will analyze all the items on your track(s) and create snap offsets at the RMS peak of all the items. If you already have created snap offsets, it will keep those settings. If you have a folder track selected, it will average all the peaks (excluding outliers) and use the start/end times of contiguous items
If Snap Offsets is disabled and there are no existing snap offsets on the items, it will calculate the peak as a percentage of the item. If you manually add snap offsets but have the snap offsets option off, it will calculate the peak as a percentage based on the snap offset location.
The Offset slider allows you to manually change where the peak is based on a percentage of the item length (with snap offsets disabled) or up to one second in either direction (with snap offsets enabled).
Control various settings for the automation as well as the doppler plug-ins. Depending on the doppler plug-in you are using the sliders will change.
The Randomize button (dice icon) will randomize the slider values and the percentage box next to it will determine how much randomization can be applied.
Change the doppler plug-in you are using
Opens/closes the plug-in UI
Bypass the effect so you can hear what it sounds like without the doppler effect. When using nvk_DOPPLER, it will also bypass the playrate automation
Removes the plug-in and any automation as well as closes nvk_AUTODOPPLER.
Adjust the envelope of the playrate automation independently of the doppler automation.
Renders the current time selection or the full track if no time selection is made. Note: For nvk_DOPPLER, playrate automation is also rendered, so the render will sound different unless you move the items to a part of the track without playrate automation or remove/bypass the playrate automation
These presets are designed to work well with nvk_AUTODOPPLER. If you are making your own presets or want to modify the existing ones, there are a few "best practices" to keep in mind:
TRAVELER presets should be automatically installed the first time you select TRAVELER as your plug-in. These steps are only necessary if for whatever reason the installation fails or you have your own presets that you would like to save (in which case you will have to add the presets manually)
If you don't know where this is you can find it from the REAPER menu (Options->Show REAPER resource path in explorer/finder)
GRM Doppler may not output stereo properly without this setting
Renders using your latest settings (saved the last time you close nvk_AUTODOPPLER). It has different behavior depending on what you have selected in the REAPER arrange window, described below.
Note: If the doppler fx is already on the track used for render, the script will always render on a separate track (confusing I know but it makes sense when you think about it).
Same as Quick Render but randomizes silder values before rendering.
This script allows you to write automation to any plug-in you want. Just click the fx parameter you want to write automation for then run the script. If you would like to change to a different fx parameter, click on it and then click 'Get FX Parameter'. If 'Save Values' is checked, the script will automatically add the last FX you used along with automation for the last parameter you had selected when you run the script.
Note: these are mostly included here as an archive and there are almost certainly more recent changes. The most recent changelog is included in the script and can be read when updating.