Home Troubleshooting

Troubleshooting

Carmine Paolino
By Carmine Paolino •
4 articles

Troubleshooting USB drives and exports

Solco doesn't see the USB drive The bottom of the sidebar says No USB drive connected. 1. Check that the drive is mounted: it should show in Finder, File Explorer or your file manager. 2. Click the refresh button beside No USB drive connected to look again. 3. If you unplugged and plugged the drive back in, or Windows gave it a different letter, refresh and choose it again. The bottom of the sidebar: No USB drive connected, with the refresh button that looks again If Solco sees the drive but won't export to it: - "macOS hasn't let Solco use KITKAT." or "macOS didn't let Solco erase this drive." In System Settings, open Privacy & Security, then Files and Folders, and turn on Removable Volumes for Solco. Then try again. - "No CDJ or XDJ reads NTFS." (or APFS, or another format) Back up the drive, then choose Erase and prepare drive… from its menu in the sidebar, and keep FAT32 (recommended). This erases it. - "It's journaled HFS+, which players may not read." On a Mac, turn journaling off in Terminal with diskutil disableJournal /Volumes/NAME, using the drive's name, then look for drives again. Or erase it as above. - "Solco writes HFS+ drives on a Mac only." Export to it from a Mac, or erase it as FAT32. - "It's case-sensitive HFS+, which players might not recognise." Erase it as above. - "This drive is read-only, so nothing can be added to it." Check the drive's write-protect switch, or repair it with your system's disk tool. You can still import from it: the page opens on Import. Some devices that aren't DJ drives show up as a USB drive too, such as a keyboard or controller that carries its own software on a small read-only drive. Solco only reads a drive's library when it has one (rekordbox's or Solco's), so such a drive simply says it has no DJ library. Nothing failed, and you can ignore it. Solco says the drive writes slowly When you export to a drive that writes slowly, Solco says so before it writes anything, for example KITKAT writes slowly. On Linux, the computer waits after every file it writes to that drive. On Windows, the drive is set to Quick removal, so Windows writes every file straight through to it. - Click Make this drive fast, then enter your password, or allow the change on Windows, when your computer asks. Solco changes that drive only, and your export goes on by itself. - Or click Export slowly this time. Solco asks again the next time you open it, unless you tick Don't ask again. A drive that writes quickly keeps some writes in memory for a moment, so always eject it before you unplug it, and give it a few seconds. Solco's own exports still finish writing before they say they're done. To make a drive fast later, or to put it back, right-click it at the bottom of the sidebar and choose Make this drive fast… or Undo fast writing…. If your Linux computer has no password prompt Solco can use, the window shows a command to paste in a terminal instead, then Reconnect the drive. If the drive is set up in /etc/fstab or mounted with sync, the window says where to change it. On Windows, if a window or app has the drive open, the new setting can't apply at once: close it and click Try again, or eject the drive and plug it back in. rekordbox has the drive open If Solco says The OneLibrary database on this drive is still open, probably in rekordbox, so nothing will be changed, quit rekordbox and try again. If the message stays, open the drive in rekordbox once and quit it. Solco changes nothing on the drive until then. Importing your rekordbox library is different: rekordbox can stay open. If Solco says rekordbox kept changing its library while Solco copied it, try again in a moment, or quit rekordbox first. The update stopped because the drive changed rekordbox exporting to a drive Solco made is fine: Solco keeps rekordbox's tracks and playlists and adds its own beside them (see "Exporting to a CDJ or XDJ USB drive"). An update stops only when a track or playlist Solco wrote was changed or removed, for example by deleting a Solco playlist from the drive in rekordbox, or when another app changed the drive's library in a way Solco can't keep. The plan says what changed and nothing on the drive is written. On that line you can: - click Import from USB to bring those changes into your library, then export to an empty drive; or - choose Restore Solco’s library…. The Ready card's button then reads Restore Solco’s library. Solco keeps a copy of the drive's library files on your computer first. The plan's line when a drive's library was changed outside Solco: nothing on it is written, with Import from USB and Restore Solco's library If an update would remove a track that one of your played sets uses, it stops too. Keep those tracks, use an ordinary export, or bring the sets into your library first: on the page's Import side, choose Chosen playlists and tick them under Played sets. rekordbox or a player using a Solco drive is normal: rekordbox adds its profile and My Tags, and its own tracks and playlists when it exports to the drive, and players record played sets and play counts and keep the cues you set on them. Solco keeps all of it, and checking the drive says so in a note. Cues you set on a player come into your library with your next export to that drive (see "Exporting to a CDJ or XDJ USB drive"). A player says it can't find the library on the drive Players read one of two libraries on a drive, and the newest ones read only the newer library. Export to the drive again: every drive Solco prepares gets both. If it still says so, open Options on the Export page and check that Libraries on the drive is Both, then export again. An update takes as long as the first export With Check files already on the drive on Full, the default, every update reads all the files already on the drive, so it takes about as long as reading the whole drive. It reads them once: the export button writes the plan the check made without reading the drive again, and checking again while Solco stays open reads only the files that changed. If you update the same drive often and trust it, choose Quick under Options: Solco then checks each file's size, date, start and end, and an update with nothing new takes seconds. Turning off Read back copied files from the drive saves the time of reading the new copies. Before a gig, go back to Full, or turn on Re-read the whole drive afterwards. The plan lists tracks your library doesn't have Tracks on the drive that your library no longer has, for example after you rebuilt your library, aren't a problem: an export keeps them on the drive as they are. To have them in your library again, click Import them on their line. The page turns to its Import side with exactly those tracks, and copies them with their cues, grids and covers when you press its button, which says how many tracks and how much audio. The plan says tracks on the drive changed If another app or you changed tracks on the drive after Solco's last export, the plan says so, and they stay on the drive as they are: Solco never writes over them. A player rewriting a track's waveform and cue files is not one of these: the cues you set there come into your library, then the files are written again. If a track's files are damaged (cut short, or no longer waveform files at all), the plan lists the tracks under Repairing before anything is written: Solco writes its own version again when your library has the track, and otherwise leaves it as it is. Neither stops the export. Only a track whose file is gone from the drive does: put the file back, or bring the track into your library and export again. An export finished with a warning about a track Before Solco puts a new library on the drive, it reads back everything it wrote. - "The drive may be failing": a track's copy didn't read back as it was written, twice, though the file in your library is fine. The track is on the drive as copied. Try it on a player, and use another drive if you can; the next update copies it again. - Shortened on the drive: a title or tags were too long for the players' library. The drive's copy is shortened; your library and your files keep everything. - In the classic library only: the track's entry in the newer library didn't read back as it was written. The track is on the drive and players that read the classic library list it; the newest players won't, this time. Export again to put it back. - Left out: Solco's own waveform files for the track still came out wrong after being made again. The track stays off the drive, or keeps the copy the drive already had, and everything else goes on. Export again to try it once more. If it keeps happening, use Report a problem (see "Contacting the Solco team"). An export was interrupted If you stop an export, the card says Stopped and that nothing on the drive changed. Export again with the same choice: Solco checks the files it already copied and reuses the good ones. The drive keeps the library it had until an export finishes. If the next export won't use what a stopped one copied, the drive card says Files from a stopped export with their size; Remove… lists them, and says what removing them frees, before anything is removed. Checking a drive before a gig - Keep Check files already on the drive on Full and Read back copied files from the drive on, the defaults, so every file on the drive and every new copy is read. Quick and No check are faster because they trust files whose size and date still match what Solco noted; they can miss damage that keeps both. - Turn on Re-read the whole drive afterwards for the drive you take to the gig. It reads every file again after the update, trusting nothing Solco noted. - From a terminal, solco verify /path/to/drive checks a Solco drive without opening your library. Then eject safely, load a few tracks on a player, and check the grid, cues, playlist order, waveform and level. Still stuck? In Activity, click Tell us beside the problem. It opens Feedback with the error filled in. See "Contacting the Solco team". Activity, under Needs you: a failed export with what went wrong, and the Tell us button

