The output of my script is 29.97 fps interlaced. You should use that in CCE. And if you convert to RGB for TMPGEnc you should use ConvertToRGB24(interlaced=true). Otherwise the chroma channels will get messed up.Originally Posted by mickgreen58
+ Reply to Thread
Results 31 to 40 of 40
-
-
Thanks for responding
I always use the settings that I learned on this forum.
https://forum.videohelp.com/topic222898.html?sid=99eaa31f95e62651cce16f43b94e18db
The only difference is of course, the N/M values and M value, which of course, we talked about changing to 3.
Also, "for DVD" is never checked.
To go off on a tangent for a second. I only use the "ConvertToRGB24()" because FitCD puts that in there as a default.
Alexander thought I should use "ConvertToYUY2()" and Jagabo says "ConvertToRGB24(interlaced=true)". Obviously, I don't know the difference, so could someone help me with this portion? Also, if I ever need to use my old encoder (sometimes I do) WinAvi, would that change what this value should be? I automated alot of my encoding by writing an app in VB.Net and I would just change my code to put in a correct value for this in the avs script.
Okay, so now I will encode at 29.97 and I am assuming I keep N/M=3 and M=3? I will give details, once I am done. -
No, I said if you are using ConvertToRGB24() for TMPGEnc you should use ConvertToRGB24(interlaced=true) when using my script. Note that TMPGEnc will also accept YUY2 and YV12 but it will internally convert them to RGB.Originally Posted by mickgreen58
CCE works best (fastest, and it's always best to avoid conversion to RGB) with YUY2 video so you would use ConvertToYUY2(interlaced=true) for CCE (assuming your source is YV12, if it's YUY2 already you don't need to do the conversion again). The "interlaced=true" argument is necessary because the AVS script produces interlaced frames from your progressive source.
Note that my script outputs bottom field first interlaced frames. If you want top field first add AssumeTFF() right after the AVISource() line. -
An important thing about resizing. Since this script makes video interlaced (by separating fields and combining them from different frames), you have to be careful and resize (or apply other filters) while video is yet progressive - before separating fields and better before doubling framerate (to make it faster). This prevents serious artifacts.Originally Posted by mickgreen58
As jagabo already explained, for CCE you need YUY2 (RGB is for TMPGEnc) and if it is used in the end (where the video is interlaced), it should have 'Interlaced=true' parameter.
Then if you use CCE, its setting for field order should match the script's output which is BFF here (in CCE 'Advanced' tab 'Output TFF' should be unchecked with 'offset line' = '0'). So it will look like this:
AVISource("C:\myavi.avi")
LanczosResize(656,336,0,0,512,384)
AddBorders(32,72,32,72)
ChangeFPS(59.94)
SeparateFields()
SelectEvery(4, 0, 3)
Weave()
ConvertToYUY2(Interlaced=true)
Or for TFF in CCE ('Output TFF' checked,'offset line' = '0'):
AVISource("C:\myavi.avi")
LanczosResize(656,336,0,0,512,384)
AddBorders(32,72,32,72)
ChangeFPS(59.94)
AssumeTFF()
SeparateFields()
SelectEvery(4, 0, 3)
Weave()
ConvertToYUY2(Interlaced=true)
If you want progressive, try that MVTools thing, it is also potentially better in motion reproduction since doesn't use repeated fields.
As for your GOP size question: unless you plan applying pulldown after encoding (the above scripts are for encoding at 29.97), leave default settings which in CCE templates are 15 (3x5) for NTSC (legal values up to 18) and 12 (3x4) for PAL (up to 15). -
Thanks for the feedback everyone.
After my last run (details are below), the video and audio was out of sync. I have finally decided to give up on this one (which sucks because this anime is pretty rare) and just wanted to thank everyone for their help the last couple of days.
AVS Script
AVISource("C:\mymovie.avi")
ChangeFPS(59.94)
SeparateFields()
SelectEvery(4, 0, 3)
Weave()
LanczosResize(656,336,0,0,512,384)
AddBorders(32,72,32,72)
ConvertToYUY2()
CCE
29.97 FPS
N/M=3, M=3
DGPulldown
Custom = 20.00 to 29.97 -
No! Don't run DGPulldown after the hard pulldown script. The video is already 29.97 fps interlaced out of the script. All you have to do is encode as 29.97 fps interlaced MPEG (as you've done) and author to DVD.Originally Posted by mickgreen58
And as Alex_ander has already pointed out, move the LanczosResize() and AddBorders() before ChangeFPS(). -
Okay, I did all of the above and all of the 20 FPS video clips played through its entirety. I noticed a a significant amount of what I would describe as jerkiness, if anyone knows how to handle that, I would be grateful, if not, I am content with the results as only 4 out 26 files have this frame rate.Originally Posted by jagabo
-
If they look more jerky than earlier efforts you probably have the wrong field order. The script outputs bottom field first video.
In CCE go to the Advanced Video Settings dialog. Make sure that Output Top Field First Stream is disabled and Offset Line is set to 0. Or enable Output Top Field First Stream and set Offest Line to 1. -
Jagabo, your suggestion worked brilliantly.Originally Posted by jagabo
I want to thank everyone that took the time to provide me with the information I needed to complete my task.
- Mike G.
Similar Threads
-
To synchronize 29,970 audio fps for 23.976 fps
By DruidCtba in forum Newbie / General discussionsReplies: 1Last Post: 27th Sep 2009, 13:01 -
Sync 29.970 FPS audio to 23.976 FPS video?
By LCO1971 in forum Newbie / General discussionsReplies: 3Last Post: 13th Sep 2008, 16:23 -
Difference between 23.976 fps and 23.98 fps ???
By wasimismail in forum Authoring (VCD/SVCD)Replies: 5Last Post: 27th May 2008, 01:42 -
Converting 23.976 fps to 29.97 fps
By wasimismail in forum Video ConversionReplies: 8Last Post: 14th May 2008, 19:26 -
Converting 23.976 fps to 29.9 fps
By zanos in forum Video ConversionReplies: 4Last Post: 13th Apr 2008, 10:03



Quote