表达式编码器 - 文件尺寸的限制 - 最小大小为 64 * 64 并且必须是 4 的倍数？
当文件宽度或高度不是四的倍数或小于 64 时，我尝试在 Expression Encoder 中对文件进行编码时收到错误消息。我在文档/网络搜索中找不到这方面的信息，但什么也没有这解释了哪些设置可能会导致/减轻这些限制。我认为它与底层数据类型有关。
错误消息：指定的宽度无效。该值必须是 64 到 4096 之间的整数，并且是 4 的倍数。
任何人都可以提供有关为什么/可以操纵哪些设置来更改此行为的更多详细信息：IE 质量、压缩等。
I receive error messages when attempting to encode files in Expression Encoder when the file width or height is not a multiple of four, or is smaller than 64. I have been able to find very little in the documentation / web searches on this, and nothing that explains what settings may cause / alleviate these limitations. I assume it has something to do with the underlying data type.
Error Message: Invalid Width Specified. The value must be an integer between 64 - and 4096 and be a multiple of 4.
Can anyone provide further details on why / what settings can be manipulated to change this behavior: I.E. quality, compression etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在几个 MS 网站上发帖后，我收到了 Microsoft 的回复（如果它有帮助的话）。
WMSDK（我们编码 WMV 的主要依赖项）具有这些限制。请注意，这些限制也在 WME 中强制执行。
您是否正在尝试对宽度或高度小于 64 像素的内容进行编码？如果是这样，我建议你信箱。当前的 VC-1 或 H.264 配置文件不支持 4096 宽度，因此限制已经超出了您使用我们支持的输出格式可以完成的任务。
这将留下“可被 4 整除”的限制，我建议您只需使用信箱或稍微裁剪其他方式来绕过该限制。 WMSDK 不仅要求“可被 4 整除”限制，而且在编码（宏块大小）和解码（无需扫描线填充）期间也有帮助。
After posting on several MS sites, I recieved this response from Microsoft should it be of assistance.
The WMSDK, our main dependency to encode WMV, has those limitations. Note that those limits were also enforced in WME.
Are you trying to encode something smaller than 64 pixels wide or tall? If so, I suggest you letterbox. Current VC-1 or H.264 profiles do not support 4096 width, so the limit is already over what you can accomplish with our supported output format.
That would leave the "divisible by 4" limitation, which I would suggest you simply either letterbox or slightly crop the other way to get around that limit. Not only the "divisible by 4" limit is required by the WMSDK, but it also helps during encoding (macroblock size) and decoding (no scanline padding necessary).