Thanks for the report!
Le ven. 5 mai 2023 à 03:35, p····· g······· <pra...@gmail.com> a écrit :
>
> hi Romain!
> oh wow, 2.3 is round the corner already? ;o
>
>
> some more data about 2.2 behaviour on win:
>
> sometimes it gives interesting insigths on the tracks finding them as
> video - is it because of embedded artwork?
>
> [decoder.ffmpeg:3] FFmpeg recognizes "a:/Vladislav Delay - iS.mp3" as video:
> {codec: mjpeg, 700x700, yuvj444p}, audio: {codec: mp3, 44100Hz, 2
> channel(s)}
Yes, correct. This ffmpeg's way of reporting a cover image metadata tag.
> also permission denied errors plague logs now:
>
> 2023/05/04 23:02:34 [decoder.ffmpeg:3] Decoded content-type for
> "a:/Vladislav Delay - iS.mp3": {audio=pcm(stereo)}
> 2023/05/04 23:02:34 [decoder.id3:2] Error while decoding file tags:
> Permission denied in read()
> 2023/05/04 23:02:34 [decoder.id3:2] Error while decoding file tags:
> Permission denied in read()
>
> i'm not sure what's up with these permission denied things. how can the tags
> have other permissions than music data of same file?
This is weird. I have pushed some tweaks to the metadata library.
Anything special about these files?
> also i noticed some increased CPU usage by one of my radios and a strange
> latency fluctuation - how comes? nothing changed, catchups used to be very
> short and rarely happen, and now this, extensively, with elevated CPU usage,
> around 10% instead of usual 2%:
>
>
> 2023/05/04 22:11:53 [clock.main:2] We must catchup 6.26 seconds!
> 2023/05/04 22:11:54 [clock.main:2] We must catchup 6.77 seconds!
> 2023/05/04 22:11:55 [clock.main:2] We must catchup 7.13 seconds!
> 2023/05/04 22:11:56 [clock.main:2] We must catchup 7.49 seconds!
> 2023/05/04 22:11:57 [clock.main:2] We must catchup 7.93 seconds!
> 2023/05/04 22:11:58 [clock.main:2] We must catchup 8.32 seconds!
> 2023/05/04 22:11:59 [clock.main:2] We must catchup 8.54 seconds!
> 2023/05/04 22:12:00 [clock.main:2] We must catchup 8.65 seconds!
> 2023/05/04 22:12:01 [clock.main:2] We must catchup 8.76 seconds!
> 2023/05/04 22:12:02 [clock.main:2] We must catchup 8.96 seconds!
> 2023/05/04 22:12:03 [clock.main:2] We must catchup 9.12 seconds!
> 2023/05/04 22:12:04 [clock.main:2] We must catchup 9.42 seconds!
> 2023/05/04 22:12:05 [clock.main:2] We must catchup 9.66 seconds!
> 2023/05/04 22:12:06 [clock.main:2] We must catchup 9.99 seconds!
> 2023/05/04 22:12:07 [clock.main:2] We must catchup 10.15 seconds!
> 2023/05/04 22:12:08 [clock.main:2] We must catchup 10.44 seconds!
> 2023/05/04 22:12:09 [clock.main:2] We must catchup 10.92 seconds!
> 2023/05/04 22:12:10 [clock.main:2] We must catchup 11.26 seconds!
> 2023/05/04 22:12:11 [clock.main:2] We must catchup 11.49 seconds!
> 2023/05/04 22:12:12 [clock.main:2] We must catchup 11.85 seconds!
> 2023/05/04 22:12:13 [clock.main:2] We must catchup 11.76 seconds!
> 2023/05/04 22:12:14 [clock.main:2] We must catchup 11.26 seconds!
> 2023/05/04 22:12:15 [clock.main:2] We must catchup 10.87 seconds!
> 2023/05/04 22:12:16 [clock.main:2] We must catchup 10.36 seconds!
> 2023/05/04 22:12:17 [clock.main:2] We must catchup 9.93 seconds!
> 2023/05/04 22:12:18 [clock.main:2] We must catchup 9.43 seconds!
> 2023/05/04 22:12:19 [clock.main:2] We must catchup 9.00 seconds!
> 2023/05/04 22:12:20 [clock.main:2] We must catchup 8.51 seconds!
> 2023/05/04 22:12:21 [clock.main:2] We must catchup 8.09 seconds!
> 2023/05/04 22:12:22 [clock.main:2] We must catchup 7.62 seconds!
> 2023/05/04 22:12:23 [clock.main:2] We must catchup 7.25 seconds!
> 2023/05/04 22:12:24 [clock.main:2] We must catchup 6.79 seconds!
> 2023/05/04 22:12:25 [clock.main:2] We must catchup 6.36 seconds!
> 2023/05/04 22:12:26 [clock.main:2] We must catchup 5.94 seconds!
> 2023/05/04 22:12:27 [clock.main:2] We must catchup 5.56 seconds!
> 2023/05/04 22:12:28 [clock.main:2] We must catchup 5.10 seconds!
> 2023/05/04 22:12:29 [clock.main:2] We must catchup 4.64 seconds!
> 2023/05/04 22:12:30 [clock.main:2] We must catchup 4.17 seconds!
> 2023/05/04 22:12:31 [clock.main:2] We must catchup 3.71 seconds!
> 2023/05/04 22:12:32 [clock.main:2] We must catchup 3.27 seconds!
> 2023/05/04 22:12:33 [clock.main:2] We must catchup 2.80 seconds!
> 2023/05/04 22:12:34 [clock.main:2] We must catchup 2.37 seconds!
> 2023/05/04 22:12:35 [clock.main:2] We must catchup 1.87 seconds!
> 2023/05/04 22:12:36 [clock.main:2] We must catchup 1.41 seconds!
> 2023/05/04 22:12:39 [clock.main:2] We must catchup 0.21 seconds!
> 2023/05/04 22:30:40 [clock.main:2] We must catchup 0.32 seconds!
>
> what's also strange is that it elongates and shortens by itself. is it some
> drifty clock in play? is it something to do with hpet vs other types of
> timers in PC? parts of program using one timer and parts - another?
Let's figure this one out. Do you use replaygain in the script?
Anything more you could share about the script in question?
Thanks,
-- Romain
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
