Print

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

[bob]

This is a first crack at a debian stretch AMD64 build of MC23 with GCC 6. It requires libraries that are equivalent to the default ones on stretch OR newer.
Please post bugs here.  Please start a new thread for anything requiring discussion.  Non-bug posts will be deleted.

Download:
http://files.jriver.com/mediacenter/test/MediaCenter-23.0.51-amd64.deb

Use the current Jessie revision instead. See the top of the forum for the latest version.

Also in the BETA repo.

23.0.51 (9/7/2017)

1. NEW: Enabled the use of VST Plugins.

23.0.41 (8/28/2017)

1. NEW: Implement non-US keyboard support.
2. Fixed: Under some situations, menus could appear blank with some hardware/desktop manager combinations.

23.0.36 (8/18/2017)

1. Fixed: Crashing in Theater View from GCC6 non-compliant code.

23.0.31-2 (8/7/2017)

1. Changed: Relaxed package requirements to ignore the minor revision of a package.
2. Fixed: Removed libicu requirement.

23.0.31 (8/7/2017)

1. NEW: First BETA build for debian stretch AMD64.
2. Fixed: Internal structures dealing with UI functions.

[Ekpen]

Greetings:
From 23.28 to 23.31, installing just quits. It will display "install" at 9%, then goes off the screen.
I  even uninstalled 23.0.28, to get a fresh 23.0.31, still failed. It says source "unknown".
I am now back at 23.0.28.
As an addition to these issues:
The audio is skipping badly on versions 23.21 and 23.28. I wrote on another thread over the weekend, comparing to Windows version 23....xx.., we have a way to adjust the skipping and buffering in audio device setting or in DSP setting not sure exactly what specific area, but in the Linux distros, no way for this convenient adjustment.
I am on Ubuntu 1704 64 bit.

Thanks.

George Omoregie

[Hendrik]

We have an installer now?

[Awesome Donkey]

Try installing the .deb from the Terminal.

[Mike Noe]

FWIW, on TumbleWeed, libICU is up to v.59.1, so I had to create three symlinks:

Code: [Select]

ln -s libicudata.so.59.1 libicudata.so.57
ln -s libicuuc.so.59.1 libicuuc.so.57
ln -s libicui18n.so.59.1 libicui18n.so.57

I do have the 57.1 and 58.2 versions also (they appear to be orphans, however) but I set the links to 59.1 since it is the latest in TW.  Seems to be working okay, haven't noticed anything weird yet.

[Ekpen]

Try installing the .deb from the Terminal.

I deleted the 23.0.31 downloaded, re-downloaded, tried to install. The installer screen thinks it is 32.0.28. Install quits again.

Then I remembered the tutorial about apt, some snippets etc. Went to the terminal, issued all commands.. every thing fine. Installed, then loaded what I thought was 23.0.31. I went to help and about, it still says 23.0.28.
Summary : No matter how I installed it, terminal or via installer, it still does not install MC 23.0.31.
I am back now on 23.0.28.

Hendriks: Did you replace this with a version that has the installer ?

I will be happy if you can take a look at the code why audio in (movies) playback is breaking, slipping, or whatever  it is called buffering ,  In one word.. No Smooth audio Playback.. did audio analysis several times.

Thanks in advance.
George

[bob]

FWIW, on TumbleWeed, libICU is up to v.59.1, so I had to create three symlinks:

Code: [Select]

ln -s libicudata.so.59.1 libicudata.so.57
ln -s libicuuc.so.59.1 libicuuc.so.57
ln -s libicui18n.so.59.1 libicui18n.so.57

I do have the 57.1 and 58.2 versions also (they appear to be orphans, however) but I set the links to 59.1 since it is the latest in TW.  Seems to be working okay, haven't noticed anything weird yet.

Shouldn't be needing libicu, that may have been so in the past.
I am somewhat concerned about the compatibility of the AMD64 build with non-debian distros.
Here are the top level library depends:

Code: [Select]

