Media tracks or files placed directly in content is not detected

Media file information is processed and stored in the database which means that files placed in the directory outside of the UI or an FTP connection may not be detected until manually scanned.

You can run a manual scan from SSH with the folllowing command:

mediacp rescan

If you can use a secure FTP connection instead of SCP then this would be automatically detected.

  • Tracks, Audio, Content
  • 2 Users Found This Useful
Was this answer helpful?

Related Articles

AutoDJ -> Shoutcast Transcoder 2 (sc_trans v2) dj port 32kbps sounds terrible

With the latest release of sc_trans v2, there appears to be a bug (referenced here) causing low...

CentOS 6 & Debian - libstdc++.so.6: cannot open shared object file

Issue Shoutcast Server 2 will not start on CentOS 6 or Debian. When starting shoutcast server...

Creating a Relay Stream

Creating a Relay Server Create or Manage a shoutcast server. Select the Relay tab under the...

Delay between stream and listener/viewer

We are often asked why there is a delay between the stream source and the listener, this is due...

NSV / Video Streaming

Shoutcast also supports the NSV ("Nullsoft Streaming Video") protocol and it is possible to...