Topic: JRiver Media Center 21.0.90 for Debian (Jessie) AMD64 (Read 94483 times)

bob · « **on:** August 07, 2015, 04:15:39 pm »

The latest build is up at:

https://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-21.0.90-amd64.deb (also in the latest apt repository)

See the linux x86 log for specific linux changes and the windows log for general MC changes.
Only changes that apply specifically to the amd64 build will be posted here.

21.0.90 (7/14/2016)

See the main linux changelog

21.0.88 (6/10/2016)

See the main linux changelog

21.0.85 (5/27/2016)

See the main linux changelog

21.0.83 (5/20/2016)

1. Fixed: Linux detect cifs filesystems for timer supported auto imports

21.0.76 (4/29/2016)

See the main linux changelog

21.0.76 (4/12/2016)

See the main linux changelog.

21.0.63 (3/21/2016)

See the main linux changelog

21.0.61 (3/18/2016)

See the main linux changelog

21.0.54 (3/4/2016)

Changes from the main branch. Should be considered for stable repo but is in latest for now.

21.0.51 (2/26/2016)

See the main changelog for linux in this forum. More work on eliminating hard killed threads. Needs testing for stability.

21.0.48-3 (2/16/2016)

1. Changed: Recompiled eveything with GCC/G++ 4.8 to help with portability on non-debian systems that didn't support libstdc++-4.9
2. Fixed: libJRReader wasn't being properly loaded/unloaded. Could have caused instability in that code.

21.0.48 (2/15/2016)

See the main linux changelog

21.0.39 (1/25/2016)

See the main linux changelog.

21.0.37 (1/15/2016)

Changes from the main branch

21.0.34 (1/8/2016)

1. Fixed: Poor image creation performance on amd64 platforms.
2. Fixed: Options window size and placement troubles that showed up on some systems.

21.0.28 (12/17/2015)

1. Fixed socket hangs/leaks/crashes.

21.0.23 (11/23/2015)

1. Fixed: Memory leak.

21.0.16 (10/16/2015)

21.0.7 (9/15/2015)

21.0.6 (9/4/2015)

21.0.5-1 (9/1/2015)

21.0.5 (8/28/2015)

1. NEW: mimetype association for the .mjr file. This means you can click on an .mjr file in the linux file browser to install a license and it should work through a browser form the restore page as well. Works silently, needs testing.
2. Fixed: Problems with premature timeout of trialware.
3. Fixed: Library paths for the gnutls support libs under the Media Center library directory.

Awesome Donkey · « **Reply #1 on:** August 07, 2015, 06:52:00 pm »

Is the apt repository using the same mediacenter20 link or will it change for MC21? I'll post the tutorials updated for MC 21 over the weekend!

EDIT: Derp, access denied error!

BryanC · « **Reply #2 on:** August 08, 2015, 10:34:24 pm »

Yup, getting an access denied error. Can't wait to try this out.

geier22 · « **Reply #3 on:** August 09, 2015, 01:30:46 am »

Quote from: JimH on July 28, 2015, 06:28:21 pm

Tomorrow will be the last day of the special price. Thanks for the great response!

[Edit July 31 -- Upgrades are now $22.98 for Mac or Windows, $26.98 for a Master License.]

This will be our best month ever, and not by a little. This year's upgrade response will beat our old monthly record by about 30%.

These big bursts of business give us tremendous financial ability to continue to try to do our best for you. We don't always succeed, but we do always try, and we do sincerely enjoy your encouragement. Thank you.

Is there already a possibility to buy a license for MC 21 for linux?

tlcmd · « **Reply #4 on:** August 10, 2015, 09:12:27 am »

Help! I'm getting the notice below:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>B248011287E73E63</RequestId><HostId>6CncfbPcPzhAjg0OYtbr112/6kdGTVrpAkzk/g+Y5qL5Xa55bQ2cDxdMy4m1XDyrjRSeu1pZT+M=</HostId></Error>

Thanks,
tlcmd (have the Linux MC20 license)

bob · « **Reply #5 on:** August 10, 2015, 09:54:41 am »

Fixed now. Sorry.

bob · « **Reply #6 on:** August 10, 2015, 04:51:24 pm »

Check out the new fonts!

BryanC · « **Reply #7 on:** August 10, 2015, 06:52:40 pm »

Hey bob, might it be better to just combine the two build threads? The changelog could denote 64-bit specific changes. It's just one less place we've got to check for new bugs/discussion since most of the x64 specific issues have been ironed out.

geier22 · « **Reply #8 on:** August 10, 2015, 09:40:04 pm »

