More > JRiver Media Center 20 for Linux
JRiver Media Center 19.0.60 for Debian
bob:
http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter-19.0.60.deb
Purchase link
19.0.60 (10/22/2013)
1. Changed: Better ALSA device enumeration, should help to coexist with pulseaudio.
19.0.59 (10/21/2013)
1. Fixed: SSDP discovery stopped working after a short time.
19.0.57 (10/17/2013)
1. Changed: Prevent message boxes from popping up in /mediaserver mode.
2. Fixed: DLNA, problems with some http 1.1 devices.
19.0.56 (10/10/2013)
1. Changed: Attempt to back off requirements to SSE2.
2. NEW: If the default lucida font isn't found will fall back to a different font (requires the xfonts-100dpi package)
19.0.54 (10/08/2103)
1. NEW: Added support for 24-bit ALSA devices.
2. Fixed: When playback failed to start, it could lead to a crash.
3. Fixed: Mouse move tracking was not working, causing many UI issues.
4. Fixed: Typing in an edit control that showed suggestions could segfault.
19.0.53 (10/07/2013)
1. Fixed: Window minimize, maximize, and restore work.
2. NEW: Compiled without SSE support. Need Feedback.
19.0.52 (10/4/2013)
1: NEW: Fallback to S16_LE sound if the ALSA driver doesn't support S32_LE.
2: Fixed: Font spacing and switched to Lucinda.
3: Fixed: Added more package dependencies.
19.0.51 (10/3/2013)
1. NEW: First build.
RemyJ:
Seems to be working well with pulse. Thanks.
Somewhere along the way Pause doesn't work anymore.
Matt:
--- Quote from: RemyJ on October 22, 2013, 06:45:45 pm ---Somewhere along the way Pause doesn't work anymore.
--- End quote ---
I don't think it has ever really worked right.
It's near the top of our list.
Mike Noe:
--- Quote ---1. Changed: Better ALSA device enumeration, should help to coexist with pulseaudio.
--- End quote ---
Not very user-friendly, compared to the other list options, though certainly more detailed. What I think might confuse people is....
--- Code: ---mike@linux-30ty:~/bin/lib> aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default
Default ALSA Output (currently PulseAudio Sound Server)
sysdefault:CARD=SB
HDA ATI SB, VT1708S Analog
Default Audio Device
front:CARD=SB,DEV=0
HDA ATI SB, VT1708S Analog
Front speakers
surround40:CARD=SB,DEV=0
HDA ATI SB, VT1708S Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=SB,DEV=0
HDA ATI SB, VT1708S Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=SB,DEV=0
HDA ATI SB, VT1708S Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=SB,DEV=0
HDA ATI SB, VT1708S Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=SB,DEV=0
HDA ATI SB, VT1708S Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=SB,DEV=0
HDA ATI SB, VT1708S Digital
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=Generic,DEV=0
HD-Audio Generic, HDMI 0
HDMI Audio Output
--- End code ---
...shows the same device (CARD=SB,DEV=0) for the "formats" it supports. So, what would be the difference in selecting surround71:CARD=SB,DEV=0 vs. surround51:CARD=SB,DEV=0 from a device playback standpoint to MC?
Seems like distinct devices works better....
--- Code: ---mike@linux-30ty:~/bin/lib> aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: VT1708S Digital [VT1708S Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 0/1
Subdevice #0: subdevice #0
--- End code ---
Edit:
Also, I'm getting a hard crash when going to devices. Click options/audio/devices, ok or cancel out, then start playback, then go back into options/audio/devices *crash*
From the console...
--- Code: ---pure virtual method called
terminate called without an active exception
--- End code ---
bob:
More recent ALSA docs say not to use the card enumeration method.
It prevents the use of pulse (if you have it) and userland audio drivers like bluetooth.
I'm thinking we need to open the devices in multichannel mode if that's what we want to use. Now I'm for sure not the expert here on that.
Thanks for the feedback, still feeling our way through this.
Navigation
[0] Message Index
[#] Next page
Go to full version