Thanks to both, Acoustiking and Propellerhead. I followed your instructions and it worked flawlessly. Not only it was painless (Avisynth scripting gives me headaches), but the result was gorgeous, flawless 24p footage that I can edit directly in Premiere Pro. Loved it!
I've been a long time user of TMPGEnc encoder for it's quality and simplicity. After I saw your post, I updated to version 4.0, and I am very happy with the results. Once again, thanks. Awesome stuff!
Last edited by Kubrickian; 2007 December 3rd at 01:59.
I haven't got my HV20 yet but I have TMPGEnc 4.0 Xpress and I want to test it out. I downloaded the raw24p (on the first page) file but I dont know that to do with it. Which program do I use? Batch Encode Tool? or TMPGEnc 4.0 Xpress? I tried messing around with both but I couldn't get the raw 24p .mt2 footage to open
Last edited by zombiejoel; 2007 December 19th at 18:38.
Anyone?
How does it work? Capture footage with HDVSplit? Then convert the footage with TMPGEnc 4.0 Xpress using how to in the first post? Like I said before maybe i did it wrong but it wouldnt open the test .m2t file. Thats what HDVsplit will capture the video as right.. m2t?
hello everyone. I think this is great workflow. It works great. Except encoding takes way too long. I don't know what I'm doing wrong. The original clip I used was about 4 min and 50 sec long and the file size was approximately 950meg.
When I encoded with TMPG the file size was bumped up to 3.3 gig and encoding time took almost hour and half. Is this the usual time? Am I doing something wrong? I'm running pentium d 820 with 2 gig of ram. Thank you.
Problem solved. I was compiling multiple clips into one.... thanks!
I've tried this now with 10-15 different clips, and the result is always the same. My finished product looks exactly the way it did when I started it, complete with terrible interlacing. Has anyone had any problems with this but me? I've followed the step-by-step directions exactly as presented, but something isn't working. Is there any other setting I should change before I start this, or is there anything I should do with the finished video after the steps outlined in this thread? I've been working on this for a while now and I'm completely stuck.
Are you definitely processing a 24p clip (not just "cinemode")?Originally Posted by robdob
Yes, the clips I'm trying are 24p. In a day or two I'll do a video capture of exactly what I'm doing with the clips and put it on youtube and link to it here. At the very least that should make it obvious if I am doing something wrong.
I uninstalled and reinstalled TMPGEnc, and now I'm not seeing any problem. I'm not sure what was wrong before, but it works now. It looks great, too!
Thanks so much for this handy guide.
Has anyone figured out how to not have those first few frames eaten up by red in Adobe Premiere?
Using the m2t you provided, I converted and played with them. I am getting the red pixels in Premiere and they remain when I import the project into After Effects and are seen when rendering a final file out of AE.
Not a HUGE problem; should always have a good few seconds of nothing on your takes before whatever action, but it would be nice to know the cause of the problem and hopefully a solution.
I can't thank you all enough for this thread. It's probably the most helpful thing I've read so far on this forum. Sounds like I'll be dropping the hv20pulldown method and buying this program. The saved hard drive space and ease of use are my two favorite parts.
But I do have one question:
Has anyone experienced problems with audio being out of sync?
I know what you are talking about. I tried it once too. Did not see any difference when playing on PC. Got to try other methods and compare. My impression was it just made Vegas happy but the final rendering went same way as without pull-down.
What does "Change DC Component to '9 bit'" do? Why not leave it at 8?
I'm not having any problems getting 16:9 using MJ2K. I'm curious now as to what was causing the problems you were having with it.
Anyone?
From Tmpgenc XPress documentation
Some people recommend using values of 10 or higher, but there are limited returns in image processing at the expense of encoding times.DC component precision:
This controls the precision of the discrete cosine values used in the image compression (this translates the image into a series of interfering frequencies and lets the program eliminate frequencies that aren't visually relevant - this is similar to the compression used in JPEG images). Higher values results in better quality, at the expense of encoding time.
Seeing pixelation in number of frames after encoding..
First of all, I have to thank you for this wonderful thread.
I've encountered with a problem where I see pixelation in number
of frames after the encode. I set the exact value that was mentioned
in this forum and I see at least 2 or three pixelation frames in each
clip I exported. I was curious if I had bad footage but after reviewing
all the original captured clips, I found that pixelation frames only appear
on the encoded clips. Did anyone face similar problem? If so, do you
know the way around? I am at work so I can't test it out but I'll try to
reexport and see if this is some kind of error created during the encoding.
Thank you all.
Hi all,
I hope I'm OK to post this here as apposed to starting a new thread, I thought as this was the most pertinent one I should try here. I'm getting the HV30 which offers 30fps and even though I know that the 24fps is allowing a more cinematic/filmic look would the 30fps be a good compromise for the faster moving subjects without it looking too much like interlaced video. More importantly is the process for pull down removal with TMPGEnc 4 just the same except a template of 29.xxx fps
Thanks in advance
Harsha
Sorry to come so late to this thread.
I'm not so sure the statement above is correct. Theoretically they should all work the same way if they follow the MPEG-2 spec. But it's just code and some people write better code than others and someone may interpret the spec in different ways. So I wouldn't be so sure that all the difference is due to the encoding and none to the decoding.
Good luck.
Dennis
Do they run this kind of sale often?
Good luck.
Dennis
Well, it seems that I've found a rather major problem. Below is a screenshot from some footage that I have put through the method outlined on page 1. As you may see, I posted on this thread long ago, and ever since I have been using this method. But tonight I have come across these interlaced lines and I am rather worried. I have definitely used the right method (as I have just double/triple checked the settings). Either TmpgEnc doesn't work properly or something is seriously wrong. The still was captured from a Vegas timeline.
Please help me figure this out as this could be a major flaw in the workflow.
I've gone through the footage frame by frame to see if there is a pattern where the lines are appearing, but it seems to crop up somewhat randomly. There is certainly no obvious pattern that I can find (I'm a mathematician!).
I'm all ears!
I've been breaking my head about this for the past 24 hours now. My logic is as follows;
If everyone else says it works and it doesn't work for me then I must be doing something incorrectly. Then, if I was doing something incorrectly then I should change every possible parameter to try and fix the problem.
My first line of thought was that this could be due to recompressing back into an .m2t file, which we all know introduces the first generation of loss. So, to eliminate codec issues I tried several different ones, including lossless. All of them exhbited the same problem at the same frames. So, it can't be a codec problem. This led me to conclude that the problem is being introduced at the "Filter" stage in tmpgenc.
I recaptured the same footage from my hv20 (just in case the 1st capture hadn't worked properly???), then I imported it into TmpgEnc. I found a frame that exhibited particularly bad zig-zags (sorry, I don't know a better technical terms) and then I started to test out what exactly TmpgEnc is doing. As I'm sure you're all aware there is a dropdown box called "Deinterlace mode" in the relevant page of TmpgEnc. The first thing I did was to test the settings at the beginning of this thread. I set it to 24fps (Special Animation) and then I turned my attention to the Deinterlace Method dropdown menu. There are 11 options in this menu box, and I went through all of them, so I could compare the same frame output from each different method.
This is where I seemed to find the problem, or certainly a major cause for concern. I've included some screenshots so you can see for yourself what difference the Deinterlace Method makes. I have only included 4 different methods here (although I did go through all 11!)
None;
Interpolation - Adjusted
Inverse Pulldown
Weave
In my opinion, the Inverse Pulldown method absolutely does not look the best. Clearly it is not leaving me with 100% progressive frames otherwise I wouldn't have these lines. Or is it the case that this is quite simply the major flaw in having 24p in a 60i wrapper. I would love to try the cineform solution but I am way too poor to be able to buy it. Perhaps I could try the free trial, but then I'm scared there will be no way back (other than resorting to HV20 pulldown and then editing proxy files - EPIC). The Bottom line is that TmpgEnc does not work using the settings detailed in this thread.
Please give me your thoughts, or even better would be if you point out where I have made mistakes!!!
Would blowing up to 1920 x 1080 help? I don't seem to have this zig-zag problem...
pascalbrown, are you saying not to use the inverse pulldown method, and use another setting?
I'm saying that using the outlined method doesn't work. I'm not suggesting any other method because I don't yet know exactly how the other methods work. Perhaps when I get an answer regarding exactly what algorithm is being using for the various options then I will be able to reassess the situation. I would be most interested if someone else could replicate this test.
I should also add that I used After Effects CS3 to "guess pulldown" and there was no zig zaging in that footage. That leads me to conclude that there can't be a problem with the input footage as captured from the camera.
What happens when you just leave TMPGEnc on Deinterlace when necessary and don't mess with anything else? Does it still happen?
Posting Permissions
Reply With Quote
