Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bob]

http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.7.deb

20.0.7 (8/14/2014)

1. Changed: Reverted to previous device detection scheme. Because of a bug in alsa this can occasionally crash enumerating devices. It fixes detection on some platforms however.

20.0.6 (8/12/2014)

1. New: File path dialogs for Options (requires gtk 2.0)
2. Changed: Retry audio device enumeration on failure. Fixes troubles finding devices on ubuntu x64.
3. Changed: More tweaks to eventing.

19.0.160 (8/5/2014)

1. Changed: (again) the root window updating. Reverted somewhat to the previous behavior. Only the right side, bottom and bottom right corner work properly for resize.

19.0.156 (7/24/2014)

1. Fixed: One of the types of HTTP redirects was not being handled properly. This fixes troubles with some internet streams and one particular DLNA controller.
2. Fixed: The ALSA Buffer time and Period time parameters were not being used.
3. NEW: The ALSA output format can be fixed to a specific type (i.e. S32_LE) as well as auto detected (previous method).
4. Fixed: Window Size/Position issues in some dialogs (i.e. dsp studio sample rate selection).
5. NEW: Rudimentary portable drive (handheld) support (no autodetect).
6. Changed: Root window move/resize. Position/Size isn't updated until left mouse button is released. Prevents jumping, etc. This will likely change again...

19.0.152 (7/15/2014)

1. Fixed: Detection of mountpoints under /media and /mnt, treated as "drives"
2. NEW: Implemented the functions which allow "Rename, move and copy files" to work.
3. NEW: For deleting files from the library, moving to the recycle (Trash) bin implemented. Since this is desktop dependent you'll need to symlink ~/Trash to your desktop trash directory.

19.0.148 (7/3/2014)

1. Fixed: Multichannel mapping.

19.0.146 (6/26/2014)

1. Fixed: Watched folders now see subfolders properly.

19.0.144 (6/24/2014)

1. NEW: Implemented DSD over DoP. Tested with Mytek Stereo192 DSD DAC.
2. NEW: Added S24LE audio format.
3. Fixed: Registration issues (losing previous registration, etc).
4. Fixed: Socket handle leak.

19.0.143 (6/19/2014)

1. NEW: Added DPMS control to the HDMI screen option under audio.
2. Fixed: Registration issues (losing previous registration, etc).
3. Fixed: WOL Mac address were not being supplied to the access key server properly.

19.0.141 (6/13/2014)

1. Changed: Default volume mode is now "Internal" rather than "System".
2. Changed: Added command line switch for restoring license from an MJR file (/RestoreFromFile).
3. Changed: Tooltips that obscure underlying clickable fields removed.
4. NEW: Screensaver control enabled (turn on hdmi screen option under Audio).
5. NEW: Added command line alsacap to the debian package (in MC's shared library location).
6. Changed: Audio driver configuration changed to be more like windows/mac.
7. NEW: The ALSA driver selection can be made from the WebRemote control panel.
8. NEW: DSD Encoder working.

19.0.138 (6/6/14)

1. Fixed: Asynchronous crashing triggered by Media Network being enabled.
2. Fixed: Ratings.
3. Fixed: Bug in eventing.
4. NEW: Licensing is now enabled. The trial period starts.

19.0.135 (5/9/2014)

1. Fixed: The watch folders function.
2. Fixed: A memory leak from above.

19.0.134 (5/15/2014)

1. New: The font dialog is enabled (Options->Tree and View->Select Font). You can choose from the default Lucida, GNU Unifont and a user defined font string. The User Defined font string has to be acceptable to XLoadQueryFont. If the font isn't found, MC will fall back to Lucida and then Mutt-Clearlyu. The font height can also be trimmed manually. Height in pixels of trim.

19.0.133-2 (5/12/2014)

1. Change: Reverted from requirement for dynamic ssl and crypto libs added inadvertently in 19.0.133

19.0.133 (5/9/2014)

1. Changed: The font loads orders of magnitude faster.
2. Fixed. The maximum size calculated for the font characters were not being calculated properly at load time resulting in imprecise placement of elements in the MC window.

19.0.129-3 (4/22/2014)

1. Changed: libcurl system shared lib dependencies reduced.
2. Fixed: Internet reader timeout.

19.0.129 (4/21/2014)

1. Changed: libcurl integrated into the JRReader. Greatly reduces dependencies and uses a newer version of libcurl. Needs testing to see if anything is missing and to check compatibility with distro's (unsupported) other than debian wheezy.
2. Changed: xz compression on the .deb greatly reduces download size.

19.0.128 (4/15/2014)

1. NEW: System volume control and mute control if supported by the device (controls the PCM output). The mixer is discovered during audio device config (reselect your audio device to get it).

19.0.124-5 (3/27/2014)

1. Changed: More maximize/not maximized work.


19.0.124 (3/25/2014)

1. Fixed: Use 64 bit stat functions. Fixes problems using mounted windows (and CIFS NAS) filesystems. Probably also fixes other random file problems.
2. Fixed: Moving the main window works properly now.
3. Changed: Method of screen position saving restoring (again). Needs testing.
4. Fixed: Resizing works (as long as nothing is playing).
5. Fixed: Restores maximized/not maximized state upon start.

19.0.122 (3/14/2014)

1. Fixed: Remembers size and position on re-open. Needs testing on different platforms / window managers.
2. Changed: The method used to allow moving/resizing. Needs testing on different platforms / window managers.

19.0.121 (3/11/2014)

1. Fixed: Memory leak introduced in 19.0.119
2. NEW: WMA playback support.
3. Fixed: HTTP authorization tokens weren't being done properly, so that only one server authorization was stored at a time.
4. Changed: Timeout advanced to July 10th 2014.
5. Fixed: Internet reader, HTTP redirects were not handled properly.
6. NEW: Use backing store for windows if the server supports it (UI speed increase).
7. NEW: Mouse cursor changes (on click) for main window move/resize. Intend this to work on hover in the future.
8. Changed: More tweaking of the tooltip and transient window hints (need feedback).

19.0.119 (2/28/2014)

1. Fixed: Movement and resizing of MediaCenter works properly now.
2. Fixed: HTTP authentication was broken in build 19.0.118.

19.0.118 (2/21/2014)

1. Fixed: The linux network reader fixed to handle custom methods (needed for DLNA events).
2. Fixed: When acting as a DLNA renderer, wouldn't move on to the next track in a playlist properly.
3. Fixed: Tooltip windows to work better with more window managers. Still not transparent however.

19.0.117 (2/14/2014)

1. Fixed: Enabled filesystem statistics gathering function.
2. Fixed: Allow : in filename (was filtered out by windows code).
3. Fixed: Remove special treatment of UNC style paths (windows code).
4. Fixed: Remove special treatment of . in pathnames, i.e. foo./bar (windows code).
5. Fixed: The fixing of the documents path causes the automatic database backup to occur. (~/Documents/JRiver ....)

19.0.116 (2/10/2014)

1. Fixed: Prevent tooltips and transparent windows from stealing input focus. Fixes upper right corner search box.

19.0.115 (2/5/2014)

1. Changed: Completely reworked the linux ALSA audio output device control to be more efficient and reduce latency.
2: NEW: Allow advanced user control of the latency.

19.0.112 (1/30/2014)

1. Fixed: Stability improvements.
2. Changed: Moved timeout to April 9th 2014

19.0.109 (1/23/2014)

1. Fixed: Workaround a curl bug that could cause crashing on slow dns lookups.
2. Fixed: Window focus issues. Need feedback.

19.0.108 (1/21/2014)

1. Fixed: Stability improvements.

19.0.103-3 (1/14/2014)

1. Fixed: Stability improvements.

19.0.103-2 (1/13/2014)

1. Changed: Removed system requirement for libcrypto++ and libboost-regex.

19.0.103 (1/9/2014)

1. NEW: Implemented libboost for regular expressions to match the windows and mac versions.
2. Changed: More dependencies tuning.

19.0.102 (1/3/2014)

1. Changed: Bumped timeout to February 9th 2014
2. Changed: Package no longer depends on the various linux audio encoders to install, they are recommended but not required leaving it up to the user to install. These are Lame, Vorbis-tools, Musepack-tools. They can be 32 or 64 bit.

19.0.94 (12/16/2013)

1. Fixed: Bug introduced from the column header crash fix.

19.0.92 (12/11/2013)

1. New: Added Musepack (mpc) encoder (requires system musepack-tools).
2. Fixed: Pathname length for files increased from 260 to 4096.

19.0.91 (12/10/2013)

1. Changed: More shared library work (stability).
2. Changed: Now requires system libcrypto++9 (>= 5.6.1)
3. Fixed: MPC (Musepack) input plugin.

19.0.90 (12/9/2013)

1. Fixed: .deb pacakge dependencies will allow either i386 or amd64 versions of lame and vorbis-tool and un-arched xfonts.
2. Changed: Reliability in loading shared libraries, was causing problems when switching between audio formats during playback.

19.0.89 (12/6/2013)

1. New: Added OGG encoder.

19.0.88 (12/5/2013)

1. Fixed: OGG input plugin.

19.0.85-1 (12/3/2013)

1. Faster: Drawing from an internal image to the screen is much faster (requires 0 memory manipulations before draw; previously required two copies before draw).
2. Changed: More resolutions avaiable for the dynamic MC Icon.
3. Fixed: DLNA fixes from the main code.

[Mike Noe]

I see that there is a 20.0.7 but your link is for 20.0.6...fwiw.

[bob]

I see that there is a 20.0.7 but your link is for 20.0.6...fwiw.

Fixed, thanks!

[InflatableMouse]

I'm on holiday so hopefully someone else can test the ALSA device enumeration too.

[danrien]

Bug with the window size. New install of 20.0.07, go to Tools -> Options, Options window was a minuscule little sliver. Using Linux Mint 17 64-bit.

[UdoS]

The rename/move function not working correct:
I renamed a number of files and mc should move it to the new location. But only the database entries were changed to the new location, the files were left in the original place.

[mwillems]

Bug with the window size. New install of 20.0.07, go to Tools -> Options, Options window was a minuscule little sliver. Using Linux Mint 17 64-bit.

Are you using Cinnamon or Mate for your desktop environment?

I was testing Cinnamon last night and got the same thing the first time I opened the options window (tiny sliver).  If you close the options window and reopen it (without restarting JRiver), does it happen the second time?  I got a full-size window after the first time I opened it.  

FWIW, I've tested on five different Linux DE's at this point (Cinnamon, Gnome 3, KDE, XFCE, Openbox), and on none of them does JRiver reliably open the options window the first time correctly.  The "sliver" issue seems local to Cinnamon; with the other DE's I usually get a full-sized blank window the first time I open the options (although occasionally, it just works correctly in Gnome).

[UdoS]

Exporting to a device (eg. directory), mc applies the same filename rule than for the basic data base.
For a handheld, very often it's more comfortable to have a simple filename rule to organize the files, so it is very nice, to declare filename rules separate for each handheld.

[tlcmd]

I have installed MC20.0.7 alongside MC19.160. All of the computer sound settings and MC20 sound settings seem the same, but I am not getting sound from MC20. MC19 plays fine. MC20 does show that it is playing based upon the sound bars in the current file playing box at the top of the screen. Suggestions, please??


Where did I go wrong? I am running Linux Mint Debian Edition (Mate).


Thanks,
tlcmd

[martinmopar]

this is great, but I can't get output for subwoofer.

alsa/jack. tried many different settings in jriver, but jack connections shows only two outputs from jriver. tested some other programs using the same alsa settings and all channels shows up when using them.
running jriver for windows via wine with the same sound settings gives all outputs to jack.
am I missing something, or is it a bug?

[UdoS]

I have installed MC20.0.7 alongside MC19.160. All of the computer sound settings and MC20 sound settings seem the same, but I am not getting sound from MC20. MC19 plays fine. MC20 does show that it is playing based upon the sound bars in the current file playing box at the top of the screen. Suggestions, please??


Where did I go wrong? I am running Linux Mint Debian Edition (Mate).


Thanks,
tlcmd

Try the command: '/usr/lib/jriver/Media Center 20/alsacap'   from a terminal window as it is written including the ' ' and watch the output. Maybe, it gives you a clue where to look.
Good luck
 

[mcollier]

Just installed 20.0.7 on Wheezy 64bit Gnome 3.

All is well except if I go to tools->options the options panel/box appears, but is a blank grey box.  If I resize the box bigger or smaller, all the gadgets appear.

Also, if I use the Ctrl+O hotkey, the window is displayed properly.

Very happy to have the file requester in the library import!!

[tlcmd]

UdoS, I tried that command and did include the 's and got (my computer is named "library", and I am Dick.
 
Dick@library ~ $  '/usr/lib/JRiver/Media Center 20/alsacap'
bash: /usr/lib/JRiver/Media Center 20/alsacap: No such file or directory
[127]dick@library ~ $

Any other suggestions, please. BTW, MC19 plays well as does youtube and other sound providers including Banshee. I think I've got to have either a wrong setting or a "mute" somewhere in MC20. Do I need to uninstall MC19???

Thanks very much.
tlcmd

[Mike Noe]

Why don't you just go to Audio Device options and make sure that 20 is using the same thing as 19?  Or did you already do that?

[UdoS]

UdoS, I tried that command and did include the 's and got (my computer is named "library", and I am Dick.
 
Dick@library ~ $  '/usr/lib/JRiver/Media Center 20/alsacap'
bash: /usr/lib/JRiver/Media Center 20/alsacap: No such file or directory
[127]dick@library ~ $

Any other suggestions, please. BTW, MC19 plays well as does youtube and other sound providers including Banshee. I think I've got to have either a wrong setting or a "mute" somewhere in MC20. Do I need to uninstall MC19???

Thanks very much.
tlcmd

The alsacap is located in the "***/MediaCenter***/usr/lib/jriver/Media Center 20", where *** depends on your installation location.
 

[Hendrik]

Note that JRiver in the path is meant to be lowercase, but the forum reformats it.
If you know your way around Linux, you should be able to find it.

[maged918]

Trying to connect to Last.fm now opens up the browser (previously didn't open up the browser), and Last.fm asks for authentication and everything, but clicking OK after that doesn't show that it's connected in the menu, and it indeed doesn't scrobble.

[Awesome Donkey]

Trying to connect to Last.fm now opens up the browser (previously didn't open up the browser), and Last.fm asks for authentication and everything, but clicking OK after that doesn't show that it's connected in the menu, and it indeed doesn't scrobble.

Already been mentioned. Bob's been working on getting it working, so a big kudos to him!

[tlcmd]

FIXED IT!!!
Changed it from "Internal Volume" to "System Volume" (unlike MC19 settings) and I got great sound!!
Thanks for all the helpful suggestions!!
tlcmd

[geier22]

The Link Bar does not work properly.

When I click on the link "AMG", the following page opens (Figure)
In the address-Bar appears the following:

Code: [Select]

file: /// var / tmp / kdecache-hans / Krun / 9517_0_Aaron% 20Nevillewhen I click a link from this page, the right AMG page appears.
The Google-link and the image-link works correctly

The same as AMG happens with the WIKI-link and the YouTube-link. The YouTube-links gives all: "File not Found"

In the notification window (KDE) the following appears when I click a link (eg Youtube)

Code: [Select]

Copying process completed:
/ var / tmp / kdecache-hans / Krun / 9922_0_results
Is this just me or is this still a BUG?

[jcd201406]

Installed on Kubuntu 14.04 LTS, same as 19, crash after about 3 minutes while reading or not :

~$ uname -a
Linux pcdl 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:49:09 UTC 2014 i686 i686 i686 GNU/Linux

~$ mediacenter20
Found 0 devices (devices will be listed below)

Total time: 5 ms
Result: 0
Erreur de segmentation (core dumped)

~$ dmesg |grep mediacenter20
[185659.008775] mediacenter20[15381]: segfault at 0 ip b51d9969 sp bfab0a50 error 4 in libJRReader.so[b50fd000+516000]
[186098.520653] mediacenter20[16194]: segfault at 0 ip b51f3969 sp bfa09d10 error 4 in libJRReader.so[b5117000+516000]
[186648.703557] mediacenter20[16619]: segfault at 0 ip b5108969 sp bfdc7780 error 4 in libJRReader.so[b502c000+516000]
[188137.647802] mediacenter20[17866]: segfault at 0 ip b51b4969 sp bfb79e60 error 4 in libJRReader.so[b50d8000+516000]
[188353.228543] mediacenter20[18232]: segfault at 0 ip b510e969 sp bf99da70 error 4 in libJRReader.so[b5032000+516000]
[188411.749750] mediacenter20[18585]: segfault at 0 ip b5169969 sp bffae1b0 error 4 in libJRReader.so[b508d000+516000]
[188485.705123] mediacenter20[18686]: segfault at 0 ip b51cb969 sp bfd9beb0 error 4 in libJRReader.so[b50ef000+516000]
[188800.930943] mediacenter20[18761]: segfault at 0 ip b5141969 sp bfa23d80 error 4 in libJRReader.so[b5065000+516000]
[238009.929336] mediacenter20[28370]: segfault at 0 ip b5112969 sp bf8db870 error 4 in libJRReader.so[b5036000+516000]
[238329.144448] mediacenter20[28863]: segfault at 0 ip b5127969 sp bfbe54b0 error 4 in libJRReader.so[b504b000+516000]

[UdoS]

Installed on Kubuntu 14.04 LTS, same as 19, crash after about 3 minutes while reading or not :

~$ uname -a
Linux pcdl 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:49:09 UTC 2014 i686 i686 i686 GNU/Linux

~$ mediacenter20
Found 0 devices (devices will be listed below)

Total time: 5 ms
Result: 0
Erreur de segmentation (core dumped)

~$ dmesg |grep mediacenter20
[185659.008775] mediacenter20[15381]: segfault at 0 ip b51d9969 sp bfab0a50 error 4 in libJRReader.so[b50fd000+516000]
[186098.520653] mediacenter20[16194]: segfault at 0 ip b51f3969 sp bfa09d10 error 4 in libJRReader.so[b5117000+516000]
[186648.703557] mediacenter20[16619]: segfault at 0 ip b5108969 sp bfdc7780 error 4 in libJRReader.so[b502c000+516000]
[188137.647802] mediacenter20[17866]: segfault at 0 ip b51b4969 sp bfb79e60 error 4 in libJRReader.so[b50d8000+516000]
[188353.228543] mediacenter20[18232]: segfault at 0 ip b510e969 sp bf99da70 error 4 in libJRReader.so[b5032000+516000]
[188411.749750] mediacenter20[18585]: segfault at 0 ip b5169969 sp bffae1b0 error 4 in libJRReader.so[b508d000+516000]
[188485.705123] mediacenter20[18686]: segfault at 0 ip b51cb969 sp bfd9beb0 error 4 in libJRReader.so[b50ef000+516000]
[188800.930943] mediacenter20[18761]: segfault at 0 ip b5141969 sp bfa23d80 error 4 in libJRReader.so[b5065000+516000]
[238009.929336] mediacenter20[28370]: segfault at 0 ip b5112969 sp bf8db870 error 4 in libJRReader.so[b5036000+516000]
[238329.144448] mediacenter20[28863]: segfault at 0 ip b5127969 sp bfbe54b0 error 4 in libJRReader.so[b504b000+516000]

I had a similar crash after installing MC20. The reason was: some links were still pointing to the old MC19 files. After rerouting, every thing runs fine.

[mwillems]

Also, a minor UI issue that I wanted to bring up:

Gnome 3.12 integration is slightly broken in a way that results in some keyboard shortcuts not working correctly.  Details:

One of the main ways to navigate between windows in Gnome 3 (other than alt-tab) is to press super and then start typing the name of the program (super-search).  When you have a lot of windows, pressing super and typing "fire" to get back to firefox is much quicker (and more certain) than alt-tabbing ten or fifteen times.  The problem is that Gnome doesn't seem to connect a running instance of Media Center with that name;  attempting to super-search Media Center just launches a new Media Center instance, and never finds open instances.  I've found no search string that will successfully return an open MC instance.

A few notes on why this might be:

The Gnome 3 topbar, by default, shows an application menu for the currently focused application in the top left (next to the "activities" hot corner).  So for example, when firefox is in focus, it shows the firefox icon, the word firefox and a drop down menu.  When JRiver is in focus, it shows the JRiver icon correctly, but the text reads "Unknown."

On the "Activities" quick launch bar on the left, typically a running program is "stacked under" it's quick launch icon (accompanied by a "halo" light effect).  That is not the case with MC, which instead spawns a second bar entry below the first one (as though it were a program that wasn't pinned to the bar at all).  Hovering over a pinned launcher icon for MC shows the correct program name, but hovering over a running instance of MC shows  "Unknown."  Multiple running instances of MC do not stack under each other like other programs, meaning that Gnome seems to think that each running instance is a separate program.  The Gnome system monitor shows "mediacenter20" as the process name, but without any attached icon (unlike, say, firefox which shows up with an icon).  

So all of that suggests that Gnome is not successfully connecting the name "Media Center 20" with the running process mediacenter20.  

Like I said, not a huge issue, but it breaks some parts of the UI (like super-search), and the cosmetics of all those Unknowns are probably not desirable over the long-term.

[Awesome Donkey]

I've been extracting buttons (close/maximize/restore/minimize) from Ubuntu (both Ambiance and Radiance themes) and Xfce 4 if you're interested in them for Noire. I'm also working on getting GNOME 3's currently.

[mcollier]

I just install Debian Jessie using the Beta 1 installer.  I am pleased to report that MediaCenter is functioning well.

I would also like to echo MWillems comments about UI issues.

I am also seeing the same behavior in the options panel that I mentioned in an earlier post.  This installation is also running on different hardware.

[mwillems]

I just found a repeatable (for me) crash to desktop:

If I'm playing a file with a 96KHz or above sampling rate, attempting go into options and select "Device Settings" during playback triggers a crash to desktop.  I haven't been able to reproduce it with lower sample rate files at all.  My player is capable of 96KHz playback, and playback works fine unless I try to tinker with device settings.

[Awesome Donkey]

Is there a folder (other than /usr/lib/jriver that requires admin) where we can install skins easily? Same question applies to the Mac version too.

[geier22]

The German keyboard does not work properly (at least for me):

The Num-Pad does not work. All buttons give this back: ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ

If I insert something with CTRL+V,  MC prints a "v" in addition to the inserted text

[UdoS]

The German keyboard does not work properly (at least for me):

The Num-Pad does not work. All buttons give this back: ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ

If I insert something with CTRL+V,  MC prints a "v" in addition to the inserted text

confirmed

[geier22]

The Link Bar does not work properly.

With the help of Debian forum, this problem could be solved:
There seems to be a bug in KDE:  https://bugs.kde.org/show_bug.cgi?id=297491
Here's what I did:
System Settings ---> Standard components ---> web browser -> with the following browser:

Code: [Select]

firefox $s (the $ s has been added)

Now the links work well.

[bob]

I just found a repeatable (for me) crash to desktop:

If I'm playing a file with a 96KHz or above sampling rate, attempting go into options and select "Device Settings" during playback triggers a crash to desktop.  I haven't been able to reproduce it with lower sample rate files at all.  My player is capable of 96KHz playback, and playback works fine unless I try to tinker with device settings.

The reversion to the previous method of device detection exposes a bug in ALSA.
Unfortunately we'll have to live with that until they fix it since the other method didn't expose all of the devices on all platforms.
I suggest you stop playback before altering the settings. They can't take effect until after the end of a track anyway.

[bob]

The German keyboard does not work properly (at least for me):

The Num-Pad does not work. All buttons give this back: ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ ㅁ

If I insert something with CTRL+V,  MC prints a "v" in addition to the inserted text

I assume you never tried this before? (It's not a regression).

[mwillems]

The reversion to the previous method of device detection exposes a bug in ALSA.
Unfortunately we'll have to live with that until they fix it since the other method didn't expose all of the devices on all platforms.
I suggest you stop playback before altering the settings. They can't take effect until after the end of a track anyway.

One other quirk of the new enumeration; I have a system without any pulse audio related packages or libraries installed (no pulse-audio, no libpulse, nothing).  On that system JRiver shows a "pulse" audio output in output devices.  MC is the only program that shows a pulse output, and any attempts to playback to the "pulse" device (unsurprisingly) fail.  Is this expected behavior? 

I had a look at some of my alsa config files, and I don't see any references to pulse, but maybe I'm looking in the wrong place?

[bob]

One other quirk of the new enumeration; I have a system without any pulse audio related packages or libraries installed (no pulse-audio, no libpulse, nothing).  On that system JRiver shows a "pulse" audio output in output devices.  MC is the only program that shows a pulse output, and any attempts to playback to the "pulse" device (unsurprisingly) fail.  Is this expected behavior? 

I had a look at some of my alsa config files, and I don't see any references to pulse, but maybe I'm looking in the wrong place?

Not sure.
We are just asking for all of the PCM playback devices and that's what it's giving us.
It could be that it's a placeholder for ALSA that gets overridden when pulse is installed.
The logic flow when using pulse as a device under ALSA is bizarre.

[geier22]

I assume you never tried this before? (It's not a regression).

The num pad has never worked. See here: http://yabb.jriver.com/interact/index.php?topic=85770.msg612072#msg612072

[InflatableMouse]

One other quirk of the new enumeration; I have a system without any pulse audio related packages or libraries installed (no pulse-audio, no libpulse, nothing).  On that system JRiver shows a "pulse" audio output in output devices.  MC is the only program that shows a pulse output, and any attempts to playback to the "pulse" device (unsurprisingly) fail.  Is this expected behavior? 

I had a look at some of my alsa config files, and I don't see any references to pulse, but maybe I'm looking in the wrong place?

Alsa-plugins (and its 32-bit lib equivalent) will do that.

Aplay -L will show a pulse device as well.

[mwillems]

Alsa-plugins (and its 32-bit lib equivalent) will do that.

Aplay -L will show a pulse device as well.

Confirmed on both counts (alsa-plugins is installed and aplay -L shows a pulse device). Thanks for the solution.

[InflatableMouse]

No probs. If you're not sure whether you need the plugins just remove them it will remove the pulse device from MC's device list.

Libpulse on the other hand is completely safe to have installed, it won't give you a pulse device like the plugins do. Some applications will require libpulse as a dependency but its just some libs for compatibility. It doesn't install or run any pulse daemons nor does it change ALSA config. ps aux|grep pulse will confirm that.

[mwillems]

No probs. If you're not sure whether you need the plugins just remove them it will remove the pulse device from MC's device list.

Libpulse on the other hand is completely safe to have installed, it won't give you a pulse device like the plugins do. Some applications will require libpulse as a dependency but its just some libs for compatibility. It doesn't install or run any pulse daemons nor does it change ALSA config. ps aux|grep pulse will confirm that.

I need the plugins for a few things I'm doing, so I'll live with it for the moment; pulse isn't installed/running on that system anyway.  The only issue is the dummy audio device for Pulse that doesn't do anything. 

I know what you mean about libpulse; I have it on another machine because it's a dependency for VLC (which I hopefully won't need too much longer!) and it seems to be relatively harmless.