Version 1.2.1.1 is out. The new version contains improvements and new features for the Channels page + new settings and features for playback
Again, bunch of thanks to @
guizmox for his advice.
Channels page:
- Improved the performance of the Refresh action, now it should work lot faster
- Added a Feed with the latest videos from each channel. 90 days was just a magic number which came to my mind, there was no objective reason to use this specific number, just FYI
- Added Sorting and Searching
In general, data are retrieved from RSS feeds, so some of the properties are missing, e.g. one can't get a video's duration, determine whether it's a live stream or not, number of views, etc. And don't mix up this search with the one on the Search page. The former is a local search, the latter is the YouTube search (i.e. remote). Besides, it's worth mentioning that feed videos are retrieved on the fly, they are not stored in the app's database, so
the 'Feed' option is disabled after launching the app, you must Refresh at least once to get the data.
Other improvements and features requested by the community:
- Some channels are configured to redirect to another channel, e.g. Ozzy Osbourne. Previously the app was showing the "Channel not found" error while opening such a channel, now it handles redirects properly. @
NaGMeT
- New settings: 'default tab' and 'default video quality' - self-explaining. @
ichengfu
- Increase the height of the list on the Player page showing similar/related videos on Passport. @
ichengfu
- 'Repeat one' option on the Player page. @
TrumpetTiger
I also tried to implement a custom speed for videos and videos did play faster or slower but the audio channel was lost. I got a similar error message as for fast-forwarding Audio streams - UNSUPPORTED. One can also reproduce the same issue even in the Browser. Just open a YT video, try to change the speed and you'll see that the audio channel will be lost. Since BBMo is not going to release an update for codecs and system components for playing media any time soon I'm afraid we'll have to live with those issues. And yeah, I've reverted that broken implementation. @
ichengfu (and, perhaps, @
TrumpetTiger FYI).
Thanks for your feedback!