FAQ - olyrhc/nanometer GitHub Wiki

Troubleshooting

How do I assign the sliders, knobs and buttons on the nanoKontrol2 to a specific plugin parameter or function in FL Studio?

Solution:

First, edit the config and change ControllerLinkMode to True (Don't forget to save the file and reload the script). Next, you need to setup a controller link for each button, slider and knob you want to link.
Follow these steps:

  1. First, use the mouse to move/change the desired parameter/function in FL Studio or a plugin window.
  2. In the TOOLS menu, select "Last tweaked" and then click "Link to controller...".
  3. Make sure "Omni" is selected in the Link-window.
  4. On the nanoKontrol2, use the cycle button to switch to the Controller Link Mode (it's located after the Playlist mode).
  5. Press/Move the button/slider/knob you want to use to control the selected feature. If successful, the link-window will close and the link should then be active/working.

Note: Instead of using the Controller Link Mode described above, you can also hold down the cycle button and then move a slider / press a button in step 4-5. (the knobs can not be linked this way, it will be fixed in a later version).

When I load my project, some of my mixer-track colors are missing!

Solution:

The 8 mixertracks that are highlighted by the script will unfortunately be saved with the project because FL Studio can't differentiate between colors that were set by the user and colors that were set by the script. This means that any projects you saved while the script was running most likely won't retain the correct colors for the 8 mixertracks that was highlighted at the time.

There are however a few things you can do to avoid this:

  • Use the nanometer quick-save function by holding down the cycle button and pressing the record button.
  • Switch to another mode before you save. The highlighted mixertracks only appear when the mixermode is active.
  • Set the ColoredRange option to False in the config to disable the highlights permanently.

The script doesn't allow me to change the colors of any highlighted mixertracks!

Solution:

This is intentional. To change the color of one or more tracks that are currently highlighted you must first move the highlighted area away from the track you want to change. Alternatively, you may switch away from the mixer-mode by pressing the cycle-button and then change the colors of any tracks you want.

Note: If you don't want the controlled mixertracks to be highlighted at all, the highlight-feature can be disabled with the ColoredRange option in the config.

I don't like the color used for the highlighted tracks!

Solution:

You can set it to your prefered color with the HighlightColor option in the config. Due to the way FL Studio works, the option only accepts negative float-values in RGBA-format. To get the correct value for a chosen color, you can do the following:

  1. Right-click on an empty (not highlighted) track in the mixer. We'll use track 9 in this example. Select the "Change color..." option in the mixertrack menu.
  2. Select the desired color. In this example, we'll pick Steel Blue. Click Accept.
  3. Enter the View-menu on the menu-bar and click on "Script output".
  4. Click on the field below the "Command to execute"-title and type: getTrackColor(9) and press Enter.
    Note: It's important to write "get" in lowercase and "TrackColor" with capital letters!
  5. Look for the negative number in the text-output. This is the number you want!
  6. Find the HighlightColor-line in the config-file and replace the number like this: HighlightColor = -13279841.
  7. Save the config and click on the "Reload script" button in the Script output window. The highlighted mixertracks are now blue!

The solo/mute button status-lights takes an unusual amount of time to light back up after I play a sound!

Solution:

The only way for the script to determine if sound playback has stopped is to wait for the sound-signal to die down. This normally takes just a few seconds and as soon as it's quiet, the solo/mute-buttons will become active again. This is not always the case though; If you're using a lot of reverb on a mixertrack, it can take a very long time for the sound-signal to die down enough for the script to detect it.

One way to avoid this is to enable the PlayingOnly option in the config. This will force the peak meter lightbars to only respond while FL Studio is in pattern/song playback mode and consequently will also make the solo/mute buttons work immediately as soon as playback is stopped.