How to check if silan is working


how can i check if silan is working or not
running from console, i get this

silan /any/file
*** stack smashing detected ***: <unknown> terminated
Aborted (core dumped)

silan --version

hi, ive found this

i get this result in my database
silan_check | count
f | 530
(1 row)

so that means silan is not working ? 530 is the amount of tracks in my current library

I’m not sure. I honestly haven’t taken the time to dig deep into silan and really figure out how well it is working etc.

The “f” in the SQL output indicated that no tracks where scanned by silan, so it isn’t working.

If silan segfaults when you call it (as indicated by “Aborted (core dumped)”) then it certainly is broken and needs fixing if you want to use it. It looks like this has already been reported to the silan project:

Did you follow the instructions on to install a current version? I think they might be broken at this stage but haven’t tried them in a while.

When reporting issues with distro packages like silan it is always important to always include the operating system and version you are installing on. Generally Debian Buster, Ubuntu 20.04 and newer will have silan 0.4.0 which will most likely fix the segfaulting issue.

Hello, I’ve got the same issue with silan 0.3.3 under ubuntu 18.04
Did you find any solution for this issue please?

I’ve investigated if an upgrade to silan 0.4.0 is possible but it seems that some dependencies will cause issues:

Did you mean that silan 0.3.3 is crashing and thus not implementing the silence detection or is it giving incorrect ie shorter values. One alternative to installing the debian package would be to install it from the source but that would probably be more complicated.

Hello Robbt,

I mean silan is crashing whatever the mp3 analysed so the is no silent detection at all:

silan -bv test.mp3

ad_open_ffmpeg(): ffmpeg - test.mp3
ad_open_ffmpeg(): ffmpeg - sr:44100 c:2 d:203285 f:8964911
ad_dump_nfo(): sample_rate: 44100
ad_dump_nfo(): channels: 2
ad_dump_nfo(): length: 203285 ms
ad_dump_nfo(): frames: 8964911
ad_dump_nfo(): bit_rate: 132652
ad_dump_nfo(): bit_depth: 0
ad_dump_nfo(): channels: 2
ad_dump_nfo(): meta-data: -
*** stack smashing detected : terminated*

I’ll give a try to the debian package, thanks !


I’ve just been here :

Download the deb package and installed it:

dpkg -i silan_0.3.3-dmo1+deb9u1_amd64.deb 

the install shown me warnings:

Selecting previously unselected package silan.
(Reading database … 105629 files and directories currently installed.)
Preparing to unpack silan_0.3.3-dmo1+deb9u1_amd64.deb …
Unpacking silan (1:0.3.3-dmo1+deb9u1) …
dpkg: dependency problems prevent configuration of silan:
silan depends on libavcodec57 (>= 10:3.3.7); however:
Version of libavcodec57:amd64 on system is 7:3.4.6-0ubuntu0.18.04.1.
silan depends on libavformat57 (>= 10:3.3.7); however:
Version of libavformat57:amd64 on system is 7:3.4.6-0ubuntu0.18.04.1.
silan depends on libavutil55 (>= 10:3.3.7); however:
Version of libavutil55:amd64 on system is 7:3.4.6-0ubuntu0.18.04.1.

dpkg: error processing package silan (–install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.8.3-2ubuntu0.1) …
Errors were encountered while processing:

then when I run silan, same seg fault…

It seems to be related to libav* not compatible with 0.3.3-1 as it happen in the past with debian for @hairmare :

@maydo opened an issue with the same exact problem here:

Hello @hairmare

I followed the instructions on

For the 0.3.2~trusty~sfo-1, the website is down since november 2018

For the OBS instructions, it crashed, probably installing it on a Ubuntu 18.04 is not compatible?

wget -qO- | apt-key add -


echo 'deb ./' > /etc/apt/sources.list.d/hairmare_silan.list

apt-get update

Get:1 bionic InRelease [242 kB]
Get:2 bionic-updates InRelease [88.7 kB]
Get:3 bionic-backports InRelease [74.6 kB]
Get:4 bionic-security InRelease [88.7 kB]
Ign:5 ./ InRelease
Get:6 ./ Release [1,011 B]
Get:7 ./ Release.gpg [481 B]
Ign:7 ./ Release.gpg
Reading package lists… Done
W: GPG error: ./ Release: The following signatures were invalid: EXPKEYSIG E0B6917E66E21B07 home:hairmare OBS Project
E: The repository ‘ ./ Release’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Thanks for your really appreciated help guys :slight_smile:

