VideoHelp Forum
+ Reply to Thread
Page 41 of 41
FirstFirst ... 31 39 40 41
Results 1,201 to 1,210 of 1210
Thread
  1. The Fix framerate code wasn't changed since version 3.3.0.04.
    Did you do the fix with the sample or the complete video?
    Last edited by ProWo; 22nd Oct 2024 at 13:58. Reason: typo
    Quote Quote  
  2. @ProWo I tried the Fix Framerate to 23.976 using Beta v3.3.0.03 & v3.3.0.04 & both had the same results with the sample I provided & the complete video, I can't get it to change from 23.81 fps to 23.976 fps.
    Quote Quote  
  3. Originally Posted by oniiz86 View Post
    @ProWo I tried the Fix Framerate to 23.976 using Beta v3.3.0.03 & v3.3.0.04 & both had the same results with the sample I provided & the complete video, I can't get it to change from 23.81 fps to 23.976 fps.
    Try another way.
    Load this video, click main page, click extract streams.
    Select only the hevc videostream on the left and click extract. Select as raw stream.
    In your target folder you'll find a new file with .h265 extention.
    Load this file in clever FFmepg-GUI, it will ask you for the FPS. Insert 23.976 and click ok.
    The file is copied and reloaded automatically. It should show 23.976 fps now.
    If so, click on multiplex, drag & drop your original 23.81fps video into the grid, deselect it's videostream and click multiplex.
    Quote Quote  
  4. @ProWo That seems to have worked successfully but when it told me to enter the fps, I entered 23.976 which then turned the raw hevc video stream into the mp4 file container, so while the re-muxed file now reports 23.976, the frame rate mode is "Variable" not "Constant" like it ought to be.
    General
    Unique ID : 327239617099157056412992474514578398043 (0xF6300EC91AB2F692D4ECE15DD702DB5B)
    Complete name : C:\Clever ffmpeg GUI\Beetlejuice 1988.mkv
    Format : Matroska
    Format version : Version 4
    File size : 3.63 GiB
    Duration : 1 h 32 min
    Overall bit rate : 5 646 kb/s
    Writing application : clever FFmpeg-GUI
    Writing library : Lavf61.1.100
    ErrorDetectionType : Per level 1

    Video
    ID : 1
    Format : HEVC
    Format/Info : High Efficiency Video Coding
    Format profile : Main 10@L4@Main
    Codec ID : V_MPEGH/ISO/HEVC
    Duration : 1 h 32 min
    Bit rate : 4 510 kb/s
    Width : 1 920 pixels
    Height : 1 080 pixels
    Display aspect ratio : 16:9
    Frame rate mode : Variable
    Original frame rate : 23.976 FPS
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 10 bits
    Stream size : 2.90 GiB (80%)
    Writing library : x265 3.5+37+12-4e46995bc:[Windows][MSVC 1931][64 bit] 10bit
    I wasn't clear if you had altered the code in the upcoming Beta v3.3.0.05 for the "Fix Framerate" setting & that is why you were successful in getting my sample file to report 23.976 after the fixing process, I suppose it would be a long shot if it were a Windows 7 issue & that is why the "Fix Framerate" setting isn't working for me, I know sounds pretty doubtful.
    Last edited by oniiz86; 24th Oct 2024 at 02:12.
    Quote Quote  
  5. Originally Posted by oniiz86 View Post
    @ProWo That seems to have worked successfully but when it told me to enter the fps, I entered 23.976 which then turned the raw hevc video stream into the mp4 file container, so while the re-muxed file now reports 23.976, the frame rate mode is "Variable" not "Constant" like it ought to be.

    I wasn't clear if you had altered the code in the upcoming Beta v3.3.0.05 for the "Fix Framerate" setting & that is why you were successful in getting my sample file to report 23.976 after the fixing process, I suppose it would be a long shot if it were a Windows 7 issue & that is why the "Fix Framerate" setting isn't working for me, I know sounds pretty doubtful.
    I've found the reason for our different results. It is your ffmpeg version.
    I have seen that you are using version 7.0.1 essentials.
    I did the fix framerate test with this version and got your results.
    So update your ffmpeg version, preferably with the latest nightly (if you have a 64 bit OS).
    You should also always use a full version.
    Quote Quote  
  6. Originally Posted by ProWo View Post
    I've found the reason for our different results. It is your ffmpeg version.
    I have seen that you are using version 7.0.1 essentials.
    I did the fix framerate test with this version and got your results.
    So update your ffmpeg version, preferably with the latest nightly (if you have a 64 bit OS).
    You should also always use a full version.
    Thanks for troubleshooting, unfortunately Windows 7 & 8 no longer support full or shared builds, only essentials, previously I was always using full shared builds, the following was posted back in June in the changelog here https://www.gyan.dev/ffmpeg/builds/

    "release 7.0 and git 2024-05-23-git-ece95dc3dc are the last full builds to support Windows 7 and 8. The rav1e lib can no longer be built for that target"
    Quote Quote  
  7. @ProWo I used the FFmpeg 7.0 full build you linked above but had the same result, the file using the Fix Framerate setting remains at 23.81 fps.
    Image
    [Attachment 83073 - Click to enlarge]
    Quote Quote  
  8. Then you're out of luck.
    I would upgrade to Windows 11.
    Quote Quote  
  9. ----------------------------------------------------------------------------------
    October 25 2024 release version 3.3.1.
    ----------------------------------------------------------------------------------
    Added:
    Change framerate without recoding for mpeg2 videos.
    h264_qsv and hevc_qsv encoding with hardware acceleration (for Intel GPU's).
    h264_amf and hevc_amf encoding with hardware acceleration (for AMD GPU's).
    mpeg2_qsv (for Intel GPU's), h264_nvenc and hevc_nvenc (for nVidia GPU's) hardware accelerated encoders.
    (I cannot test the nVidia and AMD hardware acceleration because I do not have the related hardware. So test it and report here if it works or if errors occur.)
    Output filename check for existing files or batch tasks.
    Chapters creating: automatic insertion of start chapter at starttime 0 (video start), so that chapter 1 is now reached by the player commands.
    Output file names check.
    webvtt subs muxing in 3gp,mp4,mov.

    Fixed:
    Bug in mpeg1/mpeg2 stream extraction raw or container(thx to Amiga for the hint).
    Bug in mpeg2 encoding/extractiing.
    Bug in filterchain with scaling.
    Muxing hevc to mp4 gave wrong FPS values.
    Encoding HDR to BT709 without tonemapping error (thx to javieracdc for the hint).
    App vanishing when minimized.
    Bug with av1 encoding (thx to Marcellos for the hint).
    Bug in chapters naming.
    Bugs in output file naming.
    Bug in forms positioning.
    Bug in audio channels remap.
    Bug in batch file handling.
    Bug in crops handling.
    bug in change framerate (various)

    Improved:
    Recognition of already processed streams and still open tasks.
    Video stream indexing (completely rewritten).
    HDR Info,.
    Muxing grid handling.
    Join grid handling.
    Many code improvements.
    Application stability.
    Crop handling code.

    Changed:
    ffmpegsource2 instead of lwlibavvideosource because of missing UTF8 support (with avisynth).
    FFmpeg commandline execution code is centralized now.
    Output files destination handling.
    Output file naming.
    Commandline for nvenc hardware encoding.
    ----------------------------------------------------------------------------------
    Quote Quote  



Similar Threads

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