Page 1 of 3

Version 4.1.0 is released

Posted: Tue Sep 02, 2014 3:58 pm
by SubJunk
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:
  • 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

Re: Version 4.1.0 is released

Posted: Tue Sep 02, 2014 6:49 pm
by Madoka
Thanks for the new release. One nice thing is that every engine has something to do now. :D

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.

Re: Version 4.1.0 is released

Posted: Wed Sep 03, 2014 12:46 am
by Wolfgan
Thanks for the release!

Re: Version 4.1.0 is released

Posted: Wed Sep 03, 2014 1:17 am
by gatty
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

Re: Version 4.1.0 is released

Posted: Wed Sep 03, 2014 9:51 am
by SubJunk
Madoka wrote:Thanks for the new release. One nice thing is that every engine has something to do now. :D

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.
Nice catch with the temporary subs, I've fixed it now for the next release, thanks!
Ideally we shouldn't be using FFmpeg at all if it is deferring to MEncoder for that video.
Wolfgan wrote:Thanks for the release!
Thanks Wolfgan!

Re: Version 4.1.0 is released

Posted: Wed Sep 03, 2014 10:30 pm
by FlyMcDoogal
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...

Re: Version 4.1.0 is released

Posted: Thu Sep 04, 2014 3:11 pm
by CappySpectrum
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.

Re: Version 4.1.0 is released

Posted: Thu Sep 04, 2014 5:49 pm
by SubJunk
FlyMcDoogal 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...
Thanks for the report, FlyMcDoogal! This will be fixed in 4.1.1 which will be released soon
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.
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:
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

Posted: Fri Sep 05, 2014 5:11 am
by pipin
Thx for the new version, but the external subtitles won't work on Samsung F Series again.

Re: Version 4.1.0 is released

Posted: Fri Sep 05, 2014 5:23 pm
by SubJunk
Thanks pipin, I've fixed that now and it will be in 4.1.1