Linked by Thom Holwerda on Tue 21st Aug 2007 06:08 UTC, submitted by Kaj de Vos
Syllable, AtheOS Kelly Wilson ported the Gnash Flash player clone to Syllable [screenshot], enabling the playing of Adobe Flash content. It uses the Boost C++ libraries, the SDL and Anti-Grain Geometry libraries for graphics rendering and FFMPEG for multimedia decoding. Work on the player is continuing to add the FreeType library and make the player native to Syllable, so it can be integrated in the web browser. Also, on some Adobe Flash news, an upcoming update will be supporting native h.264 videos, HE-AAC audio support, as well as hardware accelerated, multi-core enhanced full screen video playback.
Permalink for comment 264903
To read all comments associated with this story, please click here.
RE[2]: gnash & flash video...
by snozzberry on Tue 21st Aug 2007 23:24 UTC in reply to "RE: gnash & flash video..."
Member since:

If the coding was referred to as HMML (HyperMedia), I'd be inclined to agree with you.

Unfortunately it's HTML, and the point of XHTML was to reinforce the point that HTML is a document language, not an interactive multimedia engine. The entire point of deprecating all rectangular nontextual elements (even IMAGE) in favor of OBJECT was to keep HTML from being needlessly corrupted by technology-based elements whose purpose and definitions were likely to be corporately controlled and highly mutable over time.

The consequences of this austerity measure are as follows:
1. The W3C is not in the position of mandating minimum codec requirements as the situation is not directly comparable to mandating alpha-enabled PNG support.
2. Content providers recognize that codecs tether users to players, providers to expensive server software, and OSS solutions like OGG offer no content protection which like it or not is a dealbreaker.
3. Macromedia provided a platform-neutral VM with its own server technology, affordable authoring tools, and noncomplex content protection (albeit crackable).

I work in this field for a university. I'd prefer everyone stuck with Real, myself, but Macromedia's solution was the least painful for end users, and they drive standards adoption as much as we try to push it.

Reply Parent Score: 1