Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Zhillsguy]

I installed the latest JRiver (22.0.93) on a fresh install of 32 bit LM18.1..... been quite a few years since using Linux.

This is on an old Dell Core2Duo Laptop, 2 gig ram, JRiver Benchmark of 1250. Install went smooth following instructions, and I did a full update of all apps but no help.

I configured MC for no auto import, just imported a few folders on an external USB drive to test. When MC is open but not playing, ~2% CPU usage. When playing any audio files, MP3 or FLAC, even with playback paused, top shows Xorg and MC through the roof at ~77% and ~51%, whether minimized or not, standard view. Overall load average runs 1.4 to 1.5.

I can dual boot into Win 7 Enterprise x86, playing even much larger 6 channel flacs only takes <2% CPU. Can this be a missing video driver or something else I need to install?

EDIT: I just installed the latest 32 bit Ubuntu Studio, same results.

Thanks.

[mwillems]

Disable the spectrum analyzer in the playing now bar; for some reason it uses a huge amount of CPU on Linux.

[Zhillsguy]

THANK YOU! it's more where it should be now..... ~9%/~6%. Maybe the Spectrum Analyzer should be disabled by default?

This is more or less just an experiment, my Scarlett 2i2 DAC drives me nuts in Windows, works flawlessly in Linux even on this anemic machine. Very revealing.

Maybe when USB Audio 2.0 is fully implemented sometime after Win 10 Creators update gets released it will get better.... only time will tell.

[Awesome Donkey]

Maybe the Spectrum Analyzer should be disabled by default?

I agree with this and was going to suggest this very thing, at least on Linux until if/when it can be improved.

Maybe when USB Audio 2.0 is fully implemented sometime after Win 10 Creators update gets released it will get better.... only time will tell.

Windows 10 Creators Update has native USB Audio 2.0 support finally, I've verified it myself. Not sure if it's "complete" or not (playback is support, recording probably won't be until Redstone 3 or later - but playback is the most important, IMO), but it works fine without needing to install drivers to get sample rates beyond 96 kHz.

[Zhillsguy]

Windows 10 Creators Update has native USB Audio 2.0 support finally, I've verified it myself. Not sure if it's "complete" or not, but it works fine without needing to install drivers to get sample rates beyond 96 kHz.

A little OT... I installed the very latest updates including prerequisite to Creators Update on my Win 10 machine (Enterprise) - my 2i2 and Behringer UMC202HD are recognized as USB Audio 2.0, but both indicate "Additional Setup is Required", and can't get audio out of either one.

I may end up with a Master License for Ver. 23 (have one for Ver. 20) when it comes out.... opens up many more options than Win alone.

[bob]

Disable the spectrum analyzer in the playing now bar; for some reason it uses a huge amount of CPU on Linux.

It is disabled on arm
Really only an issue with very slow machines.

[mwillems]

It is disabled on arm
Really only an issue with very slow machines.

It can also be a serious issue on laptops or anywhere that power usage matters.  I can see anywhere from 20% to 40% CPU utilization (of one core) with it enabled on a U SKU Haswell i5, which doesn't affect playback, but eats up battery like nobody's business. It also seems to create some issues with video playback on mid-tier machines.  It's easy enough to disable it, but it might be worth turning it off by default Linux-wide as it can create a sub-optimal user experience on other than modern desktop CPUs.

I feel like for every person who comes here to troubleshoot a mystery 20%-30% CPU usage, another person will notice the usage and just assume the program is "bloated" and pass it by.  Which is a shame because (generally) MC is the most resource efficient database-driven media player I've ever seen. 

Just my 2 cents 

[bob]

It can also be a serious issue on laptops or anywhere that power usage matters.  I can see anywhere from 20% to 40% CPU utilization (of one core) with it enabled on a U SKU Haswell i5, which doesn't affect playback, but eats up battery like nobody's business. It also seems to create some issues with video playback on mid-tier machines.  It's easy enough to disable it, but it might be worth turning it off by default Linux-wide as it can create a sub-optimal user experience on other than modern desktop CPUs.

I feel like for every person who comes here to troubleshoot a mystery 20%-30% CPU usage, another person will notice the usage and just assume the program is "bloated" and pass it by.  Which is a shame because (generally) MC is the most resource efficient database-driven media player I've ever seen. 

Just my 2 cents 

Makes sense and easy enough to do.