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.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 27th June 2015, 02:46   #2541  |  Link
Magik Mark
Registered User
 
Join Date: Dec 2014
Posts: 666
zach can we port super xbr in chroma upscaling? I'm getting nicer result compared to jincs in madvr
Magik Mark is offline   Reply With Quote
Old 27th June 2015, 04:47   #2542  |  Link
Anima123
Registered User
 
Join Date: Jun 2005
Posts: 504
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.
Anima123 is offline   Reply With Quote
Old 27th June 2015, 09:01   #2543  |  Link
madshi
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.
madshi is offline   Reply With Quote
Old 27th June 2015, 10:01   #2544  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,650
Quote:
Originally Posted by madshi View Post
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.
I've run into this a number of times and clearing out appdata and deleting the extensions folders before reinstalling has always fixed it.

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.
ryrynz is offline   Reply With Quote
Old 27th June 2015, 10:19   #2545  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,140
Quote:
Originally Posted by ryrynz View Post
I've run into this a number of times and clearing out appdata and deleting the extensions folders before reinstalling has always fixed it.

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.
I did all that. But I found what the problem was:

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?
madshi is offline   Reply With Quote
Old 27th June 2015, 12:14   #2546  |  Link
Shiandow
Registered User
 
Join Date: Dec 2013
Posts: 753
Quote:
Originally Posted by Anima123 View Post
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.
This is just getting weird now, but I'm glad that it works.
Shiandow is offline   Reply With Quote
Old 27th June 2015, 12:58   #2547  |  Link
Zachs
Suptitle, MediaPlayer.NET
 
Join Date: Nov 2001
Posts: 1,721
Quote:
Originally Posted by madshi View Post
I did all that. But I found what the problem was:

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?
I've changed the wording so hopefully that removes any ambiguities.
Zachs is offline   Reply With Quote
Old 27th June 2015, 13:01   #2548  |  Link
madshi
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.
madshi is offline   Reply With Quote
Old 27th June 2015, 13:04   #2549  |  Link
Zachs
Suptitle, MediaPlayer.NET
 
Join Date: Nov 2001
Posts: 1,721
Yeah that's correct.

I might just remove the source version from the download section actually. Advanced users can always download them from github.

@Shiandow what do you think?
Zachs is offline   Reply With Quote
Old 27th June 2015, 13:26   #2550  |  Link
Shiandow
Registered User
 
Join Date: Dec 2013
Posts: 753
Quote:
Originally Posted by Zachs View Post
Yeah that's correct.

I might just remove the source version from the download section actually. Advanced users can always download them from github.

@Shiandow what do you think?
It might be best to remove them if it prevents confusion, although I'm not too happy with making it harder for people to try playing with the code. If possible I'd prefer if MPDN detected such a conflict and asked to remove the binaries (or the sources but it's hard to tell if those have been edited).

Can you install the sources with the installer by the way? Haven't had a chance to try it out yet.
Shiandow is offline   Reply With Quote
Old 27th June 2015, 13:48   #2551  |  Link
Zachs
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.
Zachs is offline   Reply With Quote
Old 27th June 2015, 14:08   #2552  |  Link
madshi
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.
madshi is offline   Reply With Quote
Old 27th June 2015, 14:11   #2553  |  Link
Shiandow
Registered User
 
Join Date: Dec 2013
Posts: 753
Quote:
Originally Posted by Zachs View Post
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.
That might be a good compromise. I still think it's a shame that users would lose the ability to change the extension's behaviour by changing a few lines of code, but maybe nobody did that anyway.
Shiandow is offline   Reply With Quote
Old 27th June 2015, 14:12   #2554  |  Link
Zachs
Suptitle, MediaPlayer.NET
 
Join Date: Nov 2001
Posts: 1,721
Yeah that would be ideal. Just have to find out if it's possible to detect that it's a conflict and not any other errors...
Zachs is offline   Reply With Quote
Old 27th June 2015, 14:15   #2555  |  Link
Zachs
Suptitle, MediaPlayer.NET
 
Join Date: Nov 2001
Posts: 1,721
Quote:
Originally Posted by Shiandow View Post
That might be a good compromise. I still think it's a shame that users would lose the ability to change the extension's behaviour by changing a few lines of code, but maybe nobody did that anyway.
Oh I think the ones who frequent this thread know how to switch to the source version in a heartbeat when there's something they need / want to change.

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
Zachs is offline   Reply With Quote
Old 28th June 2015, 00:23   #2556  |  Link
Anima123
Registered User
 
Join Date: Jun 2005
Posts: 504
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.
Anima123 is offline   Reply With Quote
Old 28th June 2015, 15:56   #2557  |  Link
mrcorbo
Registered User
 
Join Date: Jan 2005
Posts: 171
Regarding extension versioning, prior to the binaries being implemented was using file hashing ever considered?
mrcorbo is offline   Reply With Quote
Old 29th June 2015, 02:29   #2558  |  Link
Zachs
Suptitle, MediaPlayer.NET
 
Join Date: Nov 2001
Posts: 1,721
Yes, but we wanted something more straight forward to start with. File hashing may still be implemented for the source version later. We don't even have an extensions version checker yet at the moment.
Zachs is offline   Reply With Quote
Old 29th June 2015, 14:24   #2559  |  Link
mrcorbo
Registered User
 
Join Date: Jan 2005
Posts: 171
Got it. I have some ideas about a possible process if you don't already have a mechanism in mind.
mrcorbo is offline   Reply With Quote
Old 29th June 2015, 14:26   #2560  |  Link
Zachs
Suptitle, MediaPlayer.NET
 
Join Date: Nov 2001
Posts: 1,721
Oh feel free to discuss here. Belphemur is the one looking into it.
Zachs is offline   Reply With Quote
Reply

Tags
direct3d, mpdn, nnedi3, opencl, reclock

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 12:20.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.