Troubleshooting

Most problems are one of two kinds: the sound goes to the wrong place, or Nastro cannot read a file. The log says which.

No sound

Nastro plays through your system's default audio output. If a track is playing, the clock is moving and you hear nothing:

Check the default output device. In your system sound settings, make sure the default output is the speakers or headphones you expect, and that it is not muted. Nastro follows the default device at the moment playback starts.
Check the volume of Nastro itself and of the system mixer. Some mixers keep a separate volume for each application.
On Linux, check the sound server. Nastro talks to ALSA. With PipeWire or PulseAudio, the ALSA plugin that routes it to the server must be installed: pipewire-alsa (or pipewire-audio) for PipeWire, pulseaudio-alsa (the alsa-plugins package on some distributions) for PulseAudio. Without it, Nastro may open a raw hardware device that another program is already using.
Check that something else is not holding the device. With plain ALSA, only one program can use a card at a time.
Look at the log, see below. A failure to open the output device is logged with the reason.

Quick test

Play any file with another program or run speaker-test -c 2. If that is silent too, the problem is in your system's audio setup, not in Nastro.

A file does not play

Nastro plays files with the extensions flac, mp3, mp2, mp1, ogg, oga, opus, wav, wave, aif, aiff, aifc, m4a, mp4, m4b, aac, caf, mka, mkv and webm, see Playback. Files with another extension are ignored when you add them. A file that is truncated, protected by DRM or encoded in a format Nastro cannot decode is skipped when its turn comes, the display shows the error, and the reason is written to the log.

Opus is not decoded yet, so .opus files, and Ogg files that contain Opus, do not play.

If you moved or renamed files after adding them to a playlist, those tracks fail the same way, because playlists store the path of each file. Add them again from their new place.

A track is not in the playlist

Dropping or adding a folder skips hidden files and folders (names that start with a dot) and playlist files found inside it. A file with an extension Nastro does not know is not added. Check that the track list is not being narrowed by text in the Filter box.

Keyboard shortcuts do nothing

The single-key shortcuts (Space, Z to B, the arrows and so on) do not work while a text field has the focus, for example after you click the playlist Filter box. Click on the player or on a track to give the focus back. See Keyboard shortcuts.

Panels and the window

All the panels live inside one transparent window. This has some consequences you may notice:

A panel cannot go to the left of, or above, the top-left panel of the window. Positions never go negative. To place the group elsewhere on your screen, drag the player's title bar, which moves the whole window. To put the equalizer or the playlist on the other side of the player, use View, Layout.
On Linux with Wayland and on Windows, clicks in the gaps between panels go to the windows behind Nastro. On Windows the thin shadow around each panel still belongs to Nastro. On X11 and macOS the gaps still belong to Nastro's window, so a click there does not reach what is under it.
While a menu is open, the window grows downwards to make room for it. The extra space is transparent and the window goes back to its size when the menu closes.

Classic skins

Importing classic .wsz skins is planned and not available yet. Nastro uses its own skin.toml skins, see Skins.

The log

The log file is in the folder listed under Files and folders. On Linux:

$ tail -f ~/.local/state/nastro/nastro.log

By default (the level Information) it records startup, the tracks played, settings changes, warnings and errors. To see what Nastro is doing, start it with a more detailed level:

$ NASTRO_LOG=debug nastro

NASTRO_LOG takes off, error, warn, info, debug or trace, in any case. It overrides the level for that run only. A value that is not one of them is ignored.

You can also change the level while Nastro runs: Preferences has a Log level setting with the choices Off, Errors, Warnings, Information, Debug and Trace, and it shows the path of the log file. It is saved in settings.toml as log_level, see Settings. Trace is very verbose, use it only to report a bug.

Reporting a problem

Open an issue on GitHub with your system, how you installed Nastro and the relevant lines of a NASTRO_LOG=debug log. The log holds file paths, so look it over before posting it.

Found a mistake? Edit this page on GitHub or open an issue.