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 > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 4th January 2018, 11:07   #21  |  Link
thecoreyburton
Guest
 
Posts: n/a
Thanks for all your help, and apologies for the slow response (I was testing the script out on the full source)! That last script is much more successful than the first. At a glance, I almost didn't notice anything wrong. I did manage to find a case (14.5kb) where the screen is dark and the line is not detected, but other than outliers such as this it seems good (and in theory, the contrast of the detection clip could be boosted to perhaps overcome this). I really appreciate all the effort.

Quote:
Originally Posted by creaothceann View Post
the garbage might disappear if you disable anti-aliasing in your GPU's driver settings?
No luck, unfortunately. It might be a case of requiring profile inspector and antialiasing compatibility, but the viewport is already wildly inaccurate and I don't think a single pixel off each side isn't going to matter much. I can play with the plugin's settings via registry, but at this point I've had to resync the entire clip multiple times and don't really want to volunteer for anther nightmare haha.

Last edited by thecoreyburton; 4th January 2018 at 11:19.
  Reply With Quote
Old 4th January 2018, 20:20   #22  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
Quote:
where the screen is dark and the line is not detected,
Is detected for me with the default args as given.

EDIT: Frame 16 (last frame 16 of frames 0->16)
Code:
When adding last sample frame to previous given 16 frames (was slightly different Framerate).

From DebugView if giving Debug=True to RT_YInRangeLocate (I added to the script)


RT_YInRangeLocate:  16] Top    1 : x1=1    y1=1    x2=638  y2=407   638x407  (outer edge passing Th : 100.000% 638.0 pixels)
RT_YInRangeLocate:  16] Bot  407 : x1=1    y1=1    x2=638  y2=407   638x407  (outer edge passing Th : 100.000% 638.0 pixels)
RT_YInRangeLocate:  16] Lft    1 : x1=1    y1=1    x2=638  y2=407   638x407  (outer edge passing Th : 100.000% 407.0 pixels)
RT_YInRangeLocate:  16] Rgt  638 : x1=1    y1=1    x2=638  y2=407   638x407  (outer edge passing Th :  99.754% 406.0 pixels)
RT_YInRangeLocate:  16] Perimeter no recan detect @ x1=1 y1=1 x2=638 y2=407 (638x407)
RT_YInRangeLocate:  16] Successful Detection @ x1=1 y1=1 x2=638 y2=407 (638x407)  # Height 407 (excluding scanline 0, so total 408 lines)
RT_YInRangeLocate:  16] Returned Locals YIRL_X=1 YIRL_Y=1 YIRL_W=638 YIRL_H=407

From MyLog.log

0] Line = 384 (pop=100.00%)
1] Line = 384 (pop=100.00%)
2] Line = 324 (pop=100.00%)
3] Line = 384 (pop=100.00%)
4] Line = 324 (pop=100.00%)
5] Border NOT FOUND
6] Line = 384 (pop=100.00%)
7] Line = 204 (pop=100.00%)
8] Line = 84 (pop=100.00%)
9] Border NOT FOUND
10] Line = 384 (pop=100.00%)
11] Line = 384 (pop=100.00%)
12] Line = 384 (pop=100.00%)
13] Line = 384 (pop=96.55%)
14] Line = 384 (pop=90.44%)
15] Line = 384 (pop=90.60%)
16] Line = 384 (pop=76.02%)
Did you change args at all, and to what ?

EDIT: Debugview logging was from RT_Stats v2.0 beta.

EDIT: Maybe RT_Stats v2.0 was the difference, can you try with that one (I know you said you had put it in plugins).
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

Last edited by StainlessS; 4th January 2018 at 20:33.
StainlessS is offline   Reply With Quote
Old 5th January 2018, 02:44   #23  |  Link
thecoreyburton
Guest
 
Posts: n/a
It was a codec / pixel format problem on my end, sorry. The dump itself uses FFV1 and AVISource was incorrectly guessing that this clip was YV12. If I specify the correct pixel format, the detection works just fine (I compared it to a short Lagarith dump of the source itself using subtract to locate any differences). I didn't consider this until you mentioned it detecting okay for you because we'd been using Lagarith for the tests.
  Reply With Quote
Old 5th January 2018, 02:53   #24  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
Nice, job done I hope.
Have a great year, have a better than great life.
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???
StainlessS is offline   Reply With Quote
Old 5th January 2018, 03:07   #25  |  Link
thecoreyburton
Guest
 
Posts: n/a
Thank you! You too, StainlessS.
  Reply With Quote
Old 16th January 2018, 13:34   #26  |  Link
thecoreyburton
Guest
 
Posts: n/a
Unfortunately, it looks like I've ran into another (and hopefully, final) problem. When selecting random test frames, everything works as expected but when starting the full source from the beginning I get the following on-screen prompt:
Quote:
I don't know what "i" means
([GScript], line 47)
([GScript], line 54)
([GScript], line 68)
([ScriptClip], line 2)
Here's the newest test clip (provided in full frame as the size was small enough).

Quote:
for(j=i-1, 0, -1) {
The above (line 37) seems to be where the problem is occurring. It looks like i is undeclared when referencing the new test frames, but it's fine when using the old test frames. I suspect it's something to do with the background being entirely black and am currently trying to work this out myself (I'll edit this post if I have any luck). Sorry to bother you again.

Last edited by thecoreyburton; 16th January 2018 at 13:44.
  Reply With Quote
Old 16th January 2018, 17:17   #27  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
Oops, sorry. Think I changed something and condition to reveal the mistake never occurred and so did not notice the error.
Should I think be

Code:
for(j=Line-1, 0, -1) {
Untested, and about to leave the house, hope it works ok.
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???
StainlessS is offline   Reply With Quote
Old 17th January 2018, 01:48   #28  |  Link
thecoreyburton
Guest
 
Posts: n/a
That's alright! Line removal still works the same and the error message no longer pops up. Looks like it worked. Thank you once again.
  Reply With Quote
Reply

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 09:01.


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