A next-gen smart video encoding utility based on .NET 9/WPF, focused on tool/encoder orchestration, source analysis, encoding customization, parallelism tuning, modern monitoring, interrupt capability, and auto-multiplexing.
Source & Environment Validation
- Validate source video integrity from ffprobe readings
- Verify current environment & configuration
- Source checklist with Success, Warning & Error status
- Bypass feature to continue on error
Advanced Parallelism
- Physical Core & NUMA Binding on top of Thread limiting
Encode Parameter Setting
- Customize via tuned UI controls
- Encoder A/B comparison previewer
Video Filtering
- FFMPEG-VS-AVS filter editor
- Auto-generate basic AviSynth & VapourSynth scripts (Decode→Y4M)
- Auto-generate filters for FFMPEG-VS-AVS:
- VFR→CFR
- HDR→SDR (WCG)
- Color space conversion
- SAR restoration
- Resize (Separated upscale-downscale strategy)
- Deband
- Rotate
- Flip
- Crop
- Blur
- Sharpen
- Additional OpenCL filters for VapourSynth:
- Denoise
- Gaussian Blur
- AviSynth A-B previewer
- VapourSynth A/B previewer
Managed Automation
- Auto-generate video & audio encoding commandlines
- Advanced encoding modes:
- Queue Mode: Encode and filter a list of video sources
- Concat Mode: Concatenate and filter a group of video sources
- Repart Mode: Re-slice, filter, and encode a group of video sources to fix episode splits
Editable Blu-ray Chapter Import
- Parse and build a list from the PLAYLIST folder in BDMV
- Wired to Queue Mode and Repart Mode
Clip Sampling
- FFMPEG-VS-AVS sampling
- GUI to clip time or frame ranges
Encode Monitoring
- Watch memory use during encoding
- View upstream and downstream logs separately
- Interrupt upstream or downstream processes
Overwrite Protection
- Start-Encode cooldown based on file size
This software supports multiple languages, but English screenshots are used here to keep the image count low. Some UI text may be outdated, but the layout still matches. Check the version you are using.
Main Page
Script Scribe (Editor)
Encoding Settings
Parallelism Settings
Clip Sampler
Encoding Monitor
Warning Modal & Overwrite Protection
Blu-Ray Playlist Selector
Episode Repartition Configurator
Program Settings
Subtitle Track Editor (Queue Mode)
- Windows 10/11 x64
- Recommended version: 1809/21H2 (LTSC) or higher; minimum: 1607
Use this tutorial to get tools for your use case:
If you need a quick start, you can use the tools in the download package (not recommended, but it works).
Supported pipe upstream programs (decoding and filtering tools):
- ffmpeg
- vspipe (supports API 3.0 and 4.0 automatic recognition)
- avs2yuv
- avs2pipemod
- SVFI
Supported pipe downstream programs (encoders):
- x264 core 165 or newer
- x265 v4.2 or newer
- SVT-AV1 v4.1 or newer
Use the latest encoder versions for better speed, quality, compression, and fewer leaks.
- Azure icons: azureicons.com
- Game icon pack by NiewBie: GitHub/Niewbie
- Blu-ray playlist parser by tautcony: ChapterTool Core
OS Validated:
- Windows 10 22H2
- Windows 11 25H2
CPUs Validated:
- Core i5 7600k (4C4T)
- Ryzen 9 9900X (2CCD 12C24T)
- EPYC 7R13 (6CCD 48C96T)
- Intel i7 14700K
This includes L3 cache size and CCD-aware grouping detection
Long Queue Validation
- 30+ 4k videos and x265 encoding was successful (3 days uninterrupted)
It is not easy to develop these tools. If this software helps, please consider sponsoring or sharing it.
- App startup, main window, and main interface layout have been implemented, with entry points in
App.xaml.cs,MainWindow.xaml, andViews/MainUI.xaml MainVMis responsible for main interface module orchestration, including the tool area, source import area, analysis area, checklist, coding settings area, and startup area- Modal window navigation, masking states, close commands, and basic command models have been implemented
- Multi-language switching mechanism has been integrated into the main interface, cards, buttons, and modal window text
- Importing, replacing, deleting, and selecting external tools.
- Defined & supported upstream tools include
ffmpeg.exe,vspipe.exe,avs2yuv.exe,avs2pipemod.exe, andone_line_shot_args.exe - Defined & supported encoders include
x264.exe,x265.exe, andsvtav1encapp.exe - Defined & supported analytics and dependencies include
ffprobe.exeandavisynth.dll - Tool version detection, filename verification, tool partitioning, default selection, and dependency/source compatibility refresh are implemented
- Importing regular video sources, AviSynth scripts, VapourSynth scripts, and SVFI ini sources
- Supports persistent source file paths and refilling existing source files upon startup
- One-click generation of AviSynth/VapourSynth scripts is implemented, writing
.avsand.vpyfiles and refilling them into the script source card - Linkage between source type and upstream tool selection has been implemented
- For example,
vspipe.execorresponds to.vpy, andavs2yuv.exe/avs2pipemod.execorresponds to.avs
- For example,
- JSON analysis of
ffprobehas been implemented, and the original analysis results can be copied - The source inspection card has parsed and displayed progressive, bit-depth, frame rate, SAR, color metadata, chroma, HDR / Dolby Vision source info, and other inspection items
- Viewing source inspection issues, refreshing the checklist status, and manually bypassing them have been integrated into the main workflow
- The pre-coding inspection card has implemented hardware and software inspection items
- Includes checks on AC power, output directory, disk space, write permissions, output file overwrite, and AviSynth / L-SMASH
- Viewing pre-encoding issues, re-evaluating, and manually bypassing them have been integrated into the start button status
- Encoding presets, keyframe intervals, and some third-party parameter switches have been implemented and persisted
- The encoding settings card displays a summary of the current encoding parameters
- The encoding pipeline generates corresponding encoder parameters based on the current configuration
- ffprobe-derived auto parameters now also cover HDR mastering display and content light level metadata when present, and the source inspection subtitle surfaces HDR / Dolby Vision source info
- Y4M pipeline command generation, supporting output from various upstream tools to x264/x265/SVT-AV1
- Command generation derives parameters such as color, range, chroma, and lookahead from ffprobe information; frame count is only used when it is already reliable
- A parameter confirmation window pops up before starting encoding; after confirmation, the encoding monitoring window appears
- Supports selecting clips by time & frame number, and supports timestamp-to-frame-number conversion
- Sampling segments will open the encoding monitoring process in sample mode
- SVFI / OneLineShotArgs currently do not support sampling segments; a disabled message is displayed on the main interface
- Supports starting upstream and encoder processes and passing upstream stdout pipes to encoder stdin
- Supports reading upstream/downstream stderr, log folding, saving logs, viewing encoding commands, and adjusting log fontsize
- Supports encoding progress when a reliable total frame count exists, written frame count, current/estimated output size, time elapsed, remaining time, and completion time estimation
- Supports memory usage, working set peak, Page Fault, memory pressure, and memory range statistics
- Supports interrupting upstream or encoder processes; the window can only be closed after encoding is complete
- NUMA node enumeration, CPU topology reading, CPU Sets allocation, and encoder thread limit are already implemented
- Parallel settings can be saved and applied to the upstream/encoder processes started by encoding monitoring
- The encoder thread count is passed to the x264/x265 parameter; SVT-AV1 currently does not generate thread parameters
- A single 1cenc instance can only bind the downstream encoder threads to one NUMA node at a time. If you have more encode jobs than one instance can handle and the machine still has spare NUMA nodes, start as many program instances as available NUMA nodes, then let each instance take a portion of the queue, so every node stays busy.
- The instances are easy to tell apart: look at the
1cenc · PID xxxxx · vX.Y.Ztext in the title bar or taskbar button. The PID is the process's temporary identifier, unique while it is running and not reused across instances.
- The basic logic for saving/loading JSON for application configuration, tool path, source path, encoding parameters, and parallel parameters has been implemented
- Language configuration has been integrated for saving and loading
- Supports path preview, clipboard, illegal characters, reserved names, and length checks
- Output settings cards will be populated upon confirmation
- Cards, button groups, dropdown menus, settings containers, checklists, integer sliders, fragment range selectors, memory range bars, and column text components have been implemented
- The currently used one-way UI converter meets existing binding requirements
EncoderConfM.CustomParamswill be saved and appended to the final encoding command byEncodingPipeline- The "Custom Parameters" area is no longer a summary of third-party switches, but instead directly reads and writes a free text parameter
- The parameter coverage for x264/x265/STV-AV1 is still limited, but it is usable
- The scriptwriter window, AVS/VPY editing area, copying complete scripts, and copying input/output fragments
- "Save As" is implemented
- "Confirm" has implemented script saving and backfilling
- To simplify, it saves both AVS & VPY scripts simultaneously, same as the one-click generate button
BestPracsSelfCheckCardVMis a self-check reference card and does not participate in the start-encoding blocking conditions- No
RunAllChecks(), noIsBypassed, no Inspect/Bypass buttons - Marked as "Advisory - not blocking" on the UI
The Overwrite setting will append an overwrite confirmation pop-up if the output file already exists after displaying and confirming the compression command, and delay enabling the confirmation button according to the size of the overwritten file
Implemented and verified, usability confirmed
Implemented and verified, usability confirmed
When audio re-encoding is selected in Concat mode, the workflow splits audio into a dedicated ffmpeg encode step and a final mux step, so the command list shows video encode, audio encode, then mux.
Implemented and verified, usability confirmed
Implemented and verified, usability confirmed
- The source subtitle track retains the language and duration metadata extracted by ffprobe in the encapsulation editor
- Imported subtitle files are validated, and the end time of the last subtitle segment is used as the track duration
- The source subtitle track and imported subtitle files have color-coded display functionality
- Tested: Adjusting the source subtitle's "default" command-line generation works correctly
- Tested: Metadata parsing of the source subtitle is all correct
- Tested: ISO 639-2 language code recognition is correct
- Tested: Queue mode
- Tested Concat mode
This feature cannot be implemented due to the need to modify the upstream program and encoder source code
- P-Core / E-Core related checkboxes in the UI are disabled
- This is really CPU manufacturers' task
This feature cannot be implemented due to the need to modify the upstream program and encoder source code
Implementation failed due to excessive complexity and encoding time addition
- A better scene-change detection function than the video encoder's built-in method must be used
- A slower scene-change detection function will significantly increase overall encoding task duration (+50~150%)
- The final expected compression ratio & image quality improvement are only about 5% (compared to compression results without this function).
Commands/: User operation commands, modal window opening and closing, save loading, and encoding startup entry pointPipeline/: Encoding command-line building, frame counts, and muxingFFmpeg/: ffprobe analysis and FFmpeg process/argument helpersToolManagement/: Tool registration, version detection, and compatibility rulesScriptGeneration/: AVS/VPY script templatesCPU//Hardware/: CPU/NUMA topology, thread sets, and OpenCL detectionPersistence/: JSON save/load base classesFileManagement/: Source path routing, file pickers, and output path helpersModels/: Configuration models, tool definitions, language resources, checklists, and data DTOsViewModels/: Main interface, modal window, and card state managementViews/: WPF windows and interface XAMLComponents/: Reusable UI controlsConverters/: WPF binding converters
- No unit test, integration test, or automated UI test projects are there
- Some attempts were declared as not ready due to .Net 9.0 being new
- README has not yet included instructions for building, running, preparing dependencies, and typical workflows (although these are provided in the usage instructions window / AppUsageModal)
- Confirm encoding commands before starting encode, and file overwriting:
Commands/StartEncCmd.cs - Sample clip confirmation before starting encode:
ViewModels/SampleClipVM.cs - View encoding commands in the encoding monitor:
ViewModels/EncodingMonitorVM.cs - Copy/save results after script generation:
ViewModels/ScriptScribeVM.cs,Commands/SaveLoad/OneClickScriptGenCmd.cs - Source analysis and check results:
Commands/AnalyzeSrcVideoCmd.cs,Commands/InspectSrcProblemsCmd.cs - Secondary confirmation when importing tools/selecting files:
Commands/ImportToolCmd.cs,FileManagement/SrcFilePicker.cs
All persistent configuration data is stored as JSON files under {Application Base Directory}\1cenc\:
| File | Contents |
|---|---|
appconfig.json |
App settings (overwrite config, language selection) |
appdata.json |
Tool paths/versions/sizes, source video paths, output directory |
encodingconfig.json |
Encoder parameters (CRF/ABR, keyframe, presets, custom params for x264/x265/SVT-AV1) |
parallelismconfig.json |
Parallelism settings (NUMA node IDs, CPU preferences, thread count) |
Persistence base class: Persistence\SaveLoadBase.cs - all configuration models inherit from SaveLoadBase<T> which provides JSON serialization/deserialization via Save() / Load().
Other persisted data (user-selected paths, not in \1cenc\):
- Generated script files (
.avs/.vpy/.txt) viaViewModels\FilterScribeVM.csandCommands\SaveLoad\OneClickScriptGenCmd.cs - Stderr log files (
upstream-stderr.txt,downstream-stderr.txt) to the output directory viaViewModels\EncodingMonitorVM.cs
The developer shall not be liable for any direct, indirect, incidental, special, or consequential damages (including, but not limited to, loss of business profits, business interruption, computer system damage, data loss, and damage to goodwill) arising from the use or inability to use this software, even if advised of the possibility of such damages. Users assume all risks associated with the use of this software.
Video compression is a long-duration, sustained, high-load CPU computing task. Under these conditions, the following factors, among others, may cause hardware damage:
- Improper heatsink installation, unstable overclocking, or excessively high voltage settings may lead to accelerated processor aging, electrical short circuits, or other hardware failures.
- Extreme computational loads may cause system unresponsiveness, blue-screen crashes, resulting in data corruption or loss.
- x265 Stress Test Preset: The software includes an x265 stress test preset for verifying system stability. However, the actual load of this test depends on the content complexity of the input video. Use a test video consistent with the target compression task as the source file for accurate validation.
- This test can be more brutal & relentless than traditional stress-testing tools like Prime95, running it carries inherent risks. Run this test only while actively monitoring system temperature and status, and save all files before starting the test.
- No Process Priority Escalation: This software does not raise the process priority of encoding tasks. This ensures the operating system and other programs remain responsive even under extreme encoder loads.
- File Overwrite Protection: If an output file already exists before encoding begins, a confirmation window will appear. To prevent accidental data loss, the confirmation button's activation is delayed proportionally to the size of the file being overwritten.
- Use Reliable Cooling Equipment: Standard cooling fans may degrade rapidly under the wear and tear of prolonged, full-speed operation. Ensure the use of quality & heavy-duty cooling.
- Configure Stable Overclocking Strategies: CPU & memory overclocking should be tuned for stable, long-term, high-load operation rather than short-term peak performance.
- Use an Uninterruptible Power Supply (UPS): Sudden power outages during high-load operations pose severe risks to hardware. A UPS provides critical buffer time to save data and shut down the system.
- Monitor Ambient Humidity: High humidity can lead to electrical short circuits, especially under high-load, long-duration operation. Ensure the computer is in a dry environment.
This software relies heavily on proprietary Windows APIs, which form the foundation of its core functionality; therefore, it is natively bound to the Windows platform:
- WPF Presentation Layer: WPF has no official Linux support.
- Windows Kernel APIs (P/Invoke calls to
kernel32.dll):- CPU Sets: Binds encoding processes to specific physical cores, avoiding hyper-threaded virtual cores.
- NUMA Topology: Enumerates and specifies the NUMA nodes used by the encoder, ensuring that the visualization presented to the user is consistent with what the encoder sees.
- Process Enumeration: Used for tracking sub-processes during encoding monitoring.
- Power State: Checks whether the system is running on AC power before starting encoding.
- Memory Information: Retrieves total physical memory and estimates allocation based on NUMA node proportions.
psapi.dll: Provides working set and memory pressure statistics for the encoding monitoring feature.
These APIs cover critical areas such as parallel scheduling, hardware detection, process monitoring, and pre-encoding checks - functions that cannot be replaced by cross-platform UI frameworks.
Since the backend is already locked to Windows APIs, choosing WPF became the natural decision. It provides native Windows desktop integration (including features to prevent window overflow), a mature MVVM data-binding ecosystem, and requires no browser kernels or third-party dependencies. While cross-platform frameworks solve UI portability, they cannot resolve underlying API incompatibilities; instead, they would only add an extra layer of abstraction cost and testing overhead.
In summary, the best approach for other platforms is to reimplement the project's logic using the corresponding native technology stack of that platform. Because the full source code is available and Agent-assisted programming tools exist, and this project has adopted the Apache 2.0 license to lower the barrier to entry, the difficulty of redevelopment has been reduced.