I fixed the apt-repo and updated to 21.0.3 MC.
Super --- I can select dozens of fonts - and it works! Thanks a lot for this feature!

But the window with the best new features is the only one that does not have focus. If you click on "Select fonts", it remains only in the taskbar

Now I have again a 30-day trial-period. Version 21.0.2 did not start, because the trial period stood at 0 days

I ask again: When can I buy an update license for MC21
Is the License for MC 20 also valid for MC21?

bob · « **Reply #9 on:** August 11, 2015, 01:30:47 pm »

Quote from: geier22 on August 10, 2015, 09:40:04 pm

I fixed the apt-repo and updated to 21.0.3 MC.
Super --- I can select dozens of fonts - and it works! Thanks a lot for this feature!

But the window with the best new features is the only one that does not have focus. If you click on "Select fonts", it remains only in the taskbar

Now I have again a 30-day trial-period. Version 21.0.2 did not start, because the trial period stood at 0 days

I ask again: When can I buy an update license for MC21
Is the License for MC 20 also valid for MC21?

Normally you install a version 20 license code into version 21 then do "Buy Media Center" from the help menu which would get you the reduced price.
We have discovered that's not working right now and we are checking into it...

geier22 · « **Reply #10 on:** August 11, 2015, 03:59:47 pm »

I installed MC in multiple VMs. On my main system (KDE Jessie) is running MC 20 + 21
When updating MC 21.0.2. to 21.0.3 I got a 30-day trial. I could start MC 21.0.2 once only.

In Cinnamon and Gnome (Stretch) I could start 21.0.3 once only to .
Trying - as you described - the Version 20 license-code entering in MC 21, failed -
but now I got since yesterday from you 4 mjr - files for MC 20, and have only one chance to make a restore .

--- not so good.

bob · « **Reply #11 on:** August 11, 2015, 05:03:44 pm »

Quote from: geier22 on August 11, 2015, 03:59:47 pm

I installed MC in multiple VMs. On my main system (KDE Jessie) is running MC 20 + 21
When updating MC 21.0.2. to 21.0.3 I got a 30-day trial. I could start MC 21.0.2 once only.

In Cinnamon and Gnome (Stretch) I could start 21.0.3 once only to .
Trying - as you described - the Version 20 license-code entering in MC 21, failed -
but now I got since yesterday from you 4 mjr - files for MC 20, and have only one chance to make a restore .
--- not so good.

I reset your restores so that shouldn't be an issue for now.

I see where the upgrade is failing. Matt and I are working on it.. It will be done before the 30 days runs out!

bob · « **Reply #12 on:** August 11, 2015, 05:05:20 pm »

Quote from: BryanC on August 10, 2015, 06:52:40 pm

Hey bob, might it be better to just combine the two build threads? The changelog could denote 64-bit specific changes. It's just one less place we've got to check for new bugs/discussion since most of the x64 specific issues have been ironed out.

I think that would be OK but we don't always build them together, for example I had an issue specific to the arm build and just got it resolved today so it's lagging behind the others...

geier22 · « **Reply #13 on:** August 11, 2015, 05:09:48 pm »

Thank you Bob, but I think I'll run together for safety MC 20 and MC 21, until the issues are resolved.

bob · « **Reply #14 on:** August 11, 2015, 05:24:48 pm »

Quote from: geier22 on August 11, 2015, 05:09:48 pm

Thank you Bob, but I think I'll run together for safety MC 20 and MC 21, until the issues are resolved.

It's totally fine to run them both on the same machine.

bob · « **Reply #15 on:** August 14, 2015, 05:14:37 pm »

The log reading function will only work with a newer version of xdg-open that got the latest bug fixes.
It doesn't work right in wheezy or jessie but does on ubuntu vivid.

tlcmd · « **Reply #16 on:** August 15, 2015, 12:19:52 pm »

1 question, please about MC21.0.4 for linux. I've just downloaded and installed it, but it is not registered as MC20 is.

I cannot use my MC 20 install key or my MC20 buy button because I get the message that it has been used too many times. What do I do?

Thank you,
tlcmd

bob · « **Reply #17 on:** August 17, 2015, 01:24:45 pm »

Quote from: tlcmd on August 15, 2015, 12:19:52 pm

1 question, please about MC21.0.4 for linux. I've just downloaded and installed it, but it is not registered as MC20 is.

I cannot use my MC 20 install key or my MC20 buy button because I get the message that it has been used too many times. What do I do?

Thank you,
tlcmd

I reset your restores, try again...

Awesome Donkey · « **Reply #18 on:** August 17, 2015, 03:30:01 pm »

Bob, I saw you mention that MC doesn't do any file associations on Linux but perhaps this should be changed where MC has a file association for .mjr license files so it could be a little easier to get the license working (for those users having issues)?

I remember looking at the documentation for this, I'll see if I can dig it up if you're interested (or need it).

bob · « **Reply #19 on:** August 20, 2015, 01:43:50 pm »

Quote from: Awesome Donkey on August 17, 2015, 03:30:01 pm

Bob, I saw you mention that MC doesn't do any file associations on Linux but perhaps this should be changed where MC has a file association for .mjr license files so it could be a little easier to get the license working (for those users having issues)?

I remember looking at the documentation for this, I'll see if I can dig it up if you're interested (or need it).

Sure that'd be great. It should make the association for .mjr at least upon installation of the .dpkg.

Awesome Donkey · « **Reply #20 on:** August 21, 2015, 04:16:37 pm »

Quote from: bob on August 20, 2015, 01:43:50 pm

Sure that'd be great. It should make the association for .mjr at least upon installation of the .dpkg.

Here's some stuff for Debian: https://wiki.debian.org/MimeTypesSupport

I'll hunt down the stuff I was looking at before.

http://www.freedesktop.org/wiki/Specifications/AddingMIMETutor/
http://www.freedesktop.org/wiki/Specifications/mime-apps-spec/
http://standards.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-latest.html

mcollier · « **Reply #21 on:** August 22, 2015, 07:58:54 am »

Good day, I've been using 21.0.4 on Jessie 64 for a few days now and it's been working well.

A few observations:
1) Issues with window resizing: When switching from 'mini view' to 'standard view' when the standard view is not maximized, the mouse pointer does not change for resizing the window except on the left edge in the upper left corner. If the window is resized horizontally using that, a black box expands, but the window does not redraw to fill the space.

2) Since this upgrade to v21 I notice that when in 'mini view' using the Noire theme, that the play button can extend slightly outside the top of the window boundary. I noticed that 'mini view' in v21 is 3-5 pixels smaller in the vertical dimension.

3) Hovering over the rewind/play/pause/stop/ffwd buttons in 'mini view' leaves the buttons in various states of highlighting. This does not seem to be an issue in standard view.

Thanks!

EDIT: added #3

bob · « **Reply #22 on:** August 28, 2015, 05:14:29 pm »

The registration association could use some testing under different desktops and the library fixes on non-debian distros.

i386 and arm builds coming soon.

Awesome Donkey · « **Reply #23 on:** August 28, 2015, 06:49:57 pm »

Works good here on Ubuntu 15.04 x64. Good work Bob!

mcollier · « **Reply #24 on:** August 28, 2015, 08:41:31 pm »

Quote from: bob on August 28, 2015, 05:14:29 pm

The registration association could use some testing under different desktops and the library fixes on non-debian distros.

The new mime type worked fine on Debian Jessie 64.

Mediacenter was not running. I downloaded the mjr file to ~/Downloads

double-clicking the mjr icon did not *appear* to do anything, but evidently it silently ran the registration. Although this is certainly superior to having to do the registration from the command line, I think would be better if MediaCenter actually launched if it's not already running and display a message that the registration was accepted.

Thanks for the continuous improvement to MediaCenter!!

tlcmd · « **Reply #25 on:** August 29, 2015, 11:55:48 am »

I just purchased a license for Linux MC21.0.5, but was not offered the option of purchasing a MASTER LICENSE. How may I now purchase a MASTER LICENSE for the difference between the cost of the MC21 license and the reduced cost of the MASTER LICENSE??

Thanks,
tlcmd

Awesome Donkey · « **Reply #26 on:** August 29, 2015, 12:00:30 pm »

Quote from: tlcmd on August 29, 2015, 11:55:48 am

I just purchased a license for Linux MC21.0.5, but was not offered the option of purchasing a MASTER LICENSE. How may I now purchase a MASTER LICENSE for the difference between the cost of the MC21 license and the reduced cost of the MASTER LICENSE??

Thanks,
tlcmd

The Master License upgrade direct link is here: http://jriver.com/purchase_21_master_as_upgrade.html

tlcmd · « **Reply #27 on:** August 29, 2015, 12:59:52 pm »

Why can I not simply pay the difference between the MC21 Linux license and the Master License rather than having to pay the price for both since the Master License also includes the MC21 License for Linux?

BryanC · « **Reply #28 on:** August 29, 2015, 01:22:38 pm »

Quote from: tlcmd on August 29, 2015, 12:59:52 pm

Why can I not simply pay the difference between the MC21 Linux license and the Master License rather than having to pay the price for both since the Master License also includes the MC21 License for Linux?

