Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to GPUImage 3 #75

Open
alex-taffe opened this issue Jun 12, 2019 · 1 comment
Open

Migrate to GPUImage 3 #75

alex-taffe opened this issue Jun 12, 2019 · 1 comment
Assignees
Labels
blocked For items that progression is not possible on due to external factors

Comments

@alex-taffe
Copy link
Collaborator

We're currently using GPUImage which hasn't been updated in 3 years, and also uses OpenGL, which is deprecated. GPUImage3 is written in Metal and Swift, and is actively maintained

@alex-taffe alex-taffe self-assigned this Jun 16, 2019
@alex-taffe
Copy link
Collaborator Author

The ultimate goal according to the developer of GPUImage is that GPUImage2 and GPUImage3 will be identical in terms of API, however 3 will be metal based and 2 will be OpenGL based. As of right now, 3 is still missing key functionality like motion detection filters. 2 is also incomplete, for example, it is not yet possible to change the camera from front to back or the orientation of the video feed because the variable is implemented as:

public var location:PhysicalCameraLocation {
        didSet {
            // TODO: Swap the camera locations, framebuffers as needed
        }
    }

As a result, this has to be put on hold

@alex-taffe alex-taffe added the blocked For items that progression is not possible on due to external factors label Jun 16, 2019
@alex-taffe alex-taffe mentioned this issue Sep 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked For items that progression is not possible on due to external factors
Projects
None yet
Development

No branches or pull requests

1 participant