Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mixxx 1.6.1 High CPU Usage #5119

Closed
mixxxbot opened this issue Aug 22, 2022 · 8 comments
Closed

mixxx 1.6.1 High CPU Usage #5119

mixxxbot opened this issue Aug 22, 2022 · 8 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: hippako
Date: 2009-03-15T12:52:52Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp343153
Attachments: [Mixxx launch output](https://bugs.launchpad.net/bugs/343153/+attachment/585370/+files/Mixxx launch output)


(Mixxx 1.6.1) Waveform increases CPU up to 95-100%, without waveform everything is back to normal 20-30% of CPU usage. This happens with Compiz Enabled
(Mandriva Cooker) 2009.1. Also in Ubuntu Studio.

@mixxxbot mixxxbot added the bug label Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2009-03-16T03:51:39Z


please provide the specs of your machine. Type and speed of CPU, video card, video card drivers (oss+ver or proprietary+ver), RAM... anything else you feel we would need to know to recreate the conditions Mixxx runs in.

@mixxxbot
Copy link
Collaborator Author

Commented by: hippako
Date: 2009-03-16T10:36:13Z


Hi,
Now Mandriva Cooker 2009.1, also with 2009. Tested with Ubuntu Studio 8.10
too. Mixxx versions: 1.6.0 and 1.6.1. Spec: AMD Sempron 2600+ 1.6, 1024MB.
of RAM, Nvidia Geforce 6200, video drivers from Mandriva
official-proprietary driver version 180.29 (Happens with older drivers
also).

@mixxxbot
Copy link
Collaborator Author

Commented by: hippako
Date: 2009-03-16T10:39:36Z


Sorry, I reply from my Gmail account, hiend is also my account from
launchpad.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2009-04-05T17:43:42Z


Hi hiend, with compiz disabled, does this happen?

@mixxxbot
Copy link
Collaborator Author

Commented by: hippako
Date: 2009-04-09T08:46:01Z


Hi! No it doesn't happen with compiz disbled, it works at normal range at
15-20%

@mixxxbot
Copy link
Collaborator Author

Commented by: hippako
Date: 2009-05-10T12:59:36Z
Attachments: [Mixxx launch output](https://bugs.launchpad.net/mixxx/+bug/343153/+attachment/585370/+files/Mixxx launch output)


Hi, I've install Mixxx 1.7.0 Beta1 today on ubuntu 9.04 and when I try to launch it, it says: Failed to execute child process "pasuspender mixxx" (No such file or directory). So I launch it from terminal and attach the output:

  Every time when I try to start Mixxx it says: Failed to open your audio device(s) please verify your selection in the preferences, so I have to choose and switch my sound card in audio output every time I start Mixxx.

  I've noticed that CPU usage is optimised and now 1.7.0 Beta uses less than 50% of CPU, but I also noticed that Compiz doesn't causes the problem with CPU, but waveforms in Mixxx, when I switch off the waveforms to simple mode, I get 10-15% of CPU usage.

  And finally, Please improve BPM detection, comparing with 1.6.1 nothings changed, I get the same results in detection in both versions, its nice to have 64bit version for windows its nice to have good looking themes and good hardware support, but without good BPM detection Mixxx is useless. Regards!

@mixxxbot
Copy link
Collaborator Author

Commented by: Pegasus-RPG
Date: 2009-05-11T14:18:37Z


For the audio device problem, see this: http://mixxx.org/wiki/doku.php/troubleshooting#no_or_too_few_sound_cards_appear_in_the_preferences_dialog_-_how_can_i_fix_this

Yes, the waveforms are CPU-intensive by nature.

You may need to delete your library file (mixxxtrack.xml) since Mixxx won't try to re-detect BPMs that are already listed in there unless you explicitly do so by right-clicking a track. I have noticed that the BPM detection in 1.7.0 is noticeably better than in 1.6.1 (it picks up BPMs on tracks it couldn't before.) The only problem is that the range might be too restricted depending on your music, so try opening it up: Go to Preferences->BPM Detection and mark the "Allow BPM above the range" box. Let us know if that helps.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 1.7.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant