Version 9.7.1 released

Announcements about Universal Media Server
User avatar
SubJunk
Lead Developer
Posts: 3705
Joined: Sun May 27, 2012 4:12 pm

Version 9.7.1 released

Post by SubJunk »

General:

This release enables minimizing on startup for macOS, improves support for running as a service on Windows, improves transcoding support, and more!

We are busy preparing our next beta which improves, stabilizes and extends our metadata, allowing for things like recommendations, genres, ratings from major sources, etc. as well as remote access.

Download:

Windows, macOS and Linux: Our front page or our official mirrors
Docker: docker pull universalmediaserver/ums

Changes since 9.7.0
  • General:
    • Implemented the minimize on startup option on macOS
    • Added dates to the debug log zip (thanks, midhun1998!)
    • Added profiling logging for the database
    • Windows installer stops the existing service if it is running
    • Windows installer starts the service if the checkbox is enabled at the end and the service is installed, instead of starting the GUI
    • Windows installer does not try to start the GUI on computer startup if the service is installed
    • GUI warns about using it as a GUI when it is already installed as a service
    • The service uses our bundled Java instead of the system one
    • Changed the default AC-3 transcoding bitrate to 448 for better transcoding compatibility
  • Translation updates via Crowdin:
    • Czech (100%)
    • Danish (99%)
    • English (United Kingdom) (25%)
    • Finnish (100%)
    • Polish (100%)
    • Portuguese (100%)
    • Portuguese (Brazilian) (100%)
    • Russian (93%)
    • Slovak (98%)
    • Spanish (99%)
    • Turkish (100%)
    • Ukrainian (17%)
  • Dependency updates:
    • Bump maven-site-plugin from 3.9.0 to 3.9.1
    • Bump oshi-core from 5.1.2 to 5.2.0
    • Bump rome from 1.13.1 to 1.14.1
    • Bump spotbugs-maven-plugin from 4.0.0 to 4.0.4
Notes:
  • We fully support Windows 7+, and have limited support for Windows XP and Vista
  • macOS 10.10+ is fully supported
User avatar
pipin
Posts: 160
Joined: Fri Dec 28, 2012 12:17 am

Re: Version 9.7.1 released

Post by pipin »

Thanks for the release.
Regards,
Jens
-----------
Devices used with UMS : - Windows 10 PC, Samsung UE32 F4580SS, Samsung UE48H6600
Uranium
Posts: 5
Joined: Mon May 20, 2019 6:15 am

Re: Version 9.7.1 released

Post by Uranium »

This version broke launching UMS as Service (but launching wrapper as concole is ok).

Version 9.7.0 is working as Service with "wrapper.java.command=jre14-x64/bin/java" in wrapper.conf.

