![]() ![]() The HandBrake core is written in C, so Visual studio isn't used. ![]() To: HandBrake/HandBrake ggervais5 Author Re: HandBrakeCLI 1.4.2 (2021100300) (Issue #3924) I hope the above information helps you narrow down the issue with V1.4.2. I also have a C compiler on several Linux systems (Debian, Ubuntu). I mentioned Visual Studio only because if you supply me with code that queries the graphics drivers, I could compile it here and collect the graphics output directly from my two systems. Graphics: Intel HD Graphics 3000 (Toshiba) version 9. Windows: 10 Pro N Edition 64-bit Version 21H1 Graphics: NVIDIA GeForce GT635 version 30. Windows: 10 Pro Edition 64-bit Version 21H1 For comparison purposes, I can give you the information you requested: I have 2 PCs, and one works with V1.4.2 and the other does not. Did the command line parameters change, or do I need to add additional ones? The documentation still shows the above parameters as valid. net Core 5.0, which I have downloaded and installed. When I downloaded this version, I noticed that it needed. Error: invalid preset format in presets_do() hb_qsv_available: hb_qsv_info_init failed hb_qsv_info_init: failed to query qsv adapters hb_qsv_query_adapters: failed to collect information about Intel graphics adapters -9 Compile-time hardening features are enabled When I execute the above commend in a command window, I get this output: Handbrakecli -preset-import-gui -preset "H.264 MKV 720p30" -width 720 -height 405 -ab 160 -no-two-pass -quality 23 -i "input-file-name" -o "output-file-name" The 1.4.2 GUI works, but I have a script that uses this command line that I want to use instead of the GUI: ![]() I upgraded from Version 1.3 on Windows 10 and cannot get the new version of CLI to work (1.4.2). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |