Troubleshooting

From MOD Wiki
Jump to navigation Jump to search

Common connection issues

Power

If your device doesn't boot or is exhibiting erratic behavior, please make sure that:

If you have a MOD Dwarf and it stays "stuck" on the booting screen (MOD logo screen), please check the "MOD Dwarf - Stuck on 'MOD Dwarf' booting screen" chapter.

Audio

If your device doesn't input or output audio:

  • Make sure that the corresponding LEDs (input or output) on the device light up.
  • Make sure that you are properly connecting audio inputs and outputs.
    • While in software (and also on the MOD WebGUI), audio inputs are normally represented on the left of the screen and outputs on the right, on the MOD hardware, the inputs are on the right and the outputs on the left (just like on most of the audio hardware).
  • Double-check the audio cables that you are using to connect your MOD device
  • Double-check the gain levels, connection and overall condition of the device that you are using to send audio to your MOD device or to receive audio from your MOD device

If you are facing noise issues, please take a look at the Dealing with noise issues guide.

Input

If your device does not have an audio input and the input LEDs do not light up, please adjust your input levels.
That is done on the Inputs or Audio Inputs section of the Device Settings for your device.
Please check the corresponding Device Settings manual for your device:

Output

If your device is correctly inputting audio, but you don't have audio output and also the output LEDs don't light up or you have audio drops, check the following:

Headphones Output

If your output LEDs light up, but you don't have audio coming out from your headphones output port, check the Headphones Volume level on your device.
Learn how to do it at the page corresponding to your device:

In case you are using a MOD Duo X, on the MOD Duo X Device Settings - Outputs make sure that you have the "CV / HP Output" setting set to "Headphone".

USB

Not able to access the WebGUI

If you are not able to access the WebGUI via USB:

  • Make sure that you are connecting via the USB-B port on your device
  • Check the USB-B Mode on your device (and eventually experiment with a different one). To learn how to do it, check the link corresponding to your device:

Note: If you want to use the USB connection as both a USB and MIDI connection, and you are using Windows, select the "Net+MIDI (Windows)" option in the USB-B Mode of your device.

Device loses USB connection when computer enters sleep mode

If your computer enters sleep mode while your MOD device is connected, you may lose the USB connection to that machine. As a consequence, you stop being able to access the WebGUI.

The cause for this behavior is the "USB selective suspend" feature of your computer.

To solve it, there are three options:

  • After the computer wakes up from sleep mode, unplug and replug the USB cable between the MOD device and the computer. This will re-establish the USB connection.
  • Set up the computer so that it doesn't automatically enter sleep mode.
    • For users with Apple products, that is the solution that Apple officially recommends on their forums.
  • Depending on the OS of your computer, you can disable the "USB selective suspend" feature for individual USB ports in system settings. However, if you are using an external USB hub, you likely can't make use of this feature.

Windows host computer

  • In case your host device is a Windows machine, check if it is recognizing your MOD device correctly
  • Use "http://" before the MOD address and not " https://"
  • Try a different browser on your host computer
  • Make sure that no Firewall system on your browser or computer is blocking the MOD device from being recognized as a network device
  • Try a different USB cable
  • Try a different host computer

macOS host computer

If you are not able to connect to your MOD device using macOS:

  • Please make sure that your computer didn't enter sleep mode while you had your MOD device connected via USB.
  • Check Troubleshooting Mac OS Network
  • Use "http://" before the MOD address and not " https://"
  • Try a different browser on your host computer
  • Make sure that no Firewall system on your browser or computer is blocking the MOD device from being recognized as a network device
  • Try a different USB cable
  • Try a different host computer

HTTPS warning

