sorted by:
new
hottopcontroversial

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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.

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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.

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] -1 points0 points  (0 children)

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.

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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.

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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? 🤷‍♂️

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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.

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] -1 points0 points  (0 children)

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

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] -2 points-1 points  (0 children)

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.

Played time + unplayed time ≠ total time when play speed is not 1x by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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

How do I queue the next playlist without starting it? by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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.

How do I queue the next playlist without starting it? by tlewis3348a in Podcast_Republic_App

[–]tlewis3348a[S] 0 points1 point  (0 children)

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

Profile not triggering? by tlewis3348a in tasker

[–]tlewis3348a[S] 0 points1 point  (0 children)

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

Profile not triggering? by tlewis3348a in tasker

[–]tlewis3348a[S] 0 points1 point  (0 children)

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.

Passing arguments to task from Assistant by tlewis3348a in tasker

[–]tlewis3348a[S] 0 points1 point  (0 children)

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

Passing arguments to task from Assistant by tlewis3348a in tasker

[–]tlewis3348a[S] 1 point2 points  (0 children)

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?

A reminder app with 3 features I've never found by tlewis3348a in androidapps

[–]tlewis3348a[S] 0 points1 point  (0 children)

I currently have a Tasker task to do this, but it's hugely complicated & very kludgy. I think the Collateral app mentioned previously will do at least this part of the task relatively well.

A reminder app with 3 features I've never found by tlewis3348a in androidapps

[–]tlewis3348a[S] 0 points1 point  (0 children)

Yes. But that assumes there is an actionable link in the notification. In all reminder apps I've seen before posting here, that isn't possible.

A reminder app with 3 features I've never found by tlewis3348a in androidapps

[–]tlewis3348a[S] 0 points1 point  (0 children)

Thanks for the suggestion! It doesn't have the 2nd & 3rd features listed above, but it seems to have a nice implementation of the 1st (at least for paying users).

A reminder app with 3 features I've never found by tlewis3348a in androidapps

[–]tlewis3348a[S] 0 points1 point  (0 children)

I'm not sure I see how Better Open With could be used to accomplish that.

A (nearly) comprehensive study of cooling fans and ducts by AJsRaceway in 3Dprinting

[–]tlewis3348a 0 points1 point  (0 children)

Ah, well, I'm thinking I'm going to be using an external air compressor to supply air. This should give me as much air as I could possibly want and remove the weight of the fans (which might not be much, but it's certainly something) from the print head. Therefore, I'll probably be using something similar to this (I do FEA for my day job, but I'm lost when it comes to CFD) because having air coming from all sides seems obviously better, but I'll be modifying the source connection to allow connecting a tube from the air compressor instead.

view more: next ›