Get back to playing

Start with what you can observe. A moving knob on screen proves an app change. An audible response proves more of the connection.

Pedal not responding

1. Open MIDI. Does Output device name the interface connected to your pedal?
2. Follow that interface’s OUT to the pedal’s IN. Check the exact adapter wiring.
3. Open Channels. Match the app channel to the hardware receive channel. Use the hardware setup guide for the physical setup.
4. Play a phrase and make one obvious mix change. Check the pedal is engaged and the audio path works.
5. If other controls work but this one does not, check firmware and the support badge’s known gaps.

MIDI Live and outgoing activity cannot confirm receipt. Avoid changing many settings at once while testing; one working control gives you a useful reference.

No MIDI output

The MIDI panel has no device to select

Check browser MIDI support and site permission, then the USB data cable and interface connection. A USB socket on the pedal may only support updates or a proprietary editor. See cables and adapters and browser checks.

The app is waiting for an old device name

Reconnect that device or select the current port explicitly. Don’t substitute a loopback output unless you have configured it to reach the pedal. Then check the channel and repeat one audible test.

Wrong sound after recall

Check the selected pedal, channel, slot, and any bank numbering. A cloud preset update does not rewrite an assigned hardware slot. A physical overwrite does not update Nitelite’s record either.

Repeat the hardware save procedure and test recalling away and back. On a pedal with physical-only saving, the dialog’s Done action records the assignment after your hardware steps; it cannot save the sound for you.

The screen and pedal disagree

Nitelite doesn’t read physical knob movements. Load your intended cloud preset or set the app values, then Sync to Pedal if you want those values on the hardware. To preserve a sound you dialed physically, first recreate its settings in the app; saving the current screen cannot capture unseen hardware changes.

A preset saved the wrong settings

The save dialog snapshots the app’s settings when it opens. Save Copy opens that dialog; it doesn’t load the detail preset first. Close the dialog, load the sound you intended, then reopen Save. Use Update existing only when you want to replace that cloud record.

Tone Terminal isn’t doing what I expected

I got an explanation without Apply to pedal

Check the reply type. Ask produces an answer without an applicable settings block. Use Generate for a starting point or Refine to change a suggestion.

The suggestion ignores my current sound

Enable Attach current settings. It sends the screen’s values, not a readout from hardware. Describe the audible problem and check the selected pedal and firmware. The AI cannot hear your rig.

A request failed or I cannot generate

Check sign-in, your current balance, and the error shown in the app. Preserve any useful result before reloading. If it repeats, report the error text and approximate time through Feedback; another generation is not a MIDI connection test.

Send a useful report

Use Feedback or support@nitelite.ai. Include the pedal model and firmware, browser/OS, interface and adapter, output name, MIDI channel, exact control or button, expected result, and observed result. For mapping issues, the support badge also has Had issues reporting.

Crop screenshots to the problem and leave private conversations and account details out. State whether you tested on real hardware or only on screen.