View Full Version : .ts 1080i -> 720p
neo6
3rd August 2004, 22:22
I'm trying to transform a HDTV 1080i .ts 29.979fps YV12 FILM movie into 720p.
YV12InterlacedReduceBy2() does a wonderful job at deinterlacing and resizing the movie but the output is 960*544 and I want 1280*720.
I've tried:
- UnComb()
- Telecide() with different orders, guide on/off and so forth.
- TomsMoComp()
with resizers like:
- SimpleResize
- BicubicResize()
..but nothing gives the quality I get with YV12InterlacedReduceBy2(). I get frames mixed up on cuts nomatter what order I use. I also get some bluish glow on different objects now and then.
What could be wrong? Is it even possible to get the same quality on 1280*720 as YV12InterlacedReduceBy2() provides at 960*544? If so, what plugins should I use and which settings?
neo6
Emp3r0r
12th August 2004, 02:39
I've been doing a few .ts 1080i to 720p conversions lately to play back on my xbox. Here is a script I used for fightclub. I'm resizing to 960x720 for an animorphic encode.
LoadPlugin("D:\Programs\Avisynth\Plugins\dgdecode.dll")
MPEG2Source("G:\Fight Club\fc.d2v",cpu=0)
Crop(0,0,0,-8)
HorizontalReduceBy2()
LanczosResize(960, 720) #720p animorphic (0.69 megapixels)
I usually aim for 0.69 megapixels since the xbox can handle that. When a movie is 2.35 AR there is no need for animorphic. You can just encode to 1280x540 resolution. For example, here is one for Fellowship of the Ring
LoadPlugin("D:\Programs\Avisynth\Plugins\dgdecode.dll")
MPEG2Source("G:\Fellowship of the Ring\fotr.d2v",cpu=0)
Telecide(order=1)
Crop(4,144,-4,-152)
LanczosResize(1280, 540) #720p (0.69 megapixels)
Anyway, back to your question, sounds like you need to choose force film in DGIndex.
After doing some more inspection I noticed that you must use Telecide() and force film in DgIndex to get the 23.976fps
neo6
12th August 2004, 15:59
Thanks Emp3r0r. I'll try those scripts as soon as I get back to my own PC. It's vacation time.. :)
Mug Funky
12th August 2004, 17:36
have you tried IVTC on your source? if you're getting mixed up frames on a film source, that's probably the problem.
use decomb or smartdecimate (search is your friend)
if it is truly FILM source, you may be able to use the force film option of DGindex, or whatever the new dvd2avi is called :)
(btw, i work with PAL, so i don't have to deal with telecine much... however the avisynth usage forum has a load of expertise on this topic)
Toast
14th August 2004, 04:04
I've been doing a bunch of 1080i -> 720P conversions lately. Steps I take:
1. Correct errors and demux the .ts using ProjectX
2. Make cuts using Mpeg2Schnitt
3. Index the video using DGindex. Don't use Force Film option here. This will convert from 1080i at 59.94fps to 1080p at 29.97fps.
4. IVTC, crop, and resize using avisynth. This is the script I normally use:
# LOAD PLUGINS
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\DGDecode.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\UnDot.dll")
# SOURCE
mpeg2source("E:\Captures\ELR.d2v")
# DECIMATE
Telecide(order=1)
Decimate(cycle=5)
# CROP
#crop(4,0,1912,1076)
# RESIZE
LanczosResize(1280,720)
# DENOISE
UnDot()
That'll give you 23.976fps 720P if your source was film to begin with.
Emp3r0r
14th August 2004, 20:04
1. Correct errors and demux the .ts using ProjectX
Can you elaborate on this step. I've been playing around with projectX but whenever I add three 4gig ts files into a collection and try to demux them all, I get an OutOfMemoryException. I looked at Doom9's guide but I don't see anything obvious that I'm doing wrong.
Could you maybe post your projectX settings?
Also, when you demux with projectX does it give you a MPG file and an AC3 file that have errors corrected? Do you use AC3fix?
Are your cuts in Mpeg2Schnitt for commercials or to break up the filesize?
Toast
15th August 2004, 08:24
As far as ProjectX goes, the only option I have ticked is for creating .idd project files. Other than, it's a standard install. I haven't had any out of memory exceptions after updating to the latest JRE. If you're having trouble with memory errors, I'd try reducing the buffer size under the options tab and see if that helps.
ProjectX demuxes and spits out MPV and AC3 files which are analyzed and corrected for errors. The audio and video are also synchronized which is nice so that you don't have to worry about AC3 stream delay :) There should be no need to use AC3fix or Besliced afterwards as the audio stream is corrected for errors as well. The MD5 before and after using either is always the same so I stopped worrying about it.
My cuts in Mpeg2Schnitt are to cut out commercials. If you only need to split filesize, then there's no need for Mpeg2Schnitt because you can configure ProjectX to split it's output for you.
eb
16th August 2004, 05:05
Working with ProjectX there is no need to use latter any cutter.
In ProjectX you can cut off any commercials even if there are many of them. Having your file opened already in ProjectX, right click on the file name and click on OPEN CUT/SPECIALS.
eb
edited: added picture
http://img64.exs.cx/img64/4756/ProjectX1.jpg
Emp3r0r
20th August 2004, 18:40
haven't had any out of memory exceptions after updating to the latest JRE.Hey, I upgraded and that eliminated the out of memory error.ProjectX demuxes and spits out MPV and AC3 files which are analyzed and corrected for errors.I got this working. :D Thanks
Anybody get a capture of Jurassic Park III that was brodcast earlier this week? If so, was it broadcast in 1080i or 720p... what was the bitrate?
eb: is that a dvd you have open in project x?
eb
20th August 2004, 20:30
eb: is that a dvd you have open in project x?
HomemadeDVD from tvsat, but "normal" DVD can be succesivly processed by ProjectX, I mean .vobs.
eb
edit: add all vobs and process them in ProjectX with one pass, cutting off all weired pieces,
len0x
5th September 2004, 20:10
Originally posted by Toast
3. Index the video using DGindex. Don't use Force Film option here. This will convert from 1080i at 59.94fps to 1080p at 29.97fps.
Since when DGIndex changes frame rate from 60fps to 30?
Its was 30fps to begin with...
Does anyone of you have real 1080i 60fps source? (All I can see around is 30fps ones). I can see that one FAQ in this forum says that 1080i has 60fps in the specs and another one that is doesn't - where is the truth ? :)
Emp3r0r
7th September 2004, 05:03
Does anyone of you have real 1080i 60fps source? (All I can see around is 30fps ones) All the 1080i hdtv that I've seen are 29.976 fps.
Doom9
7th September 2004, 08:11
I can see that one FAQ in this forum says that 1080i has 60fps in the specs and another one that is doesn't Uhh.. there are two FAQs? The one I wrote comes directly from the specs (which I still keep around).. it ought to be as accurate as it gets.
len0x
7th September 2004, 09:01
Originally posted by Doom9
Uhh.. there are two FAQs? The one I wrote comes directly from the specs (which I still keep around).. it ought to be as accurate as it gets.
One is "ATSC (US Digital (HD)TV standard) Basics":
The ATSC standard supports the following input resolutions and framerates:
1920x1080 at 23.976/24/29.97/30 fps progressive, and 29.97/30 fps interlaced.
Another "is HDTV (US ATSC) FAQ":
What resolutions are digitally broadcast?
Vertical Aspect
lines Pixels ratio Picture rate
1080 1920 16:9 60I, 30P, 24P
Is that 60i actually meant to be 30i ?
Doom9
7th September 2004, 10:22
29.97/30 fps interlaced = 59.97I / 60I so there's no disagreement here. I'd say there's no 30I because 30 fields per second = 15 frames per second. But in the end it's a matter of how you want to specify field or frame rates. imho, the x fps interlaced/progressive makes more sense as there is no room for confusion.
len0x
8th September 2004, 00:37
Originally posted by Doom9
29.97/30 fps interlaced = 59.97I / 60I
OK, my bad - I read 60I as "60fps interlaced". Another question though: 60I - makes it 30 fps interlaced, where I assume each frame is interlaced, right? Then can we call 24fps telecined to 30fps also interlaced (like in DVDs)? Coz all I see in 1080i movie samples I have is telecined FILM material that I would never call interlaced.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.