Auto Gordian Knot: current version 2.55 [Archive] - Page 97

yetanotherid

13th March 2011, 05:14

One thing to keep in mind......
AutoGK does it best when cropping and resizing not to distort the picture in any way, which is why it crops the way it does. Forgetting about the actual video dimensions for a moment.... I'm referring to objects in the video. For instance if an object is perfectly round in the original video then it should also be perfectly round in the encoded video. That's why AutoGK lets you pick the width but it adjusts the height itself.

If you were to take your 640*??? encodes and manually resize them all to 640*272 (without cropping extra to compensate) then you'd be distorting the picture, or squashing it down. Many other conversion programs allow you to do so, and in fact most other programs will distort almost every encode a little to squish it into mod16 dimensions (even if it's usually only by a small amount), but AutoGK tries not to. That's why I keep asking if the encodes really need to be the same dimensions... because maintaining the original shape of objects in the video should be more important than the dimensions of the video itself.

kalehrl

13th March 2011, 10:37

AutoGK actually resizes and crops quite intelligently so it won't crop extra from the height or distort the aspect ratio to fit particular resized dimensions, so as long as it's not over-cropping for some reason (which it rarely does) there's actually no need to check the height of the video in advance.

I always check the height of the video in preview because it is sometimes, but very rarely, necessary to enable 'force itu resize method' to get the right aspect ratio.
I mainly encode DVB-S recordings and I once found myself in a strange situation.
I was sure the film was 16:9 and by setting the width to 624, I expected the height to be 352.
But it wasn't, it was 368.
Only by enabling the itu thing was I able to get the heigth of 352 and thus the correct aspect ratio.

yetanotherid

13th March 2011, 19:52

I was sure the film was 16:9 and by setting the width to 624, I expected the height to be 352.
But it wasn't, it was 368.
Only by enabling the itu thing was I able to get the height of 352 and thus the correct aspect ratio.

The question would be, did the picture in the encoded video look the same as the original, rather than what the final dimensions (width & height) might have been (see my previous post).

For instance I've encoded episodic DVDs in the past, and after cropping and resizing, one episode may have been 704x400 while another was 704x416. Yet they both came off the same disc so I'd assume the same pixel resizing method was used for both episodes. I recently encoded a series of old 4:3 aspect ratio TV episodes. Some episodes needed more cropping from the sides than others, so for those episodes more cropping was also required top and bottom in order to keep a 4:3 display aspect ratio, yet they all came from the same disc.

I've not encoded any DVB-S recordings so I don't know anything about what pixel aspect ratios they'd use, but..... because AutoGK crops, resizes and then crops again if necessary to maintain the aspect ratio....

What if after cropping and resizing, the real video dimensions were 618x352. You asked for a width of 624, so AutoGK would have (effectively) resized the whole picture up to 646x368, chopped another 11 pixels from each side and given you 624x368. Not as close to 16:9 dimensions, but the picture wouldn't have been distorted.
Or.... you change the resize method so AutoGK still crops the same amount from the sides before resizing, but now it resizes the image differently so the end result is 630x352 (I'm just making the numbers up for the exercise so they're probably not exact). No need to resize the image up this time, so AutoGK just chops three more pixels from each side and you end up with 624x352. But which one is really the correct aspect ratio?

Using a program other than AutoGK, and using my above example, most would probably have either (effectively) stretched the 618x352 video to fit into 624x352 dimensions or they'd squish the 630x352 video (after using the ITU resize method) to fit into 624x352 dimensions, and while in both cases it mightn't be noticeable, either way the picture would have been distorted a little. AutoGK, on the other hand, crops in order to resize more exactly, so I guess it has the potential to either not distort the picture at all, or distort it even more than other conversion software might, depending on whether the resize method you pick is the correct one.

kalehrl

13th March 2011, 20:46

The question would be, did the picture in the encoded video look the same as the original, rather than what the final dimensions (width & height) might have been (see my previous post).
I think the encoded image was a bit streched vertically which is mentioned in the AutoGK tutorial:
Simple user guide for this option is: if you feel like your encodes come out a little bit stretched vertically then turn this option on, otherwise leave it off.
I can't remember the name of the film but I am sure it was 16:9 (1.77) and the channel broadcasting it was a specialised movie channel with 16:9 aspect ratio and high bitrate.
I also think no cropping took place so at first I was puzzled by the chosen resolution before I read the manual more carefully and found the ITU option.

I also used MeGUI to index the film and in the avisynth script editor I could choose 16:9 ITU and 'normal' 16:9.
When I chose normal 16:9, and autocrop and then chose the 624 width, I also got the 368 height.
But, when I chose 16:9 ITU the height was as it should have been 352.
That convinced me that the key was in the ITU option.

But I had to use this option only once or twice so very rarely.

yetanotherid

13th March 2011, 21:27

I think the encoded image was a bit streched vertically which is mentioned in the AutoGK tutorial

In that case you probably picked the right method. I was just trying to make the point that the resize method you choose and the final video dimensions don't necessarily directly relate.

I also used MeGUI to index the film and in the avisynth script editor I could choose 16:9 ITU and 'normal' 16:9.
When I chose normal 16:9, and autocrop and then chose the 624 width, I also got the 368 height.
But, when I chose 16:9 ITU the height was as it should have been 352.
That convinced me that the key was in the ITU option.

