Re: Radio Loudness

--===============1504617178191677065==
Content-Type: multipart/signed; micalg="pgp-sha512";
	protocol="application/pgp-signature"; boundary="=-mhzxh2BLa3/YdRVJup0I"


--=-mhzxh2BLa3/YdRVJup0I
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Good afternoon,

On Thu, 2022-08-25 at 14:31 +0200, Marvin Scholz (ePirat) wrote:
> Accidentally replied off-list first, here again my reply on-list.
> Sorry for the confusion.
>=20
> Hi, see my replies inline:
> > > On 25. Aug 2022, at 13:48, [email protected] wrote:
> > > The Problem is the change from Live TV to Radio on our Android
> > > Set-Top-Box.
> > > We are looking for a solution to align the Radio Loudness over
> > > the 500 Radio Channels.
> > >=20
> > > So you don't see any possibility to send an ExoPlayer message
> > > (like a Metadata) to the Player?
>=20
> So if I understand correctly you want to send over a loudness
> adjustment parameter over for a specific radio station on start of
> playback?
>=20
> [...]
>=20
> Icecast does not send any explicit messages over to the player, it
> just provides a HTTP stream.
>=20
> One option would be to include a special HTTP header in Icecasts
> response, and make ExoPlayer use that (not sure if it provides
> necessary API for that though).
>=20
> > > A static setting on the ExoPlayer in the client is not an option,
> > > because the Player is also used by other applications.
> > > Changing Volume in Set-top-box will affect all applications.=20
>=20

> So you are not even invoking ExoPlayer programmatically in a way
> where you can set such settings? Then even the approach I suggested
> above might not be feasible.

I generally agree with what Marvin said. However there is also to be
taken into account what parts of infrastructure is under your control
and what technologies are used.

E.g. Opus supports a (R128 compatible) output gain.


> However if you want someone to look further into the matter, this
> might be beyond what volunteers on this list can do, especially as it
> is not really about solely Icecast but your specific
> integration/client software.

Fully agree here, so hopefully you don't me sending you a reply off-
list as well. :)


With best regards,

--=20
Philipp Schafft (CEO/Gesch=C3=A4ftsf=C3=BChrer)=20
Telephon:  +49.3535 490 17 92
Website:   https://www.loewenfelsen.net/
Follow us: https://www.linkedin.com/company/loewenfelsen/

L=C3=B6wenfelsen UG (haftungsbeschr=C3=A4nkt)     Registration number:
Bickinger Stra=C3=9Fe 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015

--=-mhzxh2BLa3/YdRVJup0I
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSioTDOaTVl9zTbkFXy2Q8SuF0OrwUCYwi5qgAKCRDy2Q8SuF0O
r9hHAQDjSdnKgDtlgNcAFVnDyzpYkM1Rlclx43FtzQ+rfd53iQD/f398U/q03Ni8
d+0ZtA1LROSZumxYYf0Yw6tTObamuAk=
=e0x6
-----END PGP SIGNATURE-----

--=-mhzxh2BLa3/YdRVJup0I--


--===============1504617178191677065==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Icecast-dev mailing list
[email protected]
http://lists.xiph.org/mailman/listinfo/icecast-dev

--===============1504617178191677065==--