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

Feature Request: -7 seconds (to complement +30 seconds) #83

Open
alevitan opened this issue Aug 16, 2012 · 4 comments
Open

Feature Request: -7 seconds (to complement +30 seconds) #83

alevitan opened this issue Aug 16, 2012 · 4 comments

Comments

@alevitan
Copy link

Sometimes we jump too far skipping recorded commercials, so backing up a little would be a nice new simple feature.

Thanks!!

@bherrmann7
Copy link
Owner

True. Early versions of CarCast included 15 second jump buttons too. But the interface was simplified to just have the two buttons.

@eddyp
Copy link

eddyp commented Mar 19, 2013

What do you think about a repeat feature combined with increased skip jump for the same existing buttons?
Press once = 15 second jump.
Keep pressed = skips: 15, 30, 30, 30, 60, 60, 60, 300 [max=300].

I found this mechanism to work very well on my old Nokia E71, even when used in the car.

@alevitan
Copy link
Author

I'd like to hear a second or 2 after each jump to get an idea if I am near the end of the break, and if I got too far, make it easy to go back a bit, thus the +30/-7 combination modeled after the "DAR Radio" player.

Thanks,
 
Arnie


From: eddyp [email protected]
To: bherrmann7/Car-Cast [email protected]
Cc: alevitan [email protected]
Sent: Tuesday, March 19, 2013 4:18 PM
Subject: Re: [Car-Cast] Feature Request: -7 seconds (to complement +30 seconds) (#83)

What do you think about a repeat feature combined with increased skip jump for the same existing buttons?
Press once = 15 second jump.
Keep pressed = skips: 15, 30, 30, 30, 60, 60, 60, 300 [max=300].
I found this mechanism to work very well on my old Nokia E71, even when used in the car.

Reply to this email directly or view it on GitHub.

@eddyp
Copy link

eddyp commented Mar 20, 2013

I'd like to hear a second or 2 after each jump to get an idea if I am near the end of the break

Yes, I forgot to say about this. My old Nokia E71 did that, too. Still, in practice, 2 seconds is way to long. Something like 0.5 seconds has proven enough for me. Granted, I don't generally listen to podcasts with ads, so I mainly used the REV function and I don't know if 0.5 seconds is enough to when forwarding, but it is enough when going back over something you heard before.

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

3 participants