aidan 🔥

On iOS you can totally implement this yourself using the SCCameraKitOutputRequiringPixelBufferDelegate to grab the camera frame and pipe them into an AVAssetWriter class CameraKitOutputToImage: NSObject, Output, OutputRequiringPixelBuffer, SCCameraKitOutputRequiringPixelBufferDelegate { var view: UIViewController; var…

@arashp @stevenxu update on this issue? this is putting me in the unfortunate position to migrate off Camera Kit Big hunch this fix is as simple as setting ARWorldTrackingConfiguration().providesAudioData to False. This is done somewhere inside CameraKit.start which I don't have access to. If I override the delegate, I can…

Okay, appears to be caused by and related to updating the ARKit Session after Camera Kit start. This is probably unexpected behavior? https://community.snap.com/snapar/discussion/2927/quick-tip-geolocated-lens-compass-heading-magnetic-north#latest

@arashp possibly! I think what would be more useful in this specific instance is the ability to input custom settings into ARSessionInput(session:ARSession) before initializing CameraKit. Maybe it's possible but I find it overrides the values I set

Bonus: if you'd like to get your Lens camera's x,y,z coordinates you can do so with the following. I'm using this to update the user's geolocation with finer precision func getARPosition () { if let currentFrame = self.arSessionInput.session.currentFrame { let cameraTransform = currentFrame.camera.transform let…

Okay thanks for the reply! If this ever opens up as a feature let me know

Hey @arashp, thanks for the detailed response however for my use case I need ARKit to keep alive during an active call. If I'm understanding you correctly the compass is an optional feature in ARKit so would I be able to disable the compass while using CameraKit? Then I would be able to stream the CameraKit session during…

Okay great. I have found a work around which is to toggle on the parent's physics body (with compound enabled) on and off at start and it seems to fix it. Maybe there's something up with start runtime or physics bodies that are added via scripting? I wish I could include a sample more quickly, currently working inside a…

@stevenxu woooot! thanks for the ping. If it's realistic to have it working by AWE (May 31st) would love to know as I'm going to be showing it off there and running trials with the first batch of Twitch streamers otherwise full steam ahead on gameplay over here!!

Extra Tip: If you're like me and ran into Auth issues (guess Remote Services API setup does not work!) you can still pass your header through in the Swift file by editing this section of code: var requestWithHeaders = URLRequest(url: url)requestWithHeaders.addValue(YourApiKey, forHTTPHeaderField: "x-app-secret") let task =…

@arashp @stevenxu Update #3: Confirming it does indeed suspend when receiving a call from both FaceTime and Discord during an active CameraKit session and never recovers, appearing frozen on its last rendered frame. The app remains stable, view can be dismissed, no error in console

Update #2: Confirming this error does NOT occur within a facetracking lens (back or front camera doesn't matter) so it seems to be a core issue with how ARKit is handled inside CameraKit and I have suspicion the ARSessionInput(session:ARSession()) provided to CameraKit.start() is not being used as I also don't receive any…

Update: The error doesn't seem to have anything to do with Microphone or Video usage in other apps (I disabled their permissions) Now my hunch is the error is a conflict with AVAudioSession - no matter what audio settings are set in advance CameraKit will shut down background audio making me think it collides with audio…

@stevenxu 1.20.0 iPhone 12 Pro (16.3.1) iOS only, haven't tested on Android

@stevenxu I think it has to do with the Lenses themselves. Back facing, world tracking + world meshing. Heavy on the AR feature set is my assumption of why it hangs. Otherwise, exporting Lens Studio 4.40.1, using the most recent CameraKit, loading from the Snap cloud. I've recorded two screen captures for you to review!…

* on explore you have a star * on your lenses no star * on your profile you have the Snapchat+ star Try removing the star in your Snapchat+ settings and see if it fixes it? Could be an issue between the two services.

Try deleting the Lens Studio cache and reinstalling Lens Studio. My guess is there's an incompatible file that was generated by a previous version of LS and its messing up the newest version.