David Rickard

VidCoder exposes the functionality of HandBrake. To get that feature, you'd need to ask the [HandBrake team](https://github.com/HandBrake/HandBrake/issues/new/choose) to add it.

Try it with HandBrake. VidCoder uses HandBrake for the core encoding engine, so if the issue reproduces there it's an issue with their code and you can ask them for...

I made a fix in 10.2 Beta that resolves a problem where the batch scan would stall if there was a crash in the worker process. This might resolve your...

It might help? But it would mean I would need to break out the process priority controls to allow choosing both scan and encode priority. CPU contention shouldn't cause crashes...

I can look at the minidumps. If you enable Extended logging in Global options and provide the log files, that would also be helpful.

**VidCoderWorker1**: One thread is trying to start the scan. It has p-invoked into hb.dll, calling hb_scan_list, but has gotten an c0000005 error - Access violation: It tried to look into...

It's possible I could improve VidCoder's handling of this by having the UI process kill the hung worker process. Though it would be helpful to have extended logs for both...

Taking a look at it now. Does this only happen when an encode is in progress? I did see some odd behavior where the scan process communication hung until the...

The logs are definitely interesting. It's hung where I didn't expect, right when we're about to send another chunk of log to the UI process, but *before* it tries to...

If you're throttling the CPU use to 75% it does that based on CPU core affinity. So it will pick a random core to not use to do work. I...