Universal Media Server | Forum

ExSport wrote:Maybe stupid note but if working version didn't worked when config wasn't deleted from newer version, what about backup the UMS.conf file plus renderers folder with .conf files from this working version, install first non working version after working one and replace ums.conf and renderers folder? If it will work, problem is somwhere in new settings in UMS.conf or renderer.conf file and not directly in code?

A good point but I did NOT check the "clean install" when I installed 2.5.0 so it should not have overridden the previous (working) configuration if I understand this option correctly. If I have time tonight, I'll try it.

SubJunk wrote:OK cool, there were a huge lot of changes between 2.4.2 and 2.5.0 so I've made some more builds to help narrow it down, please test them when you have time
http://www.spirton.com/uploads/UMS/UMS-486930e.exe
http://www.spirton.com/uploads/UMS/UMS-ddc22d8.exe

Thanks I'll give these a try and let you know. I'll also try what ExSport suggested.

Okay, so what ExSport suggested did not work.

The results from the two "beta" builds:
UMS-486930e WORKED
UMS-ddc22d8 DID NOT WORK

I just tried 2.6.0 with a .mt2s file with AVC encoding on my PS3 using FFMPEG and everything worked fine.
Note I think a lot depends on the codecs you are using which is outside the control of UMS.
For example, the simple upgrade of my LAV codecs from 0.55.3 to 0.56 has made a big improvement on FFMPEG playing stability.

I also tried Transcode for the same file and both Mencoder and Avisynth/Mencoder failed to play with PS3 error code 800200E1
I used to get the same error with FFMPEG on 2.6 when I used LAV 0.55.3.

Triplefun wrote:...For example, the simple upgrade of my LAV codecs from 0.55.3 to 0.56 has made a big improvement on FFMPEG playing stability....

Don't baffle people. Installed codecs don't have any influence on UMS when AVISYNTH is not used. Using direct streaming, remuxing with tsMuxeR or transcoding with MEncoder/FFMpeg/VLC never used codecs
Also for most of people it is not recommended to use AVISYNTH, it is useful only in specific scenarios.

I appreciate the input Triplefun but I don't use transcoding. My device pretty much supports any codec so I block transcoding of all supported file types. Like I already mentioned, this worked fine previously and the files have not changed and I've already confirmed there's a difference between versions.

SubJunk has a line on it for sure as one of the builds works fine. I just left it installed since it works until the official fix is release.

Triplefun wrote:Note I think a lot depends on the codecs you are using which is outside the control of UMS.

ExSport is right that codecs don't affect FFmpeg, only AviSynth. Thanks for the suggestion though

AYColumbia wrote:SubJunk has a line on it for sure as one of the builds works fine. I just left it installed since it works until the official fix is release.

I'm still trying to narrow it down since I still can't see anything in the code that would cause that bug. Here are two new test versions if you wouldn't mind
http://www.spirton.com/uploads/UMS/UMS-9d51918.exe
http://www.spirton.com/uploads/UMS/UMS-a21a33a.exe

I am not using avisynth, just ffmpeg and lav codecs.
When playing a .m2ts with avc video using lav 0.53.3 it would not play on the ps3.
Having updated to 0.56 it now plays with avc shown as the video stream.
Nothing else has changed!

@Triplefun: Something strange on your side. FFMpeg, MEncoder or tsMuxeR don't need any codecs installed and don't use them in any way. MEncoder and FFMpeg have built-in codecs and can't use external ones.
There must be another problem why after installing another version of LAV it fixed your problem
Maybe you are using AviSynth and you don't know about it?

Thanks. So please confirm that if I just use FFMPEG then I can also delete avisynth. Note my .mt2s file are playing well although I do get stuttering when network exceeds 150MB/s which is not very often. l use q9550 and gigabit network.