libc6 (>= 2.24)
libasound2 (>= 1.1.3)
libuuid1 (>= 2.29)
libx11-6 (>= 2:1.6.4)
libxext6 (>= 2:1.3.3)
libxcb1 (>= 1.12)
libxau6 (>= 1:1.0.8)
libxdmcp6 (>= 1:1.1.2)
libstdc++6 (>= 6.3.0)
libgtk2.0-0 (>= 2.24.31)
libpango-1.0-0 (>= 1.40) or  libpango1.0-0 (>= 1.40)
libpangoft2-1.0-0 (>= 1.40) | libpango-cairo-1.0-0 (>= 1.40)
libgl1-mesa-glx or libgl1
xdg-utils

[Awesome Donkey]

Yeah, no go here on Arch Linux.

Code: [Select]

mediacenter23: error while loading shared libraries: libicuuc.so.57: cannot open shared object file: No such file or directory
Easily fixed though using the symlinks posted by Mike Noe above, thanks!

[Awesome Donkey]

No go on Linux Mint either.

Code: [Select]

dpkg: dependency problems prevent configuration of mediacenter23:
 mediacenter23 depends on libc6 (>= 2.24); however:
  Version of libc6:amd64 on system is 2.23-0ubuntu9.
 mediacenter23 depends on libasound2 (>= 1.1.3); however:
  Version of libasound2:amd64 on system is 1.1.0-0ubuntu1.
 mediacenter23 depends on libuuid1 (>= 2.29); however:
  Version of libuuid1:amd64 on system is 2.27.1-6ubuntu3.3.
 mediacenter23 depends on libx11-6 (>= 2:1.6.4); however:
  Version of libx11-6:amd64 on system is 2:1.6.3-1ubuntu2.
 mediacenter23 depends on libxcb1 (>= 1.12); however:
  Version of libxcb1:amd64 on system is 1.11.1-1ubuntu1.
 mediacenter23 depends on libstdc++6 (>= 6.3.0); however:
  Version of libstdc++6:amd64 on system is 5.4.0-6ubuntu1~16.04.4.
 mediacenter23 depends on libgtk2.0-0 (>= 2.24.31); however:
  Version of libgtk2.0-0:amd64 on system is 2.24.30-1ubuntu1.16.04.1.
 mediacenter23 depends on libpango-1.0-0 (>= 1.40) | libpango1.0-0 (>= 1.40); however:
  Version of libpango-1.0-0:amd64 on system is 1.38.1-1
dpkg: error processing package mediacenter23 (--install):
 dependency problems - leaving unconfigured

[Hendrik]

Mint is based on Ubuntu or debian, probably need a new release to catch up to Debian.

For libicu, boost seems to link against those. I'll check tomorrow if thats a build error or whats up with that. Those were not required in the past, as far as I know.

Edit:
Found it, icu should not be required anymore (or once again?) in the next build.

[Awesome Donkey]

It's based on Ubuntu, which is based on Debian. But yeah, it's generally out-of-date as it uses Ubuntu 14.04 LTS as a base. I'm sure it'll change next year with 18.04 LTS. It also happens on Ubuntu 17.04 too with just one lib, so I guess that's an improvement. I'll likely switch back from Mint to Ubuntu at some point - really wanted to wait until 17.10 came out, but maybe I should give the Ubuntu daily alpha builds a go? Anyways...

Code: [Select]

dpkg: dependency problems prevent configuration of mediacenter23:
 mediacenter23 depends on libxcb1 (>= 1.12); however:
  Version of libxcb1:amd64 on system is 1.11.1-1ubuntu1.

[Hendrik]

Its an unusual situation when Debian of all things appears to have "too new" stuff. :p

[Awesome Donkey]

Its an unusual situation when Debian of all things appears to have "too new" stuff. :p

No kidding, it's usually always the other way around. Looks like Ubuntu 17.10 is *still* using libxcb 11.11.1 but hopefully that changes before the final release (thanks to the release of Debian 9).

But yeah, I got it working on Arch Linux at least, and it's working pretty good thus far (rolling distros FTW!). Otherwise it's pretty much incompatible with Linux Mint and Elementary OS due to them being based on the older, outdated Ubuntu 14.04 LTS release along with the newer Ubuntu 16.04 LTS release.

Ubuntu 17.04 does work fine regardless of the outdated libxcb1 warning. Actually, it works on Linux Mint too regardless of the warnings.

[bob]

It's based on Ubuntu, which is based on Debian. But yeah, it's generally out-of-date as it uses Ubuntu 16.04 LTS as a base. I'm sure it'll change next year with 18.04 LTS. It also happens on Ubuntu 17.04 too with just one lib, so I guess that's an improvement. I'll likely switch back from Mint to Ubuntu at some point - really wanted to wait until 17.10 came out, but maybe I should give the Ubuntu daily alpha builds a go? Anyways...

Code: [Select]

dpkg: dependency problems prevent configuration of mediacenter23:
 mediacenter23 depends on libxcb1 (>= 1.12); however:
  Version of libxcb1:amd64 on system is 1.11.1-1ubuntu1.

Fixed both issues in a new build.
It's in the repo, about to upload it to the beta location too..

[Awesome Donkey]

Fixed both issues in a new build.
It's in the repo, about to upload it to the beta location too..

Groovy! Yeah, no more errors in Arch Linux (reversed the symlinks). I'll test Ubuntu 17.04 here in a few minutes to verify the error there is gone too. If so, I'll likely replace Linux Mint 18.2 with Ubuntu 17.10 once the final beta is released (and nuke Linux Mint in the meantime).

EDIT: Yep, no more lib error on Ubuntu 17.04, nice! I'll edit the tutorial soon recommending Linux Mint 18.2 and below, Elementary OS 0.4.1 and below, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS users to either stick with 23.0.28 64-bit or install the 32-bit version of MC.

[Hendrik]

Ubuntu 17.04 does work fine regardless of the outdated libxcb1 warning. Actually, it works on Linux Mint too regardless of the warnings.

