Matthias C. Hormann

Unsure, but possibly related to https://discord.com/channels/760417466450182146/1227018148189048852/1236311158215020586 ?

@warblefly: We value your scripts, and many of us probably know them. They’re great for preprocessing, but I guess what we need here is more on the lines of "on-the-fly",...

@toots Be aware that for follow-up RMS calculations we _cannot_ simply take what’s in the frame but need to respect what has been set by previous `amplify` calculations (like ReplayGain)....

I’d say this is still in 2.3.0, if I’m not mistaken, and bugs users, show hosts, DJs and station owners alike—you simply can’t tell everyone to send a one- or...

@TheRealMattLear Thanks, that would be for production setups, yep. I’m currently evaluating AzuraCast and follow the latest Liquidsoap development with interest, so mine here is mainly a test & evaluation...

@toots If you’re working on this, please try with _both_ Icecast "burst mode" enabled and disabled. In the past, we’ve sometimes seen problems with that feature (although it is a...

I wonder if there might be some hitherto undiscovered buffer/clock problem. Without being able to exactly pinpoint it, I also experience minor audio glitches in my video stream, when listening...

@toots Yep, thanks for the explanation too. Great that you plan to tackle all that clock & buffering stuff again—thinking of how much LS can do, this must be even...

@smimram Not completely: Doesn’t throw an error with LS 2.2.0+git@661820a5a, but doesn’t respect `x=` and `y=` annotations: ```ruby v = image("Nite Radio Testbild.png") a = sine(amplitude=lin_of_dB(-23.0), 1000.0) logo = image("annotate:x=50,y=50,width=100,height=100:niteradio-cover.png")...

Yep, I know, but there are cases where it makes sense to build annotations in preprocessing, and it feels inconsistent that _size_ works but _position_ does not. :-)