Last updated on Nov 07, 2026

Backing up and restoring your Solco library

Solco keeps your playlists, cues, grids, ratings, analysis and settings for each track in one library file. Your music files are not in it: back them up separately, as you always should. Save a backup 1. Open Settings › Maintenance. 2. Under Library backup, click Save backup…. 3. Choose a new file name. Solco never replaces an existing file. Settings, Maintenance, Backups: the Library backup row with the Save backup button You can keep working while it copies. Show progress opens Activity, where copying, checking and flushing show separately. Backups work even after your licence key ends. Save one before you install a new beta, and close every Solco window before switching builds. Cover images Solco downloaded for tag matches are kept beside the library in a folder named catalogue-covers. Back it up too if you move your library to another computer. From a terminal: solco backup --output /path/to/backup.sqlite3. Backups Solco makes by itself - Before upgrading your library. When a new version needs to upgrade the library, Solco first saves and checks a copy in the library.sqlite3.backups folder beside it. If the backup fails, the upgrade doesn't happen. - Before changing a rekordbox drive. Before Solco adds to, restores or replaces the library on a USB drive, it keeps a copy of the drive's library files (never music) in usb-backups beside your library. Each drive keeps its last three copies for 30 days. Where the library is - Mac: ~/Library/Application Support/com.getsolco.Solco/library.sqlite3 - Windows: %APPDATA%\getsolco\Solco\data\library.sqlite3 - Linux: ~/.local/share/solco/library.sqlite3 (or $XDG_DATA_HOME/solco if you set XDG_DATA_HOME) Running the solco command Some steps here use Solco from a terminal: - Mac: /Applications/Solco.app/Contents/MacOS/solco - Windows: solco.com in %LOCALAPPDATA%\Programs\Solco (or in your portable folder) - Linux: solco, or ./solco in a portable folder Going back to a backup Solco never overwrites your library with a backup. To open one instead: 1. Quit Solco. 2. Make a copy of the backup, so the original stays untouched. Solco works in the copy, and upgrades it first if it needs to. 3. Start Solco on the copy from a terminal: solco --database /path/to/copy.sqlite3. Solco uses the copy only for as long as it was started that way. Started the usual way, it opens your usual library again. To keep working in the backup, start it with --database each time. Changes made after the backup are not in it, and cover images in catalogue-covers are found only beside the library Solco opens. Keep your current library file too, in case you need it. Don't copy library.sqlite3 while Solco is open, and never delete the -wal or journal files beside it to make it open: they can hold your latest changes. If the library won't open Solco shows the reason with Try again and Open another library…. The … menu beside them has Save a backup…, Copy details and Quit. Nothing is replaced. If it says This library requires a newer Solco build, a newer Solco has upgraded your library: install that version again, or open a backup made before the upgrade. If Solco can't start at all, run solco diagnostics in a terminal and send us the report: see "Contacting the Solco team".

