VideoHelp Forum




+ Reply to Thread
Page 2 of 2
FirstFirst 1 2
Results 31 to 39 of 39
  1. Originally Posted by clashradio View Post
    When I drop the file in Vegas, it sees it as progressive. I change Project Properties to UFF and the clip as well?
    Yes, again all 3 need to be UFF . Clip interpretation, Project properties, render settings

    Vegas sees something as progressive because you didn't encode the intermediate as interlaced TFF , or perhaps the format you chose didn't convey that information. It's easy to override


    Would it be easier, or better to try to figure out Sharc's script and render the video clips to 23.976? Then I could use the m2ts files (the ones at 23.976) in the Vegas timeline as well without needing to convert those to an AVI file.
    For me either way is "easy" . Some people find it difficult to set up RIFE. You have to download models, get the directory location correct. There are dozens of models. Some work better than others on specific sources. You have to fiddle a bit. It's also quite slow.

    The decision criteria for me is if the source is interpolated (resampled) cleanly, without obvious artifacts. It looks ok on that test clip, but maybe you have other clips /songs that look terrible with artifacts . Certainly 23.976p native for everything virtually eliminates any potential player playback problems with cadences or switching... but terrible artifacts would make it unusable IMO . Blends like you originally had would be better than terrible artifacts. You cannot determine the result until you try it with RIFE, there is no way to know ahead of time if it works cleanly or not.

    Pros/cons. You have to decide what's best for you
    Quote Quote  
  2. Originally Posted by clashradio View Post
    Would it be easier, or better to try to figure out Sharc's script and render the video clips to 23.976? Then I could use the original m2ts files (the ones at 23.976) in the Vegas timeline as well without needing to convert those to an AVI file.
    You mean true interlaced video clips with distinct 59.94 fields/s? You would loose motion fluidity when you convert these to 23.976 progressive. You better author these as separate 1080i29.97 titles on the same blu-ray disc, IMO. Very most players should be handling it.
    Quote Quote  
  3. Originally Posted by Sharc View Post
    You mean true interlaced video clips with distinct 59.94 fields/s?

    He only has 25p (srestore deblended) and 23.976 sources (native progressive, and some at 29.97 I'm assuming telecined). No true interlaced content for that project
    Quote Quote  
  4. Originally Posted by poisondeathray View Post
    Originally Posted by Sharc View Post
    You mean true interlaced video clips with distinct 59.94 fields/s?

    He only has 25p (srestore deblended) and 23.976 sources (native progressive, and some at 29.97 I'm assuming telecined). No true interlaced content for that project
    Oh I missed this. It makes a difference of course.
    And yes. RIFE can be a bit tricky. I am not aware of guidelines about which model to choose for what scenario. It's time consuming trial and error to find the "best". I had a case where model 25 totally failed for example.
    Last edited by Sharc; 23rd Mar 2025 at 15:01.
    Quote Quote  
  5. Member
    Join Date
    Nov 2006
    Location
    United States
    Search Comp PM
    Originally Posted by poisondeathray View Post
    Yes, again all 3 need to be UFF . Clip interpretation, Project properties, render settings. Vegas sees something as progressive because you didn't encode the intermediate as interlaced TFF.
    I had no idea about clip interpretation. I've always used all matching clips for every project. I thought I had to. (720 60p clips in a 1280x720 60p project) etc. Still don't totally understand that concept, but I'm working on it.

    It sounds like RIFE is ideally what I want, but as you said it sounds difficult and I'm sure you've figured out I'm below average on AVISynth understanding. There's no way I could understand how to find the correct models etc.
    Quote Quote  
  6. Originally Posted by clashradio View Post
    Originally Posted by poisondeathray View Post
    Yes, again all 3 need to be UFF . Clip interpretation, Project properties, render settings. Vegas sees something as progressive because you didn't encode the intermediate as interlaced TFF.
    I had no idea about clip interpretation. I've always used all matching clips for every project. I thought I had to. (720 60p clips in a 1280x720 60p project) etc. Still don't totally understand that concept, but I'm working on it.
    Many intermediate formats do not have AR or interlace field order flags, or they are not read by programs like vegas or other NLE's (not just vegas).

    The flags tell the editor what the clip should be interpreted as "automatically" . It's trivial to assign them in the editor, if it interprets the file incorrectly, or the file was not flagged, or improperly flagged . But it's important to check that all 3 categories are setup the way you want them to be setup, or "bad things happen" .


    Originally Posted by clashradio View Post
    It sounds like RIFE is ideally what I want, but as you said it sounds difficult and I'm sure you've figured out I'm below average on AVISynth understanding. There's no way I could figure out models etc.
    Really it's not that bad to setup, and you have people around if you need help. I'm just warning you that some people find it difficult, like avisynth in general

    But the quality is much better than mvtools2 interpolation overall. It's worth getting it working IMO .
    Quote Quote  
  7. Member
    Join Date
    Nov 2006
    Location
    United States
    Search Comp PM
    I'm one of those ppl that finds this difficult. Just hard to absorb and understand a lot of this stuff.

    Is it possible I'd get lucky and have all of the video-sourced clips use the same RIFE script (at least for this project)?
    Quote Quote  
  8. Originally Posted by clashradio View Post
    Is it possible I'd get lucky and have all of the video-sourced clips use the same RIFE script (at least for this project)?
    You have to check everything. Don't assume anything. People make mistakes, and production companies make mistakes or perhaps bad decisions - it happens

    You already mentioned some film clips were 23.976, others were 29.97. Don't assume the 29.97 had clean telecine. Maybe other process were applied on the way like the blended clips. Maybe other things need to be done to "fix" them

    If they were all blended like that sample clip, but from a 25p source, you'd need to double rate deinterlace / srestore first to unique frames before applying RIFE . You always need unique frames before this type of frame interpolation (resampling) to do it properly
    Quote Quote  
  9. Member
    Join Date
    Nov 2006
    Location
    United States
    Search Comp PM
    Looks like I'll definitely want to use RIFE. Don't want to re-due this project for the third time.

    Thanks Sharc & poisondeathray. I'll have to take some time to try to learn this plugin. Sounds like it's amazing for what I want to do.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!