Was your errant purchase a result of this?: http://yabb.jriver.com/interact/index.php?topic=99696.msg690953#msg690953

If so, you might want to bring it to Jim's attention in this thread: http://yabb.jriver.com/interact/index.php?topic=98538.150

tlcmd · « **Reply #29 on:** August 29, 2015, 02:41:30 pm »

In a word, YES.

Awesome Donkey · « **Reply #30 on:** August 30, 2015, 06:03:47 pm »

The libX11 segfault still exists - it's still easily reproducible.

http://yabb.jriver.com/interact/index.php?topic=96854.msg668859#msg668859

Should I start a new topic on this?

Awesome Donkey · « **Reply #31 on:** August 30, 2015, 06:12:13 pm »

Also the issue still exists where library backups dates are set ahead to the next date at 6PM every day. The date change is 6 hours too fast. Try it at 6PM your local time (which is Central US for me).

Awesome Donkey · « **Reply #32 on:** August 30, 2015, 06:13:02 pm »

And when manually saving a library backup (and one exists already for that day) there's no prompt to override the file like there is in Windows and Mac.

bob · « **Reply #33 on:** August 31, 2015, 01:28:55 pm »

Thanks for the last 3 posts AD. We'll check into the segfault and date issue. I wasn't able to reproduce the date issue in the past but it does sound suspiciously like a timezone issue. I think 2 and 3 may be related.

Awesome Donkey · « **Reply #34 on:** August 31, 2015, 02:10:26 pm »

No problem.

After thinking about it some more, perhaps the third issue with the override prompt is more of an issue with with the file browser, e.g. Nautilus in this case than MC? Not sure.

bob · « **Reply #35 on:** September 01, 2015, 06:44:34 pm »

Added a graphical feedback to license install.
Important fixes from the main stream.

Awesome Donkey · « **Reply #36 on:** September 01, 2015, 07:04:33 pm »

Awesome work. BTW, you should be able to easily reproduce the library backup date issue right now.

bob · « **Reply #37 on:** September 03, 2015, 11:31:25 am »

Quote from: Awesome Donkey on August 30, 2015, 06:03:47 pm

The libX11 segfault still exists - it's still easily reproducible.

http://yabb.jriver.com/interact/index.php?topic=96854.msg668859#msg668859

Should I start a new topic on this?

I can easily reproduce this as well but it crashes in the debugger without leaving a stack trace behind. I'm assuming it's related to the display window not going away.

Awesome Donkey · « **Reply #38 on:** September 04, 2015, 06:27:31 pm »

It's fixed.

Also skins are now easy to install/manage - I'll add that to the tutorial later this weekend!

bob · « **Reply #39 on:** September 15, 2015, 05:05:31 pm »

Changes listed here http://yabb.jriver.com/interact/index.php?topic=100183.0

geier22 · « **Reply #40 on:** September 16, 2015, 04:34:46 am »

nowadays I checked for a long time where MC stores its files. I found strange things:
In /usr/lib/JRiver/ there are two identical directories (see picture)
The program file is not in this directory, only a link to /usr/bin/ mediacenter21. There, the program is with 18.3 MiB.
I think, in Linux makes everyone what he wants now. I just installed SparkyLinux, and find a wallpaper folder in / opt / ??

To my knowledge, programs must be installed to / opt /, which are not provided by the distribution. See here.

I have all additional programs which are not come from the Debian repos installed in /opt/. I also have such a good overview of additional programs
If I'm doing a new installation I just need to copy the /opt/ directory to the new installation, copy the ~/home/ - directories of the program. I then make a entry in the start menu - that's all.

What is the reason why not JRiver makes this so?

Good news:
MC is working well now in Debian Stretch (KDE) (since the updates in the last week)
MC is also working well in SparkyLinux (LXQT and XFCE) - SparkyLinux is Debian-Stretch based

A question about the Skins:
Earlier you could download Skins as *.zip files. The files could be extracted and copied in the skin directory.
Now these are little *.mjp - files. What to do with these files?

Hendrik · « **Reply #41 on:** September 16, 2015, 05:18:15 am »

Quote from: geier22 on September 16, 2015, 04:34:46 am

What is the reason why not JRiver makes this so?

MC is installed using the normal package manager, on Debian and Ubuntu at least, and as such there is no reason to move to /opt/, IMHO. We even provide a repository for automatic updating and everything.
Why you have a MC21 dir next to Media Center 21 I cannot tell you. MC does not use that. But considering both contain the exact same files, maybe MC21 is a symlink?

geier22 · « **Reply #42 on:** September 16, 2015, 05:40:33 am »

Quote from: Hendrik on September 16, 2015, 05:18:15 am

