Issue with updating volume on any stream/track with latest Lavalink Dev build

[lavalink-devs]

Issue with updating volume on any stream/track with latest Lavalink Dev build

[shikhir-arora]

It's not limited to streams; changing volume for normal YouTube tracks breaks with the same Encoding -1 error on any Lavalink implementation using the new Lavaplayer (1.2.63) -- due to changes in sedmelluq/lavaplayer@81672b2

[freyacodes]

That sounds odd. Can you check if 33b639b works now?

[shikhir-arora]

Yes, that works fine as expected, it would have to do with the changes in AudioTrackBuilder I'd assume in 1.2.63 since it got a bit of a change.

This doesn't affect Lavaplayer clients directly, they work perfectly fine, just Lavalink, so it's something on that end. Doesn't matter the source, the volume op is broken - https://sentry.io/share/issue/9e36d12515924524967490d692c723ff/

Also if it helps, seeking works fine, so it's just a volume change. Presumably something with some buffer change since sending a 100 volume (unity) doesn't break it, only when it has to encode from volume changes.

[shikhir-arora]

One thing that may help: Frederikam/Lavalink@d643aea -- the addition of volume in the play op for the Lavalink client here caused the player to throw the error right away (i.e. with FredBoat that uses the Java client), while using another client implementation that doesn't send the volume with the play op (as shown in the initial post) works fine, until a manual volume change op is sent.

[shikhir-arora]

Strangely enough after going back, trying it a different way and looking at the process in more detail - it seemed to be an odd user permission issue with the systemd profile I was using. It works fine now and I've tested that on two servers, so it should be fine to push back to 1.2.63 -- sorry about any hassle. Was certainly not what I was expecting. 🧐