You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked that there is no other issue about this feature request.
This issue contains only one feature request.
The title of this issue accurately describes the feature request.
Feature description
Using Piped as an alternative for playing music instead of fetching stuff directly from YouTube.
Why do you want this feature?
Google has been making changes on their services that break the functioning of Innertune. Many users are struggling to play music normally. Thankfully developer is trying his best to publish hotfixes. However it takes a long time to update.
RiMusic, another open source YT Music app, has the same playback issues that you can't play user-uploaded videos and several songs uploaded by artists (or YouTube). Enabling Piped frontend has fixed this problem for me. So I thought this option would fix Innertune too.
Additional information
I saw two issues about this feature request but their reasons were different. I thought opening a new issue instead of bumping them would be a better idea.
The text was updated successfully, but these errors were encountered:
Checklist
Feature description
Using Piped as an alternative for playing music instead of fetching stuff directly from YouTube.
Why do you want this feature?
Google has been making changes on their services that break the functioning of Innertune. Many users are struggling to play music normally. Thankfully developer is trying his best to publish hotfixes. However it takes a long time to update.
RiMusic, another open source YT Music app, has the same playback issues that you can't play user-uploaded videos and several songs uploaded by artists (or YouTube). Enabling Piped frontend has fixed this problem for me. So I thought this option would fix Innertune too.
Additional information
I saw two issues about this feature request but their reasons were different. I thought opening a new issue instead of bumping them would be a better idea.
The text was updated successfully, but these errors were encountered: