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/v19/latest/MediaCenter-19.0.122.deb

Purchase link

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.

[RemyJ]

Fedora 20 x86_64, XFCE Desktop, 5 monitors.

Opened and closed about 30 times.  Only twice did it remember size and position.  The rest of the time it came up on my main display, centered and sized to about 30% of the screen.

Resizing and moving is very flakey.   Resize is very slow and continues after releasing the mouse button.   Moving by dragging the top of the app sometimes causes the app to fly off the screen and to flash and stutter if moving from one screen to another.   Moving by holding the alt key and dragging is smooth as silk.

Just to make sure this wasn't related to having multiple monitors, I ran MC on another machine with only 1 monitor and got the same results.

[bob]

Fedora 20 x86_64, XFCE Desktop, 5 monitors.

Opened and closed about 30 times.  Only twice did it remember size and position.  The rest of the time it came up on my main display, centered and sized to about 30% of the screen.

Resizing and moving is very flakey.   Resize is very slow and continues after releasing the mouse button.   Moving by dragging the top of the app sometimes causes the app to fly off the screen and to flash and stutter if moving from one screen to another.   Moving by holding the alt key and dragging is smooth as silk.

Just to make sure this wasn't related to having multiple monitors, I ran MC on another machine with only 1 monitor and got the same results.

Thanks for the feedback.
There isn't any xinerama support in MC linux yet.
I'm not too happy about the move/resize thing. It seemed to work fine on my xfce desktop.

[Mike Noe]

openSUSE 13.1, KDE4.12.3, x86_64

Restoring position seems to work as long as I don't resize.  If I start MC, resize the window, then move the window, it remembers neither.

Resizing is very jumpy, seems like the mouse goes into hyper-mode and so the window tiles or goes maximized....

Forgot to add....grabbing and moving the window around works great.

[RemyJ]

There isn't any xinerama support in MC linux yet.

Not using xinerama.  Using xrandr.

Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 16384 x 16384
DisplayPort-0 connected 1920x1080+0+1080 (normal left inverted right x axis y axis) 510mm x 287mm
DisplayPort-1 connected 1920x1080+1920+1080 (normal left inverted right x axis y axis) 510mm x 287mm
HDMI-0 connected 1920x1080+3840+1080 (normal left inverted right x axis y axis) 510mm x 287mm
DVI-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 477mm x 268mm
DVI-1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 477mm x 268mm

[RemyJ]

Hey Bob,

I just did a fresh install of Debian 7.4.0 amd64 Gnome in a vm and then installed 122.  I get the same behavior as I do in Fedora.  Dragging and dropping the app causes it to flake out when nearing the screen borders and resize is slow.  Only occasionally remembers size and position.

I'm going to try i386 next

[bob]

Remy I should have said there's no multiple monitor support yet.
I think the way it works in windows is that the screens are part of a larger virtual map I don't know if that's how it works in linux will have to figure that out before multiple screens are implemented.

I also have trouble with this build on my home system so I think it's probably best to not bother with this one too much.

[RemyJ]

With XrandR, it's the same way as windows.  Apps don't know about monitors.  It's 1 big screen to them.  In my case, it's an 5760 x 2160 screen. 

[anonymous]

Loaded up MC on my Intel Galileo through SSH running Debian Wheezy and received the error "Illegal instruction" after entering "mediacenter19" to start the program.  Not a lot of information.  What items may I look at to find the root cause and correct?  (Plan to control MC using JRemote). 

Regards,

[JimH]

Loaded up MC on my Intel Galileo through SSH running Debian Wheezy and received the error "Illegal instruction" after entering "mediacenter19" to start the program.  Not a lot of information.  What items may I look at to find the root cause and correct?  (Plan to control MC using JRemote). 

Please try this thread:
http://yabb.jriver.com/interact/index.php?topic=85957.0

[InflatableMouse]

In addition, also have a look at running MC wihtout a GUI:
http://yabb.jriver.com/interact/index.php?topic=84477.0

[anonymous]

In addition, also have a look at running MC wihtout a GUI:
http://yabb.jriver.com/interact/index.php?topic=84477.0

Thank you for your quick response!

Went through the link carefully and had two items come up: 

(1) Unable to find package "lib32stdc++6"

(2) Otherwise, the installation goes smoothly, but at the end it does not say "Processing triggers for desktop-file-utils ..."

On another note, after I get this working (pc version is fantastic), how may I find the "Access Key" via SSH?

I'll go through the next link now.

Thanks!

[InflatableMouse]

Access keys must first be generated.

I find its best to ssh into machines using public/private keypairs and disable root through ssh. With a auth-key you're not prompted for a password and its easier to use remote X programs (ssh -n actually requires key authentication).

To setup ssh with key authentication, I can recommend this link:
http://www.debian-administration.org/articles/530

[anonymous]

In addition, also have a look at running MC wihtout a GUI:
http://yabb.jriver.com/interact/index.php?topic=84477.0

Thanks again for your help.

Went through the no-GUI link...

When I run "/etc/rc.local" the machine asks for a password then responds with "-su: line 1:  3062 Illegal instruction     mediacenter19 /mediaserver" (aka same issue).

When I enter "export DISPLAY=:0", then try "xterm" the system seems to hang so it appears to be outputting to the dummy display.

When I enter "ps -ef | grep Xorg | grep -v grep" the machine comes back showing Xorg is running.

   root      2933     1  0 15:04 ?        00:00:02 Xorg
   root      3070  3043  0 15:06 pts/0    00:00:00 sudo nohup Xorg

Checked the xorg.conf file a few times - looks good.

Rebooted, still no luck. 

What may I try to find/correct the issue?

Regards,

[InflatableMouse]

What distro are you on?

Did you manage to use key authentication? If so, try:

ssh -X name@server "nohup mediacenter19"

[anonymous]

What distro are you on?

Did you manage to use key authentication? If so, try:

ssh -X name@server "nohup mediacenter19"

Debian Wheezy 32bit (wanted to use same as development platform)

Trying, but not working yet--  ssh: Could not resolve hostname server: Name or service not known

Thanks again for your help!

[InflatableMouse]

Do you have a full GUI running on that remote system (Galileo)?

I'd try to make it run there first before trying to run it remotely.

Also see if other programs can be started remotely without problems.

Other than that, I'm not sure what to tell you.

[Awesome Donkey]

Will be testing the window changes on Ubuntu here in a bit!

EDIT: Doesn't remember maximized window side on Ubuntu/Unity/Compiz.

[shadowlight]

Anyone using windows share with jriver?  I cannot seem to leverage windows share where all my music is located.  I have successfully confirmed that the mount point is correct and accessible from other media player.

[anonymous]

Do you have a full GUI running on that remote system (Galileo)?

I'd try to make it run there first before trying to run it remotely.

Also see if other programs can be started remotely without problems.

Other than that, I'm not sure what to tell you.

No, there isn't a GUI on the Galileo.  Must the Linux version be run though a GUI to setup MC before being accessed by JRemote?

On another note, the MC "Access Key" needed for JRemote is not generated by MC, but is created separately?  Just want to confirm.

Thank you again!

[InflatableMouse]

Ah, you mean the Media Network key, no that's generated by MC when you enable Media Network from Tools/Options.

And no, you don't need a GUI on that system and once it runs it should be visible on the network. But since you're having trouble I figured I'd ask.It would have been good to exclude all the extras and run it straight on that system to see what it does.

[anonymous]

Ah, you mean the Media Network key, no that's generated by MC when you enable Media Network from Tools/Options.

And no, you don't need a GUI on that system and once it runs it should be visible on the network. But since you're having trouble I figured I'd ask.It would have been good to exclude all the extras and run it straight on that system to see what it does.

Thanks for the quick response!

Is there a way to run mediacenter19 in a debug mode to find the "illegal command"?  That would help.

Will figure how to get this working.  How may I see the Media Network key via a terminal, for use in JRemote?

Regards,

[InflatableMouse]

In /home/youruser/.jriver/Media Center 19/Settings/ there are 2 files for MC settings.

But I don't think you will find a key in there, since you need to be able to start MC and enable Media Network first.

[InflatableMouse]

2. Changed: The method used to allow moving/resizing. Needs testing on different platforms / window managers.

First thing it did when I moved the window was jump off screen (it also removes itself from the taskbar).

I kept the mouse button down and when I very slowly moved the mouse, it came back (and appeared on the taskbar again).

I'm on Debian Wheezy 7.4 64-bit with XFCE.

Also the divider (between panes and file details) is very slow to move.

[shadowlight]

Has anyone successfully used JRiver for Linux to play files mounted from a Windows share?  If yes can you provide information on how your file system is mounted and permission on it?  Output of df -h would be helpful also.  I keep getting "directory could not be found" but I am able to see the directory from xterm window and able to play files from the mounted partition with another player.

I am running JRiver on Debian Wheezy 64-bit, with XFCE

Thx

[anonymous]

Do you have a full GUI running on that remote system (Galileo)?

I'd try to make it run there first before trying to run it remotely.

Also see if other programs can be started remotely without problems.

Other than that, I'm not sure what to tell you.

Since my system does not say "Processing triggers for desktop-file-utils ..." at the end of the installation, what specific item setups can I check?  Maybe an item is missing or corrupted.

Regards,

[JimH]

Has anyone successfully used JRiver for Linux to play files mounted from a Windows share?  If yes can you provide information on how your file system is mounted and permission on it?  Output of df -h would be helpful also.  I keep getting "directory could not be found" but I am able to see the directory from xterm window and able to play files from the mounted partition with another player.

I am running JRiver on Debian Wheezy 64-bit, with XFCE

Thx

Please start a new thread for anything that needs discussion.

[bob]

MC will not run on a Galileo since the Galileo has no SSE (math coprocessing) capabilities.
Also, debian isn't stable on the galileo, it sort of works. It's a known problem.

[anonymous]

MC will not run on a Galileo since the Galileo has no SSE (math coprocessing) capabilities.
Also, debian isn't stable on the galileo, it sort of works. It's a known problem.

Thank you, that helps:  Didn't know MC needed SSE capabilities.

FYI; Debian has been rock-solid on my Galileo.

Regards,

[InflatableMouse]

I thought Galileo was just a hostname, never realized it was a type/model of a machine 

[Robert Joe]

Resize testing on Linux Mint 16.

When Clicking on the square between the - and X at the top right of the application, minimize and maximize works. When minimizing it remembers the size and position.

Double click on title bar, maximizes correctly. Once maximized, a single click on the title bar restores the minimized size but the window moves to the top left. Other apps, a double click  is used to minimize.

[bob]

Thank you, that helps:  Didn't know MC needed SSE capabilities.

FYI; Debian has been rock-solid on my Galileo.

Regards,

I've not had as much luck. It crashes on ours wtih cryptic dmesgs from seemingly trivial things such as logging into an user ssh account.
What install method did you use and what firmware level (.75, .90 whatever)?

[bob]

I thought Galileo was just a hostname, never realized it was a type/model of a machine 

It's a little embedded x86 board, like a raspberry pi without a video output.

[bob]

Resize testing on Linux Mint 16.

When Clicking on the square between the - and X at the top right of the application, minimize and maximize works. When minimizing it remembers the size and position.

Double click on title bar, maximizes correctly. Once maximized, a single click on the title bar restores the minimized size but the window moves to the top left. Other apps, a double click  is used to minimize.

Those results are mostly what we're driving for.
The problem is once we've missed setting the screen size properly you get the default upper left corner window and that's saved as the new default.
The trouble has to do with the async nature of xwindows vs the way MC does windowing.
Also, this build returned MC to laggy updating because of the above changes.
Still working on it...
 

[UdoS]

The window is really touchy, specially when you have more windows open on one screen and you move eg. a terminal window around, the window looks a little scary like the screen shot.
Rezising is almost impossible due to flickering and bouncing around.

[bob]

The window is really touchy, specially when you have more windows open on one screen and you move eg. a terminal window around, the window looks a little scary like the screen shot.
Rezising is almost impossible due to flickering and bouncing around.

I've definitely got that user movement/resize problem fixed now, checked it across several desktops.
I'm still trying to get a consistent response across desktops on the initial window when maximized or not and hopefully to handle the multiple monitor case.
I hope to have a build out Thursday or Friday.

[RemyJ]

Good news!  Thanks Bob.

[geier22]

Debian Wheezy / KDE / 64 bit
MediaCenter does not forget the size of the window in Ver. 122. But resizing the window takes very long. It flickers for a long time (Ca. 30 sec)  and does not respond. The behaviour when adjusting the size of the window was much better in the last version