Hi Brian, Sounds good. I’ll take a look at the file tomorrow when you post it.
Good night, François On Jul 14, 2014, at 9:33 PM, Brian Phelps <[email protected]<mailto:[email protected]>> wrote: Thanks for your help François, I ran f265 from linux (Ubuntu) 32 bit with gcc v4.7 using asm=no and -O0. The reason I compiled it that way is I am more interested in understanding HEVC than speed. I am running it it in ddd so I can see the execution and the data structures. It is way easier to follow (except for the recursion and some of the pragmas done for efficiency) than HM and x265 which is based on HM. I can post the 265 file tomorrow. I am at home right now and don't have access to it. ---- Brian R Phelps On Mon, Jul 14, 2014 at 9:10 PM, Francois Caron <[email protected]<mailto:[email protected]>> wrote: Hello Brian, I ran a similar command to the one you posted: $ ./build/f265cli -c 1 -w 1920x1080 -v ~/Sandbox/Sequences/B/BasketballDrive_1920x1080_50.yuv ~/Desktop/f265.265 Hardware acceleration: AVX2. Encoded : 1/1 (100.0%) @ 2fps ETA 0.00sec AFAICT, the stream is valid. I checked the stream with ffprobe, Codec Visa and the HM. $ ffprobe -show_frames ~/Desktop/f265.265 ffprobe version 2.2 Copyright (c) 2007-2014 the FFmpeg developers built on Apr 1 2014 16:04:07 with gcc 4.8.2 (GCC) configuration: libavutil 52. 66.100 / 52. 66.100 libavcodec 55. 52.102 / 55. 52.102 libavformat 55. 33.100 / 55. 33.100 libavdevice 55. 10.100 / 55. 10.100 libavfilter 4. 2.100 / 4. 2.100 libswscale 2. 5.102 / 2. 5.102 libswresample 0. 18.100 / 0. 18.100 Input #0, hevc, from '/Users/francoiscaron/Desktop/f265.265': Duration: N/A, bitrate: N/A Stream #0:0: Video: hevc (Main), yuv420p(tv), 1920x1080, 25 tbr, 1200k tbn, 25 tbc [FRAME] media_type=video key_frame=1 pkt_pts=N/A pkt_pts_time=N/A pkt_dts=N/A pkt_dts_time=N/A best_effort_timestamp=N/A best_effort_timestamp_time=N/A pkt_duration=48000 pkt_duration_time=0.040000 pkt_pos=0 pkt_size=43190 width=1920 height=1080 pix_fmt=yuv420p sample_aspect_ratio=N/A pict_type=? coded_picture_number=0 display_picture_number=0 interlaced_frame=0 top_field_first=0 repeat_pict=0 [/FRAME] $ ./bin/TAppDecoderStatic -b ~/Desktop/f265.265 -o ~/Desktop/hm.yuv HM software: Decoder Version [10.1][Mac OS X][GCC 4.8.2][64 bit] POC 0 TId: 0 ( I-SLICE, QP 30 ) [DT 0.095] [L0 ] [L1 ] [:,,,(unk)] Total Time: 0.148 sec. I’ve attached a screen capture of Codec Visa. As you can see in the bottom left corner, the SPS and the PPS are both present. Could you please give me information about the environment in which you are running f265? What OS are you running? Did you compile the binaries on your system or are you using binaries provided on our website or compiled by somebody else? I do not have Elecard analyzer to test the stream unfortunately. Could you send me the coded H.265 stream you get? I would like to take a look at it. Regards, François Caron <Screen Shot 2014-07-14 at 9.06.55 PM.png> On Jul 14, 2014, at 2:02 PM, Brian Phelps <[email protected]<mailto:[email protected]>> wrote: ./build/f265cli -c 1 -w 1280:536 -v in.yuv out.265 It plays back fine in Elecard analyzer but it complains about missing SPS, PPS, and other info. ---- Brian R Phelps On Mon, Jul 14, 2014 at 11:09 AM, Francois Caron <[email protected]<mailto:[email protected]>> wrote: On Jul 14, 2014, at 9:53 AM, Brian Phelps <[email protected]<mailto:[email protected]>> wrote: I get the following error when trying to decode a file encoded by f265 using v13.0 of the HEVC reference: TDecCAVLC.cpp:572: virtual Void TDecCavlc::parseSPS(TComSPS*): Assertion `log2MinCUSize + pcSPS->getLog2DiffMaxMinCodingBlockSize() >= 5' failed. Aborted (core dumped) Here is the commit I am on in f265: commit 6ebf09cde3f7647f3bc8c01bf88caca6390ba26d Author: Francois Caron <[email protected]<mailto:[email protected]>> Date: Mon Jul 7 08:08:36 2014 -0400 Fix .DS_Store issue in f265bench The files will play in other decoders, but the PPS, SPS, etc are not there. Am I doing something wrong? What does it take to get these params in a form the reference decoder can parse? The code is much easier to follow than the HM reference BTW. ---- Brian R Phelps Hello Brian, Thank you for manifesting interest in f265! I would like to help you out, but I’m going to need a little more information about the issue you’re facing. 1) Could I get the command-line you used that generated an incompatible file according to the HM? 2) In what other decoders will the file play in? I’ll check back later today and try to fix the problem ASAP. Regards, François Caron