As long as its the same major versions thats usually the case (it wouldn't start if it were different majors), but its hard to tell if there might be subtle bugs down the road from mismatches.
Considering we don't use any fancy new features of those library (in fact we used to build against older ones just last week), its probably going to be fine.

[Awesome Donkey]

Yeah, that's true. But the package manager (Synaptic) flags MC as being a broken package and wants to remove it, so ignoring the error(s) may not be an easy option there. Probably easier just to install the i386 build.

[Mike Noe]

Confirmed on TW, installs, runs fine now without the *icu dependency msgs.

I am somewhat concerned about the compatibility of the AMD64 build with non-debian distros.

Yeah, I get that, but MC on TW is so very boring-ly stable and performant (at least with audio).

Too bad you guys couldn't leverage the Suse OBS somehow...

[bob]

Could you guys give 23.0.36 a whirl?

[Mike Noe]

Testing TheatreView on X and XWayland (Plasma5 DM, Mesa 17.1.6) on TW (single monitor).  Seems good on both so far, ESC key not available on XWayland (Plasma issue, most likely) and on first use of TheaterView, the top menu bar doesn't show up until choosing a item and than going back.  Otherwise, seemingly normal for Audio playback, changing zones, etc.  No crashes yet.

I recv'd a "pkg not signed" error on install, but I think that might be a recent TW upgrade thing.

[MRiver]

23.0.28 will work fine, but 31-2 and 36 will request GLIBCXX_3.4.21 and Others.
Then,Installing gcc 6.4 and making it correspond to GLIBCXX_ 3.4.21 will result in "segmentation fault".
23.0.28 also works under the GLIBCXX_3.4.21 environment. Do you still need a missing package?

[Awesome Donkey]

What Linux distro are you using? 31-2 and 36 have newer lib dependencies.

[MRiver]

What Linux distro are you using? 31-2 and 36 have newer lib dependencies.

RHEL base OS.

Regards,

[MRiver]

RHEL base OS.

Regards,

ldd /usr/bin/mediacenter23
   linux-vdso.so.1 =>  (0x00007fffabfd8000)
   libcryptlib.so => /usr/lib/jriver/Media Center 23/libcryptlib.so (0x00007f0b42665000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0b42417000)
   librt.so.1 => /lib64/librt.so.1 (0x00007f0b4220f000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007f0b4200b000)
   libboost_regex.so.1.59.0 => /usr/lib/jriver/Media Center 23/libboost_regex.so.1.59.0 (0x00007f0b41d28000)
   libX11.so.6 => /lib64/libX11.so.6 (0x00007f0b419ea000)
   libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f0b417e5000)
   libGL.so.1 => /lib64/libGL.so.1 (0x00007f0b41574000)
   libXrandr.so.2 => /lib64/libXrandr.so.2 (0x00007f0b4136a000)
   libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f0b40fea000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f0b40ce7000)
   libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f0b40ad1000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f0b40710000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f0b4480c000)
   libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f0b404ed000)
   libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f0b402c3000)
   libxcb-dri3.so.0 => /lib64/libxcb-dri3.so.0 (0x00007f0b400c0000)
   libxcb-present.so.0 => /lib64/libxcb-present.so.0 (0x00007f0b3febc000)
   libxcb-randr.so.0 => /lib64/libxcb-randr.so.0 (0x00007f0b3fcae000)
   libxcb-xfixes.so.0 => /lib64/libxcb-xfixes.so.0 (0x00007f0b3faa6000)
   libxcb-render.so.0 => /lib64/libxcb-render.so.0 (0x00007f0b3f89b000)
   libxcb-shape.so.0 => /lib64/libxcb-shape.so.0 (0x00007f0b3f697000)
   libxcb-sync.so.1 => /lib64/libxcb-sync.so.1 (0x00007f0b3f490000)
   libxshmfence.so.1 => /lib64/libxshmfence.so.1 (0x00007f0b3f28c000)
   libglapi.so.0 => /lib64/libglapi.so.0 (0x00007f0b3f05d000)
   libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f0b3ee36000)
   libXext.so.6 => /lib64/libXext.so.6 (0x00007f0b3ec23000)
   libXdamage.so.1 => /lib64/libXdamage.so.1 (0x00007f0b3ea20000)
   libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007f0b3e81a000)
   libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x00007f0b3e617000)
   libxcb-glx.so.0 => /lib64/libxcb-glx.so.0 (0x00007f0b3e3fd000)
   libxcb-dri2.so.0 => /lib64/libxcb-dri2.so.0 (0x00007f0b3e1f8000)
   libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00007f0b3dff1000)
   libdrm.so.2 => /lib64/libdrm.so.2 (0x00007f0b3dde2000)
   libXrender.so.1 => /lib64/libXrender.so.1 (0x00007f0b3dbd8000)
   libXau.so.6 => /lib64/libXau.so.6 (0x00007f0b3d9d3000)
   libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f0b3d772000)

[Awesome Donkey]

Honestly? You'd probably have much better luck using MC with a Debian based OS, since everything besides Debian itself is considered unsupported. RHEL (or RHEL based) likely is pushing the limits where MC can work at.

Might even have better luck with Fedora too, since there's a tutorial for that.

Media Center 23.0.31-2 and above have increased lib version requirements, matching the recently released Debian Stretch. It sounds like the RHEL based OS is possibly using older libs so it's possible you won't be able to get it to work without switching OSes. Another example of this is, Media Center 23.0.31-2 and above won't install/work correctly anymore on Ubuntu 16.04 LTS or Linux Mint 18.2 (the package manager freaks out wanting to remove MC23) due to it requiring newer libs. At least that's until there's a new Ubuntu LTS update next year (which Mint too can base itself off of).

