--input-depth 10 result in appcrash

[Former user]

i was using megui to encode, that noticed when i inserted this command it would result in ACCESS Violation .

then i tried to encode using the x265 binary , same result .

this command would result just fine .

 --preset slow --crf 23.8 --pme --pmode --psy-rdoq 10.0 --psy-rd 0.6 --bframes 7 --ref 6 --rdoq-level 1 --dither --amp --output "D:\te.hevc" --input-res 1920x1038 --fps 23.976 --input "d:\test.yuv"

but when i insert

 --input-depth 10

it crashes .

my file is 10-bit .

• Format : AVC
• Format/Info : Advanced Video Codec
• Format profile : High 10@L4.1
• Format settings, CABAC : Yes
• Format settings, ReFrames : 4 frames
• Codec ID : V_MPEG4/ISO/AVC
• Duration : 20s 270ms
• Bit rate : 13.3 Mbps
• Width : 1 920 pixels
• Height : 1 038 pixels
• Display aspect ratio : 1.85:1
• Frame rate mode : Constant
• Frame rate : 23.976 fps
• Color space : YUV
• Chroma subsampling : 4:2:0
• Bit depth : 10 bits
• Scan type : Progressive

*x265 [info]: HEVC encoder version 1.7+266-68d089360477

x265 [info]: build info [Windows][GCC 4.9.2][64 bit] 8bit*

[Former user]

this is sample to recreate the scenario . http://fs2.filegir.com/punsher2011/test.mkv.rar

[Sundar Govindarajan]

Looks like you are trying to encode a AVC file. x265 supports only uncompressed YUV/Y4M as input.

[Former user]

--input "d:\test.yuv"

i know that , i used ffmpeg to get the YUV , i know you guys are awsome but read the topic please or see the screen

ffmpeg -i <inputFile> -vcodec rawvideo <output.yuv>

[Sundar Govindarajan]

I got confused because of this

"my file is 10-bit . Format : AVC Format/Info : Advanced Video Codec Format profile : High 10@L4.1"

The screenshots didn't tell me anything that will clarify about the input video.

Can you post the log from ffmpeg conversion? Did you open the yuv file through a yuv player in 10-bit mode?

I think the correct way to convert to a 10-bit YUV is by using -pix_fmt in the command line.

ffmpeg -i <inputFile> -pix_fmt yuv420p10le <output.yuv>

[Deepthi Nandakumar]

Thanks for reporting, do you have a backtrace for the x265 crash?

You mentioned that it worked fine without --input-depth 10. For a 10-bit YUV file, without specifying --input-depth 10, the encoded output will be garbage.

[Former user]

Yes , the result is a junky video , but it won't crash as it tries to do something .

i used

ffmpeg -i <inputFile> -pix_fmt yuv420p10le <output.yuv>

to decompress my file and encode again , same result .

How can i backtrace ? t tried to debug with VS ...

Unhandled exception at 0x0000000000404BF3 in x265.exe: 0xC0000005: Access violation reading location 0x0000000002C67000.

maybe it's my ignorance of something , i would be soo sorry for disturbing you if that be the case . but i hope and think you can re-create the scenario with the 30 Second of Source File

[Former user]

Sent the patch to fix this.

[Deepthi Nandakumar]

Fix: Provide width and height of input file to dither, param may have padded that.

Fixes Issue #195

→ <<cset 98ac099a766f>>

[Former user]

thanks , awesome job . i'll try with the new build when available . so basically i should do this

--dither 1920x1080

is it any different form?

--input-res 1920x1080

[Deepthi Nandakumar]

Sorry, I didnt mean for this to be marked as resolved.

So, basically, we found a bug in the x265 executable when dither is called for resolutions which need padding. But you seem to be calling libx265, dither through ffmpeg, in which case this fix is unrelated.

[Former user]

oh , thanks.

I am using x265 executable itself .

( just using ffmpeg to get YUV and then encoding it through x265 )

[Deepthi Nandakumar]

ok, can you test and let us know?

[Former user]

Many thanks . i used 1.7+511 and everything went fine . also the result was what was expected .

[Deepthi Nandakumar]

Awesome, closing this issue.