On Mon, Feb 18, 2019 at 2:37 PM Romain Beauxis <romain.beau...@gmail.com> wrote:
> What is your crossfade code? The crossfade transition buffers a limited > amount of data, 5 seconds by default. If the transition takes longer than > that to execute, it will stop. You can increase this value via the start_next > parameter. >> Hello! >> >> I've noticed that, after a few days' operation, crossfading stops >> working. Tracks still play, but they're not blended. >> >> This seems to co-incide with no further appearances in the debug log >> of the words "buffer" or "buffering". Here's a complete log from one >> particular transition, the last time "buffer" appears: Thanks for replying, Romain. I always use the "start_next" parameter. And sometimes, it's set really, really long (automatic detection of track end) e.g. 30s, but the crossfade still works. The crossfade code is as simple as this. There's a very short fade-in and fade-out to avoid sudden 'click' starts or stops; but the playlist itself contains the "start_next" annotation that this line picks up: myplaylist = crossfade(fade_out=0.01, fade_in=0.01, conservative=true, myplaylist) It works perfectly for days—then, the crossfading stops. I'm not sure what makes it stop. It's not a full cycle of the playlist (I've calculated the timings), and the playlist is comprised of identically-encoded audio, as I deliberately make a mezzanine format to play from. If there's a way of translating the line (above) into Liquidsoap-1.4.0 testing, or dev, I'll gladly try it. with best wishes, JW _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
