Page 1 of 1
3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Tue Sep 24, 2013 12:39 pm
by LostLogic
OS: Windows 8.1 Pro x64
Java Version: Java 7 Update 25 (32 bit)
Maximum number of audio channels to output for AC-3 re-encoding doesn't save. Set to 2 channels, saved, quit UMS and it reverts to 6 channels.
Log level is not saved - Changed to trace, saved, quit UMS, and it reverts to Debug.
Maximum bandwidth in Mb/s (0 means no limit): When setting it to 0, it will show up as 1000 upon restart, not show as 0.
Font sizes for English (UK) is significantly larger than when selecting English (US)
And finally, a general question: Would it be beneficial to run a 64 bit java vs the 32 bit that is installed by default? If yes, will the installer eventually download and install a 64 bit java when upgrading etc?
Thanks for the great media server!
Re: 3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Tue Sep 24, 2013 1:53 pm
by DeFlanko
i run a x64 java... ive had no issues.
Re: 3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Tue Sep 24, 2013 6:18 pm
by Optimus_prime
No the download logic for java get's 32bit as its the safest way to avoid issues. If you want x64bit download and install it yourself. then you can remove 32bit versions of java as the 64bit version runs in containers for 32bit.
hope that makes sense
Re: 3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Tue Sep 24, 2013 11:35 pm
by SubJunk
LostLogic wrote:OS: Windows 8.1 Pro x64
Java Version: Java 7 Update 25 (32 bit)
Maximum number of audio channels to output for AC-3 re-encoding doesn't save. Set to 2 channels, saved, quit UMS and it reverts to 6 channels.
Log level is not saved - Changed to trace, saved, quit UMS, and it reverts to Debug.
Maximum bandwidth in Mb/s (0 means no limit): When setting it to 0, it will show up as 1000 upon restart, not show as 0.
Font sizes for English (UK) is significantly larger than when selecting English (US)
And finally, a general question: Would it be beneficial to run a 64 bit java vs the 32 bit that is installed by default? If yes, will the installer eventually download and install a 64 bit java when upgrading etc?
Thanks for the great media server!
Thanks for these reports, LostLogic!
I've fixed the first and third ones. The second one is by design. The fourth one is a bug and we're not sure what causes it, it seems mysterious and happens with another language too.
Re: 3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Wed Sep 25, 2013 12:03 am
by LostLogic
Optimus_prime wrote:No the download logic for java get's 32bit as its the safest way to avoid issues. If you want x64bit download and install it yourself. then you can remove 32bit versions of java as the 64bit version runs in containers for 32bit.
hope that makes sense
I know that UMS works well with 64bit Java, I just wondered if it made any difference in a positive sense when sticking primarily to the default settings configured by UMS. Maybe increased address space would be beneficial, but I figure it might only be the case if you are working with a large memory buffer.

Re: 3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Wed Sep 25, 2013 2:36 pm
by SubJunk
Yeah there's no advantage with the default settings.
Re: 3.0.0-a6 Build: 0372ae7bf (2013-09-21) - Minor bugs
Posted: Fri Sep 27, 2013 12:42 am
by ExSport
I thing installing both JAVA versions (32+64bit) is good way to have less problems.
Some users are complaining with stuttering and buffer problems reported in logs also with small (200MB) buffer (200MB is reserved for ONE! renderer so more renderers used, more memory will be used).
It depends on configuration. If you will use plugins, cache,web radios, using more renderers in time etc., it reserves much more memory so UMS can go into memory problems.
Eg. when you will import 1000 radio stations to web.conf or you will start scanning your shared folders with magnification glass icon, all scanned media files cache mediainfo+covers+thumbs in memory so 768MB allocated for JAVA by default is not optimal for all cases. In this case 64bit JAVA with bigger heapsize is a good way to avoid any problems.