More > JRiver Media Center 31 for Linux
JRiver Media Center 31.0.42 for Debian BULLSEYE (amd64, i386, arm64 and armhf)
Awesome Donkey:
What audio output are you using in Media Center itself? MC's Options > Audio > Audio Device section. Don't use the PulseAudio/PipeWire output, instead use the hw: or front: output if available.
I've noticed no issues under Fedora here while using a hw: output for my DAC. I suppose it *could* be a Manjaro (Arch Linux) related issue, who knows.
driblo:
--- Quote from: JimH on August 10, 2023, 07:35:43 am ---Pipewire?
https://wiki.debian.org/PipeWire#:~:text=PipeWire%20is%20a%20server%20and,between%20different%20pieces%20of%20software.
--- End quote ---
This is more updated wiki and more relevant to Manjaro
https://wiki.archlinux.org/title/PipeWire
BryanC:
--- Quote from: driblo on August 10, 2023, 05:14:00 am ---
* Playback of audio suddenly hangs after couple of songs, restart of application needed. Happens on different formats and songs. Happened with and without equalizer preset.
* Search box looses focus when search history/recommended dropdown appears.
* Application is sluggish, scrolling is slow and hangs every sscreen page or so. Library is big, available locally on SSD. Panes display helps a little, caching of thumbnails also helped little.
--- End quote ---
1. Try using a different output to bypass pipewire for testing. Also try checking your system logs (journalctl and dmesg) when this occurs, it could be hardware-related.
2. Probably a window manager or compositor quirk, hard to diagnose and one of those things you'll just have to put up with on an "unsupported" distro as there are too many variables at play.
3. I have the same overall sluggishness on Linux, but it's been present since the beginning. Having the tag editor open is a big culprit. It's just something I've learned to put up with over time, unfortunately. For large tagging sessions I'll usually hop on a Library client and sync changes back to the server since the sluggishness is only present on the server and not on the client, even Linux clients.
driblo:
--- Quote from: Awesome Donkey on August 10, 2023, 08:02:39 am ---What audio output are you using in Media Center itself? MC's Options > Audio > Audio Device section. Don't use the PulseAudio/PipeWire output, instead use the hw: or front: output if available.
I've noticed no issues under Fedora here while using a hw: output for my DAC. I suppose it *could* be a Manjaro (Arch Linux) related issue, who knows.
--- End quote ---
--- Quote from: BryanC on August 10, 2023, 08:12:02 am ---1. Try using a different output to bypass pipewire for testing. Also try checking your system logs (journalctl and dmesg) when this occurs, it could be hardware-related.
2. Probably a window manager or compositor quirk, hard to diagnose and one of those things you'll just have to put up with on an "unsupported" distro as there are too many variables at play.
3. I have the same overall sluggishness on Linux, but it's been present since the beginning. Having the tag editor open is a big culprit. It's just something I've learned to put up with over time, unfortunately. For large tagging sessions I'll usually hop on a Library client and sync changes back to the server since the sluggishness is only present on the server and not on the client, even Linux clients.
--- End quote ---
Ok, I switched output from
default [ALSA] output (currently PipeWire Media Server)
to
front: CARD=generic, DEV=0 [ALSA]
Played some HD flac and dsf files, no hangups or freezes, playback is smooth - MC uses from 50% to 100% of a single core in top, but it holds.
I don't have volume control through OS, which is to be expected since it now goes directly to the card through ALSA.
Also automatic downmixing of 5.1 and 4.0 mixes doesn't wok anymore - which is also expected.
I guess problem has to be somewhere in the PipeWire (my config or something still buggy in PW); since first setup was just passtrough from PipeWire to ALSA.
Rest of the problems (searchbox focus and sluggishness) persist.
I will try to see what is happening in journal and to debug it (maybe it will be faster under Wayland?), will respond if I find out anything.
Thanks for the help!
Awesome Donkey:
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
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version