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. |
19th July 2014, 18:02 | #1 | Link |
Registered User
Join Date: Feb 2013
Posts: 68
|
aWarpSharp causing green on the sides of video
aWarpSharp(depth=7.5, blurlevel=1)
I have been using this filter for years and in the past this has never happened to me. It doesn't happen on my older computer when I use this, but when I use it on my newer computer it all of a sudden has green appearing on the sides like this. If you look close enough you can see it most under his arm and close to his elbows. Its easier to see with a dark background like in my album with more examples in it. http://imgur.com/a/0aOYW#0 I'm using the same exact plugins, the same exact programs and the same encoding method. Why would these only be showing up on my newer computer and not my older one? Whats the cause of these coming up all of a sudden? Its not just this source either, its happening on every source I try on my newer computer but not on my older computer. Last edited by killerteengohan; 19th July 2014 at 18:04. |
19th July 2014, 18:05 | #2 | Link |
Registered User
Join Date: Sep 2007
Posts: 5,377
|
No idea why it only occurs on some setups, but it's a known issue, use AwarpSharp2
http://forum.doom9.org/showthread.php?t=147285 |
19th July 2014, 18:37 | #3 | Link | |
Registered User
Join Date: Feb 2013
Posts: 68
|
Quote:
I've never seen or had a problem with the green on the sides before until just now on this newer computer. Same source on old computer with same plugins and programs, no green on the sides but there sure is on the newer computer. There's got to be some kind of reason for this coming out of nowhere I would think. Last edited by killerteengohan; 19th July 2014 at 18:41. |
|
19th July 2014, 18:51 | #4 | Link | ||
Registered User
Join Date: Sep 2007
Posts: 5,377
|
Quote:
Quote:
Eitherway, Awarpsharp2 fixes everything . |
||
19th July 2014, 19:12 | #5 | Link | |
Registered User
Join Date: Feb 2013
Posts: 68
|
Quote:
No I saw no such instructions about mapping. Can you tell me where to find them? I did however find a 2012 update recently posted not too long ago and that one seems to work better than the 2009 one I had tried a couple years ago. I used to have to type awarpsharp2() and the parameter depth= didnt exist but it seems like it works in the newer one. Can I use it just like the old awarpsharp with the same parameters and not get the green? Last edited by killerteengohan; 19th July 2014 at 19:21. |
|
19th July 2014, 21:17 | #7 | Link | ||
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
For some reason I could never get the original aWarpSharp to coincide with aWarpSharp2's aWarpSharp (different outputs). From my understanding there was an update to the original aWarpSharp some time ago.
Quote:
Quote:
|
||
19th July 2014, 21:35 | #8 | Link | ||
Registered User
Join Date: Feb 2013
Posts: 68
|
Quote:
I only have a 2003 version for awarpsharp and 2009 awarpsharp2, but I did find a 2012 one here. http://forum.doom9.org/showthread.php?t=147285 I realize its awarpsharp2 but from the updates description it might do what you said you couldnt get it to do just above. Quote:
|
||
19th July 2014, 21:46 | #9 | Link | |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Quote:
|
|
19th July 2014, 22:04 | #10 | Link |
Registered User
Join Date: Sep 2007
Posts: 5,377
|
It probably won't match up perfectly when you use decimal values, because depth parameter in awarpsharp2 only takes integer values. I think it rounds the value in the auto conversion when you call awarpsharp instead of awarpsharp2 (which gives you an error). That might be the reason behind the green borders in the first place
The mapping depth = depth*blurlevel/2 eg. old awarpsharp aWarpSharp(depth=7.5, blurlevel=1) 7.5 * 1/2 = 3.75 |
19th July 2014, 22:50 | #11 | Link |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Yeah that's probably one the reasons. In addition to that, the old aWarpSharp cm parameter defaults to 3 (included documentation is wrong) and there seems to be no valid mapping in aWarpSharp2.
Mapping chroma = 0->2, 1->4, 2->3 |
20th July 2014, 01:31 | #12 | Link |
Registered User
Join Date: Feb 2013
Posts: 68
|
I did notice if you crop a multiple of 16 off the sides like 10 off the right and 6 off the left, or whatever gets you a multiple of 16, the green goes away mostly or reduces alot but theres still obvious marks on the video, its just not bright green and overly apparent.
|
23rd July 2014, 09:28 | #16 | Link |
Registered User
Join Date: Aug 2007
Posts: 374
|
aWarpSharp2 is exactly the same algorithm as aWarpSharp, only with some bugfixes. If you are getting significantly different results – you are doing something wrong. Latest aWarpSharp2 supports aWarpSharp alias that remaps the parameter values automatically if you absolutely can't read the documentation.
Btw, aWarpSharp2 has integer parameters because algorithm uses actually integers, so again aWarpSharp2 is exactly the same as aWarpSharp, just removes the false feeling that slight change in float number changes something when it actually maps to the same integer inside. |
23rd July 2014, 14:45 | #17 | Link | ||
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,666
|
Quote:
Quote:
|
||
28th July 2014, 10:05 | #20 | Link |
Retried Guesser
Join Date: Jun 2012
Posts: 1,373
|
Because since WarpSharp works by averaging* pixels over a certain area, it can "drag" some of the black pixels into view.
*EDIT not averaging of course, poor choice of word. For any kind of sharpening or blurring, each output pixel will be affected by all its neighbor pixels. Last edited by raffriff42; 28th July 2014 at 12:46. |
Tags |
awarpsharp, green |
|
|