I'm not sure I quite understand that logic. The difference between using the ITU resize method and the non ITU resize method is the shape of the original pixels and therefore the dimensions the video will be resized to, but whichever program you use the picture will be resized in exactly the same way if you use the same resizing method, so all else being equal... using the same resize method while converting with 6 different programs should give you 6 encodes of the same dimensions. However, it could be wrong all 6 times.

By the sound of it though (from your description of the encodes looking stretched vertically) changing to the ITU resize method was probably the right choice, but when it comes to DVDs at least, a 16:9 aspect ratio DVD isn't really 16:9 when you use the ITU resize method. It's actually about 1.823 (slightly different for PAL and NTSC) which stretches it horizontally a little compared to a straight 1.778 resize. Hence it fixed the problem of the video looking stretched vertically, but I'd guess some cropping took place which took you back to dimensions close to 16:9.

You can confirm the different display dimensions according to the resize method used by looking at the numbers next to the various resize options MeGUI gives you. The same applies when resizing 4:3 aspect ratio DVDs using the ITU resize method. The display dimensions aren't really 4:3.

yetanotherid

13th March 2011, 22:03

But I had to use this option only once or twice so very rarely.

Which is also the point I'm trying to make. You may need to use the option sometimes, but in your case you might be using it for the wrong reason.

Edit: If you're still around kalehrl, have a read of my post #4810 below. Working out the manual cropping for Wu-Tang is a perfect example of the difference between dimensions of an encode simply because the cropping was different by just a few pixels.
Both of the resulting output dimensions 640x272 and 640x288 have maintained the original picture aspect ratio, but a few pixels of extra cropping forced AutoGK to resize the image to the next mod16 height up and then automatically crop a few more pixels from each side to keep the picture aspect ratio intact.

Wu-Tang

13th March 2011, 22:07

manono
Ok, i understand.

yetanotherid
I had a problem at one stage getting MPC-HC to open AVISyth scripts. It seemed to only effect newer versions of the player but I guess it's possible your problem is related.
Try navigating to the AVISyth installation folder, then look in the plugins folder. By default, I think there's only two plugins:
DirectShowSource.dll and TCPDeliver.dll. If there's any other plugins, try moving them to a safe place and see if you can then preview a video.
At one stage I let ffdshow install some plugins but with them installed I couldn't use MPC-HC to open AVISynth scripts. Once I deleted them I could. I don't know why.
Look at:
http://i010.radikal.ru/1103/57/d159cce15bb9t.jpg (http://radikal.ru/F/i010.radikal.ru/1103/57/d159cce15bb9.jpg.html)
ffdshow i don't install.
What still do i can to do? Preview don't work also.
Oh, i translate your posts, but i have a some question.
I sent PM with sample of dvd length near 1 minute.
You'll have to manually adjust the cropping. It's not unusual for different video on a DVD to have different aspect ratios so AutoGK is probably cropping them correctly. If you want them to all be the same you'll have to manually crop extra from the height but you're going to have to crop a fair bit of picture because there's quite a difference between them. When you compare the encodes with the original video from the DVD, is all the picture still present? Is the height of the original DVD video all the same (ignoring any black bars)? If AutoGK didn't over-crop any of them.....
I want to do manually crop, but i don't know how pixels i must croping.
Your question i don't may to translate.
The 640*272 video is your starting point. You can't increase it's height unless you want to keep some of the black bars so you'll need to crop some extra picture from the other two.
With one of them open in AutoGK use CTRL+F9 to open it's hidden options. Tick the "Tune auto crop parameters" box. In the "Force cropping of" area increase the cropping of the top and bottom by a few pixels (they should all be on zero). Hit okay and run a preview. If the dimensions are still greater than 640*272 then go back to autocropping and increase it a little more. Run the preview again.
At first i must to do to work preview.
If you can't get the preview function to work then you can try using another program to work out the cropping required. My favourite for doing so is HDConvertToX because it's one of the few programs which still calculates the aspect ratio distortion as you crop, so you can keep the aspect ratio as close to the original as possible by adjusting the cropping accordingly.

If you were to open the video with HDConverttoX and set the width to 640, you can then adjust the top and bottom cropping while watching HDConvertToX adjust the height until it's what you want. You can then use those cropping values in AutoGK by adding them to AutoGK's forced cropping option. Or you can just use HDConvertToX to convert the video. If you add the cropping values to AutoGK manually you'll need to disable AutoGK's auto cropping by changing the auto cropping threshold to zero.
Yes, i have a this tool, but i don't try to work in.
So you know..... when auto cropping is enabled AutoGK will auto crop, then it will crop the extra according to the amount of forced cropping you add. So cropping will be autocrop + forced cropping = total cropping.

By disabling auto cropping (changing the threshold to zero) the amount cropped will be the amount of forced cropping only. Hopefully that makes sense.
Yes-yes, i would to want to do it, but i don't know what value in pixels to select.
One thing to keep in mind......