Why you have a MC21 dir next to Media Center 21 I cannot tell you. MC does not use that. But considering both contain the exact same files, maybe MC21 is a symlink?

I have now examined: It is indeed a symlink. I have the symlink now renamed. MC starts as before.
I'll wait a while and then delete it
In this installation (SparkyLinux XFCE based on Debian Stretch), I never installed MC by hand. I have added the repo of JRiver right after installation. From there I have MC installed.
The updates were always done only with the normal dist-upgrade. Last yesterday to version 21.0.7.
This symlink can therefore only come from JRiver

Hendrik · « **Reply #43 on:** September 16, 2015, 05:43:08 am »

It appears Bob added the symlink to the .deb recently. I guess its easier to access without the spaces. I would just leave it in place, its not like it harms anyone in the JRiver directory there.

geier22 · « **Reply #44 on:** September 16, 2015, 06:03:44 am »

It does not hurt - but it's confusing. It would be good if the directory /usr/lib/JRiver/Media Center 21/ would then at some point disappear.
That's what I meant by: I think, in Linux makes everyone what he wants now.

Quote from: Hendrik on September 16, 2015, 05:18:15 am

MC is installed using the normal package manager, on Debian and Ubuntu at least, and as such there is no reason to move to /opt/, IMHO.

However, there are examples where the normal installer installs the program files - in my opinion - correct to the / opt / directory.
One example is OpenOffice

bob · « **Reply #45 on:** September 17, 2015, 10:29:34 am »

Quote from: geier22 on September 16, 2015, 06:03:44 am

It does not hurt - but it's confusing. It would be good if the directory /usr/lib/JRiver/Media Center 21/ would then at some point disappear.
That's what I meant by: I think, in Linux makes everyone what he wants now.

However, there are examples where the normal installer installs the program files - in my opinion - correct to the / opt / directory.
One example is OpenOffice

/opt has been the "standardized" location for installation of third party apps since at least System V unix.
It's also basically been ignored for that long as well.

Since we are installing as a package with our own repository as Hendrik said I see no issues with installing to /usr/lib/jriver

The MC21 symlink to the Media Center 21 directory is deliberate and was needed to get some of the libraries in /usr/lib/jriver/Media Center 21 to link to other libraries in /usr/lib/jriver/Media Center 21 properly because of shortcomings with spaces in pathnames in the build system. You should leave that in place as well as anything that's part of the MC .deb package.

UdoS · « **Reply #46 on:** September 17, 2015, 12:39:38 pm »

Hi Bob,

I installed MC21.0.7 and bought the master license. But I can' install the license: it says:

CRegistrationHelper::GetLicenseFileFromRegistrationCode: error = There was a problem communicating with the license server.

ot I tried the other way by importing the .mjr file. It still says, there is no license and 29 days left.

bob · « **Reply #47 on:** September 17, 2015, 12:59:46 pm »

Quote from: UdoS on September 17, 2015, 12:39:38 pm

Hi Bob,

I installed MC21.0.7 and bought the master license. But I can' install the license: it says:

CRegistrationHelper::GetLicenseFileFromRegistrationCode: error = There was a problem communicating with the license server.

ot I tried the other way by importing the .mjr file. It still says, there is no license and 29 days left.

If you are internet connected on your linux box the error likely comes from not using debian and the root certificate store being somewhere other than the standard debian place.

From the command line, try the .mjr without the switch.

i.e.

mediacenter21 "whatever your mjr file name is.mjr" and see if you get a success popup box.
Remember .mjr's are only good for 14 days. Request another if yours is older.

UdoS · « **Reply #48 on:** September 19, 2015, 01:49:49 pm »

Quote from: bob on September 17, 2015, 12:59:46 pm

If you are internet connected on your linux box the error likely comes from not using debian and the root certificate store being somewhere other than the standard debian place.

From the command line, try the .mjr without the switch.

i.e.

mediacenter21 "whatever your mjr file name is.mjr" and see if you get a success popup box.
Remember .mjr's are only good for 14 days. Request another if yours is older.

Thanks Bob,

I tried the commandline and it works fine.

InflatableMouse · « **Reply #49 on:** September 24, 2015, 02:17:54 am »

This is the first 64-bit release I try.

When I click anywhere in the dark area on top (around the current file/slider/search box), MediaCenter responds as if I clicked the Max/Restore button.

I think in one of the recent 32-bit release this was (accidently?) solved, unless it was reintroduced?

I realize this may not be high prio, but it is kind of annoying and it's been there from the start

.

INTERACT FORUM

Author Topic: JRiver Media Center 21.0.90 for Debian (Jessie) AMD64 (Read 94483 times)