INTERACT FORUM
More => Old Versions => JRiver Media Center 23 for Linux => Topic started by: bob on September 08, 2017, 04:37:41 pm
-
This is the latest version of MC23 for Linux. Please post bugs here. Please start a new thread for anything requiring discussion. Non-bug posts will be deleted.
Download:
amd64 http://files.jriver.com/mediacenter/channels/v23/latest/MediaCenter-23.0.78-amd64.deb
i386 http://files.jriver.com/mediacenter/channels/v23/latest/MediaCenter-23.0.78.deb
arm http://files.jriver.com/mediacenter/channels/v23/latest/MediaCenter-23.0.78-armhf.deb
Also in the latest repo.
23.0.78 (10/24/2017)
1. Changed: Updated FFmpeg to version 3.4, used for file analysis, transcoding and video playback.
2. Fixed: 24-bit WMA files did not play properly.
23.0.72 (10/13/2017)
1. Fixed: Change windowing code to better determine when override_direct should be used. Affects window and menu drawing.
2. Changed: Changes from the main branch.
Lots of DLNA changes. Could use some feedback on these...
23.0.70 (10/6/2017)
1. Fixed: DLNA: Don't call GetMediaInfo if the controller options are set to Disable SetNext support.
2. Fixed: DLNA: Fix status calls for GetPosition which were not entirely correct in the previous build.
3. DLNA: Fixed: Options that aren't active depending on the current settings are grayed out.
5. DLNA: NEW: You can select the audio formats that are converted when "specified output format only when necessary" is selected. (under Add or configure DLNA servers .. [Server name]->Audio->Advanced)
6. Changed: DLNA: Move the detection for the ability to do SetNext into the track playback start. Saves on device calls.
7. Fixed: DLNA: Add a GetTransportState for Playback state = PLAYING before GetPosition because on some slow devices GetPosition was returning values from the previous track which caused a track skip on those devices that support SetNext.
8. Changed: DLNA: Because of #4 above, change the track status update for SetNext support to 5 seconds.
9. Changed: DLNA: when ignoring position failure, add a settling delay for the play command after sending the URI to the renderer. Helps with some slow renderers.
10. Changed: DLNA: changes to make the slider work when getposition is slow or fails.
11. Fixed: DLNA: get the fileinfo to update onscreen instantly when transitioning tracks.
12. Fixed: DLNA: change to the DLNA image slideshow push to renderer to work with MC as a renderer.
13. Changed: DLNA renderer. Ignore Stop commands while playing back images. Enables a smooth slideshow. WIP.
23.0.65 (9/29/2017)
1. Fixed: Longstanding bug in the networking code that could cause segfaults upon DLNA and MC devices going up and down on the local network.
23.0.61 (9/19/2017)
1. Fixed: The situation where a detached monitor will prevent detection of desktop size (stops popup windows from being created).
23.0.54 (9/14/2017)
1. Fixed: Removed the libunistring0 requirement.
23.0.52-2 (9/12/2017)
1. Fixed: The fix to edit boxes from 23.0.52 prevented Theater View from working.
23.0.52 (9/8/2017)
1. Fixed: Remove wait messages on message boxes. Because of the way timers work in MC linux, they were not getting displayed until the timeout.
2. Fixed: Change some edit boxes to remove the hard coded unmanaged window attribute which was making them show up across virtual desktops.
3. Changed: Internal window code changes to increase performance.
4. NEW: Implemented video window detaching.
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 (not for arm)
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. Fixed: Internal structures dealing with UI functions.
23.0.28 (7/31/2017)
1. Fixed: Some memory leaks in the registration code changes from 23.0.25. Will require re-entry of the license again.
23.0.25 (7/27/2017)
1. Fixed: Linux registration issues. Will need to re-enter the registration code.
2. Changed: Tweaking thread priorities from 23.0.21.
3. NEW: Theater View 3D rendering is anti-aliased for smoother edges. (not for arm)
23.0.21 (7/17/2017)
1. NEW: Implemented thread priorities. When running as a normal user requires system configuration to work. Falls back to non-prioritized threads if the system is not configured to allow prioritization.
2. FIXED: Memory leak in Linux thread parallelizer.
-
The AMD64 build is still building, it will be up later tonight.
-
The AMD64 build is still building, it will be up later tonight.
It's up now.
-
On Ubuntu 17.04, AMD64 version of MC 23.0.52 works for Me! ;D It does require that you re-enter your license code. Good work Bob.
-
It does require that you re-enter your license code.
Yep, because of the changes in 23.0.25 and 23.0.28 needed to prevent registration being lost at random. :P
Works good. :D
-
I can't seem to get thread priorities working on my arm setups (Raspberry Pi 3). I checked the limits.conf several ways, but the exact same entries that seem to work on my amd64 systems don't seem to work on the pi's. Are thread priorities supported on armhf?
-
The AMD64 build is still building, it will be up later tonight.
The Beta repository still has amd64 as "stretch" in the list file, might want to get that rolled back as well.
-
I can't seem to get thread priorities working on my arm setups (Raspberry Pi 3). I checked the limits.conf several ways, but the exact same entries that seem to work on my amd64 systems don't seem to work on the pi's. Are thread priorities supported on armhf?
I just tried this and it works fine.
You need the line in /etc/security/limits.conf
@audio - rtprio 100
And the user you are running as needs to be in the audio group.
grep audio /etc/group
audio:x:29:pi
and you need to reboot.
Are your settings different from this?
-
Greetings:
I got this version installed. I am still experiencing the audio issues reported earlier. Moreover Theater view displays a white screen. Other views work.
I was able to get my galaxy theme and skin to work on versions released earlier
I have to resort to this version xxx.52 after I tried to install the Stretch version via terminal. All I get was 23.0.19.
So I have to remove, including the settings three times.
Before installing this version, I wiped out the entire OS Ubuntu 17.04, started with a clean slate.
George
-
Greetings:
I got this version installed. I am still experiencing the audio issues reported earlier. Moreover Theater view displays a white screen. Other views work.
I was able to get my galaxy theme and skin to work on versions released earlier
I have to resort to this version xxx.52 after I tried to install the Stretch version via terminal. All I get was 23.0.19.
So I have to remove, including the settings three times.
Before installing this version, I wiped out the entire OS Ubuntu 17.04, started with a clean slate.
George
Verified the theater view issue. Checking into it.
-
I just tried this and it works fine.
You need the line in /etc/security/limits.conf
@audio - rtprio 100
And the user you are running as needs to be in the audio group.
grep audio /etc/group
audio:x:29:pi
and you need to reboot.
Are your settings different from this?
The only difference in my settings is that there is one additional member in the audio group (pulse). Otherwise the settings are identical and I don't see any changes in thread priorites.
-
Verified the theater view issue. Checking into it.
Any workaround for the audio. I did not have this audio issue when in 2015, I installed Ubuntu 15.10, then I installed 21.0.16, 21.0.23. We watched movies over DLNA on those tvs with great enjoyment
Thanks for your support.
George
-
A couple of thoughts off the top of my head; have you tried increased the buffer? Enabled thread priorities?
-
The only difference in my settings is that there is one additional member in the audio group (pulse). Otherwise the settings are identical and I don't see any changes in thread priorites.
On my Pi3 dev box:
ps -T -eo pid,tid,class,rtprio,ni,pri,comm | grep mediacenter23
902 902 TS - 0 19 mediacenter23
902 913 RR 46 - 86 mediacenter23
902 929 RR 43 - 83 mediacenter23
902 1056 RR 50 - 90 mediacenter23
902 1058 RR 50 - 90 mediacenter23
902 1060 RR 50 - 90 mediacenter23
902 1069 RR 50 - 90 mediacenter23
902 1091 RR 50 - 90 mediacenter23
902 1163 RR 50 - 90 mediacenter23
902 6831 RR 46 - 86 mediacenter23
902 6832 RR 50 - 90 mediacenter23
cat /proc/version
Linux version 4.9.35-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1014 SMP Fri Jun 30 14:47:43 BST 2017
On a MC22 IdPi
ps -T -eo pid,tid,class,rtprio,ni,pri,comm | grep mediacenter22
18225 18225 TS - 0 19 mediacenter22
18225 20532 RR 46 - 86 mediacenter22
18225 20541 RR 50 - 90 mediacenter22
18225 20543 RR 50 - 90 mediacenter22
18225 20545 RR 50 - 90 mediacenter22
18225 20656 RR 50 - 90 mediacenter22
18225 19167 RR 50 - 90 mediacenter22
18225 8408 RR 46 - 86 mediacenter22
18225 8409 RR 50 - 90 mediacenter22
18225 8410 RR 50 - 90 mediacenter22
18225 8411 RR 50 - 90 mediacenter22
18225 8412 RR 50 - 90 mediacenter22
18225 8413 RR 50 - 90 mediacenter22
cat /proc/version
Linux version 4.4.50-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #970 SMP Mon Feb 20 19:18:29 GMT 2017
Not sure what could be up with yours...
-
A couple of thoughts off the top of my head; have you tried increased the buffer? Enabled thread priorities?
Thread priorities is working here. At one time, I increased the buffer... I think I doubled it, but still no joy.
In windows, a slider is there, that was was I used to make the audio issue go away during the early days of MC 23. Now MC 23 for Windows issue on audio got fixed, the slider is way down at the default.
If someone can suggest adjusting the audio settings buffer to "What" size, or Mr. H. to design it similar to the Windows version, that will be fine.
Thanks for the help.
George
-
Thread priorities is working here. At one time, I increased the buffer... I think I doubled it, but still no joy.
In windows, a slider is there, that was was I used to make the audio issue go away during the early days of MC 23. Now MC 23 for Windows issue on audio got fixed, the slider is way down at the default.
If someone can suggest adjusting the audio settings buffer to "What" size, or Mr. H. to design it similar to the Windows version, that will be fine.
Thanks for the help.
George
I just don't think that's your issue.
There is nothing superior about the way that slider is done in windows.
Did you read my PM? There is a build there I'd like you to try...
-
I just don't think that's your issue.
There is nothing superior about the way that slider is done in windows.
Did you read my PM? There is a build there I'd like you to try...
No PM from you of recent.
I will check my mail again.
Thanks.
George
P/S
Just checked my mail box, nothing came in.
The slider is visual, it takes me to the max, with the Linux implementation, I have no idea what to set it for. I have tried several figures, but no luck
Note: I do not have to adjust anymore on the Windows platform.
Please resend the PM
Thanks.
George
-
No PM from you of recent.
I will check my mail again.
Thanks.
George
P/S
Just checked my mail box, nothing came in.
The slider is visual, it takes me to the max, with the Linux implementation, I have no idea what to set it for. I have tried several figures, but no luck
Note: I do not have to adjust anymore on the Windows platform.
Please resend the PM
Thanks.
George
Just resent the PM. You should get it in your email as well as in My Messages on the forum.
-
On my Pi3 dev box:
ps -T -eo pid,tid,class,rtprio,ni,pri,comm | grep mediacenter23
902 902 TS - 0 19 mediacenter23
902 913 RR 46 - 86 mediacenter23
902 929 RR 43 - 83 mediacenter23
902 1056 RR 50 - 90 mediacenter23
902 1058 RR 50 - 90 mediacenter23
902 1060 RR 50 - 90 mediacenter23
902 1069 RR 50 - 90 mediacenter23
902 1091 RR 50 - 90 mediacenter23
902 1163 RR 50 - 90 mediacenter23
902 6831 RR 46 - 86 mediacenter23
902 6832 RR 50 - 90 mediacenter23
cat /proc/version
Linux version 4.9.35-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1014 SMP Fri Jun 30 14:47:43 BST 2017
On a MC22 IdPi
ps -T -eo pid,tid,class,rtprio,ni,pri,comm | grep mediacenter22
18225 18225 TS - 0 19 mediacenter22
18225 20532 RR 46 - 86 mediacenter22
18225 20541 RR 50 - 90 mediacenter22
18225 20543 RR 50 - 90 mediacenter22
18225 20545 RR 50 - 90 mediacenter22
18225 20656 RR 50 - 90 mediacenter22
18225 19167 RR 50 - 90 mediacenter22
18225 8408 RR 46 - 86 mediacenter22
18225 8409 RR 50 - 90 mediacenter22
18225 8410 RR 50 - 90 mediacenter22
18225 8411 RR 50 - 90 mediacenter22
18225 8412 RR 50 - 90 mediacenter22
18225 8413 RR 50 - 90 mediacenter22
cat /proc/version
Linux version 4.4.50-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #970 SMP Mon Feb 20 19:18:29 GMT 2017
Not sure what could be up with yours...
Here are my results, they look similar to yours except the thread priorities are not working:
ps -T -eo pid,tid,class,rtprio,ni,pri,comm | grep mediacenter23
1713 1713 TS - 0 19 mediacenter23
1713 2360 TS - 0 19 mediacenter23
1713 2368 TS - 0 19 mediacenter23
1713 2372 TS - 0 19 mediacenter23
1713 2400 TS - 0 19 mediacenter23
cat /proc/version
Linux version 4.9.37-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1017 SMP Thu Jul 13 11:26:04 BST 2017
cat /etc/security/limits.conf
pi - rtprio 100
@audio - rtprio 100
grep audio /etc/group
audio:x:29:pi,pulse
On a default raspbian install there were some other files in limits.d under /etc/security which also affected audio priority, but I blew those away. No change. Not sure what my next step is. This is more or less just a default fullfat raspbian install with minor changes to get MC running.
-
Hmmmm, 23.0.52-2 is instant segfaulting on Arch Linux today. I'll mess with it later - I'm going to guess a lib upstream updated yesterday is causing it, we'll see.
-
I'd be interested to hear what the fix is. Might be why I'm getting an immediate segment fault on the Rock64 board running the .052 armhf build (after multiarch support added). Waiting for advice from the Pine64.org folks regarding how to image the tweaked build before I've added any multiarch/MediaCenter23 before I make another attempt at getting MC23 installed. Trying to save time by having a working "base" build saved before testing again.
Was anyone seeing an immediate segmentation fault on previous builds? I still swear that I got MediaCenter running, maybe the .041 build but I could be wrong.
I can confirm that the browser connection to a MediaCenter23 library works when accessing it from the Rock64 board running Debian Stretch arm64). The volume increase/decrease buttons don't work but I think that's a setting on the main library that I've seen before. Next track, previous track, start/stop, playlist selection works. Thanks.
-
23.0.52-2 fixes one issue;
1. Fixed: The fix to edit boxes from 23.0.52 prevented Theater View from working.
I'll try downgrading back down to 23.0.52 to see if it works again and report back.
EDIT: Yep, downgrading fixes it.
-
Hmmmm, 23.0.52-2 is instant segfaulting on Arch Linux today
The same in Debian Buster:
MC 23.052.2 has just been installed. As well as in KDE and in XFCE, starting MC causes a memory access error.
- System: Host: sparkyxfce Kernel: 4.12.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: SparkyLinux 5 (Nibiru)
Machine: Device: desktop Mobo: ASRock model: 970 Performance/3.1 serial: N/A
UEFI [Legacy]: American Megatrends v: P1.10 date: 01/26/2016
CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB
clock speeds: max: 3500 MHz 1: 1400 MHz 2: 1400 MHz 3: 2000 MHz 4: 2000 MHz 5: 1400 MHz 6: 1400 MHz
Graphics: Card: NVIDIA GM107 [GeForce GTX 750 Ti]
Display Server: x11 (X.Org 1.19.3 ) driver: nvidia Resolution: 2560x1600@59.86hz
OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 version: 4.5.0 NVIDIA 375.82
Audio: Card-1 NVIDIA Device 0fbc driver: snd_hda_intel Sound: ALSA v: k4.12.0-1-amd64
Card-2 TEAC driver: USB Audio
Edit:
I have now downgrading to 23.052, which works well
Here is the Protocol (strace) and systemd:
-
It's strange, 23.0.52-2 does work fine in Ubuntu 17.10 still - no segfaults in sight. But if I install it on Arch, instant segfaults.
But yeah, it's okay, I'm sure Bob will nail it in the end. ;)
-
Do you guys have libunistring installed?
-
I thought I avoided that dependency when building the security libraries.
-
I thought I avoided that dependency when building the security libraries.
That's what his strace shows missing.
It's trivial to include it in the package dependencies.
-
Maybe it slipped in during one of the recent builds for stretch and back to jessie. I kind of hate how libraries get linked or not linked depending on whats installed on the system, instead of explicitly having you enable or disable it.
I suppose its somewhat of a default library, but we could as well exclude it again if its causing issues.
-
Maybe it slipped in during one of the recent builds for stretch and back to jessie. I kind of hate how libraries get linked or not linked depending on whats installed on the system, instead of explicitly having you enable or disable it.
I suppose its somewhat of a default library, but we could as well exclude it again if its causing issues.
It's gnutls, I'm fixing it.
-
Looks like its libidn2, at least from those libs in the repo. gnutls had it specifically disabled in the script, this one apparently not.
-
Do you guys have libunistring installed?
dpkg -l libunistring*
ii libunistring2:amd64 0.9.7-2 amd64 Unicode string library for C
~$ dpkg -l libidn2*
ii libidn2-0:amd64 2.0.2-3 amd64 Internationalized domain names (IDNA2008/TR46) library
dpkg -l gnutls*
un gnutls-bin <keine> <keine> (keine Beschreibung vorhanden)
un gnutls0 <keine> <keine> (keine Beschreibung vorhanden)
un gnutls0.4 <keine> <keine> (keine Beschreibung vorhanden)
un gnutls3 <keine> <keine> (keine Beschreibung vorhanden)
-
Looks like its libidn2, at least from those libs in the repo. gnutls had it specifically disabled in the script, this one apparently not.
I know.
I rebuilt libidn2 without libunistring-dev on the system to solve it.
It can't be excluded with a switch on the configure in libidn2.
-
It can't be excluded with a switch on the configure in libidn2.
Someone should slap those people. :)
-
dpkg -l libunistring*
ii libunistring2:amd64 0.9.7-2 amd64 Unicode string library for C
~$ dpkg -l libidn2*
ii libidn2-0:amd64 2.0.2-3 amd64 Internationalized domain names (IDNA2008/TR46) library
dpkg -l gnutls*
un gnutls-bin <keine> <keine> (keine Beschreibung vorhanden)
un gnutls0 <keine> <keine> (keine Beschreibung vorhanden)
un gnutls0.4 <keine> <keine> (keine Beschreibung vorhanden)
un gnutls3 <keine> <keine> (keine Beschreibung vorhanden)
I should have said do you have libunistring0 installed.
You do not.
The next build removes that requirement.
-
This is the latest version of MC23 for Linux. Please post bugs here. Please start a new thread for anything requiring discussion. Non-bug posts will be deleted.
Download:
amd64 http://files.jriver.com/mediacenter/channels/v23/latest/MediaCenter-23.0.54-amd64.deb
i386 http://files.jriver.com/mediacenter/channels/v23/latest/MediaCenter-23.0.52-2.deb
arm http://files.jriver.com/mediacenter/channels/v23/latest/MediaCenter-23.0.52-armhf.deb
Also in the latest repo.
23.0.54 (9/14/2017)
1. Fixed: Removed the libunistring requirement introduced in 23.0.52-2.
23.0.52-2 (9/12/2017)
1. Fixed: The fix to edit boxes from 23.0.52 prevented Theater View from working.
23.0.52 (9/8/2017)
1. Fixed: Remove wait messages on message boxes. Because of the way timers work in MC linux, they were not getting displayed until the timeout.
2. Fixed: Change some edit boxes to remove the hard coded unmanaged window attribute which was making them show up across virtual desktops.
3. Changed: Internal window code changes to increase performance.
4. NEW: Implemented video window detaching.
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 (not for arm)
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. Fixed: Internal structures dealing with UI functions.
23.0.28 (7/31/2017)
1. Fixed: Some memory leaks in the registration code changes from 23.0.25. Will require re-entry of the license again.
23.0.25 (7/27/2017)
1. Fixed: Linux registration issues. Will need to re-enter the registration code.
2. Changed: Tweaking thread priorities from 23.0.21.
3. NEW: Theater View 3D rendering is anti-aliased for smoother edges. (not for arm)
23.0.21 (7/17/2017)
1. NEW: Implemented thread priorities. When running as a normal user requires system configuration to work. Falls back to non-prioritized threads if the system is not configured to allow prioritization.
2. FIXED: Memory leak in Linux thread parallelizer.
-
Removed the libunistring0 requirement (amd64 so far).
Give it a try.
-
23.0.54 has indeed fixed it on Arch Linux. Thanks. :)
-
Super -it works- Thanks ;D
I should have said do you have libunistring0 installed.
You do not.The next build removes that requirement.
libunistring0 is not available in Debian Buster
-
Finally got Wayland working with Ubuntu 17.10 and Nouveau... and MC23 works fine (make sure xwayland is installed!). :D
-
Please note I am a new Debian 9 user. I just installed the system and trying out JRiver. Please point out if any of my points below are user errors.
- Searching or tagging (either directly or via the tagging panel) doesn't work very well for me at all. I need to double click the search bar in order to search. On windows it's just one click. The search results are shown with more lag than on Windows. When typing text, it frequently jumps out of the input / edit for now reason, or stops registering keyboard presses. This seems to happen at random times, but usually when the program just suggested something just below the input field. The input then loses focus. I get this a lot this with the '-' and 'Z' character. When copy / pasting text into the new tagging window, MC crashed.
- I am fixing some broken links after moving from Windows to Linux. I need to delete a song twice before it removes the song. The first time 'round, it blinks and the song I just removed is still there. After the second time it's finally gone. Edit: it seems like JRiver does delete it the first time around after all, the lag is just very long before it updates the screen.
- Mouse clicks sometimes don't quite register. It sometimes takes more than one click before the program responds.
- The program is frequently not able to keep up with the mouse cursor position. The mouse over effect lags quite a bit.
- Changing audio views is not quite as snappy as it is on Windows. There's a noticeable lag.
- When the option window is on top of the genres view (list style: thumbnails), the main window below it still responds to mouse overs, even though the cursor is being moved inside the option window.
I don't understand why JRiver is so laggy on Linux on the very same hardware. I must be doing something wrong here.
-
Edit: merged with post above.
-
Greetings:
I am not able to import my ripped mkv movies with this build.
I do not know if import is broken.
Thanks.
George
-
Please note I am a new Debian 9 user. I just installed the system and trying out JRiver. Please point out if any of my points below are user errors.
- Searching or tagging (either directly or via the tagging panel) doesn't work very well for me at all. I need to double click the search bar in order to search. On windows it's just one click. The search results are shown with more lag than on Windows. When typing text, it frequently jumps out of the input / edit for now reason, or stops registering keyboard presses. This seems to happen at random times, but usually when the program just suggested something just below the input field. The input then loses focus. I get this a lot this with the '-' and 'Z' character. When copy / pasting text into the new tagging window, MC crashed.
- I am fixing some broken links after moving from Windows to Linux. I need to delete a song twice before it removes the song. The first time 'round, it blinks and the song I just removed is still there. After the second time it's finally gone. Edit: it seems like JRiver does delete it the first time around after all, the lag is just very long before it updates the screen.
- Mouse clicks sometimes don't quite register. It sometimes takes more than one click before the program responds.
- The program is frequently not able to keep up with the mouse cursor position. The mouse over effect lags quite a bit.
- Changing audio views is not quite as snappy as it is on Windows. There's a noticeable lag.
- When the option window is on top of the genres view (list style: thumbnails), the main window below it still responds to mouse overs, even though the cursor is being moved inside the option window.
I don't understand why JRiver is so laggy on Linux on the very same hardware. I must be doing something wrong here.
Sounds like you are running with the Nouveau video driver.
Try doing this from a prompt:
glxinfo | grep -i vendor
Report back the results.
If you get "unable to locate package glxinfo" do
sudo apt-get install mesa-utils
and try again.
-
Hi Bob,
Thank you for your advice. This the output of the CLI:
glxinfo | grep -i vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: X.Org (0x1002)
OpenGL vendor string: X.Org
I have the following installed:
- mesa-utils
- xserver-xorg-video-nouveau
- also a large number of the - xserver-xorg-video- packages.
I do not have mesa-utils-extra installed.
-
Hi Bob,
Thank you for your advice. This the output of the CLI:
glxinfo | grep -i vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: X.Org (0x1002)
OpenGL vendor string: X.Org
I have the following installed:
- mesa-utils
- xserver-xorg-video-nouveau
- also a large number of the - xserver-xorg-video- packages.
I do not have mesa-utils-extra installed.
OK thanks. How about:
lspci | grep VGA
-
OK thanks. How about:
lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
It's not the sharpest tool in the shed. But it gets the 1080P job done without a fan and drives both DVI and HDMI ports.
If an upgrade or another card will fix the problem, I am willing to think about it. On Windows JRiver ran fine. On my Mac, it is also running great. Mind you, Linux itself runs perfectly. And so do all the other applications I've used so far.
I understand Debian is not the best distro for a media pc and AMD hardware. Is it possible to try Mint instead? JRiver is my main application.
Is it worth a shot trying proprietary drivers?
-
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
It's not the sharpest tool in the shed. But it gets the 1080P job done without a fan and drives both DVI and HDMI ports.
If an upgrade or another card will fix the problem, I am willing to think about it. On Windows JRiver ran fine. On my Mac, it is also running great. Mind you, Linux itself runs perfectly. And so do all the other applications I've used so far.
I understand Debian is not the best distro for a media pc and AMD hardware. Is it possible to try Mint instead? JRiver is my main application.
Seems like that should work. I'm not sure what going on..
It might pay to do a bit of searching to see if there are specific things you need to do to get accelerated video out of your card.
Also what desktop are you using?
-
Hi Bob,
I am using the KDE desktop. I tried the instructions on https://linuxconfig.org/how-to-install-amdgpu-drivers-on-debian-9-stretch-linux but it doesn't help. Do you think another distro or desktop might help? I am willing to try it on another hard drive.
-
I think you need radeon instead of amdgpu for that card.
-
Installed this version, again, my mkv rips not working.
Same issue with version 23.0.62.
The last version that worked with import was 23.0.61.
I have copied my files to different drive, still no luck. I have import rules to watch the folders.
Food for thoughts:
On another note regarding DLNA:
The audio issue still there, now I noticed the videos will just drag on.
Well to do more testing, I found some mkv ripped from DVD... Gloria Estephan Unwrapped, Janet Jackson Velvet Rope Tours, Yanni.. Live at the Acropolis, all these concerts dvd that do not have 1080P resolution played fine with no issues. It is the 1080P/3D mkvs that have issues.
Thanks.
George
-
Hi Bob,
I have a problem getting my blue tooth headset to work. Version 22 and 23.0.65 running at the same machine (SUSE Leap42.3) but bt-headset is only working with version 22. The device setup between both versions is identical.
Version 22 switches over to headset playback after synchronization and back to speaker, after the headset is turned of, version 23 only uses the speaker. Restarting playback etc. does not solve the problem.
Same issue with 23.0.70. 22.0.108 is working fine
Note: 1909959 -> ver 22; 191020 -> ver 23.
-
?Bug? When MC has only one zone, the zonename property is not showing up in the Playback/Info MCWS results. Multi-zone MC servers are showing zonename.
Haven't tested windows and have gone back two versions (.61,56). I found this by accident when attempting to use just the Playback/Info cmd to produce a zone list.
-
Installed this version, again, my mkv rips not working.
Same issue with version 23.0.62.
The last version that worked with import was 23.0.61.
I have copied my files to different drive, still no luck. I have import rules to watch the folders.
I had no trouble importing your mkv's with the current build.
Just had a thought, check the permissions and libraries on JRWorker.
From a prompt (use your user, NOT ROOT):
ls -l /usr/lib/jriver/Media\ Center\ 23/JRworkerand
ldd -d /usr/lib/jriver/Media\ Center\ 23/JRWorker
also, does this machine have a working connection to the internet?
It needs to be able to download components to parse the video.
Do this also:
ls -lR ~/.jriver/Media\ Center\ 23/Plugins/
Food for thoughts:
On another note regarding DLNA:
The audio issue still there, now I noticed the videos will just drag on.
Well to do more testing, I found some mkv ripped from DVD... Gloria Estephan Unwrapped, Janet Jackson Velvet Rope Tours, Yanni.. Live at the Acropolis, all these concerts dvd that do not have 1080P resolution played fine with no issues. It is the 1080P/3D mkvs that have issues.
Thanks.
George
Twice as much bandwidth for the 3d. The audio buffering settings have no effect when playing to DLNA renderers (this is true for Windows as well). I was confused because I thought the playback issue was on the local Linux machine. I assume that works fine.
-
I had no trouble importing your mkv's with the current build.
Just had a thought, check the permissions and libraries on JRWorker.
From a prompt (use your user, NOT ROOT):
ls -l /usr/lib/jriver/Media\ Center\ 23/JRWorkerand
ldd -d /usr/lib/jriver/Media\ Center\ 23/JRWorker
also, does this machine have a working connection to the internet?
It needs to be able to download components to parse the video.
Do this also:
ls -lR ~/.jriver/Media\ Center\ 23/Plugins/Twice as much bandwidth for the 3d. The audio buffering settings have no effect when playing to DLNA renderers (this is true for Windows as well). I was confused because I thought the playback issue was on the local Linux machine. I assume that works fine.
The Playback issues are on the Linux server acting as a server and clients smart tvs trying to play from the server.
My setup has never used local playback on those smart tvs.
How far did you go with the mkvs on smart tvs/DLNA?
I used another user to log in, and tried to ls the JRworker.
All codes resulted in No such file or directory.
Then I tried to log in as normal root, one commands, the first one responds no such file or directory, The second command responded with a bunch of words on the screen and the the thrid listed Lame, libv.... looks like the codecx.
For the first time on the Linux server, I tried to watch a 3D movie over the network. Just testing how the Nvidia gpu will react to it. For 8 minutes, Avatar 5D played in its glory, but with same audio skimpping and jumping.
I expect the audio issue, but it was my curiosity regarding how 3D will play, since no one ever mentioned 3D compatibility for the Linux, but for the Windows platform, we see it from the Madvr settings.
I will suggest on vol 6 area, Alien- Covenant, Assassin's creed, 3.10 to Yuma, Wonder Woman to test.
In concerts- Bee Gees, Lionel Richie and Celine Dion - A new Day.
I have enough bandwidth. I am connected to the internet.
If I can not get the import issue resolved, I will just wipe out MC 23, settings and config files and start all over.
Thanks
George
-
The Playback issues are on the Linux server acting as a server and clients smart tvs trying to play from the server.
My setup has never used local playback on those smart tvs.
How far did you go with the mkvs on smart tvs/DLNA?
I used another user to log in, and tried to ls the JRworker.
All codes resulted in No such file or directory.
Then I tried to log in as normal root, one commands, the first one responds no such fil or directory, The second command responded with a bunch of words on the screen and the the thrid listed Lame, libv.... looks like the codecx.
For the first time on the Linux server, I tried to watch a 3D movie over the network. Just testing how the Nvidia gpu will react to it. For 8 minutes, Avatar 5D played in its glory, but with same audio skimpping and jumping.
I expect the audio issue, but it was my curiosity regarding how 3D will play, since no one ever mentioned 3D compatibility for the Linux, but for the Windows platform, we see it from the Madvr settings.
I will suggest on vol 6 area, Alien- Covenant, Assassin's creed, 3.10 to Yuma, Wonder Woman to test.
In concerts- Bee Gees, Lionel Richie and Celine Dion - A new Day.
I have enough bandwidth. I am connected to the internet.
If I can not get the import issue resolved, I will just wipe out MC 23, settings and config files and start all over.
Thanks
George
I will try those.
Can you do the ls -l and ldd commands above again?
I made a case error in the first. They are case sensitive.
-
The Playback issues are on the Linux server acting as a server and clients smart tvs trying to play from the server.
My setup has never used local playback on those smart tvs.
How far did you go with the mkvs on smart tvs/DLNA?
I used another user to log in, and tried to ls the JRworker.
All codes resulted in No such file or directory.
Then I tried to log in as normal root, one commands, the first one responds no such file or directory, The second command responded with a bunch of words on the screen and the the thrid listed Lame, libv.... looks like the codecx.
For the first time on the Linux server, I tried to watch a 3D movie over the network. Just testing how the Nvidia gpu will react to it. For 8 minutes, Avatar 5D played in its glory, but with same audio skimpping and jumping.
I expect the audio issue, but it was my curiosity regarding how 3D will play, since no one ever mentioned 3D compatibility for the Linux, but for the Windows platform, we see it from the Madvr settings.
I will suggest on vol 6 area, Alien- Covenant, Assassin's creed, 3.10 to Yuma, Wonder Woman to test.
In concerts- Bee Gees, Lionel Richie and Celine Dion - A new Day.
I have enough bandwidth. I am connected to the internet.
If I can not get the import issue resolved, I will just wipe out MC 23, settings and config files and start all over.
Thanks
George
Response to 1st command:tester@elitelinux:~$ ls -l /usr/lib/jriver/Media\ Center\ 23/JRWorker
-rwxr-xr-x 1 root root 2909248 Sep 29 16:35 /usr/lib/jriver/Media Center 23/JRWorker
Response to second command:
x.so.1.59.0 (0x00007faea59f9000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007faea56be000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007faea54b9000)
libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007faea52ae000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007faea4f26000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007faea4c1d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007faea4a06000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faea463d000)
/lib64/ld-linux-x86-64.so.2 (0x000056141c475000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007faea441b000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007faea4209000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007faea3fff000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007faea3dfb000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007faea3bf3000)
Response to third command:
ls -lR ~/.jriver/Media\ Center\ 23/Plugins/
ls: cannot access '/home/tester/.jriver/Media Center 23/Plugins/': No such file or directory
If I log in with Root, I get the codex like lame etc.
Thanks.
George
-
When using TAG the autocomplete function (which presents suggestions when editing) causes all typing in the entry field to stop until you click back in the entry field or select one of the suggestions. This can be tedious if what you are trying to type is not on the suggestion dropdown list. Using Ubuntu 17.04 and MC 23.0.65
-
Response to 1st command:tester@elitelinux:~$ ls -l /usr/lib/jriver/Media\ Center\ 23/JRWorker
-rwxr-xr-x 1 root root 2909248 Sep 29 16:35 /usr/lib/jriver/Media Center 23/JRWorker
Response to second command:
x.so.1.59.0 (0x00007faea59f9000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007faea56be000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007faea54b9000)
libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007faea52ae000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007faea4f26000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007faea4c1d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007faea4a06000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faea463d000)
/lib64/ld-linux-x86-64.so.2 (0x000056141c475000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007faea441b000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007faea4209000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007faea3fff000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007faea3dfb000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007faea3bf3000)
Response to third command:
ls -lR ~/.jriver/Media\ Center\ 23/Plugins/
ls: cannot access '/home/tester/.jriver/Media Center 23/Plugins/': No such file or directory
If I log in with Root, I get the codex like lame etc.
Thanks.
George
Sounds like you might have an ownership/permissions issue.
This can happen if you run MC with sudo. MC should always run a user, not with root permissions.
You can try this to fix it:
As the MC user (in the case above your user is tester), with MC not running, do this...
chown -R tester ~/.jriver
This should run with no errors. If you get an error do:
sudo chown -R tester ~/.jriver
Report your results please.
-
When using TAG the autocomplete function (which presents suggestions when editing) causes all typing in the entry field to stop until you click back in the entry field or select one of the suggestions. This can be tedious if what you are trying to type is not on the suggestion dropdown list. Using Ubuntu 17.04 and MC 23.0.65
Do you know if that is specific to the Linux build?
-
Do you know if that is specific to the Linux build?
Yes it's specific to the Linux build. Windows does not lose focus on the entry field like Linux does when an autocomplete suggestion appears.
-
Sounds like you might have an ownership/permissions issue.
This can happen if you run MC with sudo. MC should always run a user, not with root permissions.
You can try this to fix it:
As the MC user (in the case above your user is tester), with MC not running, do this...
chown -R tester ~/.jriver
This should run with no errors. If you get an error do:
sudo chown -R tester ~/.jriver
Report your results please.
Greetings:
My bad for not loading MC as non Root. I have done MC loading as non Root before, but due to the fact that I have re-installed Ubuntu and MC several times, I forgot about setting up a non Root account.
Thanks for reminding me.
Your code worked with no errors, but still will not let me import my 10 mkv rips, even when I copied or moved them to different drives.
So I just "Cleared out" the entire database, got my Windows backup zip of 07/17/2017, restored only the settings.
Then I re-ripped all new 10 BDs, just to be sure those got in.
The rips got imported, then I set up the folders to watch for. All 1500* rips are present in a fresh database.
I think the database was corrupt.
In any way The imports work very well now..
Thanks Thanks Thanks.
George
-
Lots of DLNA changes. Could use some feedback on these...
-
Also, hopefully video playback didn't break (much).
-
Lots of DLNA changes. Could use some feedback on these...
Thanks for looking at this audio issues.
I set up three different settings Generic, Sony, and Samsung each different from the other using conversion or not to convert.
The screen is not as sluggish as it used to.
The audio is still dragging especially at the opening logo and this also affects the video sluggish a bit. The audio still breaks, pulsating/jumping on all three settings.
Now, here is a sort of new info.
In the past year, MC 32 bit Windows, I have a Sony HDR.camp mkv demo and Panasonic GHA Lumix demo. These demos play , sound not distorted, but the only commonality in terms of problem is the stop and go video, but the 4K pictures are gorgeous.
When 64 bit MC was introduced, I also tested these demos, same pause and go. No different between between 64 bit and 32 bit .
On the Ubuntu 64 bit, it is not as good in terms of audio being reproduced.
I just wanted to mention this. The mkvs now have Dolby Atmos, Dts X and all the modern 3D audio , maybe maybe this is where the issues are.
Also, the write up on MC 23.0.70 mentions the slider... <grin>.
I see no slider. It is still same interface as before.
In the past, attempts were made or suggestions made for me to insert different values in the Audio - buffering field.
I tried maybe 20 different combination of numbers, with no success. Too bad the windows version does not have numeric values, if it does, I would have used the values there to test.
I know something must been affecting the audio in video .
Also, What have you noticed in terms of playback on those sample mkvs?
Can you please throw in some values to see if it will make any difference?
Can Lav filter be integrated for testing purpose?
I will continue to play with settings over the week end.
Thanks.
George
-
Also, hopefully video playback didn't break (much).
Video playback is slightly faster when it does not pulsate. Video quality, is better, I noticed. It looks like 3D with an attitude <grin>.
What part is LAV filter playing on this.
Lav as far as I read about will play 4k and handle audio very well.
Can it be integrated for testing?
The windows counterpart has Option- General- Video choice of video card in here, We do not have this under Linus.
All these little differences may contribute to Linux platform playing well or not under DLNA. <grin>
This is my humble opinion.
Thanks.
George
-
What part is LAV filter playing on this.
Likely none, because the LAV Filters are Windows-only. Same with madVR and other DirectShow filters too.
-
Still having the problem changing a TAG field with focus jumping to autocomplete and requiring a click into the field to continue entering text. This happens every time the autocomplete window pops up. Also new to 23.0.70 the field labels have moved to the right side of the pane leaving space on the left. See screenshot. None of these behaviors in the Windows version. I am using Ubuntu 17.0.4
-
Likely none, because the LAV Filters are Windows-only. Same with madVR and other DirectShow filters too.
...and he's using DLNA so MC is mostly out of the loop. No video or audio options he can set or change will make any difference, other than transcoding.
Brian.
-
Likely none, because the LAV Filters are Windows-only. Same with madVR and other DirectShow filters too.
Greetings:
Maybe I did not elaborate on the Lav Filter that I wrote about.
What I meant was Mr. H in Germany should try to inject some Lav codes or features in to MC to make it more flexible with DLNA use.
With UHD ripping coming soon, and customers would want to play uhd over the network, and these customers looking at MC, they are going to be disappointed.
The 64 bit Windows version played these movies smoothly. Last Night we watched Wonder Woman, and Pirates of Caribbean Dead men tell no tales (mkv) over DLNA, no issues at all.
And this A.M , wife listened to Gloria Estephan Live in Miami, Gloria Estephan Unwrapped, no issues.b ut these are DVD mkvs, not Blu rays <grin>
My point is, it is the Blu ray 1080P rips that have issues with audio skippy, jumping etc.
Thanks.
George
-
Hi Bob,
I have a problem getting my blue tooth headset to work. Version 22 and 23.0.65 running at the same machine (SUSE Leap42.3) but bt-headset is only working with version 22. The device setup between both versions is identical.
Version 22 switches over to headset playback after synchronization and back to speaker, after the headset is turned of, version 23 only uses the speaker. Restarting playback etc. does not solve the problem.
Same issue with 23.0.70. 22.0.108 is working fine
Note: 1909959 -> ver 22; 191020 -> ver 23.
-
Greetings:
These are observations with 1080P Blu rays mkvs.
Over the weekend, I have had a chance to test various mkvs with the 23.0.70 build. I spent average of 10 minutes loading these movies and watched the videos and listened to the audio.
50 first Dates, Above the law, Absolute power. These three movies exhibited minor audio jumping at the initial start up, but played for over ten minutes without any noticeable audio glitch or video slowing down.
300, 300 Rise of an Empire. These movies do have intensive graphics and action packed. At initial startup, movies had audio jumping, and video was a bit sluggish. I almost gave up at the three minutes mark, then I noticed the video at one point was very smooth, then later it started to craw- a sort of pausing and continue. At one point the audio was very clear, almost perfect.
Belle, Pirate of the Caribbean Dead Men Tell no Tales, Wonder Woman.. Audio was jumpy, video would freeze a bit and continues to smooth out.Overall audio was clear as a whistle for some areas, then get jumpy again. It looks like video playback need something to push it to the next frame.
3 Days to kill. 3:10 to Yuma, 12 Years a Slave, Assassin Creed, Alien Convenant Audio get jerky, jumpy video freezes almost at the point where the movies start. With Alien Convenant, you could see the video splitting, it looks like the head of Michael Fassbender was being separated from his neck.
DVD mkvs.
Janet Jackson Live in Hawaii, Velvet Rope Tours, Gloria Estephan Live in Atlantis, Live in Miami, Yanni Live in Acropolis- All Concerts played well, audio was clean as a whistle, no video breaking.
End of report.
Now MC 23.0.70, the installer reported it is MC 23.0.65, but it did installed ok, I check Help- About it reported it is 23.0.70.
On the description of this build, Where is "setnext"?
In Prior versions of MC 32 bit, I used to find the setNext.. transport options, on AMD64, i can not locate it.
Also slider was mentioned, I did not see a slider in Audio- Buffering.
Thanks.
George
-
George when you are playing to a DLNA device, the ONLY settings in MC that make any difference are the ones in the DLNA server settings in MC.
The differences between the Generic, Sony and Samsung templates mostly come down to under what situation transcoding is being used.
The only other difference between windows and linux in this area is the code used to move the data over the network.
Windows uses the windows networking stack and linux uses cURL (a generic library for network data transfer).
If your device supports the formats you are sending it, it's always best to use "original format" for the Video configuration in MC's DLNA server.
-
Hi Bob,
I have a problem getting my blue tooth headset to work. Version 22 and 23.0.65 running at the same machine (SUSE Leap42.3) but bt-headset is only working with version 22. The device setup between both versions is identical.
Version 22 switches over to headset playback after synchronization and back to speaker, after the headset is turned of, version 23 only uses the speaker. Restarting playback etc. does not solve the problem.
Same issue with 23.0.70. 22.0.108 is working fine
Note: 1909959 -> ver 22; 191020 -> ver 23.
Since that code hasn't changed between 22 and 23 there still is likely something different between in the settings between your MC22 and MC23.
I'd check the format setting under Tools->Options->Audio->Device Settings
and also the DSP studio settings.
-
Still having the problem changing a TAG field with focus jumping to autocomplete and requiring a click into the field to continue entering text. This happens every time the autocomplete window pops up. Also new to 23.0.70 the field labels have moved to the right side of the pane leaving space on the left. See screenshot. None of these behaviors in the Windows version. I am using Ubuntu 17.0.4
You can resize the tag window to eliminate the blank space. It does appear the auto field width is somewhat off.
Can't duplicate the autocomplete behavior in Debian XFCE. I suspect your window manager is setup with some focus stealing tweaks or some such. You'll need to do some investigation on that.
-
You can resize the tag window to eliminate the blank space. It does appear the auto field width is somewhat off.
Can't duplicate the autocomplete behavior in Debian XFCE. I suspect your window manager is setup with some focus stealing tweaks or some such. You'll need to do some investigation on that.
Resizing the tag window pushes the data off the right (see attached). BTW this is new behavior as of 23.0.70. Not sure what tweaks I neeed to do to fix the autocomplete focus issue. FWIW this is a virgin install of Ubuntu 17.0.4 so it would affect anyone installing that flavor. BTW thanks for the help and gudeance this is a great forum!
-
Resizing the tag window pushes the data off the right (see attached). BTW this is new behavior as of 23.0.70. Not sure what tweaks I need to do to fix the autocomplete focus issue. FWIW this is a virgin install of Ubuntu 17.0.4 so it would affect anyone installing that flavor. BTW thanks for the help and guidance this is a great forum!
Click between the field name and the tag value and you should get a divider you can move to change the field name width.
-
Click between the field name and the tag value and you should get a divider you can move to change the field name width.
Yes of course! Thanks for that. Strangely not a feature on the Windows version...
-
Running .70 Linux arm MC23 version. Connected to main library on another home computer. Can play from the library but the info in top display shows 320 bit rate on all songs. Thought I'd set everything to no conversion. No mp3s in the library, only flac files.
Others seen this in the linux build or is it a setting I missed? Thanks.
-
Solved - had changed settings on the main library to not convert remote library files. Hadn't set it on the client side. Changed the defaults and now the display shows the correct bitrate.
-
George when you are playing to a DLNA device, the ONLY settings in MC that make any difference are the ones in the DLNA server settings in MC.
The differences between the Generic, Sony and Samsung templates mostly come down to under what situation transcoding is being used.
The only other difference between windows and linux in this area is the code used to move the data over the network.
Windows uses the windows networking stack and linux uses cURL (a generic library for network data transfer).
If your device supports the formats you are sending it, it's always best to use "original format" for the Video configuration in MC's DLNA server.
Yes, I already figured these differences. What I did not know is the networking stack used by Windows, and the Linux cURL.
Thanks for the Network 101 education <grin>.
The main reason I started with Linux, was because MC was only available in 32 bit, then suddenly JR slapped us with a much anticipated 64 bit. No need shutting down the Windows server any longer.
With the Windows and Linux server running now, I am learning a lot between the two operating systems.
btw..
I have a desktop server that I had used for Windows 7 in the past. It is a special case Origen ST 21 with built-in 1080P screen. The build it 95% complete, except I need more Hard Drives, and the latest Nvidia GPU. It has 24 gig of memory.
I am planning to install Fedora 64 bit? Just to give me another exposure to a different distro.
Do you agree with using Fedora, or just stay with Ubuntu?. If Fedora, is it going to be same Jessie AMD64?
Thanks.
George
-
Since that code hasn't changed between 22 and 23 there still is likely something different between in the settings between your MC22 and MC23.
I'd check the format setting under Tools->Options->Audio->Device Settings
and also the DSP studio settings.
Hi Bob,
thanks for the reply.
I checked the configurations, but I couldn't find an difference. So, I swapped the "User Settings.ini" and the "Machine Settings.ini", but the problem still stays with the 23.xx version. The 22.xx version is running the headset also with the 23. ini files applied.
However, if you run the same source code, the must be a difference in how you pass the data to alsa. Both version running at the same machine, same configuration.
I run both versions simultaneously on speaker, when I connect to the headphone, MC22 switched over to bt-headphone, MC23 continued to use the speaker.
-
Hi Bob,
thanks for the reply.
I checked the configurations, but I couldn't find an difference. So, I swapped the "User Settings.ini" and the "Machine Settings.ini", but the problem still stays with the 23.xx version. The 22.xx version is running the headset also with the 23. ini files applied.
However, if you run the same source code, the must be a difference in how you pass the data to alsa. Both version running at the same machine, same configuration.
I run both versions simultaneously on speaker, when I connect to the headphone, MC22 switched over to bt-headphone, MC23 continued to use the speaker.
Interesting.
They were both compiled on wheezy as well.
Are you running with the thread priorities enabled??
-
Yes, I already figured these differences. What I did not know is the networking stack used by Windows, and the Linux cURL.
Thanks for the Network 101 education <grin>.
The main reason I started with Linux, was because MC was only available in 32 bit, then suddenly JR slapped us with a much anticipated 64 bit. No need shutting down the Windows server any longer.
With the Windows and Linux server running now, I am learning a lot between the two operating systems.
btw..
I have a desktop server that I had used for Windows 7 in the past. It is a special case Origen ST 21 with built-in 1080P screen. The build it 95% complete, except I need more Hard Drives, and the latest Nvidia GPU. It has 24 gig of memory.
I am planning to install Fedora 64 bit? Just to give me another exposure to a different distro.
Do you agree with using Fedora, or just stay with Ubuntu?. If Fedora, is it going to be same Jessie AMD64?
Thanks.
George
I think Fedora would work OK but it's always going to be easier to stick with a debian or debian derived system.
-
Fedora should be fine, but it requires more "hands on" setting up, versus Debian and Ubuntu.
IMO, the easiest distros to get MC working on the quickest is Ubuntu and Mint.
-
Interesting.
They were both compiled on wheezy as well.
Are you running with the thread priorities enabled??
I don't know. Where can I find this option? since I don't know it, probably not.
-
Thread priorities tutorial: https://yabb.jriver.com/interact/index.php/topic,111373.msg769735.html#msg769735
-
I think Fedora would work OK but it's always going to be easier to stick with a debian or debian derived system.
I will stick with Ubuntu or try Mint if I want to get in to something new.
Thanks.
George
-
Fedora should be fine, but it requires more "hands on" setting up, versus Debian and Ubuntu.
IMO, the easiest distros to get MC working on the quickest is Ubuntu and Mint.
Thanks.
George
-
I don't know. Where can I find this option? since I don't know it, probably not.
Hi,
I've got the thread priorities enabled and working, but no change. MC22 works, MC23 not.
Also I checked the pulse-shm-files. It seems to me, there is no difference between both versions, except the thread priorities.
-
Hi,
I've got the thread priorities enabled and working, but no change. MC22 works, MC23 not.
Also I checked the pulse-shm-files. It seems to me, there is no difference between both versions, except the thread priorities.
Hi Bob,
Problem solved! It has nothing to do with MC, because the ALSA plug-in allows different configuration for every application (see attached image). It's a little misleading, because the application will only pop up, when actually playing music. If I set this to "Beats Studio Wireless", it will switch to the headset as soon it's available.
Thanks
-
Hi Bob,
Problem solved! It has nothing to do with MC, because the ALSA plug-in allows different configuration for every application (see attached image). It's a little misleading, because the application will only pop up, when actually playing music. If I set this to "Beats Studio Wireless", it will switch to the headset as soon it's available.
Thanks
That's really useful info. Thanks for passing it on...
-
You can resize the tag window to eliminate the blank space. It does appear the auto field width is somewhat off.
Can't duplicate the autocomplete behavior in Debian XFCE. I suspect your window manager is setup with some focus stealing tweaks or some such. You'll need to do some investigation on that.
Unable to find any Ubuntu tweaks for window focus issue... any help greatly appreciated... cheers!
-
The installer correctly saw it as 23.0.72, but after installation, it says it is 23.0.65.
I removed prior version and reinstalled twice, no luck.
Thanks.
George
-
A strange phenomenon: I have MC 23.0.72 installed, but Mc shows me that it is version 23.0.65?
apt-cache policy mediacenter23
mediacenter23:
Installiert: 23.0.72
Installationskandidat: 23.0.72
Versionstabelle:
*** 23.0.72 500
500 http://dist.jriver.com/latest/mediacenter jessie/main amd64 Packages
100 /var/lib/dpkg/status
-
My old laptop also reverted to version 23.0.65 (from 23.0.70) after updating (running x64 MC).
My old desktop (using as a basic server) updated to 23.0.72 as expected (running i386 MC).
Both machines are running Mint 18.2.
-
Working off the repo I updated and then did a check at:
Help > About Media Centre ...
And the build shows up as 23.0.65
Did a double take, so I did a wget from the web address and did a deb package reinstall. The install message came up with:
~/Downloads/JRiver$ sudo dpkg -i MediaCenter-23.0.72-amd64.deb
(Reading database ... 264222 files and directories currently installed.)
Preparing to unpack MediaCenter-23.0.72-amd64.deb ...
Unpacking mediacenter23 (23.0.72) over (23.0.72) ...
Setting up mediacenter23 (23.0.72) ...
Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for shared-mime-info (1.8-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
So, the about build message looks like a typo ...
One to fix for next time?
-
Hi guys,
I'd like to report the following.
I have posted my issues running Media Center on Linux Debian 9.1 KDE earlier (I believe it was the .61 build thread). I just about tried everything since then.
My latest try was a clean install of Debian 9.2, the latest version, with KDE. I installed the AMD Radeon HD6000 series driver and verified hardware acceleration was working correctly. I then installed Media Center 23. Unfortunately, the weird problems and the poor performance of MC23 I posted earlier remain.
My hardware is:
- Asus F1A75-M Pro
- AMD A6-3500 APU
- 8 GB Ram
I tried running a clean Debian install using just the integrated motherboard graphics (Radeon HD 6430D), as well as my additional card (Radeon HD6450). I tried a lot of display drivers to tried to improve performance. So, no luck for me. Because I cannot resolve the poor performance of MC on Linux, I'm reluctantly going back to Windows for the time being. Thanks for the great software and all your great work!
-
Working off the repo I updated and then did a check at:
Help > About Media Centre ...
And the build shows up as 23.0.65
Did a double take, so I did a wget from the web address and did a deb package reinstall. The install message came up with:
So, the about build message looks like a typo ...
One to fix for next time?
According to the info regarding 23.0.72, there are lots of new features on this build, I checked, I did not see any new features regarding DLNA.
I used the installer to install, it correctly reported the version number.
Thanks
George
-
Same problem here: Installed 23.0.72 and system reports version 23.0.65. Ubuntu 17.04 64bit.
-
Yeah, it's a typo though.
-
Yeah, it's a typo though.
This is no typo.
Version 23.0.70 DLNA settings did have aacs or something like that. That version has a few tweaks on the DLNA front.
The 23.072 is supposed to have more tweaks on the DLNA.
The 23.0.65 loading now after the install has nothing that resembles 23.0.70, not to talk of 23.0.72.
Something is wrong during the compilation of the code.
Thanks.
George
-
This is no typo.
Version 23.0.70 DLNA settings did have aacs or something like that. That version has a few tweaks on the DLNA front.
The 23.072 is supposed to have more tweaks on the DLNA.
The 23.0.65 loading now after the install has nothing that resembles 23.0.70, not to talk of 23.0.72.
Something is wrong during the compilation of the code.
Thanks.
George
Yes, the AMD64 build is not correct.
I'm making a new one now.
The i386 and arm builds are not affected.
-
Yes, the AMD64 build is not correct.
I'm making a new one now.
The i386 and arm builds are not affected.
Thanks Sir,
George
-
It's up, see the first forum post about 23.0.73.