Page 1 of 1

Odd Problem With AviSynth/FFmpeg

Posted: Fri Apr 24, 2015 5:27 pm
by Dem0n
Hello!

I just recently made the switch from UMS (I had no idea it even existed T_T) and I've been having some trouble getting it set up. Upon installing UMS, I tweaked all the settings how I saw fit and restarted the server and happily watched a few things on my PS3. I came back to my computer a while later and completely closed UMS to start playing some games. Now, I've gone and opened UMS again to watch some more, but I'm receiving an error on EVERY video file I try to play via my PS3 (also tested it on my android phone with BubbleUpnp). In the logs the only error I see is "Process C:\Program Files (x86)\Universal Media Server\win32\ffmpeg64.exe has a return code of 1! Maybe an error occurred... check the log file". Restarting my PS3/PC did nothing. Finally, I gave up and reinstalled the software all over again and put all the settings back to how I had them. Magically, it worked again! Out of sheer curiosity, I closed UMS and opened it again and encountered the same exact problem. I've tried manually updating ffmpeg to the latest version, but that did nothing to help. I went ahead and attached the trace debug package.

It's probably also worth noting that I am using the Java8 version and I have the klite mega codec pack installed with every option included.

Hope you guys can help me resolve this issue soon :-\

Re: Odd Problem With ffmpeg

Posted: Fri Apr 24, 2015 7:34 pm
by valib
It seems to me that it is an AviSynth problem not FFmpeg. If you don't have any special reason to use AviSynth/FFmpeg set the FFmpeg as the primary transcoding engine (move it on the top of the list). FFmpeg is a default one for UMS.

Re: Odd Problem With ffmpeg

Posted: Sat Apr 25, 2015 3:02 am
by Dem0n
valib wrote:It seems to me that it is an AviSynth problem not FFmpeg.
I'm not sure FFmpeg is the problem. I put FFmpeg to the top of the list and I still receive the same error messages.
valib wrote:If you don't have any special reason to use AviSynth/FFmpeg set the FFmpeg as the primary transcoding engine (move it on the top of the list). FFmpeg is a default one for UMS.
Isn't AviSynth supposed to give higher quality though? Regardless, for the sake of discussion, why isn't AviSynth working and what do I need to do to get it working? And why do my settings work off a fresh install, then go haywire after I restart UMS?

Re: Odd Problem With ffmpeg

Posted: Sat Apr 25, 2015 9:55 am
by valib
Could you reproduce the bug with FFmpeg and upload the log?

Re: Odd Problem With ffmpeg

Posted: Sat Apr 25, 2015 10:26 am
by Dem0n
valib wrote:Could you reproduce the bug with FFmpeg and upload the log?
So, I changed the engine priorities to FFmpeg at the top again and tested and it failed as before. Out of curiosity, I then exited the program entirely and tested again and it worked. So it seems that a simple click of the "Restart Server" button isn't enough when you change transcode priorities (bug? oversight? I dunno). But, to reiterate, I'd like to get AviSynth working if possible.

Re: Odd Problem With AviSynth/FFmpeg

Posted: Sat Apr 25, 2015 7:32 pm
by ExSport
AviSynth is here for advanced users only or users who are using TrueMotion etc.
By default it is disabled as it adds another layer of possible problems.
AviSynth requires installed decoders on system and if they are missing, file will not play or with bad settings the output quality can be poor.
By default FFmpeg/MEncoder include all required things inside so there is no need to install or configure any additional codecs.
So general user should avoid using AviSynth totally as it can lead to unplayable file, bad quality, double subs, not working Audio/Subs peference in UMS etc. :idea: