When I start encoding with megui and x264, megui hides the command line output of x264.exe.
I would like to see that output to check the bitrate info in realtime, while encoding.
Is it possible ? Or the only option is to not use megui, but to use x264 directly, with cmd.exe ?
+ Reply to Thread
Results 1 to 5 of 5
What do you mean by check the bitrate info in realtime ?
The commandline doesn't show this (so even if you can see the commandline used it won't help you), but some x264.exe builds show the progress bitrate , filesize, elapsed and projected time for encoding, filesize, etc... as encoding progresses is that what you mean? If so, you need to use x264.exe
But I don't understand why this command works:
cd /D D:\InstalledApps\MeGUI\tools\x264\x264.exe start /low x264.exe --level 3.1 --preset slow --tune film --crf 22 --output "E:\h264 stream\disc2.264" "E:\source\disc2\VIDEO_TS\VTS_01_1.avs"
start /low "D:\InstalledApps\MeGUI\tools\x264\x264.exe" --level 3.1 --preset slow --tune film --crf 22 --output "E:\h264 stream\disc2.264" "E:\source\disc2\VIDEO_TS\VTS_01_1.avs"
start /low "" "g:\Hybrid\x264.exe" --level 3.1 --preset slow --tune film --crf 22 --output "H:\Output\test.264" "H:\TestClips&Co\test.avi"
Starts a separate window to run a specified program or command. START ["title"] [/D path] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED] [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL] [/NODE <NUMA node>] [/AFFINITY <hex affinity mask>] [/WAIT] [/B] [command/program] [parameters] "title" Title to display in window title bar. path Starting directory. B Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application. I The new environment will be the original environment passed to the cmd.exe and not the current environment. MIN Start window minimized. MAX Start window maximized. SEPARATE Start 16-bit Windows program in separate memory space. SHARED Start 16-bit Windows program in shared memory space. LOW Start application in the IDLE priority class. NORMAL Start application in the NORMAL priority class. HIGH Start application in the HIGH priority class. REALTIME Start application in the REALTIME priority class. ABOVENORMAL Start application in the ABOVENORMAL priority class. BELOWNORMAL Start application in the BELOWNORMAL priority class. NODE Specifies the preferred Non-Uniform Memory Architecture (NUMA) node as a decimal integer. AFFINITY Specifies the processor affinity mask as a hexadecimal number. The process is restricted to running on these processors. The affinity mask is interpreted differently when /AFFINITY and /NODE are combined. Specify the affinity mask as if the NUMA node's processor mask is right shifted to begin at bit zero. The process is restricted to running on those processors in common between the specified affinity mask and the NUMA node. If no processors are in common, the process is restricted to running on the specified NUMA node. WAIT Start application and wait for it to terminate. command/program If it is an internal cmd command or a batch file then the command processor is run with the /K switch to cmd.exe. This means that the window will remain after the command has been run. If it is not an internal cmd command or batch file then it is a program and will run as either a windowed application or a console application. parameters These are the parameters passed to the command/program. NOTE: The SEPARATE and SHARED options are not supported on 64-bit platforms. Specifying /NODE allows processes to be created in a way that leverages memory locality on NUMA systems. For example, two processes that communicate with each other heavily through shared memory can be created to share the same preferred NUMA node in order to minimize memory latencies. They allocate memory from the same NUMA node when possible, and they are free to run on processors outside the specified node. start /NODE 1 application1.exe start /NODE 1 application2.exe These two processes can be further constrained to run on specific processors within the same NUMA node. In the following example, application1 runs on the low-order two processors of the node, while application2 runs on the next two processors of the node. This example assumes the specified node has at least four logical processors. Note that the node number can be changed to any valid node number for that computer without having to change the affinity mask.