Brad Larson

@bradlarson I didn't play around with GPUImage 1, but is GPU Image 2's FilterShowcase crashing on Simulator intentional?

@r0unak The Simulator has no camera, so if you look on the console you’ll probably see that it’s erroring out for that reason.

@bradlarson Yep, I got that. I meant to ask, if the crash is intentional, or do you want to display a message on the screen about that?

@r0unak An error alert would probably be cleaner and easier to follow. People commonly got confused about this in the old framework.

@r0unak Can devicesWithMediaType() ever return something other than an AVCaptureDevice? If not, I wouldn’t worry about the optional there.

@bradlarson you mean L27 right? It gives a warning: Treating a forced downcast to 'AVCaptureDevice' as optional will never produce nil

@bradlarson Finished it just in time to start over using Metal Compute Shaders, right? /me ducks

@jeff_lamarche I’ve tinkered with them, but using GLSL means this may eventually work on almost everything under the sun. That’s exciting.

@bradlarson Yeah, I was just kidding. You’d only have to rewrite a small portion anyway. Have you looked at Vulkan at all?

@jeff_lamarche I’m really interested to see how that progresses. Metal, Mantle, etc. are big wins for engines but portability is a problem.

@bradlarson In reality, porting a HLSL or GLSL shader to metal is actually pretty simple, but may not be worth the effort in your case.

@bradlarson I think the real wins comes when you have lots of draw calls per frame, which I doubt is your case in GPUImage. :)

@bradlarson great post, dude

@bradlarson do you have performance benchmarks for Objective-C & Swift implementations?