Messages

1

Tips and Tricks / Re: [GUIDE] How to use Musicbee on Linux (Archlinux/Debian based distro)

« on: June 25, 2020, 03:24:00 PM »

Well i'm happy to report that it all works perfectly now.

I can confirm this was NOT a musicbee issue, and probably not even a wine issue.

If anyone experiences anything similar, all that's changed since last time I tried is that a few updates went by. So it's probably a pulseaudio or ALSA problem (or some related sound library), and either a specific bug was fixed or the config of pulseaudio was changed (very likely).

I did notice before that I had rare sound issues on other music players, even native linux music players such as clementine. So yea, probably pulseaudio bad/weird config on KDE's end, or Ubuntu's end, because I didn't really touch it.

All's well that ends well

2

Tips and Tricks / Re: [GUIDE] How to use Musicbee on Linux (Archlinux/Debian based distro)

« on: June 10, 2020, 03:30:04 PM »

Thank you for this guide.

I'm getting a weird issue, MusicBee will randomly freeze or hang, for a second or two, before resuming. The whole app is frozen for that time and I can't interact with anything. Something to note is that the music playing doesn't skip once the freezing stops, it just resumes exactly where it was.

Everything else works fine, and this freeze happens every few minutes (1,2 or 3 minutes in general).

I've tried on a 32 and 64bit prefix, i've reinstalled it on wine a few times. I was originally on the stable branch then switched to dev, same problem.

I've tried running in console to get logs or with the debug prefix, doesn't seem to be throwing errors. With the debug prefix the debug itself freezes when MusicBee freezes.

Has anyone else gotten this issue? It's frustrating because everything is working completely fine and I have no idea where this could be coming from.

On latest Kubuntu, latest wine-devel, latest MB version.

EDIT: I tried some more things, to no avail. Here's some more detail.

I have 16GB or ram, Intel i7 8700 CPU and a GTX1070 nvidia GPU, with proprietary drivers (440).

I uninstalled and reinstalled wine from scratch, switched to the staging branch. Tried both with 32 or 64 prefix.
I tried with a fresh MusicBee install with no settings touched.
I tried switching Nvidia drivers (to the open source version) just in case, no dice.
I tried disabling all player settings or switching audio output.
I tried increasing the buffer or the "entire file" option.
I tried disabling/removing any kind of visualizer.
I tried a few wine performance options related to CPU (such as threaded optimization).
I tried with different filetypes, mp3, flac, ogg.. it doesn't seem to affect it.
I went and got a different bassmix.dll file version (don't ask me why there was a mention of it on a thread somewhere) and used it, no effect.
I tried turning on event mode for WASAPI, no effect.

Here's a more precise description of the bug :
I start MusicBee, the first track plays fine (Tested this a bunch of times, can't be 100% sure though).
After playing at least 1-2 minutes of the first track, if I switch to another track (manually or not), and let if play a bit, then the bug happens.
The bug seems to be CPU related, I don't notice any rising memory or any memory change before, during or after the freeze, but I do see a CPU spike when it freezes, then the CPU usage resets on the process viewer.
The bug always seems to happen around the 1:00 to 1:30 minute mark of the track (It seems to always be around 1:10 or 1:15), and there's almost always a kind of warning sign : first there's a micro-pause that's barely noticable, then a few seconds after that the big freeze happens (musicbee stops responding for a few seconds before resuming).

Scratching my head here, would love any opinions on this.