Next/Previous Buttons Missing - With Auto-Queue Off

[desmonk]

Checklist

• I am using the latest version - x.xx.x
• I checked, but didn't find any duplicates (open OR closed) of this issue in the repo.
• I have read the contribution guidelines given at https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md.
• This issue contains only one bug. I will open one issue for every bug report I want to file.

Steps to reproduce the bug

Turning off auto-queue will make next and previous buttons go missing.

Actual behaviour

Next and previous play back buttons go missing.

Expected behavior

Should stay as normally they do.

Screenshots/Screen recordings

NA

Logs

NA

Device info

• Android version/Custom ROM version: 11
• Device model: OnePlus

[triallax]

I think that's intended behavior. If you don't have auto-queue, nothing is in the queue before/after the current video unless you add something manually, so having next/previous buttons wouldn't make sense.

[desmonk]

First, slow down and read again from a user standpoint.

Buttons should not rely on queue. They must remain static.

A user should have independence to choose from. This is like saying I won't want to play next or previous video if automatic queue is off! That is never the case. Never. We play songs and videos as we wish and that don't need to rely on whether we have some playlist or auto queue on.

This is really simple to understand and I am surprised you failed to see this clearly and closed the case without giving some deep thoughts. Always, think twice before arriving to a decision. There are always two sides to the coin.

And we all say, with great power comes great responsibility. So I hope you use your powers well.

Also, auto queue feature consumes unnecessary data if left on all the time. This give a user manual control. Hope this info has helped you!

[triallax]

A user should have independence to choose from. This is like saying I won't want to play next or previous video if automatic queue is off! That is never the case. Never. We play songs and videos as we wish and that don't need to rely on whether we have some playlist or auto queue on.

Well, the buttons are supposed to move forward/backward in the queue. If the queue is empty, there's nothing to move to, so then what are the buttons supposed to do?

Also, auto queue feature consumes unnecessary data if left on all the time.

What is your source on that statement?

[desmonk]

Buttons should play forward and backward as needed not relying on queue. See, a queue is merely an option to continue playing while buttons hit a break on it when needed. In short, they must remain independent of queue or playlist. Buttons needs to be simple buttons, that's all!

Auto-queue gonna keep going and going and that gonna consume data by definition. Are you referring to something else? If I misunderstood, do let me know.

[triallax]

Auto-queue gonna keep going and going and that gonna consume data by definition.

It does not keep going. It will just put the next video in the queue, and when the current video finishes and the next video starts playing, the third video is then automatically queued. Thus, no extra data is used up at all. This means that there are absolutely no cons to enabling auto-queue, so you should be able to use it just fine.

In short, they must remain independent of queue or playlist.

The buttons are dependent on the queue (not the playlist, as its items are added to the queue itself); that's how they're designed to work. I'm not sure I see the benefit of decoupling them from the queue. Could you explain?

[triallax]

I'll be opening this issue to continue the discussion, but I personally find this unnecessary to implement.

[desmonk]

Buttons need to be independent. It's like taking away manual gear option just because there is auto transmission! Users here can choose if they want to hit next or go back or pause. Also, about data. Think of this like this. Auto-queue will continue playing videos whether user wants or not as that is how this works unless there is some end to the list. That gonna consume data.

Meaning, auto queue actually does not stop unless it is turned off. And right now, if we turn it off, the buttons go down with it. Best analogy would be a Walkman player from old days. We need to be in control of selection, not the algorithm!

Thank you and I hope to learn from you too!

[triallax]

Ok, I think I understand what you mean now. Thanks for the explanation.

I understand why you want this now, but I thought up a solution that I found simpler and hopefully easier to implement: add an option to not go to the next video in the queue automatically, which would have the same effect that you want but you would also have to have auto-queue enabled. This option would also be more useful generally, for example when playing playlists. What is your opinion about this?

[desmonk]

That's a good one but thing is that will confuse users more. Then we have to implement say, Auto-Play option in addition to Auto-Queue. That will allow users to disable/enable auto playing of videos with queue enabled.

But again, there is no manual control here, is it? This still won't allow user to hit Forward/Backward buttons. Meaning with your options, next video won't play. But now how to play then? As there are no buttons for navigation except the touch controls.

But touch controls won't work in full screen mode and only work with side menu of videos are visible. So once again, buttons are needed.

Think of this like this. Without buttons, we can't move. With auto-play and auto-queue, we can only halt or continue, we can't still hit next or go back.

[triallax]

his still won't allow user to hit Forward/Backward buttons.

Why not? As long as the queue contains more items (which auto-queue add) they can press the forward/backward buttons as they please. Am I misunderstanding?

[desmonk]

We are on two different tracks:

You:
Auto-queue stays enabled but won't automatically plays next video. So buttons also stay present.

Me:
Buttons needs to be present all the time irrespective of any queue.

Now how your suggestion will lead to confusion is like this:
Auto-queue means to automatically queue. Right now all videos are getting played like this. It is more simple. Still no buttons. But if we halt the automatic playback, then the auto-queue which most users including myself think will play next video, won't simply play. So now we need something like auto-play and therefore we added more steps.