[Hendrik]

RHEL has a rather long lifecycle, the current version is originally from 2014, and the way those work, they don't really update software in it besides security fixes, so running something build for a distribution from 2017 is probably hard.
You can run the 32-bit version probably, which is our fallback for older systems.

[bob]

I'm wondering if we should drop the AMD64 build back to Jessie.
As you say, it doesn't run on Ubuntu 16.04 either which is supposedly a long term release. The Stretch build will also not run on the QNAP.
It's not like we are going to get any new features out of using GCC 6 while the arm and i386 builds are still on 4.9.

[Awesome Donkey]

IMO, have both but keep the Stretch build around labeled as an experimental build that is updated once-in-a-blue-moon (and has to be manually installed)?

Ubuntu LTS (along with Mint, elementary, etc.) will catch up once 18.04 LTS is released in around 7 months.

[Hendrik]

QNAP will not even run on 4.9 IIRC, and going back to 4.8 would really be painful. I don't really want to be tied to a severely old compiler for compatibility with some closed ecosystem.

[bob]

QNAP will not even run on 4.9 IIRC, and going back to 4.8 would really be painful. I don't really want to be tied to a severely old compiler for compatibility with some closed ecosystem.

Yeah, looks like you are right, it's dependent on libstdc++-4.8
I think that's for boost though. I could build it without boost and see what else breaks...

As for maintaining 2 AMD64 builds, ugh. We spend too much time making builds already. It slows down other projects...

[Awesome Donkey]

Well, could keep thing as-is then and keep/recommend the i386 build for compatibility with systems running older libs? But the last time I tried using the i386 build on an AMD64 system a few weeks back the build would instantly segfault every time on start on Linux Mint (all i386 dependencies were satisfied). I'll have to play with that more in a VM once I get more time.

[Hendrik]

Using Jessie as a base would generally be fine, since as you say yourself the other builds are based on that still - and we have to work on the lowest common denominator (and thats already quite an improvement from wheezy). But after all the work to get every platform on C++11, I would hate for Linux-amd64 to go back to 4.8, though (which only has incomplete C++11 support).

[bob]

Using Jessie as a base would generally be fine, since as you say yourself the other builds are based on that still - and we have to work on the lowest common denominator (and thats already quite an improvement from wheezy). But after all the work to get every platform on C++11, I would hate for Linux-amd64 to go back to 4.8, though (which only has incomplete C++11 support).

Well it was cool that GCC 6 exposed those "bugs"...
I'm a bit hesitant to go back to Jessie for AMD64 since I updated my dev box to Stretch.

[mwillems]

Hey bob, mattkhan and I are seeing some bugs related to streaming video formats to linux clients from windows servers over in this thread: 

https://yabb.jriver.com/interact/index.php/topic,111976.0.html

Just wanted to make sure you'd seen it since (after I opened the thread) we appear to have isolated the issue to linux clients only

[Hendrik]

I think that's for boost though. I could build it without boost and see what else breaks...

Now that you said that, we only use boost for regex, but if we had C++11 everywhere, we could use C++11 built-in regex functionality, and get rid of boost entirely.
Its practically the same syntax as well, since the boost stuff was basically moved into the C++ library.

Something for my list, i guess.

[Awesome Donkey]

Let me know when the 64-bit Stretch build lands in the stable repo. I'll rewrite the tutorial recommending users of Ubuntu 16.04 LTS, Linux Mint 18.x, etc. to use the i386 build.

[bob]

Let me know when the 64-bit Stretch build lands in the stable repo. I'll rewrite the tutorial recommending users of Ubuntu 16.04 LTS, Linux Mint 18.x, etc. to use the i386 build.

I'm still up in the air whether or not to keep the amd64 build in Stretch. Been discussing this with Hendrik.

[Kott]

23.0.51
Unfortunately, I get empty (white), unresponsive window sometimes. What should I do for proper report?

