clever FFmpeg-GUI, small FFmpeg UI, fully portable, no installation.

[ProWo]

I found batch task thing problems!
One audio batch task get processed, but two not. A 0 kb file for the first batch is created but the encoding does not start.
Video batch tasks work normal.

I cannot replicate this error.
It could be due to the fact that the index of the audio stream from batch0 does not correspond to an audio stream in the replicated video.
To avoid this in the future, I have introduced a background check for defective batch tasks.

When you have one audio batch task and switch to scan for errors batch scan, all is fine.
When you have two audio batch tasks and switch to scan for errors batch scan, the following exception occurs
immediately:

This error occurs when you hover over the action field with the mouse before the grid has loaded.
This has now been fixed.
In one of the latest nightlies, I added a new feature to the batch tasks; when you point the mouse at the action field of batch0, the command line of batch0 is displayed. This allows you to see what is being replicated.
Does not work for stream cut/error scan batches, for obvious reasons.

[ProWo]

When muxing, Clever now defaults to MKV again. Used to memorize the last format/container used. Please fix.

Cannor replicate this.
Retested. Is memorized as aspected.

[bb84000]

Hello !

Anyway, I've changed the code to avoid this conversion. Update to .19

Thanks, I will get it.

Edit: Same exception with .19 version, I select a file and then, click on cut button :

System.InvalidCastException: La conversion de la chaîne "0.000000" en type 'Double' n'est pas valide. ---> System.FormatException: Le format de la chaîne d'entrée est incorrect.

Conversion of string "0.000000" to 'Double' type is invalid. --> Incorrect input string format


à Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
   à Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   --- Fin de la trace de la pile d'exception interne ---
   à Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   à clever_FFmpeg_GUI.Form8.Indexing()
   à clever_FFmpeg_GUI.Form8.Set_v_stream()
   à clever_FFmpeg_GUI.Form8.Track_test_V()
   à clever_FFmpeg_GUI.Form8.Form8_Load(Object sender, EventArgs e)
   à System.Windows.Forms.Form.OnLoad(EventArgs e)
   à System.Windows.Forms.Form.OnCreateControl()
   à System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   à System.Windows.Forms.Control.CreateControl()
   à System.Windows.Forms.Control.WmShowWindow(Message& m)
   à System.Windows.Forms.Control.WndProc(Message& m)
   à System.Windows.Forms.Form.WmShowWindow(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hope it can help you

bb

[videoAI]

@ProWo
v3.4.4.19

By moving to an incremental update, where only components
that change get updated, the update process can be sped up.

A simple file check can verify the DLLs existence. There is no
need to unzip and over write them if they haven't changed.

As always, thank you, and keep up the good work.

[ProWo]

Edit: Same exception with .19 version, I select a file and then, click on cut button

You have PM

[bb84000]

Hello,

Same exception error with .20 version. If i choose to continue, I can set cut points and preview cut video. But if execute the cut, I get a null file with srt extension.

Thank for your support,

bb

[ProWo]

Hello,

Same exception error with .20 version. If i choose to continue, I can set cut points and preview cut video. But if execute the cut, I get a null file with srt extension.

Thank for your support,

bb

Could you please explain step by step (button by button) how you arrived at this error?
A mediainfo report (text mode) of the video file would also be helpful.

[bb84000]

Hello !

Could you please explain step by step (button by button) how you arrived at this error?
A mediainfo report (text mode) of the video file would also be helpful.

1. Launch Clever FFmpeg-GUI
2. Select file (Starmania ： l'anniversaire-événement, les 45 ans.mp4)
3. Click "Main Page" button
4. On main page, click "Cut" button/
5. Box "Indexing video" is displayed. At the same time, exception warning dialog is issued :

"La conversion de la chaîne "0.000000" en type 'Double' n'est pas valide. ---> System.FormatException: Le format de la chaîne d'entrée est incorrect."
or in english
"Conversion of string "0.000000" to 'Double' type is invalid. --> System.FormatException: Incorrect input string format"

Is it possible there is locale problem ? the decimal point here is a coma : "0,000000".

bb

Mediainfo report :
Général
Nom complet                              : D:\Replay video\Operas\Starmania ： l'anniversaire-événement, les 45 ans.mp4
Format                                   : MPEG-4
Format, Profil                           : Base Media
Identifiant du codec                     : isom (isom/iso2/avc1/mp41)
Taille du fichier                        : 1,85 Gio
Durée                                    : 2 h 6 min
Débit global                             : 2 089 kb/s
Débit im/s                               : 25,000 im/s
Application utilisée                     : Lavf61.9.100

Vidéo
ID                                       : 1
Format                                   : AVC
Format/Infos                             : Advanced Video Codec
Format, Profil                           : High@L3.1
Paramètres du format                     : CABAC / 2 Ref Frames
Paramètres du format, CABAC              : Oui
Paramètres du format, Recadrer           : 2 images
Paramètres du format, GOP                : M=1, N=50
Identifiant du codec                     : avc1
Identifiant du codec/Infos               : Advanced Video Coding
Durée                                    : 2 h 6 min
Duration_LastFrame                       : -38 ms
Débit                                    : 1 989 kb/s
Largeur                                  : 1 280 pixels
Hauteur                                  : 720 pixels
Facteur de forme l/h                     : 16/9
Type de débit im/s                       : Débit im/s constant
Débit im/s                               : 25,000 im/s
Espace de couleurs                       : YUV
Sous-échantillonnage de la chrominance   : 4:2:0
Profondeur binaire                       : 8 bits
Type de balayage                         : Progressif
Bits/(Pixel*Image)                       : 0.086
Taille du flux                           : 1,76 Gio (95%)
Gamme de couleurs                        : Limited
Coordonnées de chromaticité              : BT.709
Caractéristiques du transfert            : BT.709
Coefficients de la matrice               : BT.709
Configuration des codecs                 : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Infos                             : Advanced Audio Codec Low Complexity
Identifiant du codec                     : mp4a-40-2
Durée                                    : 2 h 6 min
Type de débit                            : Constant
Débit                                    : 96,0 kb/s
Canal(aux)                               : 2 canaux
Agencement des canaux                    : L R
Échantillonnage                          : 48,0 kHz
Débit im/s                               : 46,875 im/s (1024 SPF)
Mode de compression                      : Avec perte
Taille du flux                           : 87,0 Mio (5%)
Langue                                   : French
Par défaut                               : Oui
Groupe alternatif                        : 1

[davidt1]

When muxing, Clever now defaults to MKV again. Used to memorize the last format/container used. Please fix.

Cannor replicate this.
Retested. Is memorized as aspected.

.19 does not memorize the last format/container used.

1. Muxed to mp4. 2. Then closed the app.

[Attachment 88271 - Click to enlarge]


1. Opened the app. 2. It shows MKV for the new file.

[Attachment 88272 - Click to enlarge]

[Findu]

@ ProWo

> It could be due to the fact that the index of the audio stream from batch0 does not correspond to an audio stream in the replicated video.
To avoid this in the future, I have introduced a background check for defective batch tasks.

I found a problem with audio tasks when encoding did not start.
When you encode to mp3_mf in mono, the minimum bitrate must be 65k and not <= 64k.

ffmpeg -i input.mp4 -filter_complex [0:1]pan="mono|c0<c0+c1"[a] -map [a] -c:a mp3_mf -b:a 64k -ar 48000 -vn -sn -dn output.mp3

---

> This error occurs when you hover over the action field with the mouse before the grid has loaded.
This has now been fixed.
In one of the latest nightlies, I added a new feature to the batch tasks; when you point the mouse at the action field of batch0, the command line of batch0 is displayed. This allows you to see what is being replicated.
Does not work for stream cut/error scan batches, for obvious reasons.

The fix is working.

The command line of batch0 is displayed. Good idea and working well.

---

Behave of "Mux whole grid" and output to source:

I have folders 1, 2 and 3 with individual files: 1.mkv, 2.mkv and 3.mkv. I start the app with output source and open the empty multiplex page. Now I drop 1.mkv, 2.mkv and 3.mkv and select "Mux whole grid" (to mp4).
1.mp4 and 2.mp4 are stored in folder 1.
3.mp4 is stored in folder 2.

Shouldn't the mp4 file only be created in it's corresponding folder?
Folder 1 should contain 1.mkv and 1.mp4.
Folder 2 should contain 2.mkv and 2.mp4.
Folder 3 should contain 3.mkv and 3.mp4.

[ProWo]

[CODE]"La conversion de la chaîne "0.000000" en type 'Double' n'est pas valide. ---> System.FormatException: Le format de la chaîne d'entrée est incorrect."

Another try; check your PM.

[ProWo]

.19 does not memorize the last format/container used.
1. Muxed to mp4. 2. Then closed the app.
1. Opened the app. 2. It shows MKV for the new file.

Did you close the app with the X upper right?
If so, the next time go back to the main page/source page.

[videoAI]

@ProWo
v3.4.4.19

I decided to test the h264_amf [since I have an AMD laptop with a GPU].

Please find my notes:
=============

1- First of all, my GPU works with other apps, performance is also
verified in win 11 task manager.

2- Second, there is nothing wrong with my setup or environment:

Win 11 is up to date [Successfully installed on ‎2025-‎08-‎12]
GPU driver is up to date [Successfully installed on ‎2025-‎08-‎12]
Clever is up to date [v3.4.4.19, Successfully installed on ‎2025-‎08-‎12]

3- I am getting 3 errors as described in details below while executing
a simple encode, no scaling, resizing, cropping, or various manipulations.
Notes on the errors:

a- Although 'p010le' can preview the file, it errors without export
claiming my GPU driver is old, which is not the case.

b- 'dxva2vld' and 'd3d11va' error without export claiming colorspace 3
and filter 'auto_scale_1' conflict!!

Btw, please standardize the dropdown abbreviations as follows (no spaces):

Abbreviation.........Official Name
----------------------------------
DXVA2VLD............DirectX Video Acceleration 2 Video Decoder (VLD)
D3D11VA..............Direct3D 11 Video Acceleration
NV12....................NV12 YUV Pixel Format
YUV420P...............YUV 4:2:0 Planar Format

Test Laptop:
AMD Ryzen 3 3250U (with Radeon Graphics)
AMD Radeon Adrenalin 25.8.1 GPU driver

Tested ...
Encoder = h264_amf [with & without HA checked, with Mp4, Mkv, etc ..]

and with ... the following pixel formats:

Pixel Format = nv12 [preview ok] HW
Orig Test File size = 73.5 mb
Pixel Format = nv12 output file size = 124 mb
=========================================
Pixel Format = yuv420p [preview ok] HW
Orig Test File size = 73.5 mb
Pixel Format = yuv420p output file size = 124 mb
=========================================
Pixel Format = p010le [preview ok] ** error #1
Pixel Format = dxva2vld [no preview] ** error #2
Pixel Format = d3d11va [no preview] ** error #3

^ no preview:.. Preview window doesnt open
^ error:........... output file auto deleted by clever after errors
=========================================
error #1
Pixel Format = p010le [preview ok]

[h264_amf @ 000001e81679a780] 10-bit encoder is not supported by AMD GPU drivers versions lower than 23.30.[vost#0:0/h264_amf @ 000001e8167beb40] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.[vf#0:0 @ 000001e816aa0080] Error sending frames to consumers: Unknown error occurred[vf#0:0 @ 000001e816aa0080] Task finished with error code: -1313558101 (Unknown error occurred)[vf#0:0 @ 000001e816aa0080] Terminating thread with return code -1313558101 (Unknown error occurred)[vost#0:0/h264_amf @ 000001e8167beb40] Could not open encoder before EOF[vost#0:0/h264_amf @ 000001e8167beb40] Task finished with error code: -22 (Invalid argument)[vost#0:0/h264_amf @ 000001e8167beb40] Terminating thread with return code -22 (Invalid argument)[out#0/matroska @ 000001e8166b9e40] Nothing was written into output file, because at least one of its streams received no packets.frame= 0 fps=0.0 q=0.0 Lsize= 0KiB time=N/A bitrate=N/A speed=N/A

=========================================
error #2
Pixel Format = dxva2vld [no preview]

Impossible to convert between the formats supported by the filter 'Parsed_colorspace_3' and the filter 'auto_scale_1'[vf#0:0 @ 000002432b64fa00] Error reinitializing filters![vf#0:0 @ 000002432b64fa00] Task finished with error code: -40 (Function not implemented)[vf#0:0 @ 000002432b64fa00] Terminating thread with return code -40 (Function not implemented)[vost#0:0/h264_amf @ 000002432b36eb40] Could not open encoder before EOF[vost#0:0/h264_amf @ 000002432b36eb40] Task finished with error code: -22 (Invalid argument)[vost#0:0/h264_amf @ 000002432b36eb40] Terminating thread with return code -22 (Invalid argument)[out#0/matroska @ 000002432b269e40] Nothing was written into output file, because at least one of its streams received no packets.frame= 0 fps=0.0 q=0.0 Lsize= 0KiB time=N/A bitrate=N/A speed=N/A

=========================================
error #3
Pixel Format = d3d11va [no preview]

Impossible to convert between the formats supported by the filter 'Parsed_colorspace_3' and the filter 'auto_scale_1'[vf#0:0 @ 00000260ad910540] Error reinitializing filters![vf#0:0 @ 00000260ad910540] Task finished with error code: -40 (Function not implemented)[vf#0:0 @ 00000260ad910540] Terminating thread with return code -40 (Function not implemented)[vost#0:0/h264_amf @ 00000260ad62eb40] Could not open encoder before EOF[vost#0:0/h264_amf @ 00000260ad62eb40] Task finished with error code: -22 (Invalid argument)[vost#0:0/h264_amf @ 00000260ad62eb40] Terminating thread with return code -22 (Invalid argument)[out#0/matroska @ 00000260ad529e40] Nothing was written into output file, because at least one of its streams received no packets.frame= 0 fps=0.0 q=0.0 Lsize= 0KiB time=N/A bitrate=N/A speed=N/A

=========================================

[videoAI]

@ProWo
v3.4.4.19

My 2c, hope this helps ...

General Debugging Tip
Try running the command with the `-report` option to generate a detailed log file.

=========================================
error #1
Key Issues Identified
1. Incorrect Parameters: The message suggests that there may be incorrect parameters such as bit_rate, rate, width, or height. Double-check these settings in your encoding command.

Suggested Solutions
Check Encoding Parameters
- Review the parameters you are using for the encoder. Common parameters to check include:
- Bit Rate: Ensure it is set appropriately for your video quality needs.
- Resolution: Verify that the width and height are supported by your GPU.
- Frame Rate: Make sure the frame rate is compatible with your settings.
=========================================
error #2,#3
These error messages suggest issues with the video processing pipeline, particularly related to the filters and encoder settings.

Errors Breakdown:
1. Filter Conversion Error:
- Message: "Impossible to convert between the formats supported by the filter 'Parsed_colorspace_3' and the filter 'auto_scale_1'"
- Cause: This indicates that the output format of one filter is incompatible with the input format of the next filter in the chain.

2. Reinitialization Error:
- Message: "Error reinitializing filters!"
- Cause: This typically occurs when the filter chain cannot be set up correctly due to the previous error.

3. Encoder Opening Error:
- Message: "Could not open encoder before EOF"
- Cause: This suggests that the encoder could not be initialized, likely due to the previous filter issues.

4. Output File Error:
- Message: "Nothing was written into output file, because at least one of its streams received no packets."
- Cause: This is a consequence of the earlier errors, where no valid data was processed to write to the output file.

Potential Solutions
1. Check Filter Compatibility
Ensure that the filters you are using are compatible with each other. You may need to adjust the parameters or the order of the filters. For example, if you are using color space conversion, ensure that the output of that filter matches the expected input of the next filter.

2. Specify Output Format
Explicitly set the output format using the `-f` option in your command. This can help the encoder understand what format to expect.

3. Simplify the Command
Try simplifying your command to isolate the issue. Start with a basic command that just encodes without filters, then gradually add filters back in to identify which one causes the problem.
=========================================

[davidt1]

.19 does not memorize the last format/container used.
1. Muxed to mp4. 2. Then closed the app.
1. Opened the app. 2. It shows MKV for the new file.

Did you close the app with the X upper right?
If so, the next time go back to the main page/source page.

Yes I closed by clicking the X. I believe that's the only to close. Yes, it starts on the main page. Then I click on Multiplex. Then I drag and drop the files. Unlike previous versions, Clever now defaults to MKV even though I muxed the MP4 the last time.

[videoAI]

@ProWo
v3.4.4.19

Edit #1
The Apple ecosystem does not support MKV (Matroska Video) files natively across its devices and software.
While macOS and iOS can play some MKV files through third-party applications, such as VLC or Infuse, the
default media players like QuickTime do not support this format directly.

If you want to play MKV files on Apple devices, consider using one of the mentioned third-party apps or
converting the files to a compatible format like MP4.

.. and all the other screens that have an mp4 checkbox please.
I don't understand why you still want to force us to use mkv??

.19 does not memorize the last format/container used.

Unlike previous versions, Clever now defaults to MKV even though I muxed MP4 the last time.

[bb84000]

Hello,

Another try; check your PM.

Fine. This one is properly cutting the video. No longer indexing exception.

Thank you very much for your support !

bb

[ProWo]

I decided to test the h264_amf [since I have an AMD laptop with a GPU].

Test Laptop:
AMD Ryzen 3 3250U (with Radeon Graphics)
AMD Radeon Adrenalin 25.8.1 GPU driver

Tested ...
Encoder = h264_amf [with & without HA checked, with Mp4, Mkv, etc ..]

and with ... the following pixel formats:

Pixel Format = nv12 [preview ok] HW
Orig Test File size = 73.5 mb
Pixel Format = nv12 output file size = 124 mb
=========================================
Pixel Format = yuv420p [preview ok] HW
Orig Test File size = 73.5 mb
Pixel Format = yuv420p output file size = 124 mb
=========================================
Pixel Format = p010le [preview ok] ** error #1

Thx for testing.
I think that p010le needs profile high. Please test this.

Pixel Format = dxva2vld [no preview] ** error #2
Pixel Format = d3d11va [no preview] ** error #3

I don't have an AMD GPU, so I can't test it and comment on it.
I got my information about h264_amf from this site:
https://trac.ffmpeg.org/wiki/Hardware/AMF

If these two pixel formats don't work, I can remove them.

[h264_amf @ 000001e81679a780] 10-bit encoder is not supported by AMD GPU drivers versions lower than 23.30.

This is an FFmpeg message and has nothing to do with clever.

[ProWo]

I found a problem with audio tasks when encoding did not start.
When you encode to mp3_mf in mono, the minimum bitrate must be 65k and not <= 64k.

Thx for the hint.
Unfortunately, there is very little information available about this encoder.
I found some information at Microsoft which indicates that the default bitrate for mono is 128kb and for stereo 320kb.

https://learn.microsoft.com/en-us/windows/win32/medfound/mp3-audio-encoder

The permitted frequencies are also restricted.
I have adjusted this.

Behave of "Mux whole grid" and output to source:
I have folders 1, 2 and 3 with individual files: 1.mkv, 2.mkv and 3.mkv. I start the app with output source and open the empty multiplex page. Now I drop 1.mkv, 2.mkv and 3.mkv and select "Mux whole grid" (to mp4).
1.mp4 and 2.mp4 are stored in folder 1.
3.mp4 is stored in folder 2.

Bug, should be fixed now.

[davidt1]

@ProWo
v3.4.4.19

Edit #1
The Apple ecosystem does not support MKV (Matroska Video) files natively across its devices and software.
While macOS and iOS can play some MKV files through third-party applications, such as VLC or Infuse, the
default media players like QuickTime do not support this format directly.

If you want to play MKV files on Apple devices, consider using one of the mentioned third-party apps or
converting the files to a compatible format like MP4.

.. and all the other screens that have an mp4 checkbox please.
I don't understand why you still want to force us to use mkv??

.19 does not memorize the last format/container used.

Unlike previous versions, Clever now defaults to MKV even though I muxed MP4 the last time.

I don't think he is forcing us to use MKV, as previous versions of Clever defaulted to the last used format/container.

It seems like every time he updates Clever, something is messed up somewhere.

[Findu]

@ ProWo

Thanks for adjusting mp3_mf default bitrate and permitted frequencies.

"Mux whole grid" and output of/to multible sources has been fixed. Also other combinations work now.

---

If you drop two files into the mux grid, unselect all checkmarks and select one stream, I would expect "Mux whole grid" to appear again. But it only appears when you click First after the grid has no checkmarks.

---

Header text "Scan for errors mode" only show up with one task in the grid.
If you have a normal batch task and go to scan for errors batch tasks, this mode is displayed under the header. If you drop a file, that text and the HWA selection disappears. If you swap the stream or delete the normal batch task, HWA reappears. That's logical.
But the header text "Scan for errors mode" does not reappear.
The same applies if you only have one task to scan for errors from the beginning and drop another.
Or is that intentional?

---

How about sharing the space for the output and the new success notification including the timer?


[Attachment 88287 - Click to enlarge]

[Attachment 88288 - Click to enlarge]

[videoAI]

@ProWo
v3.4.4.20

Edit#2, I think it is safe to remove p010le, dxva2vld, & d3d11va from drop down for h264_amf

GPT-4o mini:
The -pix_fmt p010le pixel format is not compatible with the h264_amf encoder.
The AMD AMF H.264 encoder typically supports pixel formats like yuv420p or yuv422p.

Claude Haiku 3.5
I'll do a quick verification to ensure accuracy.
The h264_amf encoder typically works best with specific pixel formats.
Based on the search results and my knowledge,

I can confirm that p010le is NOT a compatible pixel format for h264_amf

Let me clarify the compatibility of -pix_fmt dxva2vld with h264_amf
No, dxva2vld is not directly compatible with h264_amf

Let me clarify the Compatibility of -pix_fmt d3d11va with h264_amf
No, d3d11va is not directly compatible with h264_amf

The h264_amf encoder typically works best with:
yuv420p
nv12

-----

Edit#1 [Trying p010le with profile = high]

ffmpeg -hide_banner -loglevel error -stats -vsync 0 -y -fflags +genpts -i "C:\T\Test\Test.mp4" -vf "fps=30000/1000,colorspace=all=bt709:iall=bt709,format=p010le" -map 0 -c:a copy -c:s copy -c:v:0 h264_amf -profile:v high "C:\T\Test\Test_V0.mp4"

Returned error

10-bit encoder is not supported by AMD GPU drivers versions lower than 23.30.

BTW, this is my GPU ver check by a PS script:
GPU Name: AMD Radeon(TM) Vega 3 Graphics
Driver Version: 31.0.21923.11000
Video Memory: 2048 MB
===

Please see my responses ...

I decided to test the h264_amf

I think that p010le needs profile high. Please test this.

[will do]

Pixel Format = dxva2vld ** error #2
Pixel Format = d3d11va ** error #3

I don't have an AMD GPU, so I can't test it and comment on it.

1- You can use online tools like FFmpeg Online or ffmpeg.wasm
to simulate FFmpeg functionalities directly in your browser.

2- I could help you test modified ffmpeg commands.

If these two pixel formats don't work, I can remove them.

No need. We can still fix this

[h264_amf @ 000001e81679a780]
This is an FFmpeg message and has nothing to do with clever.

I know, but may be the order of the filters is causing the errors.

Potential Solutions
1. Check Filter Compatibility
Ensure that the filters you are using are compatible with each other.
You could adjust the parameters or the order of the filters. when
using color space conversion, ensure that the output of that filter
matches the expected input of the next filter.

[videoAI]

Based on my analysis, here's a comprehensive list of pixel formats that are not compatible with the AMF encoder:

Pixel Formats NOT Recommended/Compatible with AMF Encoder:
1. d3d11va
2. vaapi
3. yuv444p
4. yuv422p
5. yuv411p
6. yuv410p
7. yuvj420p
8. yuvj422p
9. yuvj444p
10. gray
11. monow
12. monob

Recommended Pixel Formats for AMF Encoder
- nv12
- yuv420p

Key Compatibility Notes
- Preferred formats are 8-bit and 10-bit planar formats
- Avoid color spaces that are not standard YUV

Unrelated, but useful info ..

[Attachment 88289 - Click to enlarge]

[davidt1]

.20 defaults to last used format/container. Thank you, ProWo.

[ProWo]

If you drop two files into the mux grid, unselect all checkmarks and select one stream, I would expect "Mux whole grid" to appear again. But it only appears when you click First after the grid has no checkmarks.

That's intentional

Header text "Scan for errors mode" only show up with one task in the grid.

If you have a normal batch task and go to scan for errors batch tasks, this mode is displayed under the header. If you drop a file, that text and the HWA selection disappears. If you swap the stream or delete the normal batch task, HWA reappears. That's logical.
But the header text "Scan for errors mode" does not reappear.
The same applies if you only have one task to scan for errors from the beginning and drop another.
Or is that intentional?

That's intentional too.
The message should appear only, if you enter batch scan for errors, to make it clear that no other batches can be inserted here.
Later, in the batch tasks window, you can choose the task type for further files with the batch0 replication.
That's why the message is superfluous here.

How about sharing the space for the output and the new success notification including the timer?

I don't like that.

[ProWo]

v3.4.4.20
Edit#2, I think it is safe to remove p010le, dxva2vld, & d3d11va from drop down for h264_amf

Thx for testing.
I'll remove p010le, dxva2vld, d3d11va.
But I'll insert yuv420p10le (for 10 bit encoding) in the next nightly (for h264_amf and hevc_amf, to test).

[videoAI]

Sounds good.
Thank you ..

v3.4.4.20
Edit#2, I think it is safe to remove p010le, dxva2vld, & d3d11va from drop down for h264_amf

Thx for testing.
I'll remove p010le, dxva2vld, d3d11va.
But I'll insert yuv420p10le (for 10 bit encoding) in the next nightly (for h264_amf and hevc_amf, to test).

[videoAI]

Bug resolved since v.18.
Issue closed.

@ProWo,
v 3.4.4.14

Another crash ...
Bug #11 Source Page Crash

*********** Exception Text **************
System.InvalidOperationException:
This operation cannot be performed while an auto-filled column is being resized.

[videoAI]

Bug resolved since v.18.
Issue closed.

@ProWo
v3.4.4.18

Edit #3
[Aug 11, using v3.4.4.18 now. The index crashes seems very Rare now.
Stability has been greatly enhanced.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range.

[videoAI]

@ProWo
v3.4.4.20

Based on my research, I can provide my best answer about the compatibility
of yuv420p10le with H.264 AMF & H.265 AMF encoders

Pixel Format Support

- yuv420p10le compatibility with h264_AMF is limited,
h264_AMF has more restrictive pixel format support
- yuv420p10le is not supported by H.265 AMF

Key Findings

- According to the research, there are compatibility challenges with H.264 AMF
& H.265 AMF encoders using 10-bit pixel formats

Sources

- AMD AMA Video SDK Documentation
- FFmpeg encoding documentation
- FFmpeg Encoding Guidelines
- Academic Software Foundation encoding guidelines
- GitHub discussions on pixel format compatibility
- Community Discussions on Video Encoding

But I'll insert yuv420p10le (for 10 bit encoding) in the next nightly (for h264_amf and hevc_amf, to test).