View Full Version : Wrong output DAR
rtjnyoface
26th October 2009, 02:41
I was unsure if this should go in a different forum or not but I suppose the issue is with megui in some fashion.(disregard that part as I was given a suggestion to post in this fom) On to the issue.
XP Pro SP3
Megui rev 1056
Dgindex 1.5.5
Source: Planet Earth series Ocean deep dvd.
Make a .d2v file, open it in megui's avisynth creator. Input DAR is set correctly as 16:9 (1.88...). Now, after I encode the file the output file is set at 4:3 (1.5). What in the world changed in between encoding and file output? On top of it I've lost about half the film. When I play the file about half of it plays correctly and then near the middle of the film it gets very screwy. I can't forward through the movie past the screwy point. I've remuxed with mkvtoolnix and set the correct DAR but it doesn't fix the film cut/screw up and I would still like to understand what the heck went on. I don't wish to do this for the other 10 or so in the series.
DGDecode_mpeg2source("C:\Planet Earth\Ocean Deep\VTS_02_1.d2v", info=3)
ColorMatrix(hints=true, interlaced=true, threads=0)
tfm(order=-1).tdecimate(hybrid=3)
#crop
#resize
#denoise
Any suggestions or ideas?
thewebchat
26th October 2009, 02:59
Don't know what axioms you're using, but in the mathematics I was taught, 4/3 != 1.5.
Inspector.Gadget
26th October 2009, 03:00
Did you somehow include VTS_01_0.VOB (likely a 4:3 menu) in your indexing?
rtjnyoface
26th October 2009, 04:38
Don't know what axioms you're using, but in the mathematics I was taught, 4/3 != 1.5.
I guess I wasn't clear enough. My input DAR is 16x9. My resulting file is 4/3. Definitely not what I want.
Did you somehow include VTS_01_0.VOB (likely a 4:3 menu) in your indexing?
Nope. They are all without menues.
aegisofrime
26th October 2009, 05:02
When you open the .avs file in MeGUI, it sets a default DAR of 1.5. Try setting it to 1.778 and see what happens.
I might be on the wrong track here, since I don't use the avs creator. I always write the avs myself.
rtjnyoface
26th October 2009, 05:18
When you open the .avs file in MeGUI, it sets a default DAR of 1.5. Try setting it to 1.778 and see what happens.
I might be on the wrong track here, since I don't use the avs creator. I always write the avs myself.
I set it to it's original AR of 1.822... whatever. I'm also going to use the d2v creator in megui (which I've never done before) to create the file. Guess I'll report back here in a few.
aegisofrime
26th October 2009, 05:27
I set it to it's original AR of 1.822... whatever. I'm also going to use the d2v creator in megui (which I've never done before) to create the file. Guess I'll report back here in a few.
To clarify, when you open the .avs file it opens up the preview window right? You can set the DAR there. Hope this clears up any potential confusion.
mgh
26th October 2009, 05:53
Use the avs script creator in megui.
Assuming that the original encoded resolution is 720x480, you have two choices- resizing or anamorpic encoding to get the correct AR.
by default-megui chooses neither, so it will encode at 720x480 giving AR of 1.5
in the megui script creator, you have to choose
either
Clever (TM) anamorphic encoding and one of the options in the dropdown box next to it
or
Resize and the Suggest Resolution (mod 16) check box next to it
to get correct AR during playback
rtjnyoface
26th October 2009, 07:19
Assuming that the original encoded resolution is 720x480, you have two choices- resizing or anamorpic encoding to get the correct AR.
[quote]Auto cropping changes nothing. There is no need to resize or to encode anamorphic. by default-megui chooses neither, so it will encode at 720x480 giving AR of 1.5[quote]
Thanks for the suggestion. Upon opening the script I chose the original AR. That fixed that issue.
As far as the strange encoding "error" I thought I had, megui chose 24fps when the film is actually 30. Who cares though I guess, it fixed the issue. I then encoded with megui's suggestion of IVTC. Wow, that sucked. Guess I'll stick with TomsMoComp. It's not all that great either but at least the film isn't fidgity.
Thanks to all those that responded. I thank you for your time and suggestions.
davidhorman
26th October 2009, 12:06
As far as the strange encoding "error" I thought I had, megui chose 24fps when the film is actually 30.
Things might be complicated slightly by the fact that the original would have been 25fps, having been mastered for broadcast in the UK, so depending on how they converted it (and assuming they didn't do an "NTSC slow-down") you won't get away with something as simple as IVTC.
David
Didée
26th October 2009, 13:05
Ermh, I thought Planet Earth was originally shot mainly in 24p? I don't have the DVDs, but when it was aired on TV, I had a look at it and it was progressive. Googling for reviews confirms that it should be progressive (except perhaps for some extra stuff).
If so, PAL versions should be progressive (speedup), and NTSC versions should be progressive with soft pulldown (or hard pulldown, but hopefully not.)
In case of doubt, you might consider to upload a representative sample.
davidhorman
26th October 2009, 14:22
It's definitely progressive (though there may be one or two interlaced shots, say from starlight cameras), but that doesn't really come into it.
Whether it was shot at 24fps or 25fps (or higher - they seem to like a bit of slowmo in these nature shows), I'm pretty sure it would have been edited with 25fps broadcast in mind - otherwise they would have to do a speed-up, as you say, and Mr Attenborough's dulcet tones would be a little squeaky. Does the US version has the same narration?
It wouldn't be unusual for the BBC to shoot film at 25fps - they did it for years whenever a drama or sitcom left the studio.
David
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.