VideoHelp Forum

Try DVDFab and download streaming video, copy, convert or make Blu-rays,DVDs! Download free trial !
+ Reply to Thread
Results 1 to 7 of 7
  1. I usually use the the KeyInt 250 default x264 setting when encoding videos for Blurays as it saves about 1 GB a disc compared to KeyInt 100 for 720p 50fps videos. It's no longer Bluray compliant when I do that but I've not seen a player that can't play it. When playing the video back on MPC-HC on my PC the seek time when clicking on a random time in the video is about a second or so but I didn't notice any delay on a Bluray played on a physical Bluray player when using the fast forward and rewind buttons on my remote control.

    Why isn't there a delay on the physical Bluray player? If there's no delay then is there any reason why I shouldn't use a really high KeyInt setting to lower the file size?

    What is the maximum KeyInt setting I can use?
    Quote Quote  
  2. The max keyint value to be fully Blu-ray compatible is 1 second. For a 50 fps video that's 50 frames.

    Your Blu-ray player is probably seeking to the nearest keyframe, not the frame you specified (unless it happens to be a keyframe). MPCHC has a "fast seek" option for this too.
    Quote Quote  
  3. Thanks. I was told for a 2 second GOP you could use KeyInt 100 and it would be Bluray compatible. As mentioned here:
    I'm using a much higher KeyInt anyway for a Bluray disc (I know it's not Bluray compliant but it still plays fine).

    What's the maximum KeyInt setting I can use? Any reason why I shouldn't use it?
    Last edited by VideoFanatic; 22nd Apr 2018 at 18:59.
    Quote Quote  
  4. You only need BD compatibility if you're authoring a physical BD disc.

    If you're just playing files off USB or non authored disc, usually the restrictions are much more relaxed. Then it depends on the particular model, but most can play typical settings with L4.1 . Some will still exhibit stutter and seek issues with longer GOP's or many b-frames or >4 reference frames . Some can play anything.
    Quote Quote  
  5. The compression benefit of higher keyints diminishes anyways as you go higher. 250 is already pretty high for most content. I find ~4 seconds to be a good sweet spot.

    Originally Posted by VideoFanatic View Post
    I was told for a 2 second GOP you could use KeyInt 100
    --keyint is defining the GOP length. --keyint 50 for a 25 fps movie: 50 / 25 = 2 seconds GOP length.
    You are allowed to use 2 seconds on Blu-Ray if the --vbv-maxrate is <= 15000.

    But as you found out most players don't really care unless you go too extreme where seeking makes them crash. Same with bframes. Blu-Ray allows not more than 3 consecutive ones but it doesn't really matter for most decoders.
    Quote Quote  
  6. I usually use about a keyframe interval around 50 myself. That gives a good balance between seekability and compression. I don't care about blu-ray compatibility. You can the interval as long as you want. But imagine how long it will take to seek to a random spot in the middle of a 2 hour movie encoded as a single GOP. The decoder has to go back to the first frame and decompress every frame up to the one you requested. It will take forever off optical media. If you're set for fast seeks you'll only be able to seek to the first frame of the movie.
    Quote Quote  
  7. Mr. Computer Geek dannyboy48888's Avatar
    Join Date
    May 2007
    Texas, USA
    Search Comp PM
    The only time I've had issues with high intervals is when cuttong media to remux. As you must cut on a I frame if you have a GOP of 250 you may have 9-10 seconds of extra material and some av sync. Same applies when inserting chapters. For just straight playback most players dont care on playback, just may act funny when Fast forwarding etc
    if all else fails read the manual
    Quote Quote  

Similar Threads