Hi, Romain!
Oh yeah, so it's not then that the windows compiler sucks.
Well, I have another radio running which does not leak and does not use
flac, BUT being lossless is my main point... the one and only lossless radio
nation wide and hell knows, maybe in whole baltics :)
if i used compression at with liquidsoap it would lead to double compression
(compressed input -> decode -> compress -> output) and that way, non-kosher
archive files. now it's all pure, lossless signal comes in at the event, it
goes through liquidsoap's pipeline in same format without any alterations,
goes out to archive file untouched and also goes out on air without any
mangling, just a slight gain decrease (to avoid overload bug).
there are players (windows media player classic, vlc, winamp) which play
lossless flac radio just fine and some people use it.
my lossless radio with liquidsoap is kind of statement and it shows that it
is possible to sustain even on personal / private basis.. and it's been like
that for five years.
i remember version 1.2 (32bit only) didn't leak. it had other bugs and often
it took two attempts to connect to source, but it didn't leak..
so, although flac-less version could be the work around, i wouldn't go for
that.
the other interesting thing is that memory bloat doesn't only occur on
harbor connect (although that's the only foolproof way to kickstart it i've
found), but also sometimes on telnet connect to the radio that's using ogg
flac.
for example now it's been two days since process start and no harbor
connects, and mem usage is at 650MB and not growing at the moment.
eventually it will, but who knows when. it's a sign that it's already
corrupted in some way and telnet trick should work.
so i connect to telnet and it starts ticking up... 664MB now... and going up
at around 10 kilobytes per second.
uptime
2d 11h 36m 04s
END
i won't have any flac incoming till monday evening (nothing to change in
harbors, right?) and i'm also shutting down flac output till then.. let's
see if it doesnt start leaking, two days should be enough.
yet the FLAC stream support is what makes liquidsoap a proper tool for
audio. lossy codecs are a piss in the soup, you may not notice, but it's
still there! let's leave them to soundcloud and the likes ;)
regards,
Pranas
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
