VideoHelp Forum




+ Reply to Thread
Page 115 of 115
FirstFirst ... 15 65 105 113 114 115
Results 3,421 to 3,439 of 3439
  1. Originally Posted by ProWo View Post
    I changed that because I noticed that in many movies with stereo audio, the two channels aren't balanced.
    yes, for stereo audio it makes more sense as long as stereo and multichannel are properly detected and separately processed.
    Quote Quote  
  2. btw, i noticed that latest ffmpeg builds (at least starting with 8.x?) are having issues writing the finished file to the disk if dynaudnorm applied only to one channel and there's splitting and joining involved. something to do with how newer builds are handling the buffering? not sure. are you aware of this "issue" and what might be a possible workaround for that?
    Quote Quote  
  3. Originally Posted by mannequin80 View Post
    btw, i noticed that latest ffmpeg builds (at least starting with 8.x?) are having issues writing the finished file to the disk if dynaudnorm applied only to one channel and there's splitting and joining involved. something to do with how newer builds are handling the buffering? not sure. are you aware of this "issue" and what might be a possible workaround for that?
    To apply dynaudnorm only to one channel, you can use the h switch, instead of splitting/joining.
    To apply to the FC channel only, append
    Code:
    :h=FC
    after the other switches.
    Quote Quote  
  4. Hi. It's been a while. I hope you're doing well.

    A new issue. I just updated both clever and ffmpeg... When I try to cut a mkv file [I don't see any option other than keyframe] as I have done many times, now when I go to preview the latest cut, the video playback goes to the end of the file and not to the cut. I tried it on 3 different files with similar results. The cut file is at the cut, but the preview is as I said. The indexing seems to be taking much longer too.

    Windows 11 system

    Click image for larger version

Name:	Screenshot 2026-03-31 060455.png
Views:	35
Size:	12.4 KB
ID:	91770
    Last edited by tb52; 31st Mar 2026 at 07:16.
    Quote Quote  
  5. Originally Posted by tb52 View Post
    A new issue. I just updated both clever and ffmpeg... When I try to cut a mkv file [I don't see any option other than keyframe] as I have done many times, now when I go to preview the latest cut, the video playback goes to the end of the file and not to the cut. I tried it on 3 different files with similar results. The cut file is at the cut, but the preview is as I said. The indexing seems to be taking much longer too.
    Thx for the hint, you are right, the preview is broken.
    I've fixed this now, please update.

    Btw: The indexing has'nt changed. The key accurate cut is available for avc (h264) and hevc (h265) videos only.
    Quote Quote  
  6. @ProWo
    3.5.3.02 feedback

    Thanks for adding pixel format qsv. Depending on the source and codec, it can accelerate encoding up to 25% on my Core Ultra.

    Nice to collect problematic batch tasks as yellow tasks after finish batch processing. Thanks.


    1. I discoverd a strange behaviour. When you change the pixel format for any encoder, WHA decoding always change to qsv and does not remain unchainged.
    That also happens when you switch to some none qsv encoders like DNxHR, av1-libaom, h264-amf, hevc-amf, hevc-nvenc, h266 (vvc). Some change to WHA decoding qsv when you switch direction up, some down!


    2. I still can't use qsv HWA decoding with normal filters like resize or rotation etc. As it is expected to use the qsv filter vpp_qsv.

    -vf scale=800:450
    need to be replaced with
    -vf vpp_qsv=w=800,vpp_qsv=h=450

    Therefore I retested qsv filter with ffmpeg 8.1
    For example scale does not longer slow down the encoding speed for the ARC1 series, compared to the normal filter and ffmpeg 8.0.

    Performance test for scaling from 1080p h264 to 800x450 h264:

    6,59x
    ffmpeg -i Input1.mp4 -map 0:0 -c:v h264 -global_quality 25 Output.mp4

    17,9x
    ffmpeg -i Input1.mp4 -map 0:0 -c:v h264_qsv -global_quality 25 Output.mp4

    19,8x
    ffmpeg -hwaccel qsv -hwaccel_output_format qsv -i Input1.mp4 -map 0:0 -c:v h264_qsv -global_quality 25 Output.mp4

    ---

    22,8x
    ffmpeg -i Input1.mp4 -vf scale=800:450 -map 0:0 -c:v h264 -global_quality 25 Output.mp4

    26,0x
    ffmpeg -i Input1.mp4 -vf scale=800:450 -map 0:0 -c:v h264_qsv -global_quality 25 Output.mp4

    36,4x
    ffmpeg -hwaccel qsv -hwaccel_output_format qsv -i Input1.mp4 -vf vpp_qsv=w=800,vpp_qsv=h=450 -map 0:0 -c:v h264_qsv -global_quality 25 Output.mp4

    Here we see a nice increase in performance!
    Quote Quote  
  7. Originally Posted by ProWo View Post
    Originally Posted by tb52 View Post
    A new issue. I just updated both clever and ffmpeg... When I try to cut a mkv file [I don't see any option other than keyframe] as I have done many times, now when I go to preview the latest cut, the video playback goes to the end of the file and not to the cut. I tried it on 3 different files with similar results. The cut file is at the cut, but the preview is as I said. The indexing seems to be taking much longer too.
    Thx for the hint, you are right, the preview is broken.
    I've fixed this now, please update.

    Updated and working beautifully again. Thanks
    Quote Quote  
  8. Originally Posted by Findu View Post
    1. I discoverd a strange behaviour. When you change the pixel format for any encoder, WHA decoding always change to qsv and does not remain unchainged.
    That also happens when you switch to some none qsv encoders like DNxHR, av1-libaom, h264-amf, hevc-amf, hevc-nvenc, h266 (vvc). Some change to WHA decoding qsv when you switch direction up, some down!
    Thx, will be fixed.

    -vf scale=800:450
    need to be replaced with
    -vf vpp_qsv=w=800,vpp_qsv=h=450
    vpp_qsv=w=,vpp_qsv=h= does'nt work here with me.
    Quote Quote  
  9. Originally Posted by ProWo View Post
    To apply dynaudnorm only to one channel, you can use the h switch, instead of splitting/joining.
    To apply to the FC channel only, append
    Code:
    :h=FC
    after the other switches.
    hmm, i think "volume" filter doesn't support the "h=" switch though so you'd have to apply volume to all channels in this case. what if you only want to apply it to center channel?
    Quote Quote  
  10. Originally Posted by mannequin80 View Post
    hmm, i think "volume" filter doesn't support the "h=" switch though so you'd have to apply volume to all channels in this case. what if you only want to apply it to center channel?
    No, the h switch is for dynaudnorm only.

    For the volume filter you must apply channelsplit/merge as before.
    Example for increasing left channel only with volume=6dB from a video with stereo audiostream index 1 and exporting this audiostream only:
    Code:
    ffmpeg -i input_audio_2ch -filter_complex [0:1]channelsplit=channel_layout=stereo[l][r],[l]volume=6dB[vl],[vl][r]amerge=inputs=2[aout] -map [aout] -c:a aac -b:a 192k -ar 48000 -vn -sn -dn output.aac
    Quote Quote  
  11. When I click on "Update", Clever closes instead of updating.
    Quote Quote  
  12. Originally Posted by davidt1 View Post
    When I click on "Update", Clever closes instead of updating.
    Which version are you using?
    Post the contents of your “clever FFmpeg-GUI” folder.
    Quote Quote  
  13. Originally Posted by ProWo View Post
    No, the h switch is for dynaudnorm only.
    sent you PM.
    Quote Quote  
  14. Originally Posted by ProWo View Post
    Originally Posted by davidt1 View Post
    When I click on "Update", Clever closes instead of updating.
    Which version are you using?
    Post the contents of your “clever FFmpeg-GUI” folder.
    It's working now. Just updated to v3.5.3.02. Didn't work before.
    Quote Quote  
  15. @ProWo

    Info: Updating to versions 3.5.3.01 and 3.5.3.02 has changed the previously selected app color.

    What if you could set the RGB color values for the background and borders yourself?

    ---

    Like Intel qsv, I did some testing for AMD amf.
    The syntax is the same for qsv and amf.
    So I tested
    -hwaccel amf -hwaccel_output_format amf
    -vf format=amf
    -vf vpp_amf=w=800,vpp_amf=h=450

    My AMD Ryzen 5 7530U with Radeon Graphics (Vega 7 2017-2019) does not realy accelerate from the amf filters.
    But Navi 1x, 2x, 3x, 4x might accelerate.
    So how about adding the pixel format amf for encoders av1_amf, h264_amf, hevc_amf?
    Quote Quote  
  16. Originally Posted by Findu View Post
    Like Intel qsv, I did some testing for AMD amf.
    The syntax is the same for qsv and amf.
    So I tested
    -hwaccel amf -hwaccel_output_format amf
    -vf format=amf
    -vf vpp_amf=w=800,vpp_amf=h=450
    So how about adding the pixel format amf for encoders av1_amf, h264_amf, hevc_amf?
    Thx for testing, will add it.
    I'll also add the scale replacement (vpp_) for QSV/AMF with related HWA decoding.
    Quote Quote  
  17. ----------------------------------------------------------------------------------
    April 25, 2026 release version 3.5.4.
    ----------------------------------------------------------------------------------

    Added:
    Quality settings on vp9_qsv encoder settings
    Pixelformat qsv on all qsv encoders
    Pixelformat amf for amf encoder
    Modified scale for amf/qsv encoders used with HWA

    Fixed:
    Bug with deleted inputfile, while app is open.
    Bug with , instead of . in fps24->23.976 preset
    Bug with cut preview
    Bug with add cuts to joinlist from batches

    Changed:
    Failed batch tasks handling
    Logo alignment
    cleverNorm / DynAudNorm coupling=off only for stereo outputs.

    ----------------------------------------------------------------------------------
    Quote Quote  
  18. Hi again,

    it would be great, when you add personal options to create your own presets.

    I've to do hundreds of files, so is it possible to make it easier for me?

    I need to set the DRC to OFF.
    Change lenth & pitch FPS 23.976 -> 25
    Set channel layout 5.1 (side)

    Thanks a lot, you do a great job.
    Quote Quote  
  19. @ProWo
    3.5.4 feedback

    - Added
    Quality settings on vp9_qsv encoder settings

    Retested with ffmpeg-2026-04-22-git-162ad61486-full_build. Still no effect for vp9_qsv on my system. All output files have similar file size and quality.


    - Added
    Pixelformat qsv on all qsv encoders
    Pixelformat amf for amf encoder
    Modified scale for amf/qsv encoders used with HWA

    Everything is working as expected. Thank you for adding the performance improvements.


    - When you change the pixel format for any encoder, WHA decoding now remain unchainged. Thanks.


    - When you change the encoder, WHA decoding now change to none. Good choice! Thank you.
    Quote Quote  



Similar Threads

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