More > JRiver Media Center 32 for Linux
Which Flavor of Linux Are You Running (and how do you use MC)?
mwillems:
--- Quote from: geier22 on March 21, 2024, 01:45:05 pm ---hello mwillems, thanks for the tip, but unfortunately that doesn't work for me.
I created /etc/pipewire.conf (didn't exist).
The following is present in /etc:
--- Code: ---~# find /etc -name "*pipewire*"
/etc/alsa/conf.d/99-pipewire-default.conf
/etc/alsa/conf.d/50-pipewire.conf
/etc/pipewire.conf
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket
/etc/systemd/user/pipewire.service.wants
/etc/systemd/user/default.target.wants/pipewire.service
/etc/systemd/user/default.target.wants/pipewire-pulse.service
--- End code ---
After a restart, I had these options in MC:
"default [ALSA] Default ALSA Output (Currently Pipewire Media Server)"
or
"pipewire [ALSA]Pipewire Sound Server"
But no matter what I choose:
MC says in the audio path, that the track will be played without conversion (see picture).
But in reality it is played at 48 kHz. No matter what song I select (even 192 kHz)
Both the display on my TEAC and the terminal show 48 kHz.
Terminal with Pipewire:
--- Code: ---~$ cat /proc/asound/card2/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S24_3LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 512
buffer_size: 32768
--- End code ---
The same piece:
terminal with my default setting (hw:Card=Device,DEV=0 TEAC USB AUDIO DEVICE, USB AUDIO Direct hardware device without any conversions):
--- Code: ---~$ cat /proc/asound/card2/pcm0p/sub0/hw_params
access: RW_INTERLEAVED
format: S24_3LE
subformat: STD
channels: 2
rate: 88200 (88200/1)
period_size: 8820
buffer_size: 44100
--- End code ---
--- End quote ---
So you might want to start another thread and post everything you included in your pipewire.conf. In case it wasn't clear, you can't just drop the lines I included in an empty file and expect it to work you need the rest of the pipewire.conf configuration file. If you need a default conf file you can copy the default conf from /usr/share/pipewire/pipewire.conf to /etc/pipewire.conf and then tailor the new /etc/pipewire.conf file. It should already have lines similar to the ones in my post, but with different values so you just need to edit those lines (they're in the context.properties block).
warchild:
After years of running Debian nearly a year ago I switched to Arch Linux and Gentoo. I prefer Arch Linux by a large margin.
I only use MC for Audio and as I have a few overpriced DAC's I've had few mystifying issues (but when I do get them they're doozies!)
Using either AUR or dpkg I can easily install MC. At times there are some dependency issues (mainly things being in the wrong place) but all the dependencies are in the Video section. I've little interest in that end but in tests the video, while it plays, it can be loaded with artifacts. I've causually searched and feel comfortable that MC is the best tool for playing and cataloging my music collection by a huge margin.
antenna:
--- Quote from: bob on March 21, 2024, 10:29:22 am ---I use logitech wireless keyboards with linux all the time. The ones with the universal usb dongle.
The IR remote is likely to be the biggest stumbling block. MC on linux supports the basic remote commands through low level X calls but it appears some desktop managers intercept and don't pass along those codes.
You will likely have more success with one of the phone remotes. JRemote has a nice remote control.
--- End quote ---
Thanks for the comment about the LogiTech wireless keyboards. I will need to dig deeper in that area.
But, yeah, the IR remote, more specifically, the IR universal remote, that I use seems to be a big issue.
I do understand that JR provides a phone remote, but that's not how I enjoy media here. Indeed, my fondleslab is a distant memory whilst I enjoy my media.
And I also say, quite strongly, that the lack of IR universal remote support is not an issue that JR needs to solve.
I will now turn my queries towards the current providers of said capabilities in the Windows environment, and gently ask why they do not support Debian Linux distributions.
Wish me luck.
:)
(fwiw, the IR remote software I currently use on Windows 10 is flirc.: https://flirc.tv/ )
mwillems:
--- Quote from: antenna on March 27, 2024, 01:51:26 am ---Thanks for the comment about the LogiTech wireless keyboards. I will need to dig deeper in that area.
But, yeah, the IR remote, more specifically, the IR universal remote, that I use seems to be a big issue.
I do understand that JR provides a phone remote, but that's not how I enjoy media here. Indeed, my fondleslab is a distant memory whilst I enjoy my media.
And I also say, quite strongly, that the lack of IR universal remote support is not an issue that JR needs to solve.
I will now turn my queries towards the current providers of said capabilities in the Windows environment, and gently ask why they do not support Debian Linux distributions.
Wish me luck.
:)
(fwiw, the IR remote software I currently use on Windows 10 is flirc.: https://flirc.tv/ )
--- End quote ---
So just to be clear, if you run on Debian Linux with a lightweight desktop environment like XFCE, there's a good chance that your remote might work perfectly. Many IR remotes already have hardware support in Linux.
The main issue is with desktop environments like Gnome or KDE that consume media key presses. Programs that want to see those presses have to get them from the desktop environment via the MPRIS API. For now at least JRiver is looking to see the actual keypresses rather than interacting with the MPRIS API, so the remote codes never get to MC in those desktop environments.
But if you don't mind avoiding Gnome or KDE and using something like XFCE, your remote might just work out of the box (mine does with XFCE).
drmimosa:
I landed in an environment very similar to the one mwillems describes above, and use MC for Music and Video (1080p playback on a TV via Theater View).
I use an Ubunutu spin (Lubuntu I think) and installed a minimal XFCE desktop environment on top of the LXQT default. I was using LXQT because openbox has such easy keyboard shortcuts and I wanted to make a lot of custom commands, but I discovered that some of the On Screen Display stuff wasn't working properly in Video playback, so I switched to XFCE. Turns out keyboard shortcuts work just as well in XFCE.
--- Quote from: antenna on March 21, 2024, 12:47:07 am ---1) I currently plug an IR receiver into the USB port of the MC client, and my universal remote is able to navigate and control MC (mostly in Theater mode). Will I be able to have that same level of functionality in a Linux distribution? (for the record, here's what I use: ( https://flirc.tv/ ) iI not, what is the alternative?
--- End quote ---
I have a Flirc USB receiver, it works flawlessly. I remember some challenges at some point installing the Flirc software, but can't remember what they were. If you have any trouble let me know, I'll use my system to help troubleshoot.
The nice thing about using Flirc is that you can point any command from any IR remote to any keyboard shortcut. The flirc is recognized as a usb keyboard in linux, so you can launch scripts and stuff if you want to get really fancy. But a simple setup of arrow keys and enter will work with Theater View really well.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version