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

Call setRate instead of pause/play as they are equivalent #76

Merged
merged 1 commit into from Jul 20, 2015

Conversation

dpeek
Copy link
Contributor

@dpeek dpeek commented Jul 10, 2015

Video was resuming after seek when setRate was called after play/pause in applyModifiers. According
to Apple's docs play/pause are equivalent to setRate:1.0 and setRate:0.0, meaning that if rate was
1.0 the video resumed after seeking completed.

@brentvatne
Copy link
Contributor

This makes sense to me, @johanneslumpe what do you think?

@dpeek dpeek force-pushed the fix/paused-resumes-after-seek branch from 340d6fa to 27b8180 Compare July 14, 2015 10:05
…idlarzGroup#75)

Video was resuming after seek when setRate was called after play/pause in applyModifiers. According
to Apple's docs play/pause are equivalent to setRate:1.0 and setRate:0.0, meaning that if rate was
1.0 the video resumed after seeking completed.
@dpeek dpeek force-pushed the fix/paused-resumes-after-seek branch from 27b8180 to 153eb59 Compare July 14, 2015 10:07
@isair
Copy link
Contributor

isair commented Jul 16, 2015

Seems logical for me as well. Haven't tested but sounds like this might fix #73 too.

Edit: By the way, @dpeek, the applicationWillResignActive implementation needs to be updated for these changes as well.

Edit 2: @brentvatne I can confirm that this fixes #73, at least in my project.

@isair isair merged commit 153eb59 into TheWidlarzGroup:master Jul 20, 2015
@dpeek dpeek deleted the fix/paused-resumes-after-seek branch July 24, 2015 08:57
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

Successfully merging this pull request may close these issues.

None yet

3 participants