Whereby in my case, all we need are buttons.

[desmonk]

Thank you for that detailed response.

1. Data consumption increases as the auto queue by definition gonna start the next video after the current one ends. Simple as that. I'm not referring to thumbnails here. I am referring to player keeps on going to play next queue whether warranted.

2. Disabling video suggestions as grouped under similar and next will worsen the experience completely. This is a core YouTube feature.

3. Need buttons! They go missing in normal and also in full screen without auto queue on.

4. Same as above.

5. Need to work regardless of auto queue.

6. You're focused on queued list. Thereby you think that buttons are needed in such case. I'm focused on only buttons. Meaning say there is a next video in queue but I'd like to choose to play it or not. Not relying on auto queue at all. Present situation allows the play back to continue consuming more data. Also, full screen mode must have buttons just as stated here. We can touch the next video in normal UI but in full screen we can't as there is nothing there.

Hope I've answered well.

[SameenAhnaf]

As far as I understand, you want to enter next related video directly from full screen but manually, right? Then, we might implement this feature.

Swipe up the bottom interface for entering any related videos. Unlike YouTube app, swiping up for related videos should occur from only bottom interface as swiping up is already involved in volume and brightness gestures.

Screenrecorder-2021-05-23-14-57-06-726.mp4

Would you agree to have it instead of always-on buttons? Avoiding always-on buttons would help us know if a queue truly exists or not. I know, it doesn't match with YouTube app behaviour. But there are many users like me who never enqueue suggested videos.

An additional feature for related videos on full screen:
Single tap on thumbnail: Play and enqueue the next video (This feature is only available if 'Auto-queue next stream' is available. However, this will be useful for accessing any video at any time and adding videos to playlist)
Single tap on title bar: Clear previous queue (if exists) and start playing the video.

[desmonk]

That's a well thought out idea to be honest. But why not have buttons too? What if a user is not geared toward using gestures? Many use old UI and even Android has kept it for a reason. Besides that you pretty much nailed it!

[desmonk]

I have question now. Aren't the queued videos actually suggested ones by YouTube as they resonate with it? Buttons are still needed though as with auto queue will continue after each video and also have no option on full screen UI.

I'm not at all against implementation of gestures but if we have to develop a really good app that can cover older phones too, then we better have some options as Android have.

[desmonk]

I see that you manually created a queue. Differences here is turning of YouTube suggested videos breaks down the experience as most users would want some similar videos as this trend of so called recommended things are crucial and carefully designed and calibrated. Not just YouTube but all major apps. Example, Amazon.

My focus right now is having independence from queue completely. The swipe gesture from the bottom is a good one in full screen. But buttons too important as they represent a bold behavior. Meaning they state the obvious. So you have to think beyond queue here. Especially not manual queue as turning off recommended videos is a big let down.

Also, I observe one tiny thing. The video progress bar is so thin to manually drag the slider!

[desmonk]

Aren't similar videos function here take advantage of YouTube recommendations? If not then I have to admit how does this work? As NewPipe can't possibly have that secret sauce that need data scientists level programming to achieve this. And I'm stating a fact not comparison.

Secondly, you're a student. You are using it in a different manner. Most users are not students. And this is not some hypothesis. Entertainment is driving force here not education.

Your suggestion only solved full screen UI with swipe gestures. Again no buttons.

I'm surprised you're actually going in the wrong direction here. You are still not able to see that buttons are core functionality and having them made reliant on queue is never a good idea.

Third, I'm a long time user of this and I'm very well accustomed to the nature of the app. As a user my job is to think in ways that might help others too.

You can see my old issues opened here and understand how far I've gone to make this experience better for all and not just me or you.

[desmonk]

Calm down!

I asked you how are you doing similar and grouped suggestions? You didn't answer. Also, what on earth are you talking about? Data? Privacy? Duh! Why do you think am I here?

Also, you are being arrogant here.

What kind of arguments are these? I asked a question and you're coming back with zero reply. Buttons are a must. Buttons! Don't you get it? Carbon copy of YouTube? What?

Do you even understand what are you talking about? I'm done with your idiotic attitude. You're not in the real world but some dreams.

This must open your eyes. You lack a clear vision.
I'm disappointed to write this as you are entrapped in your own web of mismanagement.

[triallax]

@desmonk why did you close this issue?

[desmonk]

I don't want to keep pushing a button when the system is off the grid.

[desmonk]

All you came up with was swiping up gestures in full screen. This doesn't work on standard UI. Also, when I asked about how you do the grouped/similar videos, as you're opposed to YouTube's recommendation service, you didn't answer oonce and instead started talking about all those aforementioned points as you are too focused only on custom made queues, which is a very specific approach to usage.

YouTube will always primary be about entertainment.
Not gonna get entangled here again as you can read each point again.

[desmonk]

Buttons are static and required to navigate easily. They should remain independent irrespective of anything else. They are simple buttons at the end of the day! This should not be that hard to see. Imagine the buttons only become visible on any device or app if we only allow it play next or previous selection!

[opusforlife2]

Since you're available, open a new issue with the new issue forms.

[desmonk]

No problem I will open this as a feature request now as this is not a bug the default behavior.