+ Reply to Thread
Results 91 to 120 of 137
-
It's not 23.972 - this will gradually go out of sync , and actually will cause problems for MPEG2 DVD encoding
The exact number is 24000/1001 , or 23.976024.... (is an approximation)
AssumeFPS(24000,1001)
If you choose to go that route you have to slow the audio by that exact fraction (24000/1001) / 25
If you choose the other method (720x480, 25fps, pulldown flags), the audio is the same , doesn't need to be altered -
-
If I was going that route I would use eac3to (there are other methods like besweet)
There are presets for 25 => 23.976 in most audio programs
In eac3to :
Code:eac3to input.ac3 output.ac3 -slowdown
One benefit of choosing the other method, is audio doesn't have to be altered (no re-encoding or quality loss - you use the exact same audio stream, just reauthored). Your audio is pretty shabby to begin with, and re-encoding it will make it worse -
-
-
25FPS = too fast IMO. The sword fight scenes move like Looney Tunes. It's obviously been sped up.
The software mentioned will adjust the audio rate.
No. I fixed almost all of it in Avisynth with RemoveSpots(), then used LSFMod to resharpen the results. See the earlier scripts posted. Deflicker won't fix the sharp luma pumping in the sword fight scenes, either. I don't know where it's coming from, but it's not in your original post.
I adjusted audio after running QTGMC and srestore. Firt, mI converted the original .ac3 that was saved by DGindex, and made it an uncompressed .wav (PDM) file. Then this script, and saved only the audio in VirtualDub with "File" -> "Save wav..." :
Code:v=AviSource("path to video\filtered.avi") a=WAVSource("path to audio\VTS_01_2.wav") av=AudioDub(v,a) av AssumeFPS("ntsc_film",sync_audio=true) return last
Last edited by sanlyn; 19th Mar 2014 at 06:18.
-
Ok, since people think this is a good step I am starting with this:
MPEG2Source("path to d2v\VTS_01_2.d2v")
AssumeTFF().QTGMC(preset="medium")
sRestore()
AssumeFPS(23.976)
I think its a good step because I am restoring the OG frame rate. Plus, since the frame size is for NTSC, I am doing a good thing. Am I undestanding this right?
Thanks! -
If you're asking if there's an encoder that will allow you to encode for 25fps with NTSC resolution, the answer is 'yes'. HCEnc and CCE (and others) allow it. As I mentioned before, you may have to disable any DVD templates or presets that will probably be the defaults. Maybe even your current encoder will allow that, but I don't really know. Then it won't be NTSC DVD compliant until after you run it through DGPulldown set for 25->29.97fps, which I also mentioned way back on the first page:
Yes.Last edited by manono; 29th Jun 2013 at 13:53.
-
Yes. All NTSC DVDs must output interlaced 29.97fps. If you use a template in your encoder the encoder will add it automatically. If you don't use templates (I don't) and get a 23.976fps MPV or M2V out of the encoder, run it through DGPulldown set up for the default and standard 23.976->29.97fps (3:2 Pulldown).
-
-
I agree. Normally the difference between 24 vs. 25 is slight - many people can't even pick out the difference. But in that era, slight undercranking during shooting kung fu action scenes was a common practice , and done on purpose - like 20-23 fps , so the effective difference from a PAL conversion is even more noticable . (Even more "modern" martial arts films from Jackie Chan, Donnie Yen, etc.. have undercranked scenes)
-
Yes, poisondeathray, that cranking up is what I should refer to as the cause of the effect. Every Japanese action or monster-on-the-loose flick I've seen does odd things with motion ("odd" to we Westerners, anyway). I think that even Seven Samurai has some accelerated fight scenes, especially the long sequences in the rain. It doesn't make much of a pump to make it look overdone.
Hollywood goes for it, too. Every Western made in the U.S. has juiced-up chase scenes.Last edited by sanlyn; 19th Mar 2014 at 06:18. Reason: ewwww, what grammar!
-
Attached is 1.6666666:1 in a 16x9 frame, 23.976 FPS mkv (to save a little posting bandwidth). Rather blurry -- I don't have the original VOB, but worked with the squished PAL 25FPS version posted in #77 on 29-June-2013 (https://forum.videohelp.com/threads/356933-Another-Ghosting-Issue-Frame-Blending-Dillem...=1#post2250880)/ Had to resize back down and then out from SD PAL. So, any defects or noise, etc., in the PAL post are exaggerrated here. But it looks as if the aspect ratio is correct, given all the resizing, border fixes, etc. If working with the original VOB, these would be cleaner, less noise, sharper, and encoded as 720x480 NTSC, 23.976 with 3:2 pulldown, at 16:9 display aspect ratio. The revised frame size was 856x480 with borders to fill a 16x9 TV. Wish I had the source VOB, it would be cleaner. Bad flicker is obvious in the fight scene. I didn't see it in the original "MPG" post.
1.66:1 displays this way on HDTV for films made at this ratio for 20 years all over the world. 1.66:1 was the original VistaVision and European standard (Hi_Vision in Japan), which was expanded as a wider screen later. On a 4:3 TV it would be letterboxed.
Attachment 1 is near the start of the PAL clip. Attachment 2 is the fight scene (at the original film speed, it doesn't play like a Road Runner cartoon).
I might still be crazy, but....doesn't it look as if this originally was a wider vista and has been cropped on each side ?????Last edited by sanlyn; 19th Mar 2014 at 06:18.
-
Hi Sanlyn
Thank you for your samples! The difference in the aspect ratio is startling! If I understand, these are the specs I should be shooting for:
720x480 NTSC, 23.976 with 3:2 pulldown, at 16:9 display aspect ratio and I would start with this:
MPEG2Source("path to d2v\VTS_01_2.d2v")
AssumeTFF().QTGMC(preset="medium")
sRestore()
AssumeFPS(23.976)
I think this would be ok, too. I am correct?
AssumeFPS(24000,1001)
For getting the 1.6666666:1 in a 16x9 frame, what script should I use? Can it be included with the script above?
Thanks again! -
And to ask, what do you think about spline64resize? Is that a good filter? Is it better than spline32resize?
Thanks! -
Take a look at the resize options in Avisynth's documentation or at http://avisynth.org/mediawiki/Spline64Resize . There isn't much difference between spline36 and spline64, but '64' will work OK. There's also a link at the bottom of that Avisynth page to a comparison chart.
You shouldn't resize before denoising. Because some of the denoisers I used are in YUV but most of the color work and NeatVideo was in RGB, I resized in RGB. Resizing earlier will give you a big image to handle. And some denoisers require an image with mod-8 dimensions. So start by keeping all the left-hand and bottom pixels as-is and intact, as in the original VOB. For the time being you have to maintain the image aspect ratio that's on the DVD, even if it's incorrect.
I'm working out some numbers for the coding. Will return shortly.Last edited by sanlyn; 19th Mar 2014 at 06:19.
-
How to get this 16:9 video with an inner 1:666:1 image and a single resize: This will work only in RGB, and only with the 720x480 dimensions and borders as they existed on the source DVD.
After denoising and color are completed with the original 720x480 movie, resize as follows:
Code:Spline64Resize(672x488)
Thus you remove 10 pixels from the left, 1 from the top, 2 from the right, and 7 from the bottom. Then add borders to get the final image for 720x480 encoding. Height and width will both be mod-8:
Code:Crop(10,1,-2,-7).AddBorders(30,0,30,0)
Last edited by sanlyn; 19th Mar 2014 at 06:19. Reason: oooops. Wrong numbers in the script. Mmm, it's the forum's fault!
-
Hi Again,
First off, I would like to thank everyone for their help! I have a good NTSC version of the movie now, and I have learned so much in the process! I have a question, just for my own curiosity - the video's frame size was 704x480, if I am not mistaken. To make it 720x576 for PAL, could I have added borders in this manner: addborders(8,48,8,48). If I understand, the picture would have been unaffected, but it would be 720x576 for PAL.
Thanks again! You guys are brilliant! -
-
Hi Jagabo!
So adding borders stretches the frame? I figured that the center image would be the same, just framed by borders around it.
Thanks! -
-
No, you resize the existing 480 lines to 576 lines.
So that I understand, are you saying that I should use one of the various Avisynth re-sizers if I want to make a PAL frame of 720x576 frame?
And, not that I would do it, but would addborders(8,48,8,48) create a PAL compliant frame size? I am just curious.
Thanks! -
-
Hi,
By using addborders(8,48,8,48), I have created what looks like a letterbox around a 704x480 frame. That's what it looks like to me, but I have no clue really :P By adding borders all around, it also looks a bit squashed. What happens to the video when you add borders in this manner? What does it do to the picture?
Thank you again, Jedis of Videohelp!Last edited by hizzy7; 17th Jul 2013 at 09:39.
-
-
Thanks jagabo!
Would you be able to explain to me why adding bars changes the aspect ratio? I am just trying to understand. To me, adding bars shouldn't affect the picture in the middle. Why does the adding of bars throw everything off so?
You are amazing! Did youy learn all of this through trial and error?
Best
h
Similar Threads
-
Ghosting Issue/Frame Blending
By hizzy7 in forum RestorationReplies: 12Last Post: 18th May 2013, 22:31 -
How to deal with this frame blending situation?
By xuguang_he in forum RestorationReplies: 48Last Post: 3rd May 2013, 23:23 -
frame blending caused by MDegrain
By unclescoob in forum RestorationReplies: 16Last Post: 22nd Apr 2013, 01:53 -
Sporadic frame blending in PAL DVD of Soviet-era film
By chipsndukes in forum RestorationReplies: 3Last Post: 19th Apr 2009, 22:42 -
frame blending with mencoder
By spaceshotfever in forum LinuxReplies: 0Last Post: 14th Feb 2009, 12:46