vst seems to works!
but some plugins crashes MC and when open DSP studio after restart, only way to revert - delete lines with bad plugin in "Machine Settings.ini"

[Awesome Donkey]

What distro are you using? What's your GPU? Are you using the open source or proprietary drivers for your GPU? What plug-ins are you using which causes the issues?

That should help narrow the problem down somewhat.

[Kott]

What distro are you using? What's your GPU? Are you using the open source or proprietary drivers for your GPU? What plug-ins are you using which causes the issues?

That should help narrow the problem down somewhat.

openSUSE Tumbleweed, I can give list of necessary libs
NVIDIA with blob
I'haven' any such issues with MC before (be honest, it runs fine about hour now).

If we talk about crashing against vst, i say - that's normal every app do that. But that apps has some protection, in simple words: it looks in logs regarding does loading last vst *.so cause crash or not, i guess

[Awesome Donkey]

Any example VST plug-ins which always crash?

[Kott]

well, it was old version of https://www.overtonedsp.co.uk/download/download_rvb500/ which crashes JUCE hosts as well
recent version works fine
if you mind - I can upload "bad" file

But, really, it will be pretty to implement plugin protection.

[geier22]

The new "outfit" of the action window, especially the tag window, I find not helpful. It takes up too much space. There is not enough space to display the remaining MC window.

when I edit (highlight) a field in the tag editor, this field appears on all workspaces! Until now, it only appeared on the workspace, on which MC was also open.

[bob]

well, it was old version of https://www.overtonedsp.co.uk/download/download_rvb500/ which crashes JUCE hosts as well
recent version works fine
if you mind - I can upload "bad" file

But, really, it will be pretty to implement plugin protection.

A lot of the VST plugins seems to me to be really poorly implemented on linux.
There is an issue as well with the platform the plugin is developed on and the libraries they are linked to. This is the disadvantage for developers trying to make VST plugins work on linux as opposed to windows.

[bob]

The new "outfit" of the action window, especially the tag window, I find not helpful. It takes up too much space. There is not enough space to display the remaining MC window.

when I edit (highlight) a field in the tag editor, this field appears on all workspaces! Until now, it only appeared on the workspace, on which MC was also open.

You can get back the old tag window behavior if you hold down the shift key when you select tag from the right click menu.

The edit tag window behavior is not new though I never noticed it before. It's a side effect of the type of window being created (unmanaged). I'll look into it...

[hillcreative]

Hey Bob, looking forward to the tutorial to install the AMD64 Beta! Will I be able to install it over the stable 23.0.21 version? I apologize as my newbie Linux skills do not extend to installing 23.0.51 from a .deb file. I can run it from terminal but there is a library dependency problem with Ubuntu 17.0.4. BTW 23.0.51 fixes the DSP window issue : )

[Awesome Donkey]

To fix the dependency issue, just run sudo apt-get install -f in a Terminal. Otherwise 23.0.51 should work fine in Ubuntu 17.04 and above. If you're using 16.04 LTS, it won't work.

[hillcreative]

Forgive my newbiness... how do you install the new 23.0.51 properly? A double click brings up an installer but the Install button does nothing.

[Rizlaw]

To fix the dependency issue, just run sudo apt-get install -f in a Terminal. Otherwise 23.0.51 should work fine in Ubuntu 17.04 and above. If you're using 16.04 LTS, it won't work.

Bob,

I tried: sudo apt-get install MediaCenter-23.0.51-amd64.deb -f. It doesn't work for 17.04. Here is what i get after opening a terminal in the folder where I have the MC deb file:

Code: [Select]

Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package MediaCenter-23.0.51-amd64.deb
E: Couldn't find any package by glob 'MediaCenter-23.0.51-amd64.deb'
E: Couldn't find any package by regex 'MediaCenter-23.0.51-amd64.deb'
louis@Gort:~/Downloads$


[hillcreative]

I think you need to add the path to the .deb file for it to be found. If you don't know the path just right click the .deb file and copy the path. You DID download it didn't you? : )