Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
![]() |
#2542 | Link |
Registered User
Join Date: Jun 2005
Posts: 513
|
I've tried both NEDI and Super-xBR with SuperRes, the new SuperRes result in a very pleasant picture quality with NEDI, from 1024x576 -> 1920x1080 videos.
Super-xBR is too sharp, the edges of faces sometimes 'harder' than with NEDI. Also the new algorithm work great without the old rendering time increasing issue, which makes the MPDN an alternative to my choice of daily media players. |
![]() |
![]() |
![]() |
#2543 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Just a heads-up: Downloaded the standalone version of MPDN and the extension binaries and sources into new folders (using the links from the first post), copied the extensions in the right folders. But now both 32bit and 64bit MPDN complain with "One or more extensions failed to load". I had deleted the old "AppData" MPDN folder. Tried emptying the PlayerExtensions folder, didn't help.
|
![]() |
![]() |
![]() |
#2544 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,679
|
Quote:
I just downloaded latest x64 and x86 versions of MPDN and extensions from http://mpdn.zachsaw.com/Latest/ after completely uninstalling my old installation and I had no errors with either. You might want to try it again. |
|
![]() |
![]() |
![]() |
#2545 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
When only using the MPDN standalone version + the binary extensions, everything works fine. But when also extracting the binary source code and copying the binary source code "Extensions" folder over to MPDN, the problem occurs. I guess I'm not supposed to do that? Still, seems like something to look into. The first post looks like I should download and "install" all 3 (standalone version, extension binaries and extension sources). Maybe it would make sense to move the "extension source" to the "Miscellaneous" section on the first page, to make it clearer which downloads are necessary to make the standalone version work with all extensions? |
|
![]() |
![]() |
![]() |
#2547 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
|
|
![]() |
![]() |
![]() |
#2548 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Ah, now I understand! I can either use the binary or the source version of the extensions, correct? If that's correct, then the wording should be clear now. Might still make sense to investigate why it gets broken if you install both the binary and source version? I mean, maybe someone installs the binary version first, then wants to switch to the source version, or something. Would be nice if that would still work.
|
![]() |
![]() |
![]() |
#2550 | Link | |
Registered User
Join Date: Dec 2013
Posts: 753
|
Quote:
Can you install the sources with the installer by the way? Haven't had a chance to try it out yet. |
|
![]() |
![]() |
![]() |
#2551 | Link |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
No. The installer only installs the binary version. If we want auto update / update checker for the extensions, the only way is to have the binary version, which has a product version that is tied to github release version.
I'll see if there's a way to detect if a conflict has occurred but that's just one of the many mistakes users could make when using the source version. I think end users shouldn't be tinkering with the scripts anyway. Anyone interested in poking around should be knowledgeable enough to download the source from github. What we can do is perhaps distribute a readme with the binary version with instructions on how to get the source version. Anyone who's interested in poking around would surely have looked into the extensions folder and readme would be the first thing that stands out. |
![]() |
![]() |
![]() |
#2552 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Maybe you can detect the conflict and change the wording of the message box to guide the user in solving the conflict? E.g. point the user to the readme. The current message box text is very generic and sounds more like some extension is corrupt/damaged.
|
![]() |
![]() |
![]() |
#2553 | Link | |
Registered User
Join Date: Dec 2013
Posts: 753
|
Quote:
|
|
![]() |
![]() |
![]() |
#2555 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
The installer is really meant to make it easy for users who simply just want a media player and don't necessary even know much about image scaling, let alone tinkering with it ![]() |
|
![]() |
![]() |
![]() |
#2556 | Link |
Registered User
Join Date: Jun 2005
Posts: 513
|
With the upgraded version of Super-xBR, I cannot distinguish it from NEDI with SuperRes now. I'd say it becomes as good with one of my test video.
Edit: For other video clips, NEDI still more 'natural' for me. Last edited by Anima123; 28th June 2015 at 06:00. |
![]() |
![]() |
![]() |
Tags |
direct3d, mpdn, nnedi3, opencl, reclock |
Thread Tools | Search this Thread |
Display Modes | |
|
|