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

Duration metric unit difference between iOS and Android breaks seekTo in iOS #162

Open
joshstallnick opened this issue Jan 13, 2020 · 0 comments

Comments

@joshstallnick
Copy link

I currently have an audio example of:

Android duration: 260049
iOS duration: 260.048875

Without realizing, I implemented the seekTo method using the android duration which I assume is in milliseconds. The documentation for the seekTo method states that it is in seconds, which would lead me to believe that seeking by milliseconds would provide incorrect results.

It currently breaks with a calculation of the the iOS duration - which I assume is in seconds since my audio file is roughly 4 mins. This makes sense that it would break if it handles for the android. This calculation is of the effect of (0.15 * 260.048875) to seek to 15% of the duration.

I tried to mutiply the iOS seek to value by 1000 to get it to equal what the android does but that still breaks and ends the recording.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant