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

Add jump forward and backward buttons to playback controls #76

Open
vsekhar opened this issue May 18, 2019 · 3 comments
Open

Add jump forward and backward buttons to playback controls #76

vsekhar opened this issue May 18, 2019 · 3 comments

Comments

@vsekhar
Copy link

vsekhar commented May 18, 2019

Add jump forward and backward buttons to playback controls (for on-device playback as well as Chromecast playback). Similar to Netflix controls.

I suggest a 30 seconds forward (since it might require lots of forward jumps to get back to where you were previously) and 10 seconds back (so you can use it to fine tune where you are after you've gone a bit too far).

@DSteve595
Copy link
Owner

For on-device playback, the app uses whatever video player you have, so you should be able to get that feature by installing another video player that has it.

@vsekhar
Copy link
Author

vsekhar commented May 18, 2019

The flow I think you're referring to (which I just discovered) is:

  1. Open file in Put.io app
  2. Tap Stream (or Stream
  3. Choose video player (if necessary)
  4. Tap Cast icon in video player
  5. Use controls in video player

whereas my usual flow is:

  1. Tap Cast button in Put.io app
  2. Open file in Put.io app
  3. Tap Stream (or Stream original)
  4. Use controls in Put.io app (?)

In the second flow, the controls seem to be provide by the app. It has the advantage of maintaining the cast session rather than having to re-cast (and choose display) at the start of each file.

Is this a deprecated flow?

@DSteve595
Copy link
Owner

Sorry, I was talking about playing and watching on a phone. Yeah, the UI for casting leaves a lot to be desired. Improvements can definitely be made.

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

2 participants