So the issue you are running into is the Silan package provided by Ubuntu Bionic isn’t working ? I’ve always assumed that it worked because it didn’t provide incorrect data causing tracks that are too short but I never actually tested whether it worked because I didn’t see the functionality of Silan being very useful in the first place. (ie not a lot of music tracks have a bunch of silence at the end of them that I’ve noticed).

So are you trying to fix this because you need Silan to help fix tracks that have excessive silence ? I’m just curious. I guess the next step is for other people to determine whether that the silan debian package bundled with 18.04 produces the same results you are experiencing.

I think that the problem come from an incompatibility between silan 0.3.3-1 and ffmpeg + the libav dependencies under Ubuntu 18.04 :grimacing:

The use case we have:
1 webradio feeds by different people and we have about 900 tracks some are good without +2 secs silence other not with +5 secs more of silence. We cannot rework all tracks that’s why the silence detection is very helpful for us :smiley:

At least @maydo have this issue…
Unfortunately I’m not a C developer so it will not help to find the root cause…

As a workaround, what about using ffmpeg-4.2.1-amd64-static (the version 3.4.6-0ubuntu0.18.04.1 have a start -0 bug) in order to detect the silences and then update the database using a script?

./ffmpeg -i ../test.mp3 -af silencedetect=noise=-50dB:d=1 -f null -

[silencedetect @ 0x75d1b00] silence_start: 202.25487 bitrate=N/A speed=72.3x
frame= 1 fps=0.4 q=-0.0 Lsize=N/A time=00:03:23.27 bitrate=N/A speed=71.9x
video:1kB audio:35017kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[silencedetect @ 0x75d1b00] silence_end: 203.273 | silence_duration: 1.0193

The ffmpeg proposal is a possible fix but it would require a lot of testing and coding to implement it into the framework as a replacement. You are welcome to contribute this. I’m not sure there is a good workaround, you could try installing it from scratch -
I was able to get forward from
git clone
sudo apt install dh-autoreconf autogen libavcodec-dev libavformat-dev libsound1-dev
sudo apt install
cd silan
sudo make install
which will create a 0.4 silan in /usr/local/bin
you can then sudo apt remove silan
then run
silan --version and you should have 0.4 installed.

Probably the easiest workaround for people with bad versions from their package manager.

Thanks you so much @robbt !!! it works prefect now :pray:

How can I force libretime to process the whole db again please?

For those who have the issue under ubuntu 18.04 here is the exact commands:

apt install git
git clone --branch v0.4.0
cd silan/
apt install dh-autoreconf autogen libavcodec-dev libavformat-dev libsndfile1-dev
apt install
make install
apt remove silan

silan --version
silan -b test.mp3

0.417392 Sound On
202.361224 Sound Off

1 Like

For a script to fix this I’d suggest checking out - - I haven’t tested it but it might work.

I’ve tried this .py script and it works !

Thanks for all your great help :slight_smile:

I put the commands here for those who need:

apt install python-psycopg2
pip install psycopg2


File imported/2/prince/prince/prince.mp3 {‘cueout’: 226.77966, ‘length’: 228.023923, ‘cuein’: 0.273401}
-> 1 update

1 Like

I like to report a problem with silan, related to this topic

I have Ubuntu 16.04.7 LTS
at first, I was using silan 0.3 (with original installation)

Then, I found this topic and update to silan 0.4 with the instruction of @robbt and marmotte32

And, update the database with the script from @marmotte32 (above)
So far, so good, the database was updated with the correct “Cue Out” parameter

(maybe related, but also I have problem removing song “Could not delete file because it is scheduled in the future.”, is in other topic)

But, if I upload the same track again (via upload in libretime), the problem persists
It’s really and unexpected behavior, since silen is updated (0.4)

Any guide will help,

1 Like

I think I found the problem

The “LibreTime media analyzer service” was not working
sudo systemctl restart libretime-analyzer

Also the “LibreTime playout service”
sudo systemctl restart libretime-playout



We should consider replacing silan with something ffmpeg or gstreamer based in the future… silan was always kinda a pain to get up and running and it doesn’t look like a sila based “works perfectly everywhere” solution is in our reach rn.

1 Like