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 > Video Encoding > (Auto) Gordian Knot

Reply
 
Thread Tools Search this Thread Display Modes
Old 13th March 2011, 05:14   #4801  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
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.
yetanotherid is offline   Reply With Quote
Old 13th March 2011, 10:37   #4802  |  Link
kalehrl
Registered User
 
Join Date: Feb 2011
Posts: 331
Quote:
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.
kalehrl is offline   Reply With Quote
Old 13th March 2011, 19:52   #4803  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by kalehrl View Post
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.

Last edited by yetanotherid; 13th March 2011 at 20:36.
yetanotherid is offline   Reply With Quote
Old 13th March 2011, 20:46   #4804  |  Link
kalehrl
Registered User
 
Join Date: Feb 2011
Posts: 331
Quote:
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:
Quote:
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.
kalehrl is offline   Reply With Quote
Old 13th March 2011, 21:27   #4805  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by kalehrl View Post
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.

Quote:
Originally Posted by kalehrl View Post
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 is offline   Reply With Quote
Old 13th March 2011, 22:03   #4806  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by kalehrl View Post
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.

Last edited by yetanotherid; 14th March 2011 at 08:41.
yetanotherid is offline   Reply With Quote
Old 13th March 2011, 22:07   #4807  |  Link
Wu-Tang
Registered User
 
Wu-Tang's Avatar
 
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
manono
Ok, i understand.

yetanotherid
Quote:
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:

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.
Quote:
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.
Quote:
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.
Quote:
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.
Quote:
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.
Quote:
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: ((((((
Quote:
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.
__________________
There is time for everything and to everyone the hour.

If do you want to live-be able to twist.

Last edited by Wu-Tang; 13th March 2011 at 22:10.
Wu-Tang is offline   Reply With Quote
Old 13th March 2011, 22:27   #4808  |  Link
CWR03
Custom User Title
 
CWR03's Avatar
 
Join Date: Mar 2005
Posts: 3,733
Quote:
Originally Posted by Wu-Tang
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.
CWR03 is offline   Reply With Quote
Old 14th March 2011, 02:37   #4809  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by Wu-Tang View Post
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.

Last edited by yetanotherid; 14th March 2011 at 12:17.
yetanotherid is offline   Reply With Quote
Old 14th March 2011, 08:16   #4810  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
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.



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.

Last edited by yetanotherid; 14th March 2011 at 08:22.
yetanotherid is offline   Reply With Quote
Old 14th March 2011, 14:42   #4811  |  Link
kalehrl
Registered User
 
Join Date: Feb 2011
Posts: 331
Quote:
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.
kalehrl is offline   Reply With Quote
Old 14th March 2011, 15:20   #4812  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by kalehrl View Post
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.
yetanotherid is offline   Reply With Quote
Old 15th March 2011, 17:50   #4813  |  Link
Wu-Tang
Registered User
 
Wu-Tang's Avatar
 
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
CWR03
Quote:
Use Gordian Knot to crop. Transfer those numbers into AutoGK.
And there how?
yetanotherid
Hi,
Quote:
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 -
2) Then i select aspect -
I select 16, 24, 78, 80.
3) And I will go mad. )))

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 -
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)
Quote:
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
Quote:
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.
Thank you very much for your help.
__________________
There is time for everything and to everyone the hour.

If do you want to live-be able to twist.
Wu-Tang is offline   Reply With Quote
Old 16th March 2011, 02:38   #4814  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
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.



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.

Last edited by yetanotherid; 16th March 2011 at 02:43.
yetanotherid is offline   Reply With Quote
Old 17th March 2011, 23:51   #4815  |  Link
Wu-Tang
Registered User
 
Wu-Tang's Avatar
 
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
yetanotherid
Quote:
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?
Quote:
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?
Quote:
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.
Quote:
(remember the width and height have to be multiples of 16).
And i find that:
Quote:
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
Quote:
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.
__________________
There is time for everything and to everyone the hour.

If do you want to live-be able to twist.

Last edited by Wu-Tang; 18th March 2011 at 04:09.
Wu-Tang is offline   Reply With Quote
Old 18th March 2011, 15:14   #4816  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by Wu-Tang View Post
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).

Quote:
Originally Posted by Wu-Tang View Post
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.

Quote:
Originally Posted by Wu-Tang View Post
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.

Quote:
Originally Posted by Wu-Tang View Post
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.

Last edited by yetanotherid; 18th March 2011 at 15:20.
yetanotherid is offline   Reply With Quote
Old 18th March 2011, 17:49   #4817  |  Link
Wu-Tang
Registered User
 
Wu-Tang's Avatar
 
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
Quote:
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!!!
Code:
[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:
Code:
[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:
Code:
[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.
Quote:
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...
Quote:
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:


__________________
There is time for everything and to everyone the hour.

If do you want to live-be able to twist.

Last edited by Wu-Tang; 18th March 2011 at 18:02.
Wu-Tang is offline   Reply With Quote
Old 18th March 2011, 18:49   #4818  |  Link
yetanotherid
Banned
 
Join Date: Apr 2008
Posts: 723
Quote:
Originally Posted by Wu-Tang View Post
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.
yetanotherid is offline   Reply With Quote
Old 23rd March 2011, 03:33   #4819  |  Link
Wu-Tang
Registered User
 
Wu-Tang's Avatar
 
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
Quote:
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
Quote:
Your encodes look pretty good.
Thanks
Recently i riped fourth part:
__________________
There is time for everything and to everyone the hour.

If do you want to live-be able to twist.
Wu-Tang is offline   Reply With Quote
Old 27th March 2011, 01:09   #4820  |  Link
Wu-Tang
Registered User
 
Wu-Tang's Avatar
 
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
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:
__________________
There is time for everything and to everyone the hour.

If do you want to live-be able to twist.
Wu-Tang is offline   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 03:34.


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