since installing yesterday, I’ve twice noticed when my machine was idling on the lock screen that my fans were spinning more than normal.
Popping into the task manager, I see Audirvana Origin is reporting high power usage and about 10% CPU usage. Player is stopped and not playing, connected to a local USB DAC, in Mini Player mode.
Switching back to Regular view (from Mini Player), CPU usage stops.
Any idea what’s going on here? I’d like to be able to keep Audirvana running while in the background so I can still access it from the remote.
Update: This seems to be an intermittent issue. Left audirvana in full window mode for a couple of hours and came back to it, no significant CPU usage.
When switching to the (basic) mini player with the task manager open, the CPU usage spiked to about 10% on my system and the GPU becomes active. Power usage goes from Very Low to Moderate or High and stays there.
Switching back to full window and the CPU usage goes away. Note, I’m not playing any music while doing this.
Oddly when switching back to the mini player I didn’t experience this again.
I’m wondering if it’s whatever routine is being used to generate the blurred album art on the mini player’s background? Might be a Windows Acrylic API or maybe directx shader programming?
I think I’ve seen the high CPU usage two times out of about 6 visits to my computer since installing.
after switching back to Regular View, the CPU and GPU activity went back to 0. again, I wasn’t playing anything and as far as I could tell there was no database activity going on in the background. It was just idling.
I’m actually trying to reproduce your issue with a HP 845 G7 with AMD CPU but I do not have this behavior at all. The RAM usage is also really low compared to you (66 MB on my side) while I have the mini player opened without a track being played on Audirvāna Origin
I just updated to 1.0.4 (Win11) and so far everything looks good. It did seem to only happen after I’d been idling for sometime on the lock screen, so I’ll see if this new version has the same issue.
A note about our relative differences in RAM usage: my library has almost 30k tracks in it which might have something to do about our memory usage. Several smart playlists as well.
I’ll report back later today and let you know if the problem occurs.