I also tested the version 3.5.43 of the wrapper, as well as adding the dll compiled in 64 bits (https://www.krenger.ch/blog/tag/java-service-wrapper ; renamed "wrapper-windows-x86-64.dll", this allows to continue using the 32 bits version when it is necessary), it seems to work (obviously without counting the problem above).
User avatar
SubJunk
Lead Developer
Posts: 3705
Joined: Sun May 27, 2012 4:12 pm

Re: Version 9.7.1 released

Post by SubJunk »

pipin wrote: Mon Jul 06, 2020 7:38 pm Thanks for the release.
You're welcome :)
Uranium wrote: Tue Jul 07, 2020 2:51 am This version broke launching UMS as Service (but launching wrapper as concole is ok).

Version 9.7.0 is working as Service with "wrapper.java.command=jre14-x64/bin/java" in wrapper.conf.

I also tested the version 3.5.43 of the wrapper, as well as adding the dll compiled in 64 bits (https://www.krenger.ch/blog/tag/java-service-wrapper ; renamed "wrapper-windows-x86-64.dll", this allows to continue using the 32 bits version when it is necessary), it seems to work (obviously without counting the problem above).
If you're using a modified version of the wrapper.conf that won't work anymore. The command is now wrapper.java.command=jre14/bin/java
Uranium
Posts: 5
Joined: Mon May 20, 2019 6:15 am

Re: Version 9.7.1 released

Post by Uranium »

SubJunk wrote: Tue Jul 07, 2020 8:55 am If you're using a modified version of the wrapper.conf that won't work anymore. The command is now wrapper.java.command=jre14/bin/java
I used it only for testing.

Version 9.7.1 broke the launching as service : wrapper launch the JVM but not UMS, check the wrapper log.

Code: Select all

STATUS | wrapper  | 2020/07/07 11:07:22 | Universal Media Server service installed.
STATUS | wrapper  | 2020/07/07 11:07:38 | --> Wrapper Started as Service
STATUS | wrapper  | 2020/07/07 11:07:39 | Java Service Wrapper Community Edition 32-bit 3.5.17
STATUS | wrapper  | 2020/07/07 11:07:39 |   Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper  | 2020/07/07 11:07:39 |     http://wrapper.tanukisoftware.com
STATUS | wrapper  | 2020/07/07 11:07:39 | 
STATUS | wrapper  | 2020/07/07 11:07:39 | Launching a JVM...
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager: Initializing...
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager: 
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           The file is located on the path at the following location but
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           could not be loaded:
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:             C:\Program Files (x86)\Universal Media Server\win32\service\wrapper.dll
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           Please verify that the file is both readable and executable by the
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           current user and that the file has not been corrupted in any way.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           One common cause of this problem is running a 32-bit version
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           of the Wrapper with a 64-bit version of Java, or vica versa.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           This is a 64-bit JVM.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           Reported cause:
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:             C:\Program Files (x86)\Universal Media Server\win32\service\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           System signals will not be handled correctly.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager: 
STATUS | wrapper  | 2020/07/07 11:08:39 | <-- Wrapper Stopped
EDIT :

Version 9.7.1 (clean install) as Service : launch JVM but not UMS
Version 9.7.1 (clean install) as Console (wrapper -c) : OK
Version 9.7.0 (clean install but only corrected Java path) : OK

EDIT 2 :

When Service installed but not running, if i launch UMS, it display a Warning box. If i click "Cancel" and re-launch UMS, it display again the Warning box.
Re-launch UMS a third time, Warning box not displayed, and launching as Service correctly working.

EDIT 3 :

In UMS.conf, if "show_service_warning = true", it break launching as Service, if "show_service_warning = false" it's OK ;)
User avatar
chickyboom
Posts: 12
Joined: Sat Apr 18, 2020 12:01 pm

Re: Version 9.7.1 released

Post by chickyboom »

9.7.1 CPU usage while UMS is idle seems bugged, constant 4-10% keeping my CPU at full speed.
User avatar
pipin
Posts: 160
Joined: Fri Dec 28, 2012 12:17 am

Re: Version 9.7.1 released

Post by pipin »

chickyboom wrote: Thu Jul 09, 2020 6:32 am 9.7.1 CPU usage while UMS is idle seems bugged, constant 4-10% keeping my CPU at full speed.
Over 10 or even 11 % here. :shock:

And I was wondering, why my PC didnt go to sleep any more.
Regards,
Jens
-----------
Devices used with UMS : - Windows 10 PC, Samsung UE32 F4580SS, Samsung UE48H6600
JohnnyG
Posts: 4
Joined: Fri Jul 10, 2020 3:39 pm

Re: Version 9.7.1 released

Post by JohnnyG »

Bug report :
I'm on WIndow 10 64

Download from Fosshub
https://www.fosshub.com/Universal-Media ... -9.7.1.exe

Windows Defender smart screen activate and refuse to launch the installer because unknown editor.
User avatar
SubJunk
Lead Developer
Posts: 3705
Joined: Sun May 27, 2012 4:12 pm

Re: Version 9.7.1 released

Post by SubJunk »

Uranium wrote: Tue Jul 07, 2020 6:44 pm
SubJunk wrote: Tue Jul 07, 2020 8:55 am If you're using a modified version of the wrapper.conf that won't work anymore. The command is now wrapper.java.command=jre14/bin/java
I used it only for testing.

Version 9.7.1 broke the launching as service : wrapper launch the JVM but not UMS, check the wrapper log.

Code: Select all

STATUS | wrapper  | 2020/07/07 11:07:22 | Universal Media Server service installed.
STATUS | wrapper  | 2020/07/07 11:07:38 | --> Wrapper Started as Service
STATUS | wrapper  | 2020/07/07 11:07:39 | Java Service Wrapper Community Edition 32-bit 3.5.17
STATUS | wrapper  | 2020/07/07 11:07:39 |   Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper  | 2020/07/07 11:07:39 |     http://wrapper.tanukisoftware.com
STATUS | wrapper  | 2020/07/07 11:07:39 | 
STATUS | wrapper  | 2020/07/07 11:07:39 | Launching a JVM...
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager: Initializing...
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager: 
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           The file is located on the path at the following location but
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           could not be loaded:
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:             C:\Program Files (x86)\Universal Media Server\win32\service\wrapper.dll
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           Please verify that the file is both readable and executable by the
INFO   | jvm 1    | 2020/07/07 11:07:39 | WrapperManager:           current user and that the file has not been corrupted in any way.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           One common cause of this problem is running a 32-bit version
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           of the Wrapper with a 64-bit version of Java, or vica versa.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           This is a 64-bit JVM.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           Reported cause:
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:             C:\Program Files (x86)\Universal Media Server\win32\service\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager:           System signals will not be handled correctly.
INFO   | jvm 1    | 2020/07/07 11:07:40 | WrapperManager: 
STATUS | wrapper  | 2020/07/07 11:08:39 | <-- Wrapper Stopped
EDIT :

Version 9.7.1 (clean install) as Service : launch JVM but not UMS
Version 9.7.1 (clean install) as Console (wrapper -c) : OK
Version 9.7.0 (clean install but only corrected Java path) : OK

EDIT 2 :

When Service installed but not running, if i launch UMS, it display a Warning box. If i click "Cancel" and re-launch UMS, it display again the Warning box.
Re-launch UMS a third time, Warning box not displayed, and launching as Service correctly working.

EDIT 3 :

In UMS.conf, if "show_service_warning = true", it break launching as Service, if "show_service_warning = false" it's OK ;)
Thanks for reporting this, it's fixed in the next version
pipin wrote: Thu Jul 09, 2020 9:09 am
chickyboom wrote: Thu Jul 09, 2020 6:32 am 9.7.1 CPU usage while UMS is idle seems bugged, constant 4-10% keeping my CPU at full speed.
Over 10 or even 11 % here. :shock:

And I was wondering, why my PC didnt go to sleep any more.
This is fixed too, thanks for letting us know
User avatar
SubJunk
Lead Developer
Posts: 3705
Joined: Sun May 27, 2012 4:12 pm

Re: Version 9.7.1 released

Post by SubJunk »

JohnnyG wrote: Fri Jul 10, 2020 3:43 pm Bug report :
I'm on WIndow 10 64

Download from Fosshub
https://www.fosshub.com/Universal-Media ... -9.7.1.exe

Windows Defender smart screen activate and refuse to launch the installer because unknown editor.
Thanks for reporting this. Can you please take a screenshot of this so we can see exactly what the error is? Then we can likely report it to Microsoft to fix a false positive
Post Reply