Last updated on Nov 14, 2026

Missing files and moved music

Solco follows your files when you move or rename them: it adds its own ID tag to each file, so a track moved within your music folders keeps its cues, playlists and analysis. A track shows under Missing files only when a full scan of a folder Solco can reach no longer finds its file. Missing files in the sidebar Missing files appears in the sidebar when there are some, with a count. Tracks on a drive or network share that isn't connected are never counted: their folder shows as Offline in Settings › Library, and they come back by themselves when it's connected. A missing track keeps its cues, playlists and analysis, and exports keep the copy already on a USB drive. Open Missing files to see them, with these buttons above the list: - Rescan folders looks for the files again in your music folders. Try it first if you just moved or restored files. - Locate… asks for the folder the files are in now. Solco finds them there by their ID tag and reconnects them. A folder outside your music folders is added as one. - Search on USB looks for them on the connected USB drives, for example the drive you exported them to: by Solco's record of the drive, by name and size, and by their sound. It shows what it found, and Put 4 back (it says how many, and their size) copies those files to where your library expects them. Nothing is written until you click it. - Remove from library… forgets the tracks that are really gone. A damaged file you moved to the trash from the Analysis page, keeping its track for a new copy, also waits here. Add the new copy to your music folders and Solco gives it the track's cues and playlist entries. See "Analysing your tracks". In a search, state:missing finds them too. A whole folder moved If you moved a whole music folder, for example to a new drive, open Settings › Library, click ⋯ beside the folder and choose Relocate…. Pick its new place and every track in it is found again. See "Music folders, Downloads and gathering your files". Forgetting missing tracks Remove from library… in Missing files, or Review… beside Forget missing tracks in Settings › Maintenance, shows what forgetting does before it happens: the file locations are forgotten, the tracks leave their playlists, their cues and saved loops are deleted and their analysis is cleared. No audio file is touched, but this can't be undone from Solco, so save a library backup first if you may want them back. See "Backing up and restoring your Solco library". Only tracks a completed scan of a reachable folder confirmed missing are forgotten. Tracks on unplugged drives are kept. Missing files and your USB drive When you export, tracks whose files are missing keep the copy they already have on the drive, and new ones are left out. The plan offers Search on USB and Locate… on that line. See "Exporting to a CDJ or XDJ USB drive".

Last updated on Nov 04, 2026

When Solco cannot open its window

Solco draws its window with your computer's graphics card, through its graphics driver. Every Mac, and every Windows or Linux computer with its graphics driver installed, has what Solco needs: OpenGL 2 or later. "Solco cannot open its window" If Solco shows this message when it starts, it found no graphics it can draw with. The message names the cause and offers to open this page. Your library is not opened or changed, and Solco opens normally once the graphics work. Windows A Windows PC without its graphics driver uses the Microsoft Basic Display Adapter, which offers only basic graphics. Solco then draws its window with Windows' own software renderer instead: it opens, but scrolling, playback and the waveforms are slower, and the processor does the drawing work. If even that fails, Solco shows the message. To install the driver: 1. Open Device Manager and expand Display adapters. Microsoft Basic Display Adapter means no graphics driver is installed. 2. Open Settings › Windows Update › Advanced options › Optional updates and install any driver offered for your display, or download the driver from your graphics card's maker (NVIDIA, AMD or Intel) or your computer's maker. 3. Restart the computer and open Solco again. Windows on ARM: graphics drivers for Snapdragon processors have no OpenGL of their own; Windows gets it from Microsoft's OpenCL, OpenGL & Vulkan Compatibility Pack. If Solco shows the message on one of these PCs, its button opens the pack's page in the Microsoft Store: install or repair it there, then open Solco again. Remote Desktop: a remote session can give Solco only basic graphics. Open Solco on the computer itself, or ask whoever manages the remote computer to turn on hardware graphics for remote sessions. Virtual machines: turn on 3D acceleration in the virtual machine's display settings, and install its guest tools, which include the graphics driver. Linux Install your graphics card's driver, or Mesa, which provides OpenGL for most graphics cards and a software fallback. Your distribution's packages are usually called mesa or libgl1-mesa-dri. Over a remote X11 session, Solco needs the remote computer's OpenGL; run it on the computer itself instead. Mac Every Mac Solco supports has the graphics it needs. If you see the message on a Mac, update macOS, restart, and contact the Solco team if it stays. See "Contacting the Solco team".

Last updated on Oct 27, 2026