aplay: Weird delay millisecs shown when overrun/underrun occurs without -v

[kabe-gh]

[root@cygnus ~]# aplay -D pipewire a.wav
Playing WAVE 'a.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
underrun!!! (at least 1746767081231.829 ms long)
underrun!!! (at least 1746767081072.539 ms long)
underrun!!! (at least 1746767081112.852 ms long)
underrun!!! (at least 1746767081097.655 ms long)
underrun!!! (at least 1746767081099.998 ms long)
underrun!!! (at least 1746767081083.744 ms long)
underrun!!! (at least 1746767081100.482 ms long)
underrun!!! (at least 1746767081219.076 ms long)
underrun!!! (at least 1746767081111.242 ms long)
underrun!!! (at least 1746767081071.547 ms long)

With -v, the delay display is sane.
This seems that some initialization of alsa-lib is only done when -v is added.
The attached patch fixes this, but was it had a reason to not initialize without -v ?

patch-overrun-diag-monotonic.patch

[perexg]

This problem should be reported for pipewire plugin code. The trigger timestamps MUST be updated ALWAYS (they do not depend on the setup for timestamps for the hw_ptr updates - snd_pcm_sw_params_set_tstamp_mode).