i think i found what really causes extreme memory leaks - that's the
harbours in the first place.
also, i thought it was "fixed" in v2, but that was just a coincidence that
i've put LS behind firewall and allowed only known IPs to connect.
once i opened it to the wild again, the radio processes
hello!
can it be that liquidsoap processes share some data inbetween them somehow?
via some temporary files even perhaps?
i noticed strange behaviour - sometimes a radio would start and get stuck
playing nothing, and the only fool-proof method is to shut down all the
radios which share that
hiya!
some more insights:
as there is still a memory leak if harbors are being used (and on some
radios they are, daily...), i have to re-start service every night.
it used to be "kill forcefully" with v1.x, so as we see it's getting
somewhat better ;)
however.
one time out of ten it still
so, i have let the LS v2 run for a little longer and here's the conclusion:
if there are _no harbours / no activity in harbours_ and _no activity over
telnet_ LIQUIDSOAP DOES NOT BLOAT!!! it kept under 300MB of RAM after
running for 10 days.
i have connected through telnet a few hours ago to
Hi,
I'm glad to hear that the memory leak is getting better.
We have started a migration page to help users migrating from 1.4.x to
2.x so this feedback is very useful.
Le lun. 21 juin 2021 à 17:57, p· g··· a écrit :
> now this crossfade doesn't work:
>
> def crossfade
Thanks, Romain!
the vorbis issue is sorted, all cool!
all radios working with some features disabled and i'll list the parts i had
to comment-out here:
strip_blank doesn't work - as you've already explained that skip_blank is
now blank_skip, same might apply here.
now this crossfade
Le jeu. 17 juin 2021 à 09:38, p· g··· a écrit :
>
> hello!
>
> so eventually i've managed to move my radios to a V2
> however i had to throw away great deal of configuration and loose
> functionality.. would be a huge message if i put it all together, so first
> the main ones (and perhaps
hello!
so eventually i've managed to move my radios to a V2
however i had to throw away great deal of configuration and loose
functionality.. would be a huge message if i put it all together, so first
the main ones (and perhaps you could give me the key to solving such
issues):
#1
ogg
to vorbis there..
>
> thx,
> p
>
> -----Original Message-
> From: Romain Beauxis
> Date: 2021 m. birželio 4 d. 02:04
> To: savonet-users
> Subject: Re: [Savonet-users] Liquidsoap 2.0.0-beta1 - windows issues
>
>
> Yes, we're having issues compiling w
g has flac encoder, but how to
put it into an ogg container?.. all ogg references link to vorbis there..
thx,
p
-Original Message-
From: Romain Beauxis
Date: 2021 m. birželio 4 d. 02:04
To: savonet-users
Subject: Re: [Savonet-users] Liquidsoap 2.0.0-beta1 - windows issues
Yes, we're
Yes, we're having issues compiling with both `ffmpeg` support and all other
encoders. We believe that ffmpeg brings all the other encoders
functionalities and more so it was decided to only build with ffmpeg
enabled. I'll make sure to add it to the release description.
For a mp3 encoder, you
so here we are, all the configs wouldn't start.
for example, it wouldn't spit out even mp3:
Error 12: Unsupported format:
%mp3(stereo,bitrate=320,samplerate=44100,id3v2=fal
se).
You must be missing an optional dependency.
and also it swears about my fades:
fade.out =
12 matches
Mail list logo
