Thanx both Inc and Rui. I see I'll have to update my tools.

If there's any trouble in the code, I'm sure you'll fix it in a second, Inc.

Good job.

Inc, I tried now with DGIndex 1.43, and here is the first lines in my d2v:

It's still recognized as 16:9 by d2vReader-0.02b, so I'm afraid it's not an old version DGIndex issue. :(

Hey, Doc.

Im very busy these days and Im going to Nizza from sunday till thursday, so Ill "enter" a d2v file, changing the AR line to 4:3 and see what happens.

So main bug fixing wont be possible before next week/thursday. :)

Andrej, I hope you travel on a nice free weekend.

Have a nice time!.

"See" you when you come back "home" :lol: .

Some Bugs have been fixed

Version 0.03b
http://home.arcor.de/packshot/d2vReader_0.03b.exe

Read the changelog in the first post.

Hi Andrej,

Downloaded!
Title still says 0.01, though :)

-kwag

it IS 0.03 8O Ill fix the name immediately :)

Hi Inc,
so you're back. First congratulations: I don't know if you're a basketball fan, but germany has just beat spain in EuroBasket. It was a nice game WE played better and deserved to win... but this is basketball.

Well, related with last update, it doesn't work well for me now. Even when I keep a copy of dgdecode both in d2vreader and in avisynth plugin folders, it complains about dgdecode missing, and doesn't preview nor crop. Frame count 1234567890.

I can see the generated script, and when I preview the script it plays properly. But I can get anything else to work... :(

Im still here, the trip starts tomorrow morning, thats why I had some time to get into some bugs.

Many people did report that there where bugs finding the location of the used dll for decoding d2v files. So I got a hint to parse the registry and there the value in "Avisnth" which shows the correct plugins folder location on your system.

BUT! I do see that maybe some users did move that avisynth fodler after installation to a diff. location, which makes the registry string senseless.

So I did at least make the Errormessage outputting now WHERE the Avisynth plugins/dgdecode.dll "should" exist as read out of the users registry.

Please do upload 0.03b again:
http://home.arcor.de/packshot/d2vReader_0.03b.exe
... as the message will be more informative about the plugins path now. ;) No other chages have been made so I didnt release a higher number.
When the Error appears, do make a screenshot and post it in here.
Then I'll see whats recognised as your avisynths plugins folder.

Thanks for your tests doc!

THEN when you gave me the screenshot from the erormessage of 0.03b you can do the next step downloading and testing 0.04b:

In 0.04b I did implement a check routine that if the registry does output a path which doesnt contain the dll, then at least the location of the apps. current folder will be used (as it had to).

http://home.arcor.de/packshot/d2vReader_0.04b.exe

Well Inc, this is the first time I upload a screenshot (thanks ImageShack for hosting it), I hope I won't do anything wrong. Here it is:
http://www.digitalfaq.com/archives/error.gif

As you can guess, in this path:
I've got an updated copy of DGDecode.dll.
I see your path lacks a "\" between plugind and DGDecode. I don't know if it's of any importance...

And finally, v.0.04b worked OK. It also shows correctly that source is 4:3 AR.
8)

Inc, every film I backup I test your nice tool, and compare output with that of FitCD (in case FitCD is to be considered as a reference...)

I got different results in a film. I don't know if it's important at all.
With d2vreader:
With FitCD:
Both were tuned the same way: accurate cropping round to 4; 2 blocks of overscan/resize; resize macroblock optimized round to 16; anamorph source and destination,...
I took film area from your tool: 684x576

Both options look quite similar, so I don't think it's of an importance. But I post in case it helps you.

Cheers.

shh did a Trick ("seems" like a cropping barrier).
As you see in "my" calcs the height gets cropped more to fit the MOD16 at width and height finally. So FitCD does "disrespect" the MOD16 at least at the Width to keep as much mixels as possible in the height. THATS why imho for shure both outputs dont look similair, as FitCD does apply right an left borders of 24 each when selecting 2 Blocks of Overscan.

So its your decision what you do prefer.

Ill implement in the Appl. a Preferences Option where a user can choose a "HQ Crop/Resizing" including a less interpolated (via resizing) result or a "forced for compression at its best" result which for shure will result in more resizing and therefore in more interpolation --- and thats what most peolpe are used to do (Mencalc, Moviestacker, GripFit, FitCD) which makes sources blurrier.

Update...

http://home.arcor.de/packshot/d2vReader_0.05b.exe

See changelog in first post for details.

:ole: :D

-kwag

This weekend is updating weekend :lol:

New Release:
http://home.arcor.de/packshot/d2vReader_0.06b.exe

- Resizing core obtained some "check" modes for more userfriendly results
- Generic Par Mode can now be choosen above under "Settings" (more settings will be added and able to be safed as ini soon).

Generic par is related to the "Keep ITU...." Option.
Means with that u can fix a bad par source as known from FitCD.
Sometimes even DVDs are digitized at 702 or 704 and encoded at 720.
That bug also often happens when noobs do take a 704 source and do a 720 directly-resized out of it also vice versa 720 to 704.

So 720 encoded using a generic PAR would end up in a correct picture IF it would be just resized in its width on the TV o 768 PAL or 640 NTSC, ... but no SAP will do that. Thats why this ITU Box is included in FitCD and in this appl.

Update:

http://home.arcor.de/packshot/SizeMe_0.07b.exe

see changelog in the first post.

mpeg4 target size supported!

Thanks, Incredible
 

Hi Andrej !! Thanks for the continuous upgrade, you're superb!! One information: BJ_ from BDVD Team has a tool also named "Size Me". :o

JFYI.

Cya!

@Incredible

How about calling it "Super Size Me" :D

:lol:

That is not the same that "Me? Super size!"

:rotf: :rotf: :rotf: