29.08.2022, 18:21
Hybrid is a graphical user interface, it is single threaded.
In when using x264 it uses the x264 command line encoder, when using x265 it uses the x265 command line encoder.
Both have options to requires xy threads from the OS.
How those are distributed is decided by the OS.
There is no such thing as as using a whole processor.
Process priorities and threads assinged to an application is decided by the OS, so unless the tools you use runs with admin rights (which Hybrid doesn't) it can't influence which threads it or the tools it uses gets assigned.
Error code 0x0000007f stands for UNEXPECTED_KERNEL_MODE_TRAP, cause for this usually is:
If you think that this is just causes by the encoder requesting to many thread both x264 and x265 allow to limit the number of requested threads.
x265->Misc->Threading&Co->Pools/Threads->1/XXX
x264->Base->Threads->XXX
Cu Selur
In when using x264 it uses the x264 command line encoder, when using x265 it uses the x265 command line encoder.
Both have options to requires xy threads from the OS.
How those are distributed is decided by the OS.
There is no such thing as as using a whole processor.
Process priorities and threads assinged to an application is decided by the OS, so unless the tools you use runs with admin rights (which Hybrid doesn't) it can't influence which threads it or the tools it uses gets assigned.
Error code 0x0000007f stands for UNEXPECTED_KERNEL_MODE_TRAP, cause for this usually is:
- a defect (or overheated) RAM module
- combination of non compatible RAM modules
- a defect (or overheated) main module
- buggy mainboard drivers
- Symantec AntiVirus or Norton AntiVirus running (see: https://docs.microsoft.com/en-us/trouble...0x0000007f)
If you think that this is just causes by the encoder requesting to many thread both x264 and x265 allow to limit the number of requested threads.
x265->Misc->Threading&Co->Pools/Threads->1/XXX
x264->Base->Threads->XXX
Cu Selur