INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Linux => Topic started by: scrutinizer on August 26, 2019, 12:09:42 pm
-
Hi,
I’m having some responsiveness issues with the Linux version (only the Linux version).
I have a rather large music library, Switching tracks during playback by double-clicking on some random track can take a very long time sometimes up to a whole minute to make the actual switch.
This does NOT happen when switching tracks using a remote control like Gizmo.
The top right search box is also very slow to respond – typing itself is delayed quite considerably and even clicking inside the box to make it active usually takes two or more tries.
Running Debian 10 buster (same thing happened on Stretch).
Any idea?
*Still waiting for a Gizmo update. It keeps on crashing after a while.
-
Hi,
The top right search box is also very slow to respond – typing itself is delayed quite considerably and even clicking inside the box to make it active usually takes two or more tries.
Yeah, this search behavior is very inconvenient. Devs says that is WM/DE related, especially in KDE.
Though I didn't experienced so long track switching issue.
-
Yeah, I don't see either issue at all in Gnome on Arch Linux. Can you provide some more details about your debian setup?
-
Well I am indeed using KDE but what about it can cause such behavior only with JRiver?
I also noticed that after track has been switched it takes an additional 30 seconds to a minute for the cover art on the bottom left to reflect the playing track.
Minimizing JRiver window and reopening it often results in a blank white window which again can take up to a minute to redraw properly.
I'm using Debian (amd64) on a Kaby Lake I7 Desktop with 32gb ram and Nvidia (proprietary) drivers.
The same thing happens on my thinkpad (t470s running debian with intel drivers) to an even worse degree.
-
CAn you try a wayland session instead of X? Last Plasma update (5.6) enabled Wayland support (EGLStreams) for nVidia proprietary. You might see different behavior with MC running in XWayland.
-
CAn you try a wayland session instead of X? Last Plasma update (5.6) enabled Wayland support (EGLStreams) for nVidia proprietary. You might see different behavior with MC running in XWayland.
Plasma 5.6 isn't on Debian 10...
-
CAn you try a wayland session instead of X? Last Plasma update (5.6) enabled Wayland support (EGLStreams) for nVidia proprietary. You might see different behavior with MC running in XWayland.
Wow, Fedora works with wayland on NVIDIA too now. I so missed that! Gotta try that today!
I don't really have massive delay problems (although everything he said I also have, but not nearly as bad). Mostly, when I move the Window is hinks after the cursor a lot and laggs around the screen. On my notebook with an intel igpu its flawless (on wayland). Maybe the laggs would increase if my desktop had a worse GPU with xorg.
Could try xorg on my notebook and see what happens too. Yeah, when I switch to xorg on my notebook its also a mess... It is night and day better on wayland!
-
I haven't had a problem with kde on debian testing
-
I haven't had a problem with kde on debian testing
So, under KDE you have the one click in search field and then you able to type text?
I have to click twice at least.
-
So, under KDE you have the one click in search field and then you able to type text?
I have to click twice at least.
No I have that but I don't class this as a responsiveness problem, it is just one of the many ui glitches (which are mostly to do with how it handles active window areas). The more obvious example is any dialog box (like options or DSP studio)
-
I too experience UI issues with MC 25.0.102 using KDE 5.16.4 on Manjaro (arch based) Dell 7530 laptop. I have no issues with any other programs UI on my system. MC runs fine unless you try to interact with the UI like moving the window or using the search box. The menu drop downs are a little slow to open and close. To move the window I have to ALT left click it and it moves fine. If I try to drag without the ALT it barely registers the mouse moves.
-
Try the current build. There was an issue with the mouse tracking code after opening a popup window.
-
The current build is deffinitely better. Before 108 I tried the new releases for about a minute and reverted to .97.
-
The current build is deffinitely better. Before 108 I tried the new releases for about a minute and reverted to .97.
Great, thanks for the report.