When you are connecting to the MOD device for the first time through a web browser, the browser might try to use an HTTPS connection.
The connection to the device is a local one (which means that it doesn't require an internet connection to access), thus the communication cannot be encrypted through the usual means.
Basically, HTTPS will not work and this is completely expected.

So if/when the web browser complains about the connection being non-secure, this is normal and expected.

My USB MIDI Controller is not recognized

  • Ensure that your MIDI controller is correctly functioning and sending MIDI data. If needed, connect directly to a computer and use a MIDI monitor tool to check if data is coming in
    • Use the MIDI monitor also to ensure that the MIDI controller is sending the required type of message for your needs in the MOD device (Note On/Off, Control Change, Program Change, etc.)
  • Try a different connection cable
  • Ensure that the MIDI Controller is listed on your MIDI Ports Setup window
  • Install the MIDI Display plugin (currently still in beta) and connect it to the MIDI input port representation on the WebGUI. Check which type of data is being received on your MOD device.
    • Note: if in your MIDI Ports Setup you have selected "Aggregated Mode", your standard MIDI port and any USB MIDI controllers will not be differentiated on the WebGUI.
  • In case you want to use the MIDI controller with a Generator plugin, make sure that you have the virtual MIDI cable on the WebGUI connected between your controller input and the Generator plugin.

Not able to create a backup or restore from a USB stick

Ensure the USB stick has sufficient disk space and preferably is formatted with a FAT32 file system.

Device crashes when connecting a MIDI controller via USB

Ensure that your MIDI Device is not creating "MIDI feedback" with your MOD device; in other words, constantly sending and requesting MIDI messages from the MOD device.

MIDI

I can't find my MIDI controller on the MIDI ports setup menu

Please note that when you connect a MIDI controller via traditional MIDI ports (DIN and not USB ports), the host device will not be able to recognize the name of the connection and will show it simply as a MIDI input coming from the MIDI interface.
On the MOD WebGUI, it is shown as a "Hardware Serial MIDI In". This is the virtual representation of the Hardware MIDI input port of your MOD device. On the other hand, in the output section of the Pedalboard Constructor, you will find the "Hardware Serial MIDI Out". This is the virtual representation of the Hardware MIDI output port of your MOD device.

If in the MIDI ports setup menu you have selected the Aggregated Mode, you will see "Hardware All MIDI In" and "Hardware All MIDI Out". Those are representations not only of the physical MIDI ports on your device, but also any other USB MIDI controller that you may have connected.

I can't make MIDI assignments

  • Make sure that everything is properly connected to your device
    • The MIDI out cable from your MIDI device is connected to the MIDI Input of your MOD device
    • Your MIDI cable is functional
  • Check the type of message that your MIDI controller is sending from the interfaces that you want to assign
    • A direct MIDI assignment to a plugin parameter on the MOD system requires a MIDI CC (Control Change) message
    • To do that inside your MOD device, please load a MIDI Display plugin and connect it directly into the Hardware MIDI input on the WebGUI Pedalboard Constructor

I can't input MIDI via the MIDI ports on my MOD Dwarf

Since the MOD Dwarf uses TRS MIDI ports, you would need a TRS MIDI adapter to connect a traditional DIN into it.

  • Make sure that you are using a TRS Type A MIDI adapter
  • Make sure that you are connecting the MIDI output of your controller to the MIDI input of the MOD Dwarf

Control Chain

MOD XF4

I can't update my MOD XF4

If updating your MOD XF4 via WebGUI Settings does not work, please try the Manual update.

My MOD XF4 assignments don't show up

If your XF4 does not show any assignment:

  • Make sure that you have anything assigned to it
    • If you did the assignments in a previous use of the pedalboard, make sure that you have saved the pedalboard after creating those assignments
  • Try to reconnect the XF4 to the Control Chain port of your MOD device
  • Try a different connection cable

Pedalboard and plugin troubleshooting

If you are facing issues with a particular pedalboard or plugin:

  • Make sure the pedalboard is not running beta plugins
    • Most of the time, beta plugins are fully functional, yet they are still considered beta because they lack testing. With this testing, some issues may show up, issues that sometimes appear in specific use cases or after some MOD OS update.
  • Check if all your virtual cables are properly connected
    • More often than not, you may have a stereo plugin input with two virtual audio cables connected to it. That can happen when you connect the cables in a quite low zoom setting on your Pedalboard Constructor.
  • Make sure that you are not using Trial Plugins
  • If nothing helps, try to rebuild the pedalboard using the same plugins and save it.


Pedalboard miniature not showing on Pedalboard Library

Sometimes, when a new Pedalboard is saved, the device needs some extra time to save the screenshot of the pedalboard. If that doesn't happen and you turn off the device, your pedalboard will be saved without a snapshot. That should create no problems with the pedalboard functionality. Yet, if you intend to share the pedalboard in the Pedalboard Feed, that won't be possible.
To get the screenshot, you can re-save the pedalboard with a different name, open the Pedalboard Library, and wait until the screenshot shows up over there. Then you can disconnect your device or keep creating.

MOD Cloud-related issues

Failed to connect to MOD Cloud

If you see the "Failed to connect to MOD Cloud" message, you should try the following:

  • First of all, double-check your internet connection
  • There have been reports of some browser extensions that might prevent the MOD Web GUI from connecting to the cloud.
    • Try deactivating some extensions.
      • One extension reported was the "Firefox Privacy Badger". Do you know of any other extension that is causing issues? Please share with us!

On Firefox

'noscript' add-on prevents loading of cloud pedalboards

  1. Open noscript preferences,
  2. Go to the advanced tab, then 'ABE'.
  3. The system ruleset should look like this:
# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Accept from http://integrate.moddevices.com/
Deny
  2. Note the new 'Accept from ...' rule.
    1. This makes noscript accept requests from cloud pedalboards into the local network.

Noise-related issues

MOD produces noise when plugged into my current setup (Ground Loop)

If you use other equipment along with your MOD and it starts producing loud noises when plugged in, you might be experiencing a Ground Loop. This could be other pedals, an amplifier, or even your computer.

In short, ground loops may occur when multiple audio equipment devices are grounded to different power sources but are connected. This situation can occur with MOD devices because they are devices that are actually referenced to Earth.

To check if that is the case, try to isolate the power of your MOD device and see if it changes your results. One thing that helps is to make sure your MOD device and all other equipment are connected to the same power socket.

Another way these ground loops can occur is by connecting to a PC or laptop (via USB) that has a really bad power supply, so try disconnecting it from the PC.

References on Ground Loops:

Dealing with noise issues

It is common nowadays in modern music setups to have noise issues that require some thought and experience to sort out.

If you are experiencing noise issues on your setup, we recommend that you check the following aspects:

  • Gain staging: check the gain levels both on the input and on the output of all of the devices in your setup;
  • Pedalboard: check the effects on your pedalboard (both virtual inside your MOD Device or other physical devices in your setup) and pay attention to potential sources of noise (take a look at the "Gain staging related issues" chapter for more info) ;
  • Ground loop: check for potential ground loop issues in your setup. Multiple grounded devices in your setup may generate noise issues.

For more detailed explanations and info, please check the "Dealing with noise issues" page.

Gain staging related issues

Dealing with "too hot" audio signals

Certain plugins in the MOD platform - especially Distortion, Dynamics or Simulator plugins - may increase the internal gain staging levels beyond the advisable. That can happen, especially when multiple plugins of this type are used together in series.

This can lead to unwanted noise issues and a lack of control over your signal. In some cases, it can even activate the safety mechanism built into the MOD devices that automatically shuts down any audio output!

To protect your MOD pedalboards from such issues, we suggest using meter plugins to check your level, especially after any potentially problematic plugin, and dial down the level control (when available) on that particular plugin.
If the plugin doesn't have a "level" or "master" control, you can place a gain or volume plugin (like Gain, tinyGain or Volume) after that plugin (in series) and dial down the level to compensate. In this case, place the meter plugin after the gain or volume plugin to have an accurate result.

Either use a built-in level control or an external plugin to dial down the level until your meter plugin indicates a reasonable output value coming from the plugin.

You may need to repeat this process between other plugins in your entire chain to achieve a stable gain staging on your virtual pedalboard.

Dealing with "too cold" audio signals

Sometimes your signal may be too quiet, which makes it barely listenable.
Increasing the level at the wrong stages may boost mostly unwanted noise that can even blend with the desirable sound.

We recommend that you use a meter plugin to check the stage where your signal is getting quiet. It may be a plugin with the level set too low or other parameters that are causing that issue.
After finding the source of the problem, re-dial the level controls (and if needed, also other parameters) in order to have a better signal.
You can also use gain or volume plugin (like Gain, tinyGain or Volume) to increase your level. Another option is to use Dynamics plugins.

In any of these cases, do it with caution to not increase the ground floor noise.

If you are using an external sound source via the input of your MOD device, make sure that the output of that source is strong enough. In this case, take a look at your input gain levels.

Final notes on gain staging

  • If you are using a physical MOD device, they all possess LEDs that help you check the incoming and outgoing signals.
    • Make sure that your output LEDs stay mostly green and maximum turn yellow at times. Never going red!
  • Gain levels between other devices in your setup may not be uniform.
    • When available, use the gain LEDs from the devices (just like on the MOD devices) to help you balance your signal.
    • If you use some other device connected to your MOD inputs, make sure that the MOD inputs also stay in green and never go red.
  • Make sure that the final output in your chain doesn't exceed 0dB.

Resources-related issues (device's CPU and RAM)

High CPU or RAM usage may cause X-runs, which in practice translates to audio drops, which can be extremely inconvenient for live performances.
The higher the resource usage is, the more frequent these audio drops will be. Therefore, we recommend CPU usage to stay below 80%.
Relevant to note is that the presented CPU value is an average calculation.

Dealing with high resource consumption

In case your CPU and RAM resources are too high, you can try multiple techniques to reduce them:

Avoid placing plugins in series

When you place the plugins in series, like the following:

Each plugin must wait for the previous one to finish its processing before it can start its own. All the plugins will also be allocated to the same CPU core, which will cause an overusage of a single core, while others have low to no usage.


Although it is often required for this type of chain, you can sometimes avoid it, resulting in better utilization of all CPU cores.

For example, if you want to create something similar to an effects loop where you use time-based plugins like delays or reverbs, you can take advantage of the Portal plugins ((Portal Sink and Portal Source) to force the effects loop to use a different CPU core. Just like the following:

With this technique, the plugins in between the (Portal Sink and Portal Source (therefore, on the effects loop) will be allocated to the next CPU core.
More branches like this will be allocated to the other available CPU cores, thereby distributing your CPU consumption across all available cores. This will result in less CPU consumption, as each plugin will need to wait for fewer plugins to finish their processing needs. Additionally, each branch will be able to utilize different CPU cores, enabling the simultaneous processing of different plugins.

Portal plugins (Portal Sink and Portal Source) do in practice?

On the "backstage", the Portal plugins force a single chain to be split into two.
This means both chains can run in parallel, each on its own CPU core.

We can run as many series as there are cores in the system while keeping good performance.

For more info, check the plugin description pages:

Reduce Buffer size

Reducing the buffer size on your device will also help reduce CPU usage.

You have essentially two methods to do it:

  • reducing the Buffer size on a device basis, which will affect all your pedalboards
  • on a plugin chain or branch basis

On the first possibility, you can:

  1. Access the Advanced Settings on the WebGUI
  2. Check the box "Use 256 frames as Buffer Size."

To reduce the Buffer size on a plugin chain or branch basis, you should use the technique described in "Avoid placing plugins in series".

Note that both methods increase latency
On the first one, this latency will be on a pedalboard basis and on the second one, you will have one cycle of latency coming out of the Portal Source plugin. For effects like delay and reverb, this could be a worthy compromise.

Replace plugins with similar ones that require fewer resources

The MOD Plugin Store is full of options for each type of plugin.
Most of the plugins have actually pretty low requirements of CPU and RAM consumption. Particularly problematic for that matter could be:

  • Reverbs and Delays
  • Modeling plugins
  • IR-based plugins

In the case of Modeling or IR plugins in which you can load your own models or files (like AIDA-X, Neural Amp Modeler, IR loader cabsim, Cabinet Loader, IR Convolver or Convolution Loader), you can try to load less heavy models or impulse response files.

In case of other modeling or impulse response-based plugins, in which you are not able to load your own files, you can:

  1. Try using other models or impulse responses available on the same plugin
  2. Search for alternatives on the Plugin Store that don't use these technologies and try them

Typically, modeling-based plugins model physical amplifiers or effects. On the MOD Plugin Store, you have a lot of amplifiers and effects alternatives that don't use this technology (therefore tend to be lighter on CPU and RAM consumption) and still sound great, if not sometimes better. Just give them a shot; you will likely be impressed.

The same happens with IR-based plugins. They are either a capture of the impulse response of an amplifier cabinet or a reverb from a particular space. You will find a lot of alternatives on plugins fully based on processing algorithms that will free up some CPU and RAM resources.

The same can be said with any other plugin that may be a bit heavier on the device resources and limit your pedalboard too much. Sometimes, all those "shiny features" and possibilities make the plugin heavy and you don't really make use of them. Quite often, you will be able to find a more stripped-down plugin with exactly what you need, or you will be able to put it together with a conjunction of audio plugins and perhaps Control Voltage plugins.

Take this opportunity to get to know the wonderful possibilities for plugins available on the MOD platform and get creative.

MOD Dwarf specific issues

Stuck on 'MOD Dwarf' booting screen

If the unit becomes unbootable for some reason, we might need to reinstall the OS inside.
We can boot the unit in recovery mode for safe reinstall, boot over USB if the recovery partition is broken, or perform a full factory reset (which will erase all your data).

For more information, see Troubleshooting Reinstall.

Note that the MOD Dwarf is not software brickable; you can always reinstall its OS.

Factory reset & firmware updates

Sometimes, the best way to resolve a software issue with your device is to perform a factory reset.
If you are going to perform a factory reset, we recommend creating a backup of your device first to avoid losing any important saved data. Check the Backup & Restore chapter to learn how to create a backup of your device and later restore that data.

Check the Factory Reset Images page to download the factory reset image for your device and check the instructions on how to do a factory reset.

Please note that a factory reset will not remove any license from plugins that you purchased previously.

Get external help

If, after all your attempts, you still face issues, feel free to reach out to our great community at the MOD Forum or contact our support directly at support@mod.audio

Retrieved from "https://wiki.mod.audio/index.php?title=Troubleshooting&oldid=17082"