OpenASIC
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • \[\[global:header.users\]\]
    • \[\[global:header.groups\]\]
    • \[\[global:header.search\]\]
    • Register
    • Login

    H265 ENCODER RTL V2.0仿真教程

    Scheduled Pinned Locked Moved 新闻文档 | News & Documents
    62 Posts 29 Posters 245.1k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      jie
      last edited by jie

      原始YUV格式的测试数据
      http://140.118.175.164/PCChang/APSIPA2013/HEVCDataHiding/

      用window版 f265.exe, linux 版可能 segment fault

      G 1 Reply Last reply Reply Quote 0
      • G Offline
        gavinchen @jie
        last edited by

        @jie
        0_1561519972869_936685f7-abfe-4fd7-bdb7-2097c18a7480-image.png

        1. 缺少 rc_coefficient.txt 和rc_frameqp.txt文件。
        2. 对于ime_cfg.dat文件,对于不同的分辨率/帧数的视频,ime_cfg.dat文件应该是不同的,有没有相关文件可以提供,或者release相应的软件来生成需要的ime_cfg.dat文件
        T 龙 2 Replies Last reply Reply Quote 0
        • T Offline
          tang @gavinchen
          last edited by

          @gavinchen

          1. 那些测试序列是HEVC官方序列,搜HEVC测试序列即可
          2. rc相关文件不影响正常仿真
          3. ime_cfg仅配置运动搜索范围、形状等参数,一般情况下可用同一套参数
          1 Reply Last reply Reply Quote 0
          • J Offline
            jie
            last edited by

            测试了一下,ffmpeg libx256 软件默认(GOP 250, 50帧)压缩比大概150,而该IP相同码率 (QP = 34)压缩比大概50。后来一看只支持 I frame 和P frame, 没有B frame。

            B 1 Reply Last reply Reply Quote 0
            • B Offline
              bo @jie
              last edited by

              @jie 我们最新的C model 压缩比 相当于 x265 medium 水平,后期准备优化到比medium更好一点。 开源2.0版压缩率没有过多优化

              X 1 Reply Last reply Reply Quote 0
              • Y Offline
                yfor @tang
                last edited by

                @tang 在windows上,使用exe测试了416240、19201088分辨率的,都是可以运行的,但是对于480480、12001200的分辨率(这些文件用H264源码测试是没有问题的),没有报任何错误,就直接返回了,生成的文件都为空。

                参数设置:
                0_1562031426970_parameters.png

                测试结果:
                0_1562031458186_result.png

                想问下,是那里出了问题,还是有那些参数没有设置了?

                T B 2 Replies Last reply Reply Quote 0
                • T Offline
                  tang @yfor
                  last edited by

                  @yfor debug之后发现是熵编码里面的dump_buf设置不够大,一般情况下是足够的,dump_buf是用来导出测试TV的。但是特殊情况下,输出码流比较大,超出dump_buf的大小,无法正常导出文件,所以会出现这个问题。PS:与编码过程无关

                  1 Reply Last reply Reply Quote 0
                  • F Offline
                    Fudh @wr115946873
                    last edited by Fudh

                    @wr115946873 您好,想问下问题解决了吗?

                    J 1 Reply Last reply Reply Quote 1
                    • F Offline
                      Fudh @tang
                      last edited by

                      @tang 您好,不知道我的理解是否正确,如果f265软件生成的rec.yuv被认为是正确的,作为check文件,那么这个软件是怎么得到的,HM?

                      T 1 Reply Last reply Reply Quote 0
                      • T Offline
                        tang @Fudh
                        last edited by

                        @Fudh 您好,这个软件是我们实验室自己开发的,谢谢

                        F 1 Reply Last reply Reply Quote -1
                        • F Offline
                          Fudh @tang
                          last edited by

                          @tang 那么请问这个软件是开源的吗, 是否可以提供,谢谢

                          T 1 Reply Last reply Reply Quote 0
                          • T Offline
                            tang @Fudh
                            last edited by

                            @Fudh 暂不开源,抱歉我不能提供。如果只是确认rec.yuv是否正确,直接和.hevc解码得到的YUV对比即可。谢谢

                            F 2 Replies Last reply Reply Quote 0
                            • F Offline
                              Fudh @tang
                              last edited by

                              @tang 好的, 谢谢

                              1 Reply Last reply Reply Quote 0
                              • J Offline
                                jadick
                                last edited by

                                Hello.
                                I always get a "segmentation fault" warning when trying to run the command "./f265 -c f265_encode.cfg" and no data is generated from my .yuv.

                                Anyone knows what could be the reason to that issue?
                                I am using sudo and all the files have the necessary permissions.

                                Thanks.

                                H 1 Reply Last reply Reply Quote 0
                                • F Offline
                                  Fudh @tang
                                  last edited by

                                  @tang 想问下Xilinx的板子硬件已经实现了吗 z7020?可以提供下具体的硬件清单吗

                                  T J 2 Replies Last reply Reply Quote 0
                                  • T Offline
                                    tang @Fudh
                                    last edited by

                                    @Fudh 我们用的zcu102,zynq ultrascale+,谢谢

                                    F K X 3 Replies Last reply Reply Quote 0
                                    • F Offline
                                      Fudh @tang
                                      last edited by

                                      This post is deleted!
                                      1 Reply Last reply Reply Quote 0
                                      • B Offline
                                        Bryant
                                        last edited by

                                        This post is deleted!
                                        1 Reply Last reply Reply Quote 0
                                        • Y Offline
                                          yinbanghui1982
                                          last edited by

                                          请问cabac_bina.v中的两处for循环,都以i作为循环变量,是不是有问题?

                                          // --- Specail --- //

                                          reg ctx_spflag[0:3];
                                          integer i;

                                          always @ (*)
                                          begin
                                          for (i=0; i<4; i=i+1)
                                          begin
                                          case(ctx[i])
                                          9'd8:

                                          1 Reply Last reply Reply Quote 0
                                          • K Offline
                                            kemberly @tang
                                            last edited by

                                            @tang 您是否使用Xilinx板(尤其是Zynq ultrascale + zcu102板)成功实现了代码?

                                            T 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 1 / 4
                                            • First post
                                              Last post
                                            Copyright © 2016 OpenASIC.XinKai
                                            VIP Lab @Fudan University | XK Silicon