AutoGK does it best when cropping and resizing not to distort the picture in any way, which is why it crops the way it does. Forgetting about the actual video dimensions for a moment.... I'm referring to objects in the video. For instance if an object is perfectly round in the original video then it should also be perfectly round in the encoded video. That's why AutoGK lets you pick the width but it adjusts the height itself.
I understand it so i want to do true all.
P.S Thank your very much for your help.
P.S. I want to sent you PM, but i saw: ((((((
yetanotherid has chosen not to receive private messages or may not be allowed to receive private messages. Therefore you may not send your message to him/her.

CWR03

13th March 2011, 22:27

I want to do manually crop, but i don't know how pixels i must croping.
Use Gordian Knot to crop. Transfer those numbers into AutoGK.

yetanotherid

14th March 2011, 02:37

Yes, i have a this tool, but i don't try to work in.

It's pretty easy. Open the video with HDConvertToX. You'll need to install ffdshow and enable the mpeg2 decoder.
When it opens the video HDConvertToX will automatically crop it. Change the width to 640. Now adjust the top and bottom cropping until the height changes to the desired height. HDConvertToX will calculate the aspect ratio distortion as you crop (which is why I like using it). When you reach the desired height adjust the cropping so that the aspect ratio distortion is as low as you can get it. Take the cropping values from HDConvertToX and use them as the forced cropping values in AutoGK, after changing the auto crop threshold to zero.

Or you can use HDConvertToX to convert it for you.

It'd be much easier if the AutoGK preview function worked but I'm at a loss as to why it's not. Maybe try uninstalling AVISynth and re-installing it. Are you using the latest version of AutoGK?
You can download AVISynth separately here: http://sourceforge.net/projects/avisynth2/
I'm not sure that's the problem though given you can convert the video but just can't open a preview.

You should be able to send me a PM now.

yetanotherid

14th March 2011, 08:16

Okay, I downloaded the samples. When I tried converting each one, the first three gave me the same dimensions. Only the fourth was different. However they all looked like they should have been cropped the same, but AutoGK didn't crop the right side of the fourth one properly. After looking a few times I discovered what I think was messing with the auto-cropping. Here's a picture with the colour enhanced to make it obvious.

http://i10.photobucket.com/albums/a142/dashpb1/1.jpg?t=1300086142

It's a screen shot of the bottom right hand corner and the little coloured box appears intermittently (it just flashed quickly). I'm not sure what that's about but it's probably why AutoGK wasn't cropping properly.

I worked out your manual cropping amounts. There's two choices because AutoGK's resizing method gives you different dimensions according to which one you use. The first:
Left 16, top 78, right 22, bottom 80.
Using that cropping you'll always get a 640x272 output but you'll retain a few pixels of the black bars either side. They're not sharp so it just makes the sides of the picture appear a little fuzzy if you look closely.

Cropping number two:
Left 18, top 78, right 24, bottom 80. As you can see there's only two more pixels cropped each side but it forces AutoGK to resize to the next mod16 height so it'll always give you 640x288. This cropping cuts the black bars completely from the sides but it also cuts an extra bit of the picture each side. Around 6 pixels of picture each side, I'd guess.

I'd prefer to use the second cropping because I'm obsessive about sharp edges around the picture but either cropping will give you the same dimensions as long as you use the same one each time. Don't forget to change the auto-cropping threshold to zero.

kalehrl

14th March 2011, 14:42

Both of the resulting output dimensions 640x272 and 640x288 have maintained the original picture aspect ratio, but a few pixels of extra cropping forced AutoGK to resize the image to the next mod16 height up and then automatically crop a few more pixels from each side to keep the picture aspect ratio intact.

Yes, I'm aware of this and sometimes if a channel has a logo in a black bar, autocrop will leave it so I must use megui to work out cropping and then enter the values in autogk.
This often results in a part of picure being cropped from the sides which you mention and which I try to avoid.
Still, autogk is my favourite because of compression test and the simplicity megui lacks.

yetanotherid

14th March 2011, 15:20

Still, autogk is my favourite because of compression test and the simplicity megui lacks.

Yeah, I'll agree there. I still prefer AutoGK for creating AVIs despite it's age, although I'll admit my AVI days are almost behind me (except when I convert something for someone else in the house). These days I always use MeGUI and anamorphic x264 encoding for DVDs because the quality is better.

Wu-Tang

15th March 2011, 17:50

CWR03
Use Gordian Knot to crop. Transfer those numbers into AutoGK.
And there how?
yetanotherid
Hi,
It's pretty easy. Open the video with HDConvertToX. You'll need to install ffdshow and enable the mpeg2 decoder.
When it opens the video HDConvertToX will automatically crop it. Change the width to 640. Now adjust the top and bottom cropping until the height changes to the desired height. HDConvertToX will calculate the aspect ratio distortion as you crop (which is why I like using it). When you reach the desired height adjust the cropping so that the aspect ratio distortion is as low as you can get it. Take the cropping values from HDConvertToX and use them as the forced cropping values in AutoGK, after changing the auto crop threshold to zero.
I try to use it and some don't understand.
1) I open the file and see - http://i015.radikal.ru/1103/b2/852f348e1ecdt.jpg (http://radikal.ru/F/i015.radikal.ru/1103/b2/852f348e1ecd.jpg.html)
2) Then i select aspect - http://i062.radikal.ru/1103/33/d3f50489fc1ft.jpg (http://radikal.ru/F/i062.radikal.ru/1103/33/d3f50489fc1f.jpg.html)
I select 16, 24, 78, 80.
3) And I will go mad. )))
http://s008.radikal.ru/i306/1103/5e/2dde540a5643t.jpg (http://radikal.ru/F/s008.radikal.ru/i306/1103/5e/2dde540a5643.jpg.html)
What is it: crop obey to ar, ar error, set mod block, anamorphic shape.
So, this tool select second side - 400, why?
I try to convert with 16, 24, 78, 80 - http://s005.radikal.ru/i209/1103/8a/531a3194e17at.jpg (http://radikal.ru/F/s005.radikal.ru/i209/1103/8a/531a3194e17a.jpg.html)
And I receive 640*272, but if i select as you write - 18, 24, 78, 80 - i receive 640*288 yet. Difference only 2 pixels. Delirium!!!
4) Also i try to use dvd2avi - http://www.softportal.com/get-4090-dvd2avi.html
It's select 16, 24, 80, 80, it;s show after convert will 640*288, but i try with that preference and give 640*272, tool was trick me!
5) I worked out your manual cropping amounts. There's two choices because AutoGK's resizing method gives you different dimensions according to which one you use. The first:
Left 16, top 78, right 22, bottom 80.
Using that cropping you'll always get a 640x272 output but you'll retain a few pixels of the black bars either side. They're not sharp so it just makes the sides of the picture appear a little fuzzy if you look closely.
Cropping number two:
Left 18, top 78, right 24, bottom 80. As you can see there's only two more pixels cropped each side but it forces AutoGK to resize to the next mod16 height so it'll always give you 640x288. This cropping cuts the black bars completely from the sides but it also cuts an extra bit of the picture each side. Around 6 pixels of picture each side, I'd guess.
Why because of two pixels such difference?
6) Now about preview
It'd be much easier if the AutoGK preview function worked but I'm at a loss as to why it's not. Maybe try uninstalling AVISynth and re-installing it. Are you using the latest version of AutoGK?
You can download AVISynth separately here: http://sourceforge.net/projects/avisynth2/
I'm not sure that's the problem though given you can convert the video but just can't open a preview.
Yes, i installed new avisynth and i use autogk 2.55.
But preview doesn't work neither in autogk nor in HDConvertToX. http://i.smiles2k.net/angry_smiles/banghead.gif
Thank you very much for your help. http://i.smiles2k.net/aiwan_smiles/good.gif

