Can I convert 30p to 24p using TMPGEnc? If so can anyone show me the steps?
Can I convert 30p to 24p using TMPGEnc? If so can anyone show me the steps?
Thanks for your reply BoobyMurcerFan
[QUOTE=BobbyMurcerFan;17461]Well it seems like HV20Pulldown is creating an AVI with 24bit sound and TMPGenc is creating one with 16bit sound. ]
Just to be clear, it is video sample size (by windowsXP file properties) that differs between the output files of the TMPGEnc and HV20pulldown.exe methods, not audio sample (which is PCM 16bit 1536 kbs for both methods)
...as above, after googling this parameter, my best guess is that this difference in *video sample size* reflects the colour space used leading in to AVI coding and may be increased by VirtualDubMod's "Full processing mode" video setting? Although i could be wrong.
I doubt it reflects a true difference in video quality, as the reverse pulldown should simply involve removing frames, and the coding to Lagarith should be essentially identical between methods. Although again I could be wrong.
"What format are you going to be working with in your NLE?"
I'll likely be editing in Vegas 7, 24p 1080x1440. As MPEG re-encoding is lossy I will probably export from TMPGEnc (or HV20pulldown.exe) to lagarith. The playback from this is too choppy to be able to edit efficiently so I will need to learn how to create intermediate files.
I'm editing my wedding footage and will want to have crisp HD quality output for eventually burning to BluRay or HDDVD, but in the interim will also produce an SD DVD for family.
One method I have used is to edit with m2t and then swap in the lossless AVI when it is time to render/export. All you do is move the source files to a different location on your hard drive, then open your project and when your NLE asks you where the missing files are, you point it to the replacements (of course, depending on how many files you are dealing with, this could be a little tedious).Originally Posted by von_Rodg
Thanks Frank, I'll definitely give that a go.
von,
Well I actually wasn't much help, sorry. But Frank ROCKED! Thanks so much.
Dang! This thread needs to be stickied... it worked for me! Thanks!
As I understand it, you're going to have compression losses if you use any lossy codec such as MPEG to output your final product.
Personally I use TMPGEnc only for stripping out the pulldown and publishing to 1440x1080/24 or 1280x720/24 WMV files that I can playback through my Xbox360.
When I decide to start cutting down the footage I've collected over the summer, similar to what you've suggested, I'll either use the Cinepak codec or one of the lossless codecs as an intermediate during editing and for creating a final "print". I'll then use TMPGEnc to rerender the final "print" as a WMV, HDV or QT file depending on how I want to publish the material.
hey guys, i followed all the steps in perfectly but for some reason my footage is still horribly interlaced after i encode with TMP.
is the footage still supposed to be interlaced after the pulldown is removed? or is de-interlacing a whole different process altogether that i need to take care of?
De-interlacing is part of the reverse pulldown process. If you are seeing interlacing artifacts, i.e. "combing", then either you didn't remove pulldown or else it wasn't done correctly.
For example, if you use 2:3:3:2 pulldown removal on HV20 footage, it will look terrible, because it has 3:2 pulldown added so you need to use 3:2 pulldown removal.
I did this and for the most part the video looked great. I only had a few problems. The beginning had the first few red frames like was said earlier I believe. Then, at random parts of the video I get random artifacts that seem to show frames from previous scenes. I use premiere pro cs3 to capture and tmpeg to remove pulldown.
UPDATE: I noticed these glitches are only showing up in premiere, because when I use my media player to play back the file, they're not there. Also, I'm using the Canon 24p preset in premiere pro cs3.
Last edited by morphinapg; 2007 September 13th at 18:37.
Okay, if anyone else is having this problem, try changing your settings in TMPGenc 4 to program stream instead of transport stream. That seemed to fix it. I guess premiere didn't like working with transport streams.
i figured how to use it and it works like a charm. no problems at all.
my video looks great now. pure, beautiful 24fps
this program is great because it's fast and easy
Sorry guys, I know this is an HV20 forum, but you guys have been doing some amazing work/research.
Do any of you use HVR-V1Us and follow this same approach? I just bought Aspect HD because I thought it was my only choice, I had no idea there were all these alternative solutions.
Wanted to let you all know that TMPGEnc is on sale right now for ~$70 from their website.
Thanks very much for this info, I successfully converted to 24p files! I am now editing in Vegas 7, 24p 1080x1440.
I am still unclear on what are the steps to create:
1. 24p SD DVD
2. 1080p wmv file
How do I export from Vegas and then how to make the DVD so that I maintain optimal quality?
file > render
Thanks, I actually mean what presets exactly, etc. There are tons of options, and I have rendered with lots of them but the output looks choppy. What presets/custom settings do you use?
Usiong CS3 I started new project with HDV 1080p30. When I go into Project> Project Settings> General I see:
Editing = HDV 1080
Timebase = 29.97
Both these options are greyed out and will not allow me to change them to 23.976. Any ideas?
I think once you create a project, you can't change the settings. You need to choose 24p when creating the project. If not available, I think there is a plugin to address that.
Isn't this method going to cause three generations of transcoding for a typical workflow? Capture to MPEG2, remove pulldown and re-encode to MPEG2, and then edit and re-encode again for your final output? This introduces an extra transcode that isn't really needed doesn't it?
Taynt: it's really no different than using the other pulldown removal methods, and it can be exported as uncompressed from tmpgenc if so desired.
As an aside, I agree this would be a good thread to make sticky, as it is a very straightforward easy to use method for doing pulldown removal.
TMPGEnc 4.0 XPress & Pulldown
I bought Xpress 4.0 and I also bought Morgan MJ2k, I also downloaded the demo of Edius, from mi finding I see that the best codec is Canopus HQ. The transcoding from m2t to canpus HQ codec takes 4 minutes for each minute of m2t files, the transcoding to Morgan MJ2k, takes abut 9 minutes for each minute of m2t files. I have found a problem with Morgan mj2k codec it only outputs to 4:3 ratio no mater what I do while Canopus HQ does 16:9.
The canopus HQ files play with out any stutter, as they are with out problems while the MJK2 do stutter, unless I adjust the layers to 1. my computer is a Pnetium4-HT 3ghz, with 1.5gigas of ram. The biggest problem I see with the morgan codec is this 4:3 ratio thing which I do not see any way to fix it. If I open the files in any media player the files appear square, and when I see the the properties of the files it states that it has 4:3 ratio.
Any Ideas on how can I get 16:9 on the morgan codec?
Morgan MJPEG2000 is intended as an intermediate codec, NOT for distribution. Any NLE worth its salt should be able to handle anamorphic video such as HDV (PAR=1.333).
Morgan MJPEG2000 is an intermediate codec
I thank you for your comment, I do understand, that Morgan MJPEG2000 is an intermediate. I capture my video with the HDVsplit, to remove the pulldown I use the Tmpeg 4.0 Xpress, as explained here, I choose the morgan MJ2k, as the intermediat codec, the resulting file has the HDV resolution, but the ratio is 4:3. If I use this file in premier with the HDV parameters, and I rerender with the HDV parameters again in the morgan codec the resulting video has the HDV resolution but with the 4:3 ratio. That is what I find odd.
If it has HDV resolution but is 4:3, all that means is that your NLE is assuming square pixels. Interpret Footage and tell it the pixel aspect ratio is 1.33 and you should be good.
If you are already doing this, then maybe you need to export from Premiere as 1920x1080 with square pixels. That way whatever you play it on doesn't have to worry about the PAR.
My point is that until you output for distribution, you should be working in software where you can set the PAR. When you do get to that final output, you shouldn't be using MJPEG2K (or any other intermediate) because noone who doesn't have the codec will be able to play it.
Last edited by Frank; 2007 November 23rd at 13:31.
Posting Permissions
Reply With Quote