The quality can’t go higher than the default Remote Quality set at the client - I would assume.
Set the client’s Remote Quality to Original/The Max you’d like to see (before playback begins) - see if the behavior changes.
I recently (last 6 months or so) had occasion to see if AQ worked - and it did. I have a friend that had some UberSnot Bandwidth - “Frontier” in West Virginia. I had him set the Remote Quality to Max. I turned on AQ.
He’d start - transcoding, of course - with a decent enough picture, then Frontier would start coughing up hairballs, but AQ kept the stream going, even if it had to transcode an item to the point it made Apollo 11 Video Footage look like IMAX. It was horrific.
No buffering tho. AQ worked as intended.
He got some real internet - and I turned AQ off. I did see it work however.
If you have great bandwidth it’s very likely you’ll never see AQ work as you have no need for it… unless you need to test the transcoder. AQ will absolutely have that thing engaged.
If you’re trying to employ AQ as a work-around to setting Remote Quality manually in every Client App that connects to your server - forgettaboutit.
Spend a penny in here with a vote - we’ve been screaming about it for decades and now we’re hearing a bit of hope over the background din of crickets:
