Michael wrote:
> On Monday, 29 September 2025 06:00:40 British Summer Time Dale wrote:
>> Dale wrote:
>>> Michael wrote:
>>>> I'll guess mpv is trying to play a stream and it finds some inconsistency
>>>> in the data chunks of the stored stream.  I can think of two ways to ask
>>>> it to shut up and not bother you.  Check the man page for mpv, it
>>>> mentions:
>>>>
>>>> --msg-level=<module1=level1,module2=level2,...>
>>>>
>>>> where you can set the level as "no" to silence it completely, or specify
>>>> the module which is causing all these STSC messages and just silence
>>>> that alone.
>>>>
>>>> The second potential entry is the path to store its log.  Perhaps if you
>>>> set this to /dev/null it will not print anything out.
>>>>
>>>> --log-file=<path>
>>>>
>>>> Once you find something which works on a terminal, try modifying your
>>>> ~/.config/mpv/mpv.conf file options to achieve the same.
>>>>
>>>> You may find this useful:
>>>>
>>>> https://deepwiki.com/hooke007/mpv_doc-CN/2.1-configuration-options
>>> I'm going to try the /dev/null option.  If I can't fix what it is
>>> complaining about, I'll just shut it up.  ROFL 
>>>
>>> Works for me.  ;-) 
>>>
>>> Thanks.
>>>
>>> Dale
>>>
>>> :-)  :-) 
>> I tried the /dev/null option for mpv and the file is back and already
>> north of 1Gbs.
> Can you please show the content of your ~/.config/mpv/mpv.conf 
>

I use the one in /etc.  I'm the only one on this thing anyway.  Here is
the contents of it. 


# Write your default config options here!

#ytdl-format=bestvideo[height<=?720]+bestaudio/best
ytdl-format=bestvideo[height<=?1080]+bestaudio/best

--osd-on-seek=no
--sub-create-cc-track=no
--alang=en,eng
title='${filename} - mpv'
--cache=yes
--cache-secs=480
--log-file=/dev/null



The one in /home is all commented out except for this one lonely line. 


--no-keepaspect-window


>> Either it isn't mpv, seems to me it is, then what else
>> can I do to stop this file from getting so large?  I might add, I have
>> other options in the mpv file and they work.  So, I'm dealing with the
>> right file at least. 
>>
>> Any other ideas?  I'm thinking I need to do something with sddm itself. 
>> It does seem to be the one writing to this file.  My google searches
>> turned up nothing like this.  Is this a Gentoo thing?  And maybe just
>> affecting me for some reason????
>>
>> Thanks. 
>>
>> Dale
>>
>> :-)  :-) 
> As I understand it, sddm captures what applications are reporting within the 
> desktop session.  I'm thinking if you silence the application, it will stop 
> printing logs.
>
> Did you try to find out in the terminal which mpv module is responsible for 
> these errors you see in the sddm log and silence that one specifically, or 
> silence them all if you are not bothered to catch any problems reported by 
> mpv?  For example when I silence messages from the vo/gpu and osd/libass my 
> terminal output is *very* quiet.


I looked at the man page again, like I've done in the past.  It is a lot
like reading Greek most of the time.  I did use Konqueror and the
man:mpv trick to pull up the whole thing, and then search for module.  I
found this little gem.  No idea if this works or not tho.  It's from the
man page but sometimes what it shows is only a guide, not what actually
works.


--msg-level=all=no


The file that showed back up was so large, I couldn't open it or
anything.  Honestly, I don't understand why any program will create a
file that is so large that it is useless.  At some point, either remove
some of it or just stop repeating the same things millions of times. 
Just saying.  Either way, to stop it, I deleted the file.  I can only
guess it was the same error as before. 

Oh, I've never played a video from the command line.  If this new method
doesn't work, I'll try that. 

I need to create the file again to see if that option works.  I'll post
back either way.  May help some other poor soul that runs into this. 

Dale

:-)  :-) 

Reply via email to