Yeah I have noticed some changes on that level. Essentially, it looks like
we are able to run do better parallel initialization of sources. On my
machine I can see more than one core being utilized during the initial
sources preparation, which is cool.
I'm not sure yet what to do in your case. What's the total CPU load when
running on 2.1.4? It seems to me that the script is already on the edge of
the maximum CPU/memory capacity in 2.1.4 so any increase in CPU and/or
memory usage, being a bug like we just fixed or an "improvement" as I think
this is, ends up pushing it to the wrong side and choking.
Le jeu. 18 mai 2023 à 06:16, p····· g······· <pra...@gmail.com> a écrit :
> hi Romain!
>
> just tried it - the radio in question just chokes on startup, eating all
> of
> the cpu (the config you have)
> catchup notices don't even make it to the log, that's where it ends:
>
> 2023/05/18 14:05:10 [studija:3] Decoding...
> 2023/05/18 14:05:37 [switch_17:3] Switch to buffer.producer_0 with
> transition.
> 2023/05/18 14:05:37 [add:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [add:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [fade_in:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [on_track_7:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [on_metadata_0:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [on_track_6:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [fade_in:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [amplify:3] Content type is {audio=pcm(stereo)}.
> 2023/05/18 14:05:37 [amplify:3] Content type is {audio=pcm(stereo)}.
>
> and then i have to kill it because there is no sound, just cpu usage which
> corresponds with one core eaten fully.
>
> regards,
> Pranas
>
> -----Original Message-----
> From: Romain Beauxis
> Date: 2023 m. gegužės 18 d. 03:40
> To: savonet-users@lists.sourceforge.net
> Subject: Re: [Savonet-users] 2.2 bug on windows
>
>
> I was able to identify and fix the issue I believe. I recommend you try
> the
> latest `rolling-release-v2.2.x` build!
>
>
> Le lun. 15 mai 2023 à 18:19, Romain Beauxis <romain.beau...@gmail.com> a
> écrit :
>
> It's a catch 22, the CPU will start burning when processing it too slow to
> produce content at real rate but this might start with an increase in CPU
> usage.
>
> I can indeed confirm the increase in CPU usage under normal script
> conditions. I'm investigating it now.
>
>
> Le dim. 14 mai 2023 à 16:58, p····· g······· <pra...@gmail.com> a écrit :
> hi!
> I think the CPU usage increases when "catch-up needed" start popping up...
> the question is perhaps what causes time starvation :o
> some fade implementation or what... because there are plenty of free
> resources on the server.
>
> P
>
>
>
> _______________________________________________
> Savonet-users mailing list
> Savonet-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
