More > JRiver Media Center 31 for Linux

JRiver Media Center 31.0.42 for Debian BULLSEYE (amd64, i386, arm64 and armhf)

<< < (3/3)

bob:

--- Quote from: Awesome Donkey on August 10, 2023, 09:05:19 am ---When it goes through the default output (ALSA or PulseAudio/PipeWire) it's going through the system mixer (and sometimes there's usually resampling involved, e.g. 48 kHz by default for PulseAudio). The hw: and front: outputs bypass the system mixer and are direct outputs. You can look in the Audio Path when playing back media to see if it's a direct connection or not.

If the sluggishness is what I'm thinking it is, I'm with Bryan as that's something that's been there since day one. It *has* improved over the years, but it's nowhere near Windows when it comes to that. Though last time I used macOS it was even worse there than Linux, so yeah, glass half full. :P

--- End quote ---
I'm not a big fan of the tag window.
It's overly complex and depends on MS Windows API focus and window behavior that's extremely difficult to work into the Mac and linux window API's.

driblo:

--- Quote from: Awesome Donkey on August 10, 2023, 09:05:19 am ---When it goes through the default output (ALSA or PulseAudio/PipeWire) it's going through the system mixer (and sometimes there's usually resampling involved, e.g. 48 kHz by default for PulseAudio). The hw: and front: outputs bypass the system mixer and are direct outputs. You can look in the Audio Path when playing back media to see if it's a direct connection or not.

If the sluggishness is what I'm thinking it is, I'm with Bryan as that's something that's been there since day one. It *has* improved over the years, but it's nowhere near Windows when it comes to that. Though last time I used macOS it was even worse there than Linux, so yeah, glass half full. :P

--- End quote ---

MC is much faster on Wayland KDE Plasma.
Scroll sometimes hangs, but overall it is much more pleasant experience.
Search still looses focus, but reacts much faster on typing and clicks.
Haven't been able to find anything in journal about it.

Noticed that MC when "idle" (not playing or in focus) uses 40%-50% single core, even after couple of minutes. Is that normal?

Also, when starting playback i got long error regarding to chromium plugin, VAAPI and nVidia driver.
Playback continues normally, and error is probably connected to Display pane.
I put stacktrace in attachment if it is of any help.

Navigation

[0] Message Index

[*] Previous page