Le sam. 20 mai 2023 à 23:08, Romain Beauxis <romain.beau...@gmail.com> a écrit :
> > Le sam. 20 mai 2023 à 13:02, Tyna Pelletier-Bilodeau <ecole.t...@gmail.com> > a écrit : > >> Hi Romain, >> thank you, I will try this and see how it goes. >> >> By the way I've been toying a bit with harbor, and wondered if there was >> a way to have liquidsoap waiting a little in case the live drops out >> for a few seconds instead of immediately swtching back to the main >> source? >> >> I stream to the input over wireguard, which means sometimes I'm roaming >> to get a signal from 4g towers. I'd like if I could stream some silence >> instead of immediately falling back to the main source, which is another >> live done with input.pulseaudio, and which is jarring since the >> transition happens out of nowhere. Maybe up to say 10 seconds of delay >> before giving up and switching to the main source, is this possible? >> > > Yes, it's a pretty legit use-case. I'm sure it's possible right now but > might be a little tricky to setup. I'll think about what we can do to make > this easy to setup. > I have a PR making a couple of tweaks to make it possible: https://github.com/savonet/liquidsoap/pull/3098 > > >> On Sat May 20, 2023 at 2:18 AM CEST, Romain Beauxis wrote: >> > Hi! >> > >> > Le ven. 19 mai 2023 à 02:39, Tyna Pelletier-Bilodeau < >> ecole.t...@gmail.com> >> > a écrit : >> > >> > > Hi, >> > > it looks like after a connection timeout with liquidsoap 2.1.4, it >> can't >> > > automatically retry to reconnect to icecast. I'm not sure weather it's >> > > because I use a tls enabled port or not, but in any event this >> shouldn't >> > > be happening. It is perfectly able to try reconnecting if for example >> > > the icecast server has a too low maximum number of sources allowed, >> but >> > > when it is already streaming, and out of nowhere there's a problem, it >> > > seems totally unable to do anything for itself. >> > > >> > > 2023/05/13 18:06:28 [asmrpmp3:3] Connection setup was successful. >> > > 2023/05/19 08:12:42 [asmrpmp3:2] Error while sending data: could not >> > > write data to host: connection timeout! >> > > 2023/05/19 08:12:42 [asmrpmp3:3] Closing connection... >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Source asmrpmp3 failed while >> > > streaming: could not close connection: SSL connection() error: >> > > error:00000000:lib(0)::reason(0)! >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Raised at Cry.close in file >> > > "src/cry.ml", line 193, characters 11-34 >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Called from >> > > Icecast2.output#icecast_stop in file "outputs/icecast2.ml", line 596, >> > > characters 14-34 >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Called from >> > > Icecast2.output#icecast_send in file "outputs/icecast2.ml", line 509, >> > > characters 10-27 >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Called from >> > > Output.encoded#send_frame.output_chunks.f in file "outputs/output.ml >> ", >> > > line 240, characters 10-24 >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Called from >> > > Output.output#output in file "outputs/output.ml", line 174, >> characters >> > > 10-35 >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] Called from >> > > Clock.clock#end_tick.(fun) in file "clock.ml", line 300, characters >> > > 14-22 >> > > 2023/05/19 08:12:54 [clock.pulseaudio:2] >> > > 2023/05/19 08:12:54 [asmrpmp3:3] Closing connection... >> > > 2023/05/19 08:12:54 [clock:2] Error when leaving output asmrpmp3: >> could >> > > not close connection: SSL connection() error: error:0A000126:SSL >> > > routines::unexpected eof while reading! >> > > 2023/05/19 08:12:54 [main:3] Shutdown started! >> > > >> > > Any ideas what I can do to mitigate this issue? I'm thinking of >> checking >> > > out the latest 2.2.x but I don't know if that has been solved or not, >> if >> > > it was even known to begin with, but I don't know how I could try this >> > > out if I'm using opam. >> > > >> > >> > This looks like a leak in the resources initializations. >> > >> > I would definitely try with `2.2.x`. The SSL stack was entirely >> rewritten >> > there and some resource cleaning issues were fixed. And we also have TLS >> > support now so you have two stacks to try if one still has issues. >> > >> > To use SSL/TLS in v2.2.x you can now pass an abstract transport >> variable. >> > This is explained here: >> > https://www.liquidsoap.info/doc-dev/harbor_http.html#https-support >> >> >> >> _______________________________________________ >> Savonet-users mailing list >> Savonet-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/savonet-users >> >
_______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
