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.
Thread beginning with comment 264903
To view parent comment, click here.
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

RE[3]: gnash & flash video...
by mmu_man on Wed 22nd Aug 2007 07:10 in reply to "RE[2]: gnash & flash video..."
mmu_man Member since:

... "content protection" is a moot point. It's bad ethically, doesn't and will never work correctly, only impair fair users' rights but barely stops people who really want to pirate stuff anyway. It's only a carot waved by vendors to make sure ppl use their proprietary solution instead of open and [Ff]ree ones. Notwithstanding the fact that their protection by DMCA/EUCD/... infringe the constitutionnally given freedom of speech of software developpers (software is speech) by forbidding writing breaking apps or forcing us to use them in apps thus forcing apps to be closed source (yes, have a look at DADVSI...), DRM should be banned along with flash.
"noncomplex content protection" ROTFL. As I said it only limits the rights of average joe to exercise fair use, does nothing to the people it should target.

It's also one more way to impair the "free fair competition" ("compétition libre et non faussée" in french), EU's primary official goal, in disfavor of open source solutions, because, until I see a formal proof, open source DRM is by essence impossible, except maybe in sun's DReaM ...

Did I disgress or something ?

Reply Parent Score: 2