Sun Wei

Thanks for your reply. It seems that various implementations of cLN have similar performce.

> Please see: https://developer.android.com/ndk/reference/group/audio#aaudiostream_gettimestamp > > > Note that because requestStart() is asynchronous, timestamps will not be valid until a > > short time after calling requestStart(). So AAUDIO_ERROR_INVALID_STATE should...

Note that there is no timestamp error when only using audio stream on Android 11. The error happens when I use MediaRecorder to record the video at the same time....

Update: I upgrade the Android OS. It works well on Pixel 5a with Android 12. I believe the key cause is Android 11.

> Is there has an accurate way in Android to get latency of device, no matter what OS version is? There are three numbers in timestamp.latency. What do they refer...

The difference of returned timestamps is 0. between CLOCK_MONOTONIC and CLOCK_BOOTTIME. The correct difference of my device should be 330738680632263 nanoseconds based on Java System clock APIs. It is the...

> You'll need to quantify the latency of initiating audio streaming/recording. I think when we were looking into using audio chrips for synchronization the variable latency of starting/stopping audio streaming...

> Thanks so much. Will try to figure out these challenges.

I train the coco but the minimum loss is still 3.3 while mAP is terrible. Do you guys have some ideas?

> You can back calculate the time of frame zero. But the accuracy is not great. The CDD requests an accuracy of > What use case requires microsecond accuracy? Thanks...