Paranoia: Bug Reports

incredible · #1 09-18-2005, 01:45 PM

Please do report bugs or issues in here.
Thanks

kwag · #2 09-18-2005, 01:48 PM

Thanks Andrej

danpos · #3 09-18-2005, 01:49 PM

@Andrej

THX mate!

I already got it!

Cya!

incredible · #4 09-18-2005, 01:54 PM

Please do first keep it in here so the very first known bugs will be fixed before it gets public for the ouside. Thanks

Prodater64 · #5 09-18-2005, 02:07 PM

Well done Inc.

rds_correia · #6 09-18-2005, 02:14 PM

Looking very good Andrej

.
You deserve a

.
This baby will surely become a must in my PEN disk.
Sorry but I've got too many things in hands, so no time to test it yet.
Nevertheless it's already in my HDD ready for action :P.
Cheers buddy

rds_correia · #7 09-18-2005, 02:29 PM

LOL
I said I wasn't going to test it right away, but I couldn't help it and I tried it just once

.
I went to the Source>Open D2V Source, browsed for my D2V project, clicked the name of the file xxxx.d2v and pushed the Open button.
But then I received a message saying

Code:

For decoding xxxxx.d2v the "decode.dll" is needed!
Make shure "dgdecode.dll" is included in "C:\Program Files\Avisynth 2.5\Plugins"

And then the tool did nothing!
Does it mean it is looking for the dgdecode.dll only in that specific path?
You see, all my videotools are installed in "c:\video\...".
Cheers buddy

PS: BTW the window that popped up that message showed "shure" instead of "sure", but that's obviously because of it's youth

.

rds_correia · #8 09-18-2005, 02:38 PM

It's confirmed.
I just copied all my c:\video\avs255 to c:\program files\avisynth 2.5 and now your tool works.
So it seems it's path dependent, which is not so bad after all.
As soon as I load the script on it my movie starts running.
At that time if I press "Esc" to exit the tool, it doesn't respond and keeps playing the movie.
Actually I needed to push the pause button (at the bottom) to be able to close the tool.
I'll keep bugging you with my experiences

.
BTW, you really have to come up with a name for this baby and choose a license for distribution

.
Cheers buddy

incredible · #9 09-18-2005, 02:39 PM

Yes, it looks for your windows Program path and there for /avisynth 2.5/plugins.

If that not works, put a copy of dgdecode.dll or MPEG2Dec3.dll in the applications folder.

also its forced that when playing no windowactions will be permitted except teh "pause" button, that makes it much more easy to keep out actions via gadgets when the movie is running.

digitall.doc · #10 09-18-2005, 02:58 PM

Woooow

. GrEaT pal

I just tested it. It's... incredible

Some ideas (sure no need to consider even a single one, but just in case you find them useful) after opening it once:
- I find it would be nice an exit button in main window (yes, it's in the menu, but... I advised I was not going to be very helpful) and later in avisynth script (if you don't preview or save, you need to exit) and in preview avs.
- In the info screen, you could highlight the PAR error (bold letters, or as in FitCD: blue OK, yellow hmmm, red: change settings)
- It would be nice to have more avisynth commands to use, and something like a preset, with those commands we use more often

A doubt: what does it mean Pix Detection threshold?

Good Inc, really good. Congratulation

kwag · #11 09-18-2005, 03:31 PM

I just tested several runs, and all I can say is

The cropping is just perfect

Congrats Andrej

-kwag

incredible · #12 09-18-2005, 04:35 PM

Quote:

Originally Posted by digitall.doc

- I find it would be nice an exit button in main window (yes, it's in the menu, but... I advised I was not going to be very helpful) and later in avisynth script (if you don't preview or save, you need to exit) and in preview avs.

Well an exit via menue-option and the upper right systemwindow-close button imho is enough as if I would add more buttons to the apps. surface, the main window will need to get even bigger.

Quote:

- In the info screen, you could highlight the PAR error (bold letters, or as in FitCD: blue OK, yellow hmmm, red: change settings)

Hmmmm ... in FitCD imho in its newer releases there even isnt any PAR error mentioned anymore.

Quote:

- It would be nice to have more avisynth commands to use, and something like a preset, with those commands we use more often

I do quote myself from my "to do" from the first post above:

Quote:

Originally Posted by Inc.

- Option for integrating readymade avs fuction templates into resulting scripts

