search for: 20comunicacion

...29, 2020 at 10:11 AM Yahav Shasha <yahav.shasha at gmail.com> > wrote: > >> This is a real problem that needs to be addressed. >> Anyone has figured a way to mitigate this? >> >> On Sat, Feb 29, 2020 at 4:29 PM Mikel Sanz | 20 Comunicación < >> mikel at 20comunicacion.com> wrote: >> >>> Yes, I also think that 6 years of Beta is too much and now it's too >>> late... >>> >>> El sáb., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort at gmail.com> >>> escribió: >>> >>>> Hi. >&g...

This is a real problem that needs to be addressed. Anyone has figured a way to mitigate this? On Sat, Feb 29, 2020 at 4:29 PM Mikel Sanz | 20 Comunicación < mikel at 20comunicacion.com> wrote: > Yes, I also think that 6 years of Beta is too much and now it's too late... > > El sáb., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort at gmail.com> > escribió: > >> Hi. >> >> With its 80th version, Chrome stopped serving non-secure...

@Mikel You could use Centova's port 80 proxy meanwhile couldn't you? Also. Centova Cast doesn't have an SSL setting for the servers unless you're manually overwriting the server config files.. or is it? On Sat, Feb 29, 2020 at 6:13 PM Mikel Sanz | 20 Comunicación < mikel at 20comunicacion.com> wrote: > For example, in my case, we use several servers with Centovacast, with > several Icecast2 services. Version 2.5 of Icecast2, allows to respond to > http and https connections from the same port, but takes years in beta. > Centovacast does not update its panel, waiting...

...hanks, Albert On Sat, Feb 29, 2020 at 10:11 AM Yahav Shasha <yahav.shasha at gmail.com> wrote: > This is a real problem that needs to be addressed. > Anyone has figured a way to mitigate this? > > On Sat, Feb 29, 2020 at 4:29 PM Mikel Sanz | 20 Comunicación < > mikel at 20comunicacion.com> wrote: > >> Yes, I also think that 6 years of Beta is too much and now it's too >> late... >> >> El sáb., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort at gmail.com> >> escribió: >> >>> Hi. >>> >>> With its 80t...

Hi. With its 80th version, Chrome stopped serving non-secure resources on https pages. This affected the icecast server I run also. I enabled SSL, the issue with Chrome not playing audio got fixed, but I noticed a major drop in the number of listeners. As far as I figured out, the listeners that have the http url in a playlist - listening in winamp, vlc etc. - could listen no more. Those using

Hello! I see that version 2.5 is still in beta2, with very interesting features for me (like improved support for TLS). Does anyone know when it will be launched stably? Any estimated date? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190324/2960ffc6/attachment.html>

Yes, I also think that 6 years of Beta is too much and now it's too late... El sáb., 29 feb. 2020 14:25, Alexandru Matei <alexandru.ort at gmail.com> escribió: > Hi. > > With its 80th version, Chrome stopped serving non-secure resources on > https pages. This affected the icecast server I run also. I enabled SSL, > the issue with Chrome not playing audio got fixed, but I

Hi. I'm trying to set up a mountpoint with authentication type="htpasswd". It's correctly set up, but I have problems to listen in some players. In Winamp, I've tried this URL structure: http://user:password at server:port/mountpoint. But in VLC, with same structure, a window is opened requesting that data every time. In HTML5 players, the same problem. How can I play this

Yes, I know, but, from what I see, the "allow_duplicate_users = 0" option is not really usable, because of these problems that it generates in many players. Therefore, I think it would be interesting for Icecast to allow the option to limit to 2 (or those defined in the configuration), so that it can be used and limited, at least. I think that new option is very necessary. El sáb., 14

Hello. I have same problem, and I think that it's because AAC+ uses VBR and when it's changes, is not the same bitrate, because varies... El jue., 9 may. 2019 a las 21:29, Michel van Dop (<mvandop at xs4all.nl>) escribió: > Hi Paul, > > Thank you for the information. I already try a player to discover the > stream type of both streams if the are the same. > But i can

Yes, it is the first thing I have tried, but I have encountered this problem. If I enable option <option name="allow_duplicate_users" value="1"/>, it works fine. But if set to 0, to limit one connection per user, it does not work properly and forces you to manually enter the data again. It seems that there are players who make 2 requests, and being limited to 1, makes the

I would like to have a private signal, which can only be tuned by whoever has the username and password, and know who is connected. But I wish the URL could be delivered with the username and password, to open it directly on a player or receiving device... Thanks. El sáb., 14 sept. 2019 a las 21:33, Marvin Scholz (<epirat07 at gmail.com>) escribió: > > > On 14 Sep 2019, at 21:09,