Expression Encoder 4 SP2 SDK:使用之前的Expression Encoder 4 SP1 SDK,您自己的编码器怎么样? [英] Expression Encoder 4 SP2 SDK: What about your own encoder using the previous Expression Encoder 4 SP1 SDK

查看:73
本文介绍了Expression Encoder 4 SP2 SDK:使用之前的Expression Encoder 4 SP1 SDK,您自己的编码器怎么样?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好!

我们使用Expression Encoder 4 SP1 SDK制作了自己的编码器。我们显然希望现在使用Expression Encoder 4 SP2 SDK。客户可以只安装Expression Encoder 4 SP2,新的二进制文件将自动使用而不是
旧的二进制文件?基本上我认为问题是应该选择哪种方法:

We've made our own encoder using the Expression Encoder 4 SP1 SDK. We obviously would like to now use Expression Encoder 4 SP2 SDK instead. Can the customers just install Expression Encoder 4 SP2 and the new binaries will automatically be used instead of the old binaries? Basically I suppose the question is which approach should be selected:


  1. 只需使用旧的应用程序,就会自动使用新的二进制文件。
  2. 重新编译定义编码器的项目。
  3. 更改定义新程序集编码器的项目中的引用,然后重新编译项目。

 

祝你好运,

Henrik Dahl

Henrik Dahl

 

 

推荐答案

像所有任何产品的Service Pack版本,SP2都安装在任何v4安装(RTM或SP1)上。 Encoder SDK二进制文件也在GAC中更新,这意味着RTM或SP1 SDK二进制文件不再可用。 SP版本
的性质决定了没有进行SDK更改,我们会尽最大努力遵循此规则。换句话说,使用  v4 RTM或v4 SP1 SDK构建的应用程序可以在安装了Encoder 4 SP2的PC上运行,因为SDK
是完全向后兼容的。

Like all service pack releases of any product, SP2 installs over any v4 installation (RTM or SP1). The Encoder SDK binaries are also updated in the GAC, which means that the RTM or SP1 SDK binaries are no longer available. The nature of an SP release dictates that no SDK breaking change are made and we followed this rule to the best of our abilities. In other words, the application you built with the v4 RTM or v4 SP1 SDK will work on a PC that has Encoder 4 SP2 installed as the SDK is fully backward compatible.

显然,如果您打算使用任何新的SP2技术,则需要使用最新的SDK重新编译您的应用程序,并确保您的客户安装了SP2。

Obviously, if you plan to use any new SP2 technology, you will need to recompile your application with the newest SDK and ensure that your clients have SP2 installed.

当然,虽然没有破碎,但在SP1和SP2之间的一些行为发生了变化,这些行为是我们无法控制的。其中一个可能与您相关的是使用Cuda时SP1和SP2之间GPU负载的差异。
SP2使用了更多的GPU资源,这意味着尽管GPU可以占用比SP1更多的编码过程,但它不能像编码那么多编码流。我的
SP2白皮书中有更多相关信息。因此,修改设置"GPU流数量"的方式可能是有意义的。在您的应用程序中考虑到这一点。您还可以动态地将
设置为"GPU流的数量" 如果要在SP1和SP2上支持应用程序,则取决于安装的SDK的版本。但就个人而言,随着每个SP版本带来的所有改进,我认为使用SP2 SDK重新编译您的应用程序是有意义的,并且推动您的客户也升级到SP2。

Of course, while not broken persay, a few behaviors changed between SP1 and SP2 that were beyond our control. One of them that might be relevant to you are the differences in the GPU load between SP1 and SP2 when using Cuda. SP2 uses significantly more of the GPU resources, which means that while the GPU can take more of the encode process than in SP1, it won't be able to encode as many streams as it did. There is more information about this in my SP2 whitepaper. Because of this, it might make sense to modify the way you set the "number of GPU streams" in your application to take this into account. You could also dynamically set the "number of GPU streams"  depending on the version of the SDK installed if you want to support your application on either SP1 and SP2. But personally, with all the improvements every SP release brings, I would argue that it would make sense to recompile your application with the SP2 SDK and nudge your clients to also upgrade to SP2.

 


这篇关于Expression Encoder 4 SP2 SDK:使用之前的Expression Encoder 4 SP1 SDK,您自己的编码器怎么样?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