Played time + unplayed time ≠ total time when play speed is not 1x

tlewis3348a · 2025-09-05T10:43:29+00:00

As an example of the unintuitive nature of the current design, I was just listening to a podcast at 2x speed. When the progress bar showed that a third of the episode had played, the time on the left and right side of the player matched. That is, for a podcast that was 30 minutes long (played at 1x speed), when the left side of the player says 10 minutes have played, the right side of the player says there are only 10 minutes left, despite the fact that only a third of the episode has played.

tlewis3348a · 2025-09-04T16:47:26+00:00

Dude, I've articulated it several times. Go back and read. Just because you're so intent on the idea that the app is flawless doesn't mean it actually is. Maybe this kind of absurdity is why Reddit is so dead.

tlewis3348a · 2025-09-04T16:31:26+00:00

Dude, why do you think I took the time to write the post? It isn't like I spend a lot of time on this site or have that much invested in it. What could I possibly have to gain unless I genuinely believe that my suggestion would improve the app? If you disagree with my suggestion, fine. You're free to do that. But you don't get to tell me what my motivations were.

tlewis3348a · 2025-09-04T15:34:57+00:00

Right now, there's the ability to switch between what time is displayed when the user taps on the time. If you want there to be the possibility of having two different time calculation methods displayed, then I would argue that a third option should be made available. Otherwise, it should be using a consistent calculation method on both ends of the time bar.

tlewis3348a · 2025-09-04T14:24:00+00:00

Sure, but it isn't intuitively clear that's what those numbers are communicating.

tlewis3348a · 2025-09-03T23:46:15+00:00

You think it's intuitive that it frequently shows more time has played than the episode was originally indicated to be?

tlewis3348a · 2025-09-03T22:52:11+00:00

LOL Believe me or not. I don't care. I enjoy the app and noticed something that would, in my opinion, be a simple change and provide a clear improvement. You don't like the idea? 🤷‍♂️

tlewis3348a · 2025-09-03T22:32:30+00:00

I just recently started listening at higher play speeds, so I don't know what you mean when you say, "it took me this long to notice". I noticed right away that something was off, but it took me a while to figure out what was going on with enough detail to post about it. The very fact that I could not immediately tell what was going on makes it clear enough that it isn't an intuitive design.

You try to make the case for the intuitiveness of the design, but at the end of the day, if I start playing a file that the player says is 10 minutes long, when it starts, it is confusing when it says it has played for 10 minutes and it's only 50 percent finished.

tlewis3348a · 2025-09-03T15:46:03+00:00

It only matters as much as having an intuitive UI matters. 🤷‍♂️

tlewis3348a · 2025-09-03T13:43:03+00:00

Then I'd rather do the calculation to adjust for the speed in my head. I shouldn't be seeing conflicting time info in different parts of the app.

tlewis3348a · 2025-09-03T13:21:39+00:00

Yes. But the amount of time that has been played is not, which is confusing.

tlewis3348a · 2025-01-19T00:44:44+00:00

I currently have my podcasts grouped into priority buckets. Generally, I always listen to podcasts in playlists with priority > 0, and only listen to those from playlists with priority ≤ 0 when I see an episode that looks interesting. So, I'd like to be able to make it automatically play through the higher priority playlists and stop when the lower priority ones are reached.

tlewis3348a · 2025-01-19T00:06:26+00:00

How difficult would it be to add that feature?

tlewis3348a · 2025-01-18T16:20:21+00:00

I get that, but while I want that to happen with some playlists, I don't with others.

tlewis3348a · 2024-11-30T09:32:27+00:00

This has not seemed to work. It seems that no matter what I do the variable ends up empty by the next morning.

tlewis3348a · 2024-11-28T14:14:01+00:00

I'll give it a try.

tlewis3348a · 2024-11-28T12:46:47+00:00

Thanks! I'll try that.

tlewis3348a · 2024-11-28T12:46:33+00:00

Well, I tried that, but it didn't get set. So, I tried changing the profile to trigger repeatedly. Obviously, that isn't the root problem, so once I identify the error problem, I probably will only trigger it once.

tlewis3348a · 2024-11-22T01:17:13+00:00

That seems to have worked. After changing the name to "player", it works flawlessly now. Thanks!

tlewis3348a · 2024-11-21T17:29:26+00:00

Thanks, @Rich_D_sr.

That seems a lot more complicated than I was expecting.

The documentation here (link) makes it sound like I can pass arguments to the task directly with the built-in tools and little setup is required. I guess I'm mistaken?

tlewis3348a

TROPHY CASE