Tag: buffer

  • Apple patent allows potential automatic skipping of commercials for radio, television devices

    applelogo_silver

    This could be interesting.

    Per the United States Patent and Trademark Office, Apple on Tuesday was granted a patent that allows users to skip unwanted audio and video broadcast segments such as commercials with on-device content like songs, podcasts or other media, possibly hinting at technology headed to the battle for the living room.

    Apple’s aptly titled U.S. Patent No. 8,249,497 for “Seamless switching between radio and local media” describes a system in which a mobile device will automatically switch between broadcast content and stored media to offer the user a type of customized content consumption experience.

    With the new patent, a device will allow a user listening to content from a radio station or “non-radio media or content sources” to skip past the sections they aren’t interested in, filling the gap with on-board media instead. Also of interest is that commercials are among the types of content which can be replaced by stored media.

    Covered under the invention’s umbrella are broadcasts from a “radio stream provided over any communications network,” while the stored media can include content saved in a device’s memory or from a streaming host device.

    From the patent background:
    “A user, however, may not be interested in every media item provided as part of a broadcast stream. For example, a user may not like a particular song broadcast by a radio station, or may not like a particular segment of a talk radio station (e.g., the user does not like the topic or guest of the segment). As another example, a user may not be interested in content originally generated by sources other than the media source (e.g., advertisement content). Because the user has no control over the media broadcast, the user can typically only tune to a different media broadcast, or listen to or consume the broadcast content that is not of interest.”

    By using metadata from assets like Radio Data System (RDS) data, broadcast listings or published third-party schedules, a device can “determine when an upcoming broadcast segment or media item is not of interest to the user.” When such an event is detected, the device will seamlessly switch to stored media until the unwanted content is completed. Also included as methods of discerning what a user may or may not want to consume are analysis of audio or video from the source, akin to current iOS apps Shazam or IntoNow.

    As far as calculating what a user likes or dislikes, the patent employs comparisons of media items to generate a preference profile, much like the system in place with apps like Pandora. For example, a user can “like” or “dislike” a song and the corresponding metadata will then be included in their preference profile. In another embodiment, the device can keep track of a user’s content consumption habits and make guesses as to what they would like in their preference profile. The metadata can be specific media items, such as artists, songs and genres, as well as specific types of media.

    After the system identifies that an upcoming segment is outside of the preference profile’s parameters, the device can look for an appropriate replacement from stored media to play instead. The patent notes that a “relevance algorithm” can be used to keep the stored media in line with content from the broadcast stream. To keep the experience consistent, the device can either monitor the broadcast stream to choose an opportune time to switch away from stored media playback, or buffer the broadcast stream for later consumption.

    Seemingly, Apple is proposing a way to not only transform radio listening, but also television broadcasts. While not specifically noted in the patent and mentioned here only for purposes of discussion, the system could be tweaked for cable which would lend itself nicely to the set-top box Apple is rumored to be shopping around to U.S. providers. Insiders say the cloud-based device is meant to blur the line between live and on-demand television.

    Stay tuned for additional details as they become available.

  • Google Chrome updated to 19.0.1084.52

    google-chrome-logo

    Sorry for the lack of updates yesterday, I was flying across the country and the plane lacked Wi-Fi. During the flight, “The Vow” with Channing Tatum and Rachel McAdams happened to be the in-flight movie, should you choose to plug in headphones and listen to it. During this time, I desperately wanted there to be a director’s cut where the characters are slathered in salmon juice and attacked by irate grizzly bears in every scene…

    Google Chrome, Google’s new web browser, just reached version 19.0.1084.52 for the Mac. The new version, a 38.6 megabyte download, offers the following changes:

    – [117409] High CVE-2011-3103: Crashes in v8 garbage collection. Credit to the Chromium development community (Brett Wilson).

    – [118018] Medium CVE-2011-3104: Out-of-bounds read in Skia. Credit to Google Chrome Security Team (Inferno).

    – [$1000] [120912] High CVE-2011-3105: Use-after-free in first-letter handling. Credit to miaubiz.

    – [122654] Critical CVE-2011-3106: Browser memory corruption with websockets over SSL. Credit to the Chromium development community (Dharani Govindan).

    – [124625] High CVE-2011-3107: Crashes in the plug-in JavaScript bindings. Credit to the Chromium development community (Dharani Govindan).

    – [$1337] [125159] Critical CVE-2011-3108: Use-after-free in browser cache. Credit to “efbiaiinzinz”.

    – [Linux only] [$1000] [126296] High CVE-2011-3109: Bad cast in GTK UI. Credit to Micha Bartholomé.

    – [126337] [126343] [126378] [127349] [127819] [127868] High CVE-2011-3110: Out of bounds writes in PDF. Credit to Mateusz Jurczyk of the Google Security Team, with contributions by Gynvael Coldwind of the Google Security Team.

    – [$500] [126414] Medium CVE-2011-3111: Invalid read in v8. Credit to Christian Holler.

    – [127331] High CVE-2011-3112: Use-after-free with invalid encrypted PDF. Credit to Mateusz Jurczyk of the Google Security Team, with contributions by Gynvael Coldwind of the Google Security Team.

    – [127883] High CVE-2011-3113: Invalid cast with colorspace handling in PDF. Credit to Mateusz Jurczyk of the Google Security Team, with contributions by Gynvael Coldwind of the Google Security Team.

    – [128014] High CVE-2011-3114: Buffer overflows with PDF functions. Credit to Google Chrome Security Team (scarybeasts).

    – [$1000] [128018] High CVE-2011-3115: Type corruption in v8. Credit to Christian Holler.

    Google Chrome 19.0.1084.52 requires an Intel-based Mac running Mac OS X 10.5 or later to install and run.

    If you’ve tried the new version and have any feedback to offer, please let us know in the comments.

  • Flip4Mac updated to 2.4.1.4

    flip4mac.jpg

    Early Wednesday, software developer Telestream has released version 2.4.1.4 of Flip4Mac, its QuickTime components package which allows for Windows Media files to be viewed, imported and converted under Mac OS X. The new release, a 24 megabyte download, includes the following fixes and changes:

    – Added a progress indicator while waiting for streams to buffer in web browsers.

    – Fixes an export scaling issue that causes video quality issues with source frame sizes not divisible by four.

    – Fixes a problem exporting Silverlight templates.

    – Fixes numerous problems in the Web browser plug-in that prevented streaming and playback of various sites and other problems with clicking and scrolling while in the plug-in.

    – Adds support for Windows Media scripting. Note that scripting only works with Web browsers running in 32-bit mode. You may need to select “Open in 32-bit mode” in Finder’s Info pane for Safari or Firefox for scripting to work.

    – Fixes a warning dialog issue with DRM protected content.

    Flip4Mac 2.4.1.4 is available for free but can go as high as US$179 depending on the version purchased. The new version requires Mac OS X 10.5 or later to install and run.

    If you’ve tried the new version and have any feedback to offer, please let us know in the comments.