Version 4.1.0 is released
Version 4.1.0 is released
General:
You can download it from the front page.
This release improves file support - especially for files with subtitles - improves speed, adds Xbox One support, fixes bugs and more!
Changes since 4.0.3:
You can download it from the front page.
This release improves file support - especially for files with subtitles - improves speed, adds Xbox One support, fixes bugs and more!
Changes since 4.0.3:
- General:
- Added previous and next buttons to web interface
- Added the ability to prioritize renderer loading order
- Windows uninstaller no longer deletes custom renderer configs
- Windows uninstaller no longer leaves behind unused files
- Windows automatic updater downloads the correct build for the user's Java version
- FFmpeg defers to MEncoder for transcoding subtitles by default
- Fixed subtitles stretching bug
- Fixed startup crash on non-Windows operating systems
- Fixed subtitles not being transcoded when the renderer supported streaming the file
- Fixed automatic wireless quality optimizations not being applied
- Improved logging and log packing
- Speed improvements
- Renderers:
- Added support for Xbox One via DLNA
- Improved support for Panasonic VT60 TVs
- Languages:
- Updated Spanish translation (thanks, AlfredoRamos!)
- External Components:
- Updated Java Runtime Environment automatic downloader for Windows to 8u20, which:
- Improves security
- Updated FFmpeg for Windows and OS X to builds from 2014-08-28, which:
- Improves support for many containers and codecs
- Fixes bugs
- Updated Java Runtime Environment automatic downloader for Windows to 8u20, which:
Re: Version 4.1.0 is released
Thanks for the new release. One nice thing is that every engine has something to do now. 
A long, long time ago, I asked if there were any drawbacks to enabling "Parse Framerate from FFmpeg" in the MEncoder setting page, and was told not doing so was a bit faster as it did not have to invoke FFmpeg. Now that FFmpeg is the default and hands off to MEncoder (for subs), will it still incur the penalty? (As I noticed that if "Use Fontconfig" is checked in the FFmpeg settings, FFmpeg will still make temporary subs which it doesn't need, before handing over to MEncoder). Thanks.

A long, long time ago, I asked if there were any drawbacks to enabling "Parse Framerate from FFmpeg" in the MEncoder setting page, and was told not doing so was a bit faster as it did not have to invoke FFmpeg. Now that FFmpeg is the default and hands off to MEncoder (for subs), will it still incur the penalty? (As I noticed that if "Use Fontconfig" is checked in the FFmpeg settings, FFmpeg will still make temporary subs which it doesn't need, before handing over to MEncoder). Thanks.
Last edited by Madoka on Wed Sep 03, 2014 3:29 am, edited 1 time in total.
Re: Version 4.1.0 is released
Thanks for the release!
-- UMS serving PS3, WDTV, Samsung H6400 + J5500 and Kalemsoft renderers! (no video transcoding but remuxing accepted
)

Re: Version 4.1.0 is released
Hi SubJunk,
There's still the issue I reported in viewtopic.php?f=9&t=2129&p=11876#p11876 that I have updated there.
However, this release works well on Mac, no more hang or lag
There's still the issue I reported in viewtopic.php?f=9&t=2129&p=11876#p11876 that I have updated there.
However, this release works well on Mac, no more hang or lag
Re: Version 4.1.0 is released
Nice catch with the temporary subs, I've fixed it now for the next release, thanks!Madoka wrote:Thanks for the new release. One nice thing is that every engine has something to do now.
A long, long time ago, I asked if there were any drawbacks to enabling "Parse Framerate from FFmpeg" in the MEncoder setting page, and was told not doing so was a bit faster as it did not have to invoke FFmpeg. Now that FFmpeg is the default and hands off to MEncoder (for subs), will it still incur the penalty? (As I noticed that if "Use Fontconfig" is checked in the FFmpeg settings, FFmpeg will still make temporary subs which it doesn't need, before handing over to MEncoder). Thanks.
Ideally we shouldn't be using FFmpeg at all if it is deferring to MEncoder for that video.
Thanks Wolfgan!Wolfgan wrote:Thanks for the release!
-
- Posts: 10
- Joined: Wed Sep 03, 2014 10:23 pm
Re: Version 4.1.0 is released
Hi,
I've just tried to install the Windows Java 6 build but had an issue when trying to run it, I get a requester saying:-
"UMS uses Java Runtime Environment 7.0+ it will now be downloaded"
Me thinks something is wrong
Works great my other machine with Java 7 though, cheers guys !
EDIT:-
Just tried UMS-4.0.3-Java6 and that gave the same result, also it looks as if it may be trying to download Java 8, cant verify that though...
I've just tried to install the Windows Java 6 build but had an issue when trying to run it, I get a requester saying:-
"UMS uses Java Runtime Environment 7.0+ it will now be downloaded"
Me thinks something is wrong

Works great my other machine with Java 7 though, cheers guys !
EDIT:-
Just tried UMS-4.0.3-Java6 and that gave the same result, also it looks as if it may be trying to download Java 8, cant verify that though...
-
- Posts: 30
- Joined: Thu Oct 10, 2013 11:35 pm
Re: Version 4.1.0 is released
What has changed in this version? As I cannot playback anything now with my custom render. Even the default one that has the same string as the Vizio.
Nothing is obvious in the trace but this keeps popping up after cannot play.
I go back to 4.0.3 and can play my files.
Nothing is obvious in the trace but this keeps popping up after cannot play.
Code: Select all
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] dyld: lazy symbol binding failed: Symbol not found: ___sincos_stret
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Referenced from: /Applications/Universal Media Server.app/Contents/Resources/osx/ffmpeg
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Expected in: /usr/lib/libSystem.B.dylib
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2]
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] dyld: Symbol not found: ___sincos_stret
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Referenced from: /Applications/Universal Media Server.app/Contents/Resources/osx/ffmpeg
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Expected in: /usr/lib/libSystem.B.dylib
I go back to 4.0.3 and can play my files.
Re: Version 4.1.0 is released
Thanks for the report, FlyMcDoogal! This will be fixed in 4.1.1 which will be released soonFlyMcDoogal wrote:Hi,
I've just tried to install the Windows Java 6 build but had an issue when trying to run it, I get a requester saying:-
"UMS uses Java Runtime Environment 7.0+ it will now be downloaded"
Me thinks something is wrong
Works great my other machine with Java 7 though, cheers guys !
EDIT:-
Just tried UMS-4.0.3-Java6 and that gave the same result, also it looks as if it may be trying to download Java 8, cant verify that though...
This is probably an issue with the version of FFmpeg we updated to in 4.1.0. Please replace /Applications/Universal Media Server.app/Contents/Resources/osx/ffmpeg with the one below and see if that fixes it:CappySpectrum wrote:What has changed in this version? As I cannot playback anything now with my custom render. Even the default one that has the same string as the Vizio.
Nothing is obvious in the trace but this keeps popping up after cannot play.
Code: Select all
DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] dyld: lazy symbol binding failed: Symbol not found: ___sincos_stret DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Referenced from: /Applications/Universal Media Server.app/Contents/Resources/osx/ffmpeg DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Expected in: /usr/lib/libSystem.B.dylib DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] dyld: Symbol not found: ___sincos_stret DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Referenced from: /Applications/Universal Media Server.app/Contents/Resources/osx/ffmpeg DEBUG 2014-09-04 04:04:50.644 [ffmpeg-2-2] Expected in: /usr/lib/libSystem.B.dylib
I go back to 4.0.3 and can play my files.
http://www.evermeet.cx/ffmpeg/snapshots ... 7cf1f0f.7z
and if not, please try this one:
http://www.evermeet.cx/ffmpeg/snapshots ... 8156e03.7z
Re: Version 4.1.0 is released
Thx for the new version, but the external subtitles won't work on Samsung F Series again.
Regards,
Jens
-----------
Devices used with UMS : - Windows 10 PC, Samsung UE32 F4580SS, Samsung UE48H6600
Jens
-----------
Devices used with UMS : - Windows 10 PC, Samsung UE32 F4580SS, Samsung UE48H6600
Re: Version 4.1.0 is released
Thanks pipin, I've fixed that now and it will be in 4.1.1