-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Release 0.19.6 #3862
Comments
I found something involving importing settings. On a fresh installation (or after clearing all app data), the "What's New" page loads content from the "Trending" page instead of content from "What's New" after importing settings. Steps to reproduce
Expected behaviorThe "What's New" tab should display content from subscribed channels, regardless of the freshness of imported data. Actual behaviorThe "What's New" tab displays content from the "Trending" tab when settings are imported for the first time. |
@snappyapple632 I know this issue is not specific to this release but I can't find the issue. Edit: #3312 |
So it's been around for months? I hope we could get it fixed sometime later. |
What about the HLS/DASH videos bug fix? 🥺 |
@opusforlife2 @ondernuray you are pointing out important issues/prs, but those need to be reviewed thoroughly before merge and unfortunately this release was already postponed too much. Hopefully they will be in 0.20.0 :-D |
I'm aware it is unfinished, but the release cycle is a bit too slow currently, plus 0.20 is home to the gigantic unified player PR, not to mention tabs support, Bandcamp addition, notifications and so on... I don't see 0.20 being released any time before mid September, unless some PRs are postponed further. So I hope you'll release a hot fix just after the DASH/HLS PR is finished being reviewed and tested. A large class of YouTube videos face this issue, as you know. |
@opusforlife2 We might want to ship a small update for that fix. I suggest to release 0.19.6 tomorrow unless new bugs are reported. |
@TobiGr Thanks! That would be wonderful. Also, a small observation: I've noticed in the 0.19 release series, especially, that old PRs tend to get sidelined by new PRs if they are small or medium sized features or bug fixes, which leads to postponement in the milestones. I'm no developer, but if a PR doesn't bring a high priority bug fix, wouldn't it be better to put it in a future milestone so that the PRs in the current milestone can be worked on consistently? It would free up PR authors to work on new things. Of course, if the PR author isn't available for the release cycle in question, it makes sense to postpone the PR to the next milestone. |
Fixed translations in second RC NewPipe_v0.19.6_RC2.apk.zip |
@opusforlife2: I personally don't think it's a good idea to do that until after #2907 has been merged, plus I'm not happy with the current implementation of that DASH "bug fix". I might do my own attempt soon on at least the NewPipeExtractor side though.
I'll probably postpone tabs support to a later release. I also don't think Bandcamp support and proper Android media notifications would delay that release by much. |
@wb9688 I completely understand the intention to merge the best possible code. But this is code that exists and works now. It has worked for me perfectly so far and I use that debug apk whenever possible. Would it not suffice to use this code for now and improve the implementation in a later PR, whenever you find the time to work on it? You also have a lot of other PRs pending. It's not like this is a corporate project where once something "just works" it will bit rot for years until resources need to be diverted to it again. You could take it up in the very next release cycle. The reason I'm so vocal about this particular problem is that it gives the impression to newcomers and laypersons that Newpipe is still very buggy. It's important to get rid of that misconception ASAP. The other solution would be to temporarily have mp4 360p resolution selected by default, which is, again, not ideal at all. Why ASAP? Because unlike many other FOSS apps which require explanations, comparisons and general convincing, Newpipe is an INSTANT WIN against the official app. You could meet someone in a shopping mall, have a five minute conversation about whatever, mention Newpipe (Download! Background playback! No ads!) and they readily agree to install it. But this bug, pretty quickly encountered, destroys all of that serendipity. |
@opusforlife2: I totally agree it's important, but some parts of that PR are unacceptable to me and it's better to do it right the first time, plus the NewPipe side doesn't support downloading for those streams. It's also just a waste of time to change anything about the NewPipe player until #2907 gets merged. I personally think v0.20.0 should be released as soon as #2907, #3178, #3777, and a proper fix for DASH gets merged, all other PRs would be a nice addition but not worth delaying v0.20.0 imho. #3178 and #3777 are necessary for proper Android 11 support. |
That gives me hope. I wish the rest of the team agrees with you. |
Did something change with respect to Soundcloud JSON response in 0.19.6? I'm getting a "Could not parse JSON response" error with a 0.19.5 apk, but 0.19.6 works fine. |
Changelog
App
New
Improved
Fixed
Development
Extractor
New
Improved
start=
timestamps Support start= timestamps for YouTube NewPipeExtractor#366Fixed
Development
APK for testing
NewPipe_v0.19.6_RC2.apk.zip
The text was updated successfully, but these errors were encountered: