完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
大家好我有这个M60网格设置,GPU直通模式到Win8.1 VM。
我设法通过将Windows帐户设置为自动登录,在不使用TeamViewer的情况下获得NvFBCDx9捕获和流媒体输出。 但是现在我有一个NvFBCCuda版本,它在捕获之后但在编码过程之前执行post-fx,如果没有TeamViewer,这个版本就不能正常工作。 如果我没有使用TeamViewer进行连接,它将无法锁定比特流,一旦我连接并捕获,它就可以正常工作。 我有什么想法可以绕过teamviewer? 谢谢 以上来自于谷歌翻译 以下为原文 Hi all I have this M60 Grid setup, with the GPU on passthrough mode to a Win8.1 VM. I've managed to get NvFBCDx9 capturing and streaming out fine without using TeamViewer by setting a windows account to auto-login. However now I have a NvFBCCuda version that performs post-fx after capturing but before the encoding process, and this version does not work well without TeamViewer. It will fail to acquire a lock on the bitstream if I do not connect using TeamViewer, once i connect and capture, it works fine. Any ideas how I can get around teamviewer? Thanks |
|
相关推荐
2个回答
|
|
某种失败的源代码应该是有用的。
尝试启用GRID“日志”。 它揭示了许多内部错误和失败,它们被通用错误返回所掩盖。 请参阅“NVIDIA Capture SDK编程指南.pdf”第64页 - “4.1.4。启用文本日志的生成” - 我正在使用“NVFBCLog = 42”(回答生命,宇宙和一切)。 以上来自于谷歌翻译 以下为原文 Some sort of failed source code should be useful. Try to enable GRID "logs". It disclosure many internals errors and fails that are masked by generic error return. See "NVIDIA Capture SDK Programming Guide.pdf" page 64 - "4.1.4. Enabling generation of textual logs" - I am using "NVFBCLog=42" (answer to life, the universe, and everything). |
|
|
|
感谢mcerveny的响应,我不知道详细的日志记录开关,这是最有用的!
42并没有回答我的问题,它让它消失了,可能在某个地方搭便车。 真的很奇怪,通过该开关启用任何日志记录,我的cuda版本捕获正常,没有TeamViewer .....我不喜欢这种行为,希望我能想出一个带日志的repro。 某种失败的源代码应该是有用的。 尝试启用GRID“日志”。 它揭示了许多内部错误和失败,它们被通用错误返回所掩盖。 请参阅“NVIDIA Capture SDK编程指南.pdf”第64页 - “4.1.4。启用文本日志的生成” - 我正在使用“NVFBCLog = 42”(回答生命,宇宙和一切)。 以上来自于谷歌翻译 以下为原文 Thanks for the response mcerveny, I didn't know about the verbose logging switch, this is most useful! 42 didn't just answer my questions, it made it go away, probably hitchhiking its way somewhere. It really is strange, enabling any logging at all via that switch, and my cuda version captures fine, without TeamViewer.....I don't like this behavior, hopefully I can come up with a repro with logs. Some sort of failed source code should be useful. Try to enable GRID "logs". It disclosure many internals errors and fails that are masked by generic error return. See "NVIDIA Capture SDK Programming Guide.pdf" page 64 - "4.1.4. Enabling generation of textual logs" - I am using "NVFBCLog=42" (answer to life, the universe, and everything). |
|
|
|
只有小组成员才能发言,加入小组>>
使用Vsphere 6.5在Compute模式下使用2个M60卡遇到VM问题
3069 浏览 5 评论
是否有可能获得XenServer 7.1的GRID K2驱动程序?
3488 浏览 4 评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-23 11:07 , Processed in 0.631236 second(s), Total 48, Slave 41 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号