Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
27th November 2015, 20:42 | #1 | Link |
Registered User
Join Date: Apr 2004
Location: SE Idaho
Posts: 21
|
Alleged x265 crash
Have others had frequent, serious problems with x265?
Using the most recent Staxrip with x265 1.7, 1.8, and 1.8 nightlies I've found: 1) Use of --frame-threads 1 nearly always crashes x265 after a few percent of the file, the last log entry: av_interleaved_write_frame(): Broken pipe. I tried manually installing the most recent Avisynth with no change. Attached is a log from a failed encode of a 2-minute clip from "Captain America". 2) Sometimes x265 will unceremoniously die without error, warning, or log entry. Attached is a log from such a situation (sans error). The problems may be related to StaxRip, but Stax76's software always seems so amazingly robust and well-designed, and once the encode is going I am not sure how it could cause such a failure mode. Perhaps AVISynth or other software may be involved, too. As a side note, why would Doom9 of all forums not allow users to directly upload log files? Zipping them is not a big deal, but it seems strange. |
27th November 2015, 21:03 | #2 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
If you think you found a reproducible crash in x265, the first thing to do is: Eliminate Avisynth!
There are way too many things that can go wrong on the Avisynth side. So, to be 100% sure this really is a x265 issue, run x265 directly from command-line and encode directly from an existing Y4M file. Or, maybe, pipe input from FFmpeg. If the problem then still occurs, please post your exact x265 version and the exact x265 command-line to reproduce the crash - alongside with the shortest possible a sample that can be used to reproduce the crash. Have you tried uploading your files with a .txt extension? If it still doesn't work, you probably ran into the size limit.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 27th November 2015 at 21:35. |
28th November 2015, 17:18 | #3 | Link | |
Registered User
Join Date: Feb 2015
Posts: 326
|
Quote:
http://ffmpeg.zeranoe.com/builds/ and replace ffmpeg.exe in your "C:\StaxRip\Apps\ffmpeg\" folder. |
|
29th November 2015, 19:30 | #4 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
|
|
3rd December 2015, 08:01 | #6 | Link | |
Guest
Posts: n/a
|
Quote:
Now can we change the title of this thread?! Tom |
|
4th December 2015, 00:13 | #9 | Link |
Registered User
Join Date: Jun 2006
Posts: 397
|
For the library itself it definitely makes sense, but it's also a commandline program. Making use of an external decoder lib/program would make it more usable, like x264.
Last edited by shae; 4th December 2015 at 00:19. |
4th December 2015, 14:32 | #10 | Link |
Angel of Night
Join Date: Nov 2004
Location: Tangled in the silks
Posts: 9,559
|
It's not necessary; that would be equivalent to:
ffmpeg -i file.mkv -f y4m - | x265 - --y4m .... which can be encapsulated in a batch file if you must. (Might need -strict -1 for 10-bit and up.) x264 only included it because someone else contributed it. |
8th December 2015, 05:16 | #12 | Link |
Registered User
Join Date: Apr 2004
Location: SE Idaho
Posts: 21
|
Admittedly, I haven't tried a single-thread encode again because they take a bit of time to complete. Aside from a small probability that single-thread encodes are unrelated to the other problems I ran into, it appears so far that my x265 issues were a combination of:
1. An old version of ffmpeg 2. Two bad source videos. The sources had graphical corruption in one spot roughly midway through the video. I've never experienced either until my first look into x265, and I've transcoded a lot of media and have spend hundreds of hours researching, programming for, and tweaking my transcoding hobby. I thought that gave me the right to commit the cardinal sin of assuming that correlation implied causation. My apologies to the x265 team. Last edited by Sivar; 8th December 2015 at 05:20. Reason: Added note about single-thread encoding |
9th December 2015, 09:03 | #13 | Link | |
Registered User
Join Date: Oct 2014
Posts: 476
|
Quote:
No decoder has achieved perfection, so adding a decoder is adding another project that will surely need some work. It's better to leave the decoder work to the decoder projects so x265 can concentrate wholly on encoding. |
|
Tags |
staxrip, x265 |
Thread Tools | Search this Thread |
Display Modes | |
|
|