Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Failed to create encoder component #22

Closed
tloshi opened this issue Nov 9, 2017 · 3 comments
Closed

Failed to create encoder component #22

tloshi opened this issue Nov 9, 2017 · 3 comments

Comments

@tloshi
Copy link

tloshi commented Nov 9, 2017

Every time I try to start capturing the log file shows me this message "Failed to create encoder component", can someone please tell me where should I see a full documentation in order to be able to use the SDK properly. I can't face where the problem is even thought I did all steps as I saw here:
https://github.com/facebook/360-Capture-SDK/blob/master/README.md.

Here is my log:
[ 2017-11-09 08:41:08 ][LOG]: Folder is already existed
[ 2017-11-09 08:41:08 ][LOG]: It's invalid texture pointer: null
[ 2017-11-09 08:41:08 ][LOG]: Audio device name: : Rift (Intel(R) Display Audio)
[ 2017-11-09 08:41:08 ][LOG]: Audio device name: : Speakers/Headphones (Realtek High Definition Audio)
[ 2017-11-09 08:41:08 ][LOG]: Audio device name: : Headphones (Rift Audio)
[ 2017-11-09 08:41:08 ][LOG]: Found Rift headphone. We're using Rift headphone as audio intput/output source
[ 2017-11-09 08:41:08 ][ERROR]: Failed to create encoder component
[ 2017-11-09 08:41:08 ][ERROR]: Initial configuration setting is failed

Thanks in advanced.

@cg439
Copy link
Contributor

cg439 commented Nov 17, 2017

What hardware are you using? What GPU? The null texture pointer may be related to another issue flagged by someone for non-surround capture (ie flat/rectilinear content). Are you doing 360 capture or regular content capture?

@grancia
Copy link
Contributor

grancia commented Mar 9, 2018

Hi tloshi, I believe the issue was fixed with latest one.
Can you try with FB Capture SDK v1.20? If you still encounter the issue, please let me know your AMD graphics card and driver info.
Thanks,

@grancia
Copy link
Contributor

grancia commented Jun 6, 2018

Because it has been about over two months since v2.0 was released, I want to close v1.x related issues now. If you have any issue on v2.0, please create separate thread.
Thanks,

@grancia grancia closed this as completed Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants