Endless output on the terminal since the upgrade to mpv 0.37

[pitsi]

Describe the bug
Since mpv's upgrade to 0.37, lobster's output on the terminal is that endless wall of text which scrolls until the end of the strream.

To Reproduce
Steps to reproduce the behavior:

1. Make sure you have mpv 0.37 installed.
2. Search and select something to watch as usual.
3. Notice mpv's output on the terminal creating 10+ lines each second.

Expected behavior
Mpv's output, the part where the time is, should be a single line with only the time updating, as you can see at the end.

Screenshots
Terminal output instead of screenshot. All this was created in less than a second!

$ lobster 
Search Movie/TV Show: deadpool
Now Playing - Deadpool
The shared-script-properties property is deprecated and will be removed in the future. Use the user-data property instead.
     Video --vid=1 (h264 1920x800 23.976fps) (4500 kbps)
 (+) Video --vid=2 (h264 1728x720 23.976fps) (1800 kbps)
     Video --vid=3 (h264 864x360 23.976fps) (720 kbps)
     Audio --aid=1 (aac 2ch 48000Hz) (4500 kbps)
 (+) Audio --aid=2 (aac 2ch 48000Hz) (1800 kbps)
     Audio --aid=3 (aac 2ch 48000Hz) (720 kbps)
 (+) Subs  --sid=1 '3d56b43214d80ddd99204a238ae04484.vtt' (webvtt) (external)
Using hardware decoding (vaapi).
AO: [alsa] 48000Hz stereo 2ch float
VO: [gpu] 1728x720 vaapi[nv12]
NoW PlAyInG: Deadpool
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.017 Cache: 3.2s/216KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.015 Cache: 3.2s/215KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.014 Cache: 3.2s/213KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.012 Cache: 3.1s/211KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.011 Cache: 3.1s/209KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.010 Cache: 3.0s/208KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.009 Cache: 3.0s/206KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.008 Cache: 3.0s/205KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.007 Cache: 2.9s/203KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.007 Cache: 2.9s/202KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.006 Cache: 2.8s/199KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.005 Cache: 2.9s/232KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.005 Cache: 2.8s/230KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.004 Cache: 2.8s/229KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.004 Cache: 2.8s/227KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.003 Cache: 2.7s/226KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.003 Cache: 2.7s/224KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.003 Cache: 2.7s/223KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.003 Cache: 2.6s/221KB
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.002 Cache: 2.6s/219KB
[ffmpeg] https: Stream ends prematurely at 151797, should be 3059512
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.002 Cache: 2.6s/219KB
Exiting... (Quit)
AV: 00:00:00 / 01:48:06 (0%) A-V:  0.002 Cache: 2.6s/219KB
Stopped at - 00:00:00

Desktop (please complete the following information):

• OS: Debian testing/unstable x64
• Player: mpv
• Version: 0.37

Additional context
This is more of a question to see if it also happens for other users. It does not happen if I play any other online stream or file, or if I play the m3u8 lobster would play (getting it from lobster -j) as you can see here

$ mpv https://really.long.url/playlist.m3u8
The shared-script-properties property is deprecated and will be removed in the future. Use the user-data property instead.
     Video --vid=1 (h264 1920x800 23.976fps) (4500 kbps)
 (+) Video --vid=2 (h264 1728x720 23.976fps) (1800 kbps)
     Video --vid=3 (h264 864x360 23.976fps) (720 kbps)
     Audio --aid=1 (aac 2ch 48000Hz) (4500 kbps)
 (+) Audio --aid=2 (aac 2ch 48000Hz) (1800 kbps)
     Audio --aid=3 (aac 2ch 48000Hz) (720 kbps)
Using hardware decoding (vaapi).
AO: [alsa] 48000Hz stereo 2ch float
VO: [gpu] 1728x720 vaapi[nv12]
NoW PlAyInG: playlist.m3u8
AV: 00:00:14 / 01:48:06 (0%) A-V: -0.000 Cache: 593s/150MB

The message about shared-script-properties is from the osc I use for mpv and the "NoW PlAyInG" message is from the term-playing-msg parameter that I use. Please ignore them, they have nothing to do with the rest.

p.s. What use is knowing the browser on a script that has nothing to do with browsers? I replaced the requiested parts of the info above with the ones that really matter.

[justchokingaround]

can this be fixed using --msg-level=no ?

[pitsi]

Adding msg-level=all=no in mpv.conf, which seems to be the right syntax, removes ANY terminal output!
But I have a bigger issue now. Lobster does not play anything, even if I comment out the option from mpv.conf!
Here is a log if it can help.

lobster.log

p.s. Due to broken vaapi decoding since the upgrade to mesa 23.3.x, I am forced to use xv since 2-3 weeks ago. And xv, even on 720p, gives me framedrops because the cpu has to do all the rendering.
For me, a user who has been using vdpau since it first came out 15 years ago and vaapi since it was at a pre-pre-pre-alpha level, this feels like returning to the middle ages! Or to using modern day fedora which disabled vaapi for radeon since September 2022. That is the only reason I have stopped using lobster lately, but I will return once vaapi is fixed.

[justchokingaround]

yeah, lobster is broken atm, refer to this:
#184

😔

[pitsi]

It's ok, we can wait :) Who knows, maybe the new version of lobster will come out in time with a patched/updated mesa for vaapi. Thank you for showing me msg-level, I will search for that specific parameter that kills the excessive output.

I assume that lobster uses mpv like so, so there is nothing to check in the script itself.
mpv video.m3u --sub-file=subs.vtt

[justchokingaround]

yep

[pitsi]

Testing time now that lobster works again!

Setting the msg-level to info (msg-level=all=info) makes mpv have the normal output I mentioned above. This has a few weird side effects though, both on lobster and elsewhere.
On lobster, mpv does not exit with q, so I have to press the x button to close it, which makes lobster quit with this
/home/user/bin/lobster: 484: [: Illegal number:

On a perl script that I use for youtube (youtube-viewer by trizen), mpv outputs this in the terminal
NoW PlAyInG: (a 5 mile long url, spanning across 6-7 lines)
instead of nothing at all.

p.s. As I have said above, the "NoW PlAyInG" part comes from this parameter on my mpv.conf
term-playing-msg="NoW PlAyInG: ${media-title}"
Weird setting I know, but I want it to show what song I am listening to when I use mpv to play a youtube playlist as audio only.

[pitsi]

Now that lobster is working, and 3.5 months after my last post here, I can finally test it again. Mpv was upgraded to 0.38 on early May, mesa was upgraded to 24.x on early May too and finally brought back vaapi, so lobster was the last one to complete the month.

Sadly, mpv 0.38 still pops the same endless output when lobster runs it and not on any other occasion, like I have already described. However, I noticed on another issue report that an arch user with mpv 0.37 had the same endless output, so it may be an mpv issue after all. The problem is I can not open an issue report on their github...