Sebastian Schmidt comments

Results 217 comments of


                                            Sebastian Schmidt

Offline support for Firebase Storage operations

@harrisonlo Thanks for reporting this request! Firestore and Firebase Storage are very different under the hood. Firestore is a structured datastore that is meant to store small chunks of interpreted...

🐛 [mediapipe_task_genai] On Flutter/Android llm engine crashes : failed to validate graph

Hello, this issue may have been caused by one of our older build configurations. Can you let us know if this is still a problem? If so, we will have...

module 'mediapipe.python._framework_bindings.model_ckpt_util' has no attribute 'ConvertHfTokenizer'

Sorry - we do not support Windows for our GenAI tasks at this moment as we do not have the GPU support on Windows at the moment. We hope that...

NPU Support

Thanks for filing this - and we totally agree with you. At this moment, NPU differ greatly among platforms and as such, we cannot yet build a cross-platform framework easily....

NPU Support

We currently don't have NPU support for our Vision APIs. Thank you.

Build error when adding mediapipe via cocoapods to the framework project (iOS)

Can you try to manually add MediaPipeTasksCore as a dependency?

Build error when adding mediapipe via cocoapods to the framework project (iOS)

Sorry - I indeed meant MediaPipeTasksCommon.

Flutter Package?

Hi! We are having some discussion about this, but cannot provide a timeline at this point. We certainly recognize that better Flutter support is very important to large part of...

FR: Skip re-downloading files from Storage

Thanks for filing this. You can probably do this already if you issue a `getMetadata` request and look at the generation number: https://github.com/firebase/firebase-ios-sdk/blob/2c1f5795f3aeae6b11edfbe236727162f91c0a95/FirebaseStorage/Sources/FIRStorageConstants.m#L68 @tonyjhuang might be able to provide more...

Inconsistent MediaPipe Tasks Vision version on Maven repository

Unfortunately, we published this version a while back with an incorrect version number. It does not look like we can resolve this issue until we bump our main release version.