INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Linux => Topic started by: bob on June 12, 2018, 04:44:49 pm
-
This is the latest BETA version of MC24 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/test/MediaCenter-24.0.42-amd64.deb
i386 http://files.jriver.com/mediacenter/test/MediaCenter-24.0.42.deb
arm http://files.jriver.com/mediacenter/test/MediaCenter-24.0.42-armhf.deb
Also in the BETA repo.
24.0.42 (7/10/2018)
1. Changed: Improved internal web browser operation.
24.0.39 (6/29/2018)
1. Changes from the main branch mainly dealing with JRiver Radio.
24.0.37 (6/26/2018)
1. NEW: Linux implement key release handling. Detect whether a key is being held down (key repeat).
2. Fixed: Crash on right-click release in some context menus.
3. Fixed: A key sending function in MC was sending 2 keypresses instead of a press/release.
24.0.36 (6/22/2018)
1. Fixed: In some cases, converting an audio file would leave the file type set to the old file's type.
2. Fixed: OpenGL Theater View could use more CPU then expected since 24.0.34.
3. Fixed: SRT subtitles with non-breaking spaces did not render properly.
4. Changed: DLNA, change SetNext controller option disabling so that device errors don't disable SetNext only disable it if the renderer reports that it's not implemented.
5. Changed: DLNA. Want to make sure that if a resubscribe fails we clear and do a subscribe. Have seen http error codes of 412 on resubscribe.
6. Changed: DLNA, Add a code that will do a manual transport state update if we look frozen at the end of a track (missed an event..)
7. Changed: Radio JRiver playlists will end after playing for two hours without any Media Center user interaction.
24.0.35 (6/15/2018)
1. Fixed: Licensing on i386/amd64 builds. Hopefully for the last time, will require re-entering your registration code.
2. Changed: Implemented some missing low level windowing functions.
24.0.34 (6/12/2018)
1. Fixed: A couple of memory leaks in ALSA and in the Windowing code.
2. Changed: Removed the Register function from the desktop entry because it was preventing mime type associations from working.
3. Changed: The internal web browser is more resiliant and should work better with some desktops.
24.0.32-4 (6/5/2018)
1. Fixed: On some systems we couldn't open the ALSA hardware devices.
24.0.32-2 (6/3/2018)
1. Fixed: Covert art thumbnails were not working on some platforms.
24.0.32 (6/1/2018)
1. Changed: Licensing on Intel platforms. Will require re-entering license key again.
2. Fixed: ALSA, the audio device descriptions would not line up with the device name when there was a default device in the list (no description).
3. Changed: ALSA change the order of hardware parameter settings when opening the device.
24.0.31 (5/29/2018)
1. NEW: Implemented the startup options for linux. Works with any desktop manager.
2. Fixed: A memory leak in the ALSA driver.
3. NEW: Implemented the internal browser. Needs testing.
24.0.28 ( 5/14/2018)
1. NEW: Added info to the Reporter Advanced Information showing the system memory and free memory.
2. Changed: For Linux ARM, disable multithreaded drawfast code (used in resizing) until neon is fully implemented.
3. Changed: For Linux ARM, cap maximum threads and weight for thumbnailing until neon is fully implemented.
4. Fixed: Linux ALSA output device, wasn't configuring local zones other than the default zone properly.
5. Changed: Updated the gtk dependencies from libgtk2.0 to libgtk-3-0
24.0.26-2 (5/10/2018)
1. Changed: Switched the default skin to Modern Cards: Grey Edition.
2. NEW: Implemented support for direct DSD for devices that support DSD_U32_BE (i.e. iFi iDSD and other xmos based devices). See the device options under the Audio device config.
24.0.26 (5/10/2018)
1. Fixed: The file browser wasn't working in a few places (i.e. Languages->Browse Translations Folder)
2. Changed: Another tweak to registration. Will require re-entering the license key on intel based linux platforms.
3. NEW: Work on the integrated browser (not implemented yet) requires the addition of webkit2 library dependencies to the .deb
4. Fixed: Added the libgomp dependency to the .deb
24.0.19 (4/29/2018)
1. Fixed: Tooltip box shadows were offsetting the text below the shadow.
2. NEW: Text edit boxes now have a more convenient way to add Latin characters with diacritics. Press and hold a letter key and a list of choices with diacritical versions for that letter is shown to choose from.
3. Fixed: On ARM the non-sse bilinear rendering wasn't properly handling the alpha channel resulting in some see through icons.
24.0.18 (4/24/2018)
1. Changed: Updated FFmpeg to version 4.0, used for file analysis, transcoding and video playback.
2. Changed: Optimized Video rendering image uploading for better performance and reliability.
24.0.16 (4/17/2018)
1. FIXED: A significant memory leak.
24.0.15 (4/13/2018)
1. NEW: Added support for bilinear image resizing (on ARM which didn't have it before) so that images in the program will look much better.
2. Fixed: A segfault upon startup with systems that have non-standard /dev tree.
24.0.12 (4/10/2018)
1. Fixed: Non-Root users on linux couldn't send WOL packets.
2. Fixed: Removed unsupported print commands from menus.
3. NEW: Much faster FFT code for places where spectrum analysis is used.
4. Changed: Some licensing code. Registration code will need to be re-entered.
24.0.2 (02/03/2018)
1. NEW: First MC24 build for linux
-
Won't start. Requests license. After entering license, it starts.
Note: earlier today Ubuntu issued new kernel updates to 4.15.0-23, which I installed. This might have something to do with license problem.
-
Yeah, I noticed the license was lost on Ubuntu 18.04 after doing kernel updates (again). This was before updating to 24.0.34 beta though (was using 24.0.32-4 at the time of the kernel updates though).
-
Just in Debian Buster (Gnome) get the update.
A very strange appearance.
In Xfce (also Buster) everything is normal
-
The web browser integration is known to somehow dislike GNOME. We're working on a solution or a replacement.
-
Yeah, I noticed the license was lost on Ubuntu 18.04 after doing kernel updates (again). This was before updating to 24.0.34 beta though (was using 24.0.32-4 at the time of the kernel updates though).
Are you saying you were running 24.0.32-4 licensed then updated to 24.0.34 beta, still licensed, then the license was lost after a kernel update??
If so please attach a log. IIRC you attached one for 24.0.32-4. That way I can compare them.
-
No, I was on 24.0.32-4 licensed and then kernel updates happened which lost the license (after rebooting and checking), then I updated to 24.0.34 with the license still lost.
Makes you wonder what's in those kernel updates. :P
-
No, I was on 24.0.32-4 licensed and then kernel updates happened which lost the license (after rebooting and checking), then I updated to 24.0.34 with the license still lost.
Makes you wonder what's in those kernel updates. :P
That should not have happened with anything after 24.0.32.
If I have a before and after log it would help track it down.
-
That should not have happened with anything after 24.0.32.
If I have a before and after log it would help track it down.
Figured it out by doing the kernel update on ubuntu here.
My comment:
Ok, it's going to happen again in the next build, hopefully for the last time.
PM me if you need activations reset.
You can blame it on intel's buggy cpu's (or my lack of dealing with them properly).
Doesn't affect the arm build.
-
Upgrade to MC 24.0.35 ------> License had to be renewed.
-
Yep, but that's to be expected though. :)
Update went well. Just waiting now for new kernel updates to see if it happens again, but fingers crossed it doesn't.
-
Upgrade from 24.0.34 to 35 went OK. Expected license renewal was required.
About my seventh renewal so far since updating to version 24.
I'm with AwesomeDonkey hoping this is the last time license renewal will be required.
-
1. NEW: Linux implement key release handling. Detect whether a key is being held down (key repeat).
......
3. Fixed: A key sending function in MC was sending 2 keypresses instead of a press/release.
I'm happy to report that, at least for me, 24.0.37 beta has cured the double letter problem when tagging. Hope it works for the other folks, too.
-
Yep, can confirm it's fixed here too.
-
The 24.0.39 arm build is a bit behind, it should be up later tonight.
Edit: It's up now.
-
All three links get access denied errors.
-
All three links get access denied errors.
Sorry about that, they should be good now.
-
Hi ,
I'm exporting music to a external device which does not support volume leveling. For the device, "apply DSP settings" is marked. I would expect, that the volume level is then hard coded into each frame and the Volume Level fields set to zero. But playing music with my device (iPhone / iPad), level still jumps around, which is hardly tolerable. If I misunderstand the function "apply DSP settings"a, please let me know.
Since JRemote doesn't honor the volume level information (Any reason for that?), I exported all files to a different folder using "apply DSP settings". I used a separate database to manage those files, but even running the "analyze audio" makes no change to the level (It should be close to 0 now).
To me, the DSP settings are not applied during the conversion process. I tested it by using three files 440Hz, 0db / -6db and -10db. When VL is working, all three files play the same volume (as on my PC), if not, there is a noticeable difference in volume. (the attached files need to be analyzed first)
-
Just noticed that ASIO Driver is listed under Options > General > Features. However since ASIO isn't available on Linux, it might be a good idea to hide this one. ;) Not sure if there's anything else that needs hidden though.
-
The web browser integration is known to somehow dislike GNOME. We're working on a solution or a replacement.
I have the same problem with the browser under the Deepin desktop environment, JRiver also closes/crashes if resizing the window while playing a video.
-
Hi ,
I'm exporting music to a external device which does not support volume leveling. For the device, "apply DSP settings" is marked. I would expect, that the volume level is then hard coded into each frame and the Volume Level fields set to zero. But playing music with my device (iPhone / iPad), level still jumps around, which is hardly tolerable. If I misunderstand the function "apply DSP settings"a, please let me know.
Since JRemote doesn't honor the volume level information (Any reason for that?), I exported all files to a different folder using "apply DSP settings". I used a separate database to manage those files, but even running the "analyze audio" makes no change to the level (It should be close to 0 now).
To me, the DSP settings are not applied during the conversion process. I tested it by using three files 440Hz, 0db / -6db and -10db. When VL is working, all three files play the same volume (as on my PC), if not, there is a noticeable difference in volume. (the attached files need to be analyzed first)
You're playing locally on the (iPhone / iPad) with JRemote and you have transcoding turned on in JRemote?
-
Just noticed that ASIO Driver is listed under Options > General > Features. However since ASIO isn't available on Linux, it might be a good idea to hide this one. ;) Not sure if there's anything else that needs hidden though.
Thanks
-
You're playing locally on the (iPhone / iPad) with JRemote and you have transcoding turned on in JRemote?
Hi Bob,
yes, I'm playing locally with JRemote and transcoding is turned on. Like I mentioned before, I checked several methods so far, but there was no way, to hardcode VL into the export file or to use it with JRemote.
Once more for my understanding: if I play eg. the attached files after vl, they should play almost with equal volume. (It is true for local playback at my PC, not for JRemote or any external device mot honoring the vl-tags).
Udo
Udo
-
Hi Bob,
yes, I'm playing locally with JRemote and transcoding is turned on. Like I mentioned before, I checked several methods so far, but there was no way, to hardcode VL into the export file or to use it with JRemote.
Once more for my understanding: if I play eg. the attached files after vl, they should play almost with equal volume. (It is true for local playback at my PC, not for JRemote or any external device mot honoring the vl-tags).
Udo
We talked about this a bit just now.
There isn't any DSP VL being applied to the MCWS transcoding and the tags are not preserved through that process so that the file length can be calculated in advance.
There are a couple of approaches to dealing with this.
It would be interesting if you could do a test playing non-transcoded material and see if the underlying player in JRemote (libbass) pays attention to the VL tags.
Knowing this would help in making a decision on how to handle the issue.
-
We talked about this a bit just now.
There isn't any DSP VL being applied to the MCWS transcoding and the tags are not preserved through that process so that the file length can be calculated in advance.
There are a couple of approaches to dealing with this.
It would be interesting if you could do a test playing non-transcoded material and see if the underlying player in JRemote (libbass) pays attention to the VL tags.
Knowing this would help in making a decision on how to handle the issue.
I've tested transcoded and non-transcoded files before and could find no difference. Also, I played the test files in JRemote (transcoded and non-transcoded) and find, that the player did not pay any attention to the VL tags. To me, the easiest would be, to teach the JRemote player to apply the VL values during playback.
-
I've tested transcoded and non-transcoded files before and could find no difference. Also, I played the test files in JRemote (transcoded and non-transcoded) and find, that the player did not pay any attention to the VL tags. To me, the easiest would be, to teach the JRemote player to apply the VL values during playback.
Thanks for testing.
I'll look into whether it's possible to handle this in the JRemote code. The library we are using to play locally doesn't seem to have a switch for that. Perhaps we could adjust the volume control by the offset in the the file. Will need to investigate more.
-
Thanks for testing.
I'll look into whether it's possible to handle this in the JRemote code. The library we are using to play locally doesn't seem to have a switch for that. Perhaps we could adjust the volume control by the offset in the the file. Will need to investigate more.
Thanks so far, by the way, did you ever consider to come up with MC as mobile app?
-
We're working on it.