More > JRiver Media Center 31 for Mac

JRiver Media Center 31.0.65 BETA for Mac Silicon/Intel Universal build

<< < (2/3) > >>

bob:
The 6 seconds before the end of track makes sense as you noted since it's when the buffering of the next track starts using MC's default settings.
Are you ever seeing the high CPU use that I'm seeing? That puzzles me the most.

EnglishTiger:
It's got me puzzled too as the only time I saw those higher values was when I had the things that I knew would increase the CPU usage on the screen, like the Spectrum Analysers, the DSP Analyzer Window open, or multiple images and thumbnails visible.


Hopefully it's not something we once encountered at the bank when 3 identical brand new "Dec Vax" computers kept giving different results while they were being commissioned, all 3 ended being replaced by DEC. DEC eventually discovered that they all had CPU's that were operating at different levels of efficiency.

EnglishTiger:
Bob - This morning I had MC31.0.36 running for over 4 hours and I kept getting the same values/results for the CPU and GPU as I was getting yesterday when only the Progress Bar was being updated with only a TrackInfo Plugin on the screen.

I also got the M1 MacBook Air out to see what values it would give me they were:-
between 7.1% and 8.9% for the CPU and between 3.4% and 5.3% for the GPU with a peak CPU value of 11.9% on track change.
N.B. The Macbook Air was on Mains Power during the testing.

It is possible that the increases could be down to the MacBook being less powerful and/or the fact that the tracks it was playing are held on the Internal SSD whilst the ones the Mini was playing are on a couple of M2 cards in a dual M2 shell attached via a ThunderBolt port.

I'm not sure if this is down to me or Apple coming up with an OS that is not MacBook Air friendly.

Since the MacBook hasn't been used since MC28 and was on Ventura 12.4 I updated it to Sonoma and then installed MC31.0.65

Problem #1 - No matter how many times I clicked on the MC31 menu bar they would not drop down. Thankfully I was able to do everything I needed to do to the PlayerBar Display, and TrackInfo Plugin to make it the same as the Mini.
Problem #2 - The Mac Activity Monitor was telling me that I was the "User" for every app/task/process it listed, unlike the Mini which listed several users.

This is going to make you laugh because I've come up with a Hilarious, but probable, reason why everybody is getting higher values than me.
The one obvious difference between your set-up and mine is on this side of the pond we use 200-240 Volts AC, whilst on your side of the pond it's 110 Volts.
I can't help wondering if the Transformers that accompany the US PC's are producing a lower output than those that accompany the UK PC's.

bob:
ET I feel like it's something in OS setup somehow. I'm getting wildly higher CPU usage than you simply playing a track without DSP on a M1 mini on Sonoma, 50-80% depending on whether or not I have the spectrum analyzer on.
I could upgrade the machine to the 14.1 beta to see if Apple has a problem that they fixed but it's a lot of time going backwards so I'm a bit reluctant.

I'm am NOT having the menu bar issues at all though. Do you still see that when MC is the only app running?

I am assuming that activity monitor has always produced CPU usage figures based on 100% meaning 100% of one core. If pre-Sonoma that wasn't the case it would explain the difference (but not the menu bar issue of course).

blgentry:
I think these differences in CPU usage are immaterial.  They do not affect anything that I can tell.  My 10 to 12% CPU has no effect on my system.  Even the 35 to 40% I see with Theater View open doesn't really phase me.  The system can't tell it's happening.  Everything works as it should.

The menus, which do not work properly on my system, are a much bigger functional issue.
My system:
M1 MacBook Pro 13"
Sonoma 14.0
MC 31.0.65

Menus stop working entirely after a while.  Upon restart they work, but they are very inconsistent.  Sometimes I have to click a few times to get one to come up.  Other times they pop from one menu to another as I move my mouse.  Then they stop working at all, and just highlight the menu title with no menu displayed.

Thanks for working on this.  :)

Brian.

Navigation

[0] Message Index

[#] Next page

[*] Previous page