yetanotherid

16th March 2011, 02:38

I'm out of ideas as to why you can't preview AVISynth scripts. (When you preview using AutoGK or HDConvertToX you're effectively opening the AVISynth script they create with Media Player Classic. For some reason it won't open the scripts on your system and I'm out of ideas as to why).

HDConvertToX probably selected 400 as the height when you enabled anamorphic encoding. It's a whole different subject but instead of resizing the MPEG file down to square pixel dimensions it uses the same non-square pixels as the original video. When encoding to AVI square pixels are generally used so the height of the video is reduced to maintain the aspect ratio.

"Why because of two pixels such difference?"

AutoGK lets you pick the width but it actually resizes to the closest matching height. After it's resized it then crops extra from the sides if necessary in order to not distort the picture (remember the width and height have to be multiples of 16).

Try this very rough image as an example. The inner rectangle is the 640x272 video. The outer rectangle is the next height up. It might be 670x288. By cropping an extra four pixels from the sides you forced AutoGK to resize to the next height up because it could no longer give you a width of 640 with a height of 272. In order to give you a width of at least 640 the height needs to be 288. The blue area each side is the extra picture you lost, partly because you chose to crop a little more yourself, and partly because AutoGK had to automatically crop a little more also to give you a width of 640.
Sometimes, the difference between two heights (272 and 288) is only a couple of extra pixels of cropping.

http://i10.photobucket.com/albums/a142/dashpb1/1-1.gif?t=1300239335

When cropping an extra few pixels other conversion programs will often just stretch the video a little to make it 640 again. AutoGK doesn't do that.

Wu-Tang

17th March 2011, 23:51

yetanotherid
Okay, I downloaded the samples. When I tried converting each one, the first three gave me the same dimensions. Only the fourth was different. However they all looked like they should have been cropped the same, but AutoGK didn't crop the right side of the fourth one properly. After looking a few times I discovered what I think was messing with the auto-cropping. Here's a picture with the colour enhanced to make it obvious.
Yes, yes, yes. I begin to rip and first and fourth has 640x368 .
How force autogk to do 640*288 in that parts?
I'm out of ideas as to why you can't preview AVISynth scripts. (When you preview using AutoGK or HDConvertToX you're effectively opening the AVISynth script they create with Media Player Classic. For some reason it won't open the scripts on your system and I'm out of ideas as to why).
And what still do i can do? May be is variants?
HDConvertToX probably selected 400 as the height when you enabled anamorphic encoding. It's a whole different subject but instead of resizing the MPEG file down to square pixel dimensions it uses the same non-square pixels as the original video. When encoding to AVI square pixels are generally used so the height of the video is reduced to maintain the aspect ratio.
It means that HDConvertToX is silly.
(remember the width and height have to be multiples of 16).
And i find that:
Proceeding from requirements of frequency rate 32 on X and 16 on Y it is simple to construct two rows of values for width and frame height:
- X: 704, 672, 640, 608, 576, 544, 512, 480
- Y: 528, 512, 496, 480, 464, 448, 432, 416, 400, 384, 368, 352, 336, 320, 304, 288

Try this very rough image as an example. The inner rectangle is the 640x272 video. The outer rectangle is the next height up. It might be 670x288. By cropping an extra four pixels from the sides you forced AutoGK to resize to the next height up because it could no longer give you a width of 640 with a height of 272. In order to give you a width of at least 640 the height needs to be 288. The blue area each side is the extra picture you lost, partly because you chose to crop a little more yourself, and partly because AutoGK had to automatically crop a little more also to give you a width of 640.

Sometimes, the difference between two heights (272 and 288) is only a couple of extra pixels of cropping.
Thanks, i understand it now.

yetanotherid

18th March 2011, 15:14

Yes, yes, yes. I begin to rip and first and fourth has 640x368 .
How force autogk to do 640*288 in that parts?

Are all the mpeg2 files in the same folder? If not, put them all in the same place. Open one with AutoGK. Use CTRL+F9 to open hidden options and add the cropping I worked out earlier as the forced cropping values. Change the "threshold" to zero. Tick the "tune autocrop parameters" box and select okay.

AutoGK will now use the same cropping for all the files as long as they're in the same folder (AutoGK actually saves a little autocrop file to the folder containing the video. It uses that file for all video in the folder).

And what still do i can do? May be is variants?

I don't know. It might be something to do with Windows 7. I use XP.
Try creating a file called video.avs in the same folder as one of your video files and open it with a text program such as notepad. Assuming you have a video called "video.mpeg", add the following to the text file:
DirectShowSource("video.mpeg")
Save the avs file.
(You can do this with any type of video, just make sure the name of the video in the text file matches the real video)
Now try to open the avs file with Media Player Classic. It should open it as though you were opening the video file itself (except you won't have any audio). If it does, then it's a different problem. If you get the same error as you do when previewing video then for some reason MPC isn't opening avs files properly (you preview the AutoGK video via an AVS file). I probably won't be able to tell you why, you might have to post the question in the Media Player Classic thread.

It means that HDConvertToX is silly.

No, it means you don't understand anamorphic encoding.
A PAL DVD is 720x576, but the pixels aren't square (the actual display size in square pixel dimensions might be 1024x576). Normally when converting to AVI you'd resize down, so the dimensions might be 720x400. When you encode anamorphically you use the same shaped pixels as the original DVD so the dimensions will still be 720x576 as they were originally. Anamorphic encoding is often used with the x264 encoder and MKV or MP4 files.
You can see the difference by opening your original mpeg file with Media Player Classic. It's 720 pixels wide. Now open a 720 pixel wide AVI. Notice it doesn't display as widely across the screen as the mpeg file even though they're both 720 pixels wide? The mpeg file doesn't use square pixels, the AVI does.

And i find that:

Yes, as long as they're multiples of 16. As far as resizing goes:

Think of the aspect ratio of a DVD picture. Without having to crop (no back bars) it's 16:9
When resizing to square pixels you want to resize so the dimensions are still 16:9 (or as close to 16:9 as possible).
704x400, 672x384, 656x368, 640x352 etc.

If the DVD has a 4:3 aspect ratio (it's still 720x576 but the pixels it uses are a different shape) then you'd resize to 4:3 dimensions.
704x528, 672x512, 656x496, 640x480 etc.

The most commonly used dimensions for 16:9 video are probably 704x400 or 656x384 as they're very close to or exactly 16:9
The most commonly used dimensions for 4:3 video are 704x528 or 640x480 as they're exactly 4:3.

Video with a 2.35 or 2.40 aspect ratio is used on 16:9 DVDs but then black bars are added to the top and bottom to fill the gaps and make it 16:9. Once you remove the black bars for encoding the dimensions of the encoded video will change accordingly after it's been resized.

Wu-Tang

18th March 2011, 17:49

Are all the mpeg2 files in the same folder? If not, put them all in the same place. Open one with AutoGK. Use CTRL+F9 to open hidden options and add the cropping I worked out earlier as the forced cropping values. Change the "threshold" to zero. Tick the "tune autocrop parameters" box and select okay.
AutoGK will now use the same cropping for all the files as long as they're in the same folder (AutoGK actually saves a little autocrop file to the folder containing the video. It uses that file for all video in the folder).
Of course, all vobs files in the folder video_ts!!!
[17.03.2011 12:50:54] Started encoding.
[17.03.2011 12:50:54] Demuxing and indexing.
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_1.VOB
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_2.VOB
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_3.VOB
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_4.VOB
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_5.VOB
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_6.VOB
[17.03.2011 12:55:14] Processing file: D:\VIM4\VIDEO_TS\VTS_03_7.VOB
I understood problem, i read log file and saw:
2 and 3 parts:
[17.03.2011 6:36:08] Source resolution: 720x576
[17.03.2011 6:36:08] Found PAL source.
[17.03.2011 6:36:08] Source aspect ratio: 16:9
1 and 4 parts:
[17.03.2011 12:55:14] Source resolution: 720x576
[17.03.2011 12:55:14] Found PAL source.
[17.03.2011 12:55:14] Source aspect ratio: 4:3
2, 3 aftet convert have 640*288.
1, 4 - 640*368.
Then i select checkbox aspect 16:9 in hidden option for 1 and 4 parts and start convert and after that prefs (16:9 manually), that parts have resolution 640*288 also as 2, 3.
I don't know. It might be something to do with Windows 7. I use XP.
Try creating a file called video.avs in the same folder as one of your video files and open it with a text program such as notepad. Assuming you have a video called "video.mpeg", add the following to the text file:
DirectShowSource("video.mpeg")
Save the avs file.
(You can do this with any type of video, just make sure the name of the video in the text file matches the real video)
Now try to open the avs file with Media Player Classic. It should open it as though you were opening the video file itself (except you won't have any audio). If it does, then it's a different problem. If you get the same error as you do when previewing video then for some reason MPC isn't opening avs files properly (you preview the AutoGK video via an AVS file). I probably won't be able to tell you why, you might have to post the question in the Media Player
I use winxp too. I try to creat this file and playing in mpc, but don't job!!!
Where to find this decoder...
No, it means you don't understand anamorphic encoding.
A PAL DVD is 720x576, but the pixels aren't square (the actual display size in square pixel dimensions might be 1024x576). Normally when converting to AVI you'd resize down, so the dimensions might be 720x400. When you encode anamorphically you use the same shaped pixels as the original DVD so the dimensions will still be 720x576 as they were originally. Anamorphic encoding is often used with the x264 encoder and MKV or MP4 files.
You can see the difference by opening your original mpeg file with Media Player Classic. It's 720 pixels wide. Now open a 720 pixel wide AVI. Notice it doesn't display as widely across the screen as the mpeg file even though they're both 720 pixels wide? The mpeg file doesn't use square pixels, the AVI does.
Like has understood.
I riped 3 of 4 parts, please look at screenshots:
http://i026.radikal.ru/1103/20/5c7a4256b4e0t.jpg (http://radikal.ru/F/i026.radikal.ru/1103/20/5c7a4256b4e0.jpg.html)
http://s001.radikal.ru/i193/1103/0f/7c02b82b0bc9t.jpg (http://radikal.ru/F/s001.radikal.ru/i193/1103/0f/7c02b82b0bc9.jpg.html)
http://i015.radikal.ru/1103/9d/b23c2b123808t.jpg (http://radikal.ru/F/i015.radikal.ru/1103/9d/b23c2b123808.jpg.html)

yetanotherid

18th March 2011, 18:49

I use winxp too. I try to creat this file and playing in mpc, but don't job!!!
Where to find this decoder...

I'm not sure what the problem is. Try taking another screen shot of the error message and posting it in one of these places to see if anyone can help.
http://forum.doom9.org/forumdisplay.php?f=15
http://forum.doom9.org/forumdisplay.php?f=33

Your encodes look pretty good.

Wu-Tang

23rd March 2011, 03:33

I'm not sure what the problem is. Try taking another screen shot of the error message and posting it in one of these places to see if anyone can help.
http://forum.doom9.org/forumdisplay.php?f=15
http://forum.doom9.org/forumdisplay.php?f=33
And where are to ask there?
Here? - http://forum.doom9.org/showthread.php?t=123537
Your encodes look pretty good.
Thanks
Recently i riped fourth part:
http://s001.radikal.ru/i193/1103/cc/d564b9d927bct.jpg (http://radikal.ru/F/s001.radikal.ru/i193/1103/cc/d564b9d927bc.jpg.html)

Wu-Tang

27th March 2011, 01:09

Hi
I seem understand a problem.
So, i installed ffdshow and tune decoding by.
And in autogk the preview is job. :)
Now, i want to know do you installed ffdshow or xvid or divx?
xvid dont decode yv12, and divx and ffdshow is decode it, why.
what value do you have in:
http://s002.radikal.ru/i200/1103/ca/9570522e3f65t.jpg (http://radikal.ru/F/s002.radikal.ru/i200/1103/ca/9570522e3f65.jpg.html)

VANT

8th July 2011, 13:25

i have 2 problems
-oryginal dvd Pirates of the Caribbean 1,2 and 3, after i rip it(dvdfab) i make avi, and after this audio is faster ~500ms than video.
-oryginal dvd How to Train Your Dragon autogordianknot see aspect 16:9, but during compression use 4:3
Video info: MPEG2 720x576 PAL 16:9 letbox PGC 1. Length: 1:33:50:05
[2011-07-06 14:52:02] Source aspect ratio: 4:3
audio also is faster than video ~500ms.

Any chance to fix it ??
I know that i can fix audio using virtaldubmod, and set force 16:9 ...

manono

8th July 2011, 14:19

diega

8th September 2011, 21:12

Some time ago there was the following error:

[09.09.2011 0:00:07] AutoGK 2.55
[09.09.2011 0:00:07] OS: Windows Vista (6.1.7601).2
[09.09.2011 0:00:07] Job started.
[09.09.2011 0:00:07] Input file: F:\Slava\Ish\1\VIDEO_TS\VTS_01_0.IFO
[09.09.2011 0:00:07] Output file: F:\After Effects\gy.avi
[09.09.2011 0:00:07] Output codec: XviD
[09.09.2011 0:00:07] Audio 1: English AC3 2ch
[09.09.2011 0:00:07] Subtitles: none
[09.09.2011 0:00:07] Format: AVI
[09.09.2011 0:00:07] Target size: 1493Mb
[09.09.2011 0:00:07] Custom resolution settings: fixed width of 720 pixels
[09.09.2011 0:00:07] Audio 1 settings: Auto
[09.09.2011 0:00:07] Started encoding.
[09.09.2011 0:00:07] Demuxing and indexing.
[09.09.2011 0:00:47] Processing file: F:\Slava\Ish\1\VIDEO_TS\VTS_01_1.VOB
[09.09.2011 0:00:47] Processing file: F:\Slava\Ish\1\VIDEO_TS\VTS_01_2.VOB
[09.09.2011 0:00:47] Processing file: F:\Slava\Ish\1\VIDEO_TS\VTS_01_3.VOB
[09.09.2011 0:00:47] Processing file: F:\Slava\Ish\1\VIDEO_TS\VTS_01_4.VOB
[09.09.2011 0:00:47] Processing file: F:\Slava\Ish\1\VIDEO_TS\VTS_01_5.VOB
[09.09.2011 0:00:47] Source resolution: 720x576
[09.09.2011 0:00:47] Found PAL source.
[09.09.2011 0:00:47] Source aspect ratio: 4:3
[09.09.2011 0:00:47] Analyzing source.
*************************************
EXCEPTION: Cannot open file "F:\After Effects\agk_tmp\interlace.log". Can not find the file
*************************************
[09.09.2011 0:00:47] Job finished. Total time: 40 seconds
====================================================

What could be the problem? Thanks in advance...

Monza

16th November 2011, 19:58

As for the aspect ratio, apparently the VOBs are 4:3 but the IFOs say to play it as 16:9. A DVD player gets the information from the IFOs, but AutoGK gets it from DGIndex which gets it from the VOBs. It's rare that the two disagree, but it happens. You'll have to go into the Hidden Options (CTRL-F9) and override the source aspect ratio and set it for 16:9.

The audio delay problem is most likely the result of a bad decrypt. My suggestion is that after decrypting it with DVDFab HD Decrypter you then run the VOBs through FixVTS. Either that or open the final AVI in VDubMod and set a delay in there.

I am having a similar issue, as of the release of DVDfab 8.1.3.2 all 16:9 dvd rips.(Eg:the entire Pirates of the caribbean series)
are seen by Autogk as 4:3 during compression.The source aspect ratio must be overridden ever time.
If I rip a movie using Dvdfab 8.0.8.5 everything is fine.Is there anyway to make a fix for this or a least make the override a global option ?
Your app is still the best for encoding Xvids after all these Years...

manono

16th November 2011, 22:48

Is that for me? I didn't develop the program (that was len0x) so can't modify or improve on it to do as you ask. If, as you say, it's this version of DVDFab HD Decrypter has the problem, your beef is with them. Maybe the next version will correct the problem as I doubt you're the only one experiencing it. If they have a forum, maybe look around in there.

Sanek75

24th December 2011, 15:02

I'm using AutoGK for a long time. I converted very many of files using it (big thanks to authors). But several days ago I've encountered with this problem:
http://img521.imageshack.us/img521/7133/38021845.th.jpg (http://img521.imageshack.us/img521/7133/38021845.jpg)
How can I dissolve this?

setarip_old

24th December 2011, 21:17

@Sanek75

Hi!

Sounds like a bad sector. Try re-ripping your original, commercial DVD.

Sanek75

25th December 2011, 19:24

@Sanek75

Hi!

Sounds like a bad sector. Try re-ripping your original, commercial DVD.

Thanks. It helped.

setarip_old

25th December 2011, 23:37

Thanks. It helped. Glad to hear that ;>}

datauser

8th May 2012, 08:53

I'm still using this great program for the odd Xvid encoding. Anybody successfully tried using a different version of xvid with it?

Chetwood

9th May 2012, 06:54

Nope, switched to Staxrip and H.264.

datauser

9th May 2012, 08:59

Staxrip is still supported and an excellent package of tools. H264 is the way forward but I still do the odd avi for friends or family. I may give the original version Gordian Knot a try. Which version of Xvid does it use?

kalehrl

9th May 2012, 14:38

Xvid 1.2.1 + VAQ patch.

Chetwood

9th May 2012, 15:16

Staxrip can do xvid as well, probably also with the latest revision.

kalehrl

9th May 2012, 19:41

I'm still using this great program for the odd Xvid encoding. Anybody successfully tried using a different version of xvid with it?
I did and went back to the version supplied by autogk.
I tried latest Xvid 1.3.2 but autogk kept using Mobile profile.
I now mostly use autogk for comptest.

datauser

17th July 2012, 16:18

Xvid 1.2.1 + VAQ patch.

I assume you mean that both AutoGK and Gordian Knot use this version? As I said I have never used Gordian Knot before.

Sure does, Xvid 1.3.2 sends AutoGK's settings bonkers. Don't use it as it screws up AutoGK's profiles! I can't remember where I saw it on Net, but Xvid 1.2.2 VAQ is said to be okay with some users' platforms using AutoGK. However when I tried it a few years' back I got undersized files everytime.:)

I have reverted back to AutoK from Staxrip for Xvid/avi encodings and Handbrake for my MP4's, because I'm getting a crazy VdubMod error message of a missing libsndfile-1.dll when encoding anything as source in Staxrip latest beta, despite putting it in VDubMod application folder. I tried XmediaRecode, but had trouble hitting target sizes. I still marvel at how AutoGK resizes appropriately and hits the 700mb target everytime. Pure magic!

kalehrl

17th July 2012, 19:25

I assume you mean that both AutoGK and Gordian Knot use this version?
I meant AutoGK only but now I see you asked about Gordian Knot.
I missed that, sorry.
Like you, I never used Gordian Knot.

datauser

17th July 2012, 21:42

No worries! I'm postponing installing GordianKnot as I have new laptop (maybe after a format),and because it uses very old codecs/tools etc which probably would conflict with K-Lite 9.0.2 installed files/reg settings etc, I installed portable AutoGK/Xvid 1.2.1 on an older Asus laptop. I run Xvid 1.32 and Megacodec pack on my new laptop well part from my Staxrip problem. I may give GordianKnot a blast on this old laptop as avi quality is meant to be quite excellent as you can manipulate more settings than AutoGK and I'm intrigued by the prospect.

hello_hello

5th August 2012, 09:02

I can't remember where I saw it on Net, but Xvid 1.2.2 VAQ is said to be okay with some users' platforms using AutoGK. However when I tried it a few years' back I got undersized files everytime.

It's possibly not AutoGK's fault. Some builds of Xvid are broken in that respect. I think it might depend on whether you're using a custom Xvid matrix.... I can't remember the details..... but AutoGK might use one. It depends on whether you've selected a standalone player compatibility option, and which one you use. So the undersized file problem mightn't be platform dependent as such, but the result of using (or not using) one of the standalone player options with a "broken" Xvid build.

datauser

6th August 2012, 11:15

You are probably right! Maybe not using ESS compatabilty etc allows AutoK to function better with other Xvid builds in regards to hitting the target size? if you use ESS option with other builds than built in Xvid 1.2.1 then everything screws up sizewise e.g it uses a mobile profile. I'll have to check this out for myself. Then again there is probably very little quality benefits using a codec other than the 1.2.1 build included.

hello_hello

10th August 2012, 07:47

I would have assumed using the ESS profile would be less likely to cause file size issues as it doesn't use a custom Xvid matrix. As long as the correct profile was used. However....

Looking at the AutoGK release notes, AutoGK 2.47 had Xvid downgraded to 1.2.0 because the ESS option caused file size issues, then it was upgraded to 1.3.0 for AutoGK 2.50, then downgraded to 1.2.1 for AutoGK 2.52, and AutoGK 2.55 seems only to have been released because AutoGK 2.53 was bundled with the wrong Xvid version.

I don't really know if the problem was the wrong Xvid profile when using some versions of Xvid or whether some Xvid versions were just broken. I'd assumed they were broken, but maybe not....

datauser

14th August 2012, 12:21

Interesting analysis. Here's the link for portable version if interested.

http://www.mediafire.com/?xjzxjnmvnwj

hello_hello

18th August 2012, 19:28

Interesting analysis. Here's the link for portable version if interested.

http://www.mediafire.com/?xjzxjnmvnwj

Cheers. I've downloaded it to store in my program installation archive folder.

kalehrl

18th August 2012, 19:38

Doesn't work with me.
The error is 'failed to create process default activation context.'
The system is Windows 7 Ultimate 64bit.

datauser

18th August 2012, 20:28

Doesn't work with me.
The error is 'failed to create process default activation context.'
The system is Windows 7 Ultimate 64bit.

I had no problems running it with Win7 64bit, though I prefer to use it with XP most of the time. Right click and run it under Windows compatibility mode for XP. Also look at your permissions or run it as administrator, if all else fails. Should work fine in compatibility mode though. Read below!

http://forums.whirlpool.net.au/archive/1423731

kalehrl

18th August 2012, 20:54

I have no problem running the installed AutoGK.
This portable won't run.
I tried to run it in the compatibility version of XP but now it reports:
'Recursion too deep; the stack overflowed.
Unable to load DLL ... AVIFIL32.dll'

datauser

19th August 2012, 15:31

It may be a problem associated with multi-threading due to memory allocation. I do not know an easy solution for this as I never saw similar problems using 64 bit architecture myself using a 2Ghz Pentium Dual Core CPU and 3GB of memory. Try disabling/closing all your running programs(memory guzzlers) in system tray e.g antivirus etc and see what happens.:)

http://en.wikipedia.org/wiki/Stack_overflow

Turning off your Data Execution protection(DEP) might work: Link below

http://www.winvistaclub.com/t206.html

OR TRY "Adding AutoGK" to your DEP exception list:
1.) Open "Control Panel"
2.) Click on "System and Maintenance"
3.) Click on "System"
4.) On the left side click on "Advanced System Settings"
you will be asked for permission to continue, click continue
5.) Click on the Advanced tab and then on "Settings" in the Performance area
6.) Click on the DEP (Data Execution Prevention) tab
7.) Put a tick in the little circle next to "Turn on DEP for all programs and services
except those I select" and click on the "ADD" button and
browse for and click on the .exe file for AutoGK or
any other App then click "Open" now click "Apply" then "OK"
and close all open windows and your done.