windows下创建vp9的VS版本

最新推荐文章于 2024-10-19 11:05:48 发布
最新推荐文章于 2024-10-19 11:05:48 发布
阅读量157 收藏
点赞数
CC 4.0 BY-SA版权
文章标签： c# 操作系统 php
原文链接：http://www.cnblogs.com/endv/p/6866947.html
本文详细介绍如何在Windows环境下搭建WebM及VP9的编解码环境，包括下载并配置必要的组件如yasm、cygwin等，以及安装VP9的具体步骤。通过这些步骤，读者可以顺利地在自己的开发环境中实现WebM和VP9的编解码功能。

1. webm官网

 

下载版本：
创建过程这里有比较详细的英文说明：
懒得翻译的话就继续往下看吧。
 
2. yasm和cygwin
 
a. yasm
第一步， 按照需要下载所需yasm，32位或64位；VS的Microsoft Visual Studio x.0/VC/bin 在 Program Files (x86) 还是Program Files 中，前者放32bit就可以，后者放64bit，并将yasm的任意下载版本改名为yasm.exe。
第二步， 将yasm源文件中的yasm.rules放在Microsoft Visual Studio x.0/VC/VCProjectDefaults下。
附件，yasm.rules.
 
b. cygwin
安装过程参见：
第一次安装在windows下的童鞋，还要安装下make，如果不知道是哪些，就把所有带make的都选上吧，否则后面无法使用哦。
 
c. 另外如果需要安装文档，需要PHP和Doxygen
PHP下载地址：http://php.net/
Doxygen下载地址：http://www.doxygen.org/
 
3. vp9安装
 
a. 将vp9的安装包解压在某个目录下，如D:\test\vpx,并在D:\test下新建一个build目录，即D:\test\build;
b. 双击cygwin，进入所在目录
在命令行输入，
$ cd \cygdrive\d\build
$ ../vpx/configure --target=x86-win32-vs8 --enable-static-msvcrt --disable-install-docs
vs9---VS2008；
vs8----VS2005；
--disable-install-docs表示不安装文档；
注意：vpx下面也有一个build目录，所以不要进错了，是D:\test\build目录。
c. 配置正确后，命令行
$ make
命令行下显示内容不一定完全相同。
等待创建VS工程。
e. 编译VS工程
打开VS工程，在需要编译的项目右键Custom Build Rules，在弹出框里选择yasm，OK，编译就可以了。
 

先打开vs2013命令行：

在vs2013命令行中启动msys：
C:\Program Files\Microsoft Visual Studio 12.0\VC>c:\mingw\msys\1.0\msys.bat

进入libvpx源码根目录，建立build文件夹：

mkdir build

cd build

../configure --disable-shared --enable-static --enable-static-msvcrt  --disable-docs --disable-examples --target=x86-win32-vs17--prefix=D:\dev2\libvpx\slns

 

 

../configure --disable-shared --enable-static --enable-static-msvcrt  --disable-docs --disable-examples --target=x86-win32-vs17--prefix=/usr/local/msvc #配置用vs2013工程

参数说明：

--disable-shared --enable-static --enable-static-msvcrt :允许静态库

--target：生成指定的目标工程

make   #会自动用vs2013编译工具进行编译

 

 

 

 

转载于:https://www.cnblogs.com/endv/p/6866947.html

VP9完整源代码
12-01
Google开发的VP9源代码
VP9编码器 v1.3.0
01-07
VP9相比VP8有着很多的提升。在比特率方面，VP9比VP8提高2倍图像画质，H265的画质也比H264高2倍。VP9一大的优势是没有版税。和H.264和H.265不同，它免费进行使用。
libvpx 源码，vp8-vp9
08-21
Libvpx 是一个开源的库，用于编码和解码视频，特别是VP8和VP9格式的视频。它是由WebM项目的一部分，旨在提供高质量的视频编码，同时保持高效的压缩。Libvpx 通常用于网页视频、流媒体服务和其他需要视频压缩的场景。如果你需要更具体的信息或者帮助，请提供更多的上下文或者问题。
【VP9】libvpx在Windows和Linux平台下的编译和vp9编解码器的命令行参数
fanhenghui的专栏
11-26 1704
=================================================================== 参考：https://www.cnblogs.com/endv/p/6866947.html         https://blog.youkuaiyun.com/listener51/article/details/78883975 1、libvpx下载 https...
vs2022添加vp9
06-04
在 Visual Studio 2022 中添加 VP9 支持，需要按照以下步骤操作： 1. 安装最新版的 Visual Studio 2022。 2. 安装最新版的 Windows SDK。 3. 安装最新版的 Windows Driver Kit (WDK)。 4. 下载 VP9 编码器源代码...
VS2012 c# VP检测项目框架
01-04
【标题】"VS2012 c# VP检测项目框架" 涉及的主要知识点是基于Visual Studio 2012的C#编程与National Instruments的VisionPro视觉处理库的结合应用，创建一个用于图像检测的项目框架。这个框架是为了高效、规范地实现...
为什么我的unity2021lts的版本不支持webm vp9的片吗
最新发布
07-20
WebM VP9支持情况：VP9是Google开发的下一代视频编码格式，但Unity在2021 LTS版本中可能没有默认包含对VP9的解码支持。 3. 平台差异：不同平台（Windows、Mac、Android、iOS等）对视频格式的支持程度不同，Unity...
VP9编码器外部帧缓冲区信息保存机制
资源摘要信息:"VP9编码器接口文件 vp9_dx_iface.c 的知识解析" VP9是一种开源视频编码格式，由Google的WebM项目推动，旨在提供高压缩率且免版税的视频压缩技术。VP9编码器支持在不同的软硬件平台上实现，以优化视频...
谷歌VP9 UDP视频传输源码深度解析
VP9支持高效的数据压缩，能够在不牺牲太多视频质量的情况下减小文件大小，因此常被用于视频会议、在线流媒体服务（如YouTube和Netflix）以及高分辨率视频内容的传输。 2. UDP协议及其在视频传输中的应用 UDP（用户...
Win10_LTSC_VP9_Installer:没有Windows Store的LTSC 1809（x64和x86）！
05-28
=======> Windows 10 LTSC VP9和AV1安装程序（ENG FAQ）： 注意VP9在浏览器中不起作用，例如-youtu.be/N1-Jmq7BLFE查看任务管理器中的“ GPU”，在4k（'2160p60fps'）负载下<10％。 更新GPU驱动程序，安装或升级所有（x86和x64）MS VC ++可再发行组件到最新版本，然后重新启动PC：support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads 停止所有浏览器并运行脚本'install_step1.bat'-以管理员身份再次单击（或逐行运行命令* .ps1）。 将所有附加文件* .Appx和* .AppxBundle复制到目录“ C：\ Program Files \ WindowsApps” 对于x64
VP9 视频编码标准 （谷歌官方）
06-21
官方文档，与大家共享，有经验者请留下联系方式，以后一起探讨
世界上最快的VP9视频解码器
01-07
世界上最快的VP9视频解码器 As before , I was very excited when Google released VP9 – for one, because I was one of the people involved in creating it back when I worked for Google (I no longer do). How good is it, and how much better can it be? To evaluate that question, Clément Bœsch and I set out to write a VP9 decoder from scratch for FFmpeg. The goals never changed from the original ffvp8 situation (community-developed, fast, free from the beginning). We also wanted to answer new questions: how does a well-written decoder compare, speed-wise, with a well-written decoder for other codecs? TLDR (see rest of post for details): as a codec, VP9 is quite impressive – it beats x264 in many cases. However, the encoder is slow, very slow. At higher speed settings, the quality gain melts away. This seems to be similar to what people report about HEVC (using e.g. x265 as an encoder). single-threaded decoding speed of libvpx isn’t great. FFvp9 beats it by 25-50% on a variety of machines. FFvp9 is somewhat slower than ffvp8, and somewhat faster than ffh264 decoding speed (for files encoded to matching SSIM scores). Multi-threading performance in libvpx is deplorable, it gains virtually nothing from its loopfilter-mt algorithm. FFvp9 multi-threading gains nearly as much as ffh264/ffvp8 multithreading, but there’s a cap (material-, settings- and resolution-dependent, we found it to be around 3 threads in one of our clips although it’s typically higher) after which further threads don’t cause any more gain. The codec itself To start, we did some tests on the encoder itself. The direct goal here was to identify bitrates at which encodings would give matching SSIM-scores so we could do same-quality decoder performance measurements. However, as such, it also allows us to compare encoder performance in itself. We used settings very close to recommended settings forVP8,VP9andx264, optimized for SSIM as a metric. As source clips, we chose Sintel (1920×1080 CGI content, source ), a 2-minute clip from Tears of Steel (1920×800 cinematic content, source ), and a 3-minute clip from Enter the Void (1920×818 high-grain/noise content,screenshot). For each, we encoded at various bitrates and plotted effective bitrate versus SSIM . sintel_ssimtos_ssimetv_ssim You’ll notice that in most cases, VP9 can indeed beat x264, but, there’s some big caveats: VP9 encoding (using libvpx) is horrendously slow – like, 50x slower than VP8/x264 encoding. This means that encoding a 3-minute 1080p clip takes several days on a high-end machine. Higher –cpu-used=X parameters make the quality gains melt away. libvpx’ VP9 encodes miss the target bitrates by a long shot (100% off) for the ETV clip, possibly because of our use of –aq-mode=1. libvpx tends to slowly crumble at higher bitrates for hard content – again, look at the ETV clip, where x264 shows some serious mature killer instinct at the high bitrate end of things. Overall, these results are promising, although the lack-of-speed is a serious issue. Decoder performance For decoding performance measurements, we chose (Sintel)500 (VP9), 1200 (VP8) and 700 (x264) kbps (SSIM=19.8); Tears of Steel4.0 (VP9), 7.9 (VP8) and 6.3 (x264) mbps (SSIM=19.2); and Enter the Void 9.7 (VP9), 16.6 (VP8) and 10.7 (x264) mbps (SSIM=16.2). We used FFmpeg to decode each of these files, either using the built-in decoder (to compare between codecs), or using libvpx-vp9 (to compare ffvp9 versus libvpx). Decoding time was measured in seconds using “time ffmpeg -threads 1 [-c:v libvpx-vp9] -i $file -f null -v 0 -nostats – 2>&1 | grep user”, with this FFmpeg and this libvpx revision (downloaded on Feb 20th, 2014). sintel_archs tos_archsetv_archs A few notes on ffvp9 vs. libvpx-vp9 performance: ffvp9 beats libvpx consistently by 25-50%. In practice, this means that typical middle- to high-end hardware will be able to playback 4K content using ffvp9, but not using libvpx. Low-end hardware will struggle to playback even 720p content using libvpx (but do so fine using ffvp9). on Haswell, the difference is significantly smaller than on sandybridge, likely because libvpx has some AVX2 optimizations (e.g. for MC and loop filtering), whereas ffvp9 doesn’t have that yet; this means this difference might grow over time as ffvp9 gets AVX2 optimizations also. on the Atom, the differences are significantly smaller than on other systems; the reason for this is likely that we haven’t done any significant work on Atom-performance yet. Atom has unusually large latencies between GPRs and XMM registers, which means you need to take special care in ordering your instructions to prevent unnecessary halts – we haven’t done anything in that area yet (for ffvp9). Some users may find that ffvp9 is a lot slower than advertised on 32bit; this is correct, most of our SIMD only works on 64bit machines. If you have 32bit software, port it to 64bit. Can’t port it? Ditch it. Nobody owns 32bit x86 hardware anymore these days. So how does VP9 decoding performance compare to that of other codecs? There’s basically two ways to measure this: same-bitrate (e.g. a 500kbps VP8 file vs. a 500kbps VP9 file, where the VP9 file likely looks much better), or same-quality (e.g. a VP8 file with SSIM=19.2 vs. a VP9 file with SSIM=19.2, where the VP9 file likely has a much lower bitrate). We did same-quality measurements, and found: ffvp9 tends to beat ffh264 by a tiny bit (10%), except on Atom (which is likely because ffh264 has received more Atom-specific attention than ffvp9). ffvp9 tends to be quite a bit slower than ffvp8 (15%), although the massive bitrate differences in Enter the Void actually makes it win for that clip (by about 15%, except on Atom). Given that Google promised VP9 would be no more than 40% more complex than VP8, it seems they kept that promise. we did some same-bitrate comparisons, and found that x264 and ffvp9 are essentially identical in that scenario (with x264 having slightly lower SSIM scores); vp8 tends to be about 50% faster, but looks significantly worse. Multithreading One of the killer-features in FFmpeg is frame-level multithreading, which allows multiple cores to decode different video frames in parallel. Libvpx also supports multithreading. So which is better?
openssh9p离线升级包(含依赖包及教程)-centos7.9验证
04-10
openssh9p离线升级包，含依赖包的rpm软件 及教程 升级包在centos7.9验证成功
Visual Studio 2017环境配置MPI v9.0 并行编程环境
zem12345678的博客
03-25 8677
目录 第一步：下载安装mpi 官网：http://www.mpich.org/ windows版官网：https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx   第二步：Visual Studio 2017配置环境 第一步：下载安装mpi 官网：http://www.mpich.org/ windows版官网：http...
【免费下载】 VP9 视频编码标准（谷歌官方）资源下载
gitblog_09711的博客
10-19 2520
VP9 视频编码标准（谷歌官方）资源下载 【下载地址】VP9视频编码标准谷歌官方资源下载 本仓库提供了一份官方的VP9视频编码标准文档，供大家下载和学习。VP9是由谷歌开发的一种高效视频编码标准，广泛应用于视频压缩和流媒体传输领域 ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值