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. |
13th March 2011, 05:14 | #4801 | Link |
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. |
13th March 2011, 10:37 | #4802 | Link | |
Registered User
Join Date: Feb 2011
Posts: 331
|
Quote:
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. |
|
13th March 2011, 19:52 | #4803 | Link | |
Banned
Join Date: Apr 2008
Posts: 723
|
Quote:
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. |
|
13th March 2011, 20:46 | #4804 | Link | ||
Registered User
Join Date: Feb 2011
Posts: 331
|
Quote:
Quote:
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. |
||
13th March 2011, 21:27 | #4805 | Link | ||
Banned
Join Date: Apr 2008
Posts: 723
|
Quote:
Quote:
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. |
||
13th March 2011, 22:03 | #4806 | Link |
Banned
Join Date: Apr 2008
Posts: 723
|
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. |
13th March 2011, 22:07 | #4807 | Link | |||||||
Registered User
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
|
manono
Ok, i understand. yetanotherid Quote:
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:
Your question i don't may to translate. Quote:
Quote:
Quote:
Quote:
P.S Thank your very much for your help. P.S. I want to sent you PM, but i saw: (((((( Quote:
__________________
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. |
|||||||
14th March 2011, 02:37 | #4809 | Link |
Banned
Join Date: Apr 2008
Posts: 723
|
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. |
14th March 2011, 08:16 | #4810 | Link |
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. |
14th March 2011, 14:42 | #4811 | Link | |
Registered User
Join Date: Feb 2011
Posts: 331
|
Quote:
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. |
|
14th March 2011, 15:20 | #4812 | Link |
Banned
Join Date: Apr 2008
Posts: 723
|
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.
|
15th March 2011, 17:50 | #4813 | Link | ||||
Registered User
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
|
CWR03
Quote:
yetanotherid Hi, Quote:
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:
6) Now about preview Quote:
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. |
||||
16th March 2011, 02:38 | #4814 | Link |
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. |
17th March 2011, 23:51 | #4815 | Link | ||||||
Registered User
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
|
yetanotherid
Quote:
How force autogk to do 640*288 in that parts? Quote:
Quote:
Quote:
Quote:
Quote:
__________________
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. |
||||||
18th March 2011, 15:14 | #4816 | Link | |
Banned
Join Date: Apr 2008
Posts: 723
|
Quote:
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). 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. 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. 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. |
|
18th March 2011, 17:49 | #4817 | Link | |||
Registered User
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
|
Quote:
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 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 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 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:
Where to find this decoder... Quote:
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. |
|||
18th March 2011, 18:49 | #4818 | Link | |
Banned
Join Date: Apr 2008
Posts: 723
|
Quote:
http://forum.doom9.org/forumdisplay.php?f=15 http://forum.doom9.org/forumdisplay.php?f=33 Your encodes look pretty good. |
|
23rd March 2011, 03:33 | #4819 | Link | ||
Registered User
Join Date: Jan 2009
Location: Russia, Saint-Petersburg
Posts: 62
|
Quote:
Here? - http://forum.doom9.org/showthread.php?t=123537 Quote:
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. |
||
27th March 2011, 01:09 | #4820 | Link |
Registered User
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. |
Thread Tools | Search this Thread |
Display Modes | |
|
|