Open fbagnato opened 4 months ago
Does it succeed when you go to Global Options -> Process and uncheck "Use worker process to encode"?
Also it would help if I had some more logs. Global Options -> Advanced -> Logging verbosity -> Extended, then look in %appdata%\VidCoder-Beta\Logs and get the "Encode" and "PipeServer Encode" logs.
Hello RandomEngy,
Thanks for your reply.
Sorry I haven't replied earlier but although subscribed to notifications for this thread I didn't receive a notification so I didn't know you replied until I decided to check it days later.
Your suggestion of unchecking "Use worker process to encode" worked.
The encoding goes all the way and completes normally now.
I am now running the encode again with the Logging Verbosity set to Extended to get you the logs you requested.
I will post back once the encode concludes.
Regards,
fbagnato
Hello RandomEngy,
OK, turned the "Use worker process to encode" back on and changed the Logging Verbosity set to Extended then reran the test encode which failed.
I have attached all the logs even though you only asked for the "Encode" and "PipeServer Encode" logs.
Hope they help!
Regards,
fbagnato 2024-07-22 13.47.31 Combined.txt 2024-07-22 13.48.06 Combined.txt 2024-07-22 13.48.06 General.txt 2024-07-22 13.48.26 Scan The Magnificent Seven.txt 2024-07-22 13.48.56 Encode The Magnificent Seven.mp4-failed.txt 2024-07-22 13.48.59 PipeServer Encode VidCoderWorker.43cb5f2c-90c8-4601-ab42-8f07ebaaeb71.txt
Thanks for the report. There's some odd stuff happening there. For one, the inter-process messages appear to be delayed by 3 or 4 seconds. Also the progress events are coming in batches. I'm curious, how many cores does your CPU have?
I see the reason for the failure is finding an unexpected message type while reporting progress: it's likely offset in the communication stream, though that shouldn't happen.
Just in case it helps, I'm trying to land a change in HandBrake to make the progress reports less frequent: https://github.com/HandBrake/HandBrake/pull/6200 .
Hello RandomEngy,
It is an Intel Core i5-3317U CPU @ 1.70GHz with 2 Cores and 4 Threads.
When I run a VidCoder encode, I have a few programs open and sometimes other things actively running. I rarely run an encode in a clean and quiet environment. I don't know if that is making the failures more frequent. However I can run Handbrake in the same sort of environment without failures.
So do I just wait for a new release of VidCoder then retry it again with "Use worker process to encode" checked, presuming that the problem has been fixed in Handbrake?
Regards,
fbagnato
VidCoder 11.5 Beta includes a change that makes the progress reports less frequent when no updates were found. This might help you; let me know.
Hello RandomEngy,
I installed VidCoder 11.5 Beta and ran a test encode.
The problem is still occurring.
Unticking "Use worker process to encode" ensures a full encode without failing.
Regards,
fbagnato
I'm seeing this issue occasionally in 10.15 on normal encodes with "Use worker process to encode" enabled. Usually, a retry will succeed, but of course a lot of time has been wasted. It's a fairly recent problem for me, started sometime in the past few months. I'm reverting to 11.7 Beta to see if that helps. Log from a recent failure attached. 2024-11-11 15.23.18 Encode Hemingway (2021) - S01E03 - The Blank Page (1944-1961) (1080p AMZN WEB-DL x265 t3nzin) HEVC 25.mp4-failed.zip
Alas, while 11.7 Beta worked well on quite a few videos, it just failed the same way (log attached). UPDATE: Retry of that video succeeded. Is there anything else you would like from me? 2024-11-21 06.04.14 Encode failed.zip
Problem Description
I cannot get VidCoder to successfully encode ISO video files.
The encode always fails, usually within minutes of it starting.
I can encode the same file with the same settings in Handbrake without any problems.
What version of VidCoder are you running?
10.14 VelopackInstaller
Encode Log