Flowplayer 6.0.4 is the fourth bug-fix release for Flowplayer HTML5 v6.
For this release we have addressed a bunch of scripting and API related issues. As a result Flowplayer HTML5 is even more programmer friendly than before. See the full list of fixes at the bottom of this news item.
This is a free update if you already own a license for version 6.0.0 or newer. You can find it in your account page.
- #944 - poster: add new api property when poster condition is met
- Fix #959 - Flash HLS: ready fired too early
- Fix #958 - generate_cuepoints: seeks to timeline postion, not cuepoint (regression from v5)
- Fix #955 - Prevented seek beyond cuepoint disables cuepoint once
- Fix #943 - shutdown() does not remove instance data-attribute
- Fix #942 - quality selector loses poster state with playlist
- Fix #941 - api undefined in stop callback argument in non-splash setups
- Fix #940 - autoplay: does not go into poster state on stop
- Fix #936 - IE8: no player displayed for splash setups if no height: for container
- Fix #928 - BeforeSeek Event does not working in IE11
- Fix #926 - Do not show context menu when trying to enable flash plugin
- Fix #924 - flash: play(index) and load(clip) load encoded url
- Fix #923 - Controlbar mouse over problem
- Fix #922 - Chrome: Flash object with less than 461px width does not work
- Fix #918 - Native subtitles shown when mixed native and flowplayer subtitles on same page
- Fix #912 - Crossorigin subtitles do not work on iPhone
- Fix #911 - flash hls: seeking beyond end of video causes undefined player state
- Fix #908 - ipad: tooltip appears empty, or is stuck at first position when scrubbing
- Fix #906 - bgcolor: does not override .flowplayer.is-splash background-color
- Fix #904 - flashdisabled message does not make sense when Flash is in fact enabled
- Fix #901 - RTMP: src location w/o prefix considered as HTTP
- Fix #898 - 6.0.3: live option not recognized on clip level with generic HLS
News from the Drive engine room
Video encoding is a fast moving target. In the depths of the Drive engine room we are constantly striving to enhance what's driving the Drive.
- even smoother playback over slow connections while minimizing the quality impact to a minimum using flexible scaling algorithms, tricky video buffer management etc. - as a tester you might not notice it, but your audience will be grateful if they happen to be behind a 2G connection
- hls: reduced transport stream overhead
- hls: even stricter standards compliancy, streams pass the Apple mediastreamvalidator check
- improved PAL and NTSC standard resolution detection
- lots of under the hood improvements
- drop support of legacy iOS below version 4, permitting us to push onwards with features like the hlsjs plugin
Learn more about how the Drive engine ticks.
New User Interface
Tagging and searching
We added tagging and search functions. You can now add tags to categorize your videos and then use them when searching. This functionality is essential if you have a large amount of videos to manage. You can search using keywords and videos with matching titles and filenames are returned, or you can search with tags. Searcing is really fast: it happens instantenously in a few milliseconds.
We created a separate page for managing tags -- this is where you can rename, delete and add new tags. It is a powerful tool to keep your tags organized and under control.
The new tagging and searching functionality is also available in the Drive API.
You can now select the encoding profile when you upload videos. The profile determines how our encoders treat your videos.
- Standard: Video in very good quality in all browsers and on every platform.
- Adaptive: Video in optimal quality adapted automatically to connection speed and browser/device capability (ABR), with a high-quality fallback.
- Premium: Audience may select between video in optimal adaptive quality (ABR) and up to four resolutions of a static quality level.
The Adaptive profile is a completely new option and the new default in all paid plans. With the new Adaptive profile you save around 50% in encoding fees compared to the Premium profile, which was our old default. Also the time it takes to encode your videos is reduced in half.