+ Reply to Thread
Results 2,131 to 2,139 of 2139
-
As always .. there is nothing wrong with my environment
-
@ProWo
Since you started looking at the speed issue ..
let me update you with my testing results of the 'batch scan for errors' feature.
No major issues/bugs/crashes were identified during batch processing of the scan for errors feature.
Statistics:
Clever processed 1344 files, ranging in size between [20mb - 2.2Gb] in ~24.15 hrs., found 13 damaged files.
When 'close me' was checked, Clever successfully closed after batch tasks were completed.
When 'Shutdown' was checked, Clever successfully Shutdown the PC after batch tasks were completed.
Resource Impact [Windows Task Manager]:
- Clever was light on CPU, disk i/o, & moderate on memory [23 mb].
- ffmpeg, called by Clever, was light on disk i/o, moderate on memory [40 mb], but a bit heavy on CPU [65%].
pros
- Sleep mode prevention, Abort button, Shutdown, & Close me .. were nice to have.
- A separate error text file was generated for each damaged video file.
- Each Task was automatically removed from the grid after processing.
cons
- Scan was very slow
Recommendations
- Try to speed up the scan
Potential enhancements [Advanced]
- FFmpeg parallel processing: [didn't know ffmpeg can do this]
Parallel processing in FFmpeg can be achieved through various means, including multi-threading & using multiple CPU cores.
Multi-threading: Focuses on dividing a single task into smaller, concurrent sub-tasks.
Multiple CPU Cores: Focuses on distributing the workload across different physical or logical cores of the CPU.
To leverage parallel processing in FFmpeg:
1- Multi-threading: FFmpeg can use multiple threads to process different parts of a video or audio stream simultaneously.
2- Frame-level parallelism: Some codecs & filters support frame-level parallelism, allowing multiple frames to be processed in parallel.
3- Slice-based parallelism: Some codecs support slicing, where a frame is divided into slices that can be processed in parallel.
4- CPU Affinity: Some FFmpeg builds & external libraries (like x264) support CPU affinity, which allows you to bind specific threads to specific CPU cores.
5- You might want to offload processing to the GPU on supported systems. Please refer to attached file for mote info.
Last edited by videoAI; 2nd Jul 2025 at 08:17.
As always .. there is nothing wrong with my environment -
-
@ ProWo
3.4.3.05 Feedback
The normal "Scan for errors" for proper files always ends in an error, has been fixed.
The new HW acceleration and it's selection is working, for "Scan for errors" batch tasks.
Could the "Batch tasks" page stay open when you use the "Clear tasks" button and there are no remaining tasks?
Stay open retains the last setting. But not for subtitles. -
I don't want this because the user with the blank page cannot determine which action should be performed for the file.
For the “Scan for errors” batch, the page is initialized in a certain way that only allows this action for the added files.
All other actions for the batch tasks are defined in other sections.
Stay open retains the last setting. But not for subtitles. -
When you load a source file and go to the Main Page, Various, Scan for errors and activate Batch scan, you get this empty "first opening" grid/page:
[Attachment 87700 - Click to enlarge]
When you add one or multible files
[Attachment 87701 - Click to enlarge]
with a wrong HW acceleration, you could clear all tasks and start with the same empty "first opening" grid/page.
Actually you get transfered to the Main Page when you clear all tasks.
It would be better to stay on the “Scan for errors” batch page only in that case.
But that is not important.
You could use a different color for the background of the tasks for the error scan to make it clear what is special.
---
>> davidt1: Also, How about memorizing the default for a chosen language for the streams? My default language is English (en, eng). It would be great if Clever automatically checks "default" if the language is English, or the last language checked.
> ProWo: our default language is english, but for other users it is french, spanish, german, hindi and so on.
Not useful.
Alternatively, the first subtitle stream added to the mux grid (or via drag and drop) could be marked as the default stream.
So everyone can control his language default that way. Source files and processed streams are not affected.
Maybe this is worth a try? -
@ProWo
I agree with Findu on this one ..
Think about it; you come to the batch tasks page, you are going to start from top to bottom,
you drag all your files in, then you check out the H/W acceleration drop down, which tells you
you need to select me first before adding your files !!!! so you clear all tasks in the grid, and
suddenly you are taken back to clever main page !!!!??? it doesn't make sense at all
kindly fix, and
- allow grid to stay open after clear tasks.
- allow H/A drop selection at any time, and default to 'auto'.
Also, a small change request ..
currently you can drag a folder to the tasks grid, it is treated as a single task, clicking execute takes
you to clever main page as well.
Wouldn't make perfect sense to add the files from the folder to the grid instead.
As always .. there is nothing wrong with my environment
Similar Threads
-
GUI for ffmpeg x265 encoder
By david55 in forum Video ConversionReplies: 15Last Post: 11th May 2025, 09:15 -
New small GUI for FFmpeg
By ProWo in forum Video ConversionReplies: 29Last Post: 24th Feb 2024, 02:06 -
Best GUI for ffmpeg encoding
By usta in forum Video ConversionReplies: 25Last Post: 17th Jan 2019, 11:23 -
GUI for FFMpeg amf?
By Micky in forum Video ConversionReplies: 0Last Post: 14th Jan 2018, 07:45 -
dmMediaEncoder v1.8.0 - crossplatform FFMPEG GUI
By mdalacu in forum Video ConversionReplies: 38Last Post: 29th Sep 2015, 00:19