but .... this will be not in the first priority but I had that Idea when adding the most needed functions like limiter(), converttoXXX() etc.
Also I was searching for a syntax-highlightning procedure for purebasic so that I could use one of these syntax-templates available at avisynth.org

incredible · #13 09-18-2005, 04:38 PM

@ Karl
The cropping is doing fine now, yep.
But I want to make it possible to enter the final vertical resize (you already can see the spin-option in that little gadget where the vertical resize result is shown. So we can choose for example if 720>704 will be resized or cropped.

kwag · #14 09-18-2005, 05:08 PM

Thanks Andrej.
Here, I just encoded a small 30 second or so KDVD sample with your program, using overscan factor of 2, anamorph->non-anamorph, just to see how it came out

http://sr2.mytempdir.com/164369

-kwag

digitall.doc · #15 09-18-2005, 05:10 PM

well Inc... they where just a few simple ideas.

Again, very nice tool.

incredible · #16 09-18-2005, 05:21 PM

Quote:

Originally Posted by digitall.doc

well Inc... they where just a few simple ideas.

Again, very nice tool.

And I did apreciate them! Go further on!

@ Karl

DONT trust that baby in this state 100% as I didnt had the possibility to check several NTSC inputs, the only VOB I do have is the RedPlanet chunk you gave me a time ago

EDIT: Ahhhh, saw your sample: RedPlanet ... seems to be your main testing object.
But it seems you did apply a resized overscan on that 2.35:1 source?

kwag · #17 09-18-2005, 06:19 PM

Quote:

Originally Posted by incredible

EDIT: Ahhhh, saw your sample: RedPlanet ... seems to be your main testing object.

I always use that for consistency

That way, I can compare to past encodes

Quote:

But it seems you did apply a resized overscan on that 2.35:1 source?

Yes indeed!
I just wanted to see the crop/resize result

Not bad for a CQ of 75, MIN 300, MAX 6,000 and no filters at all

From your program, safe (save?) script:

Code:

dgdecode_mpeg2source("H:\RED_PLANET\VIDEO_TS\video.d2v",cpu=6)
BicubicResize(672,256,0,0.6,6,58,708,362)
Addborders(16,112,16,112)

-kwag

fabrice · #18 09-18-2005, 11:55 PM

Hi Inc,

Thanks for that great program: I'm sure it will replace fitcd and manual cropping from now on!

Quote:

Originally Posted by incredible

Yes, it looks for your windows Program path and there for /avisynth 2.5/plugins.

If that not works, put a copy of dgdecode.dll or MPEG2Dec3.dll in the applications folder.

And what about reading the registry key that store plugin path (HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth\plugindir2_5 )? Or simply ask the user?
In my case, it don't matter, as I don't put any plugin in the plugins directory (fot stability and speed reason), and I have to copy it!

Thanks,
Fabrice

incredible · #19 09-19-2005, 03:55 AM

Quote:

Originally Posted by fabrice

And what about reading the registry key that store plugin path (HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth\plugindir2_5 )? Or simply ask the user?

A very good hint! I didn't know that its mentioned in the registry where the plugins folder does exist.

@ General
I found out that theres still a bug when loading a 704x576 source where the output will be 720x576, even its not the common procedure, the result is false! So the calculator still isn't perfect as mentioned above.

FitCD for shure is an excellent appl. as it gots its own things which this apll. doesnt have, means a total tweakable calculator. This appl. was meant to be a more comfortable one incl. some nice helping functions.
It wasn't my intention to stay in a clear concurrency to FitCD

And at least "in the state of" now FitCD is prooven to be far more accurate as this one in its beta state, so please do use this appl. to check/report bugs and still use FitCD for confiable resizing outputs up to the time when this appl. is more proofed.
Thanx

digitall.doc · #20 09-19-2005, 04:26 AM

You're right when clearing things related to FitCD, even I also think your tool will be more useful for me (and sure for others).

I'm sorry to come again with a comparison with FitCD, as you want us to consider them as different tools. Yes, in FitCD it doesn't say a thing about PAR error, but it gives a Crop AR/Resize AR that I guess is similar. And this number appears in black if OK, yellow or red. This is what I refered to when suggesting you could put PAR error in bold or colors. But the info is anyway there, so you can forget it.

I keep in a doubt: what does it mean Pix Detection threshold?. What efects can we expect if we change it?.