7 Responses

1. libeco says:

   September 19, 2009 at 5:20 am

   I couldn’t agree more!

   Reply
2. Giacomo Ratta [ITA] says:

   September 19, 2009 at 11:14 am

   Ah ah ah… I expected a very long article!
   Very funny!
   However I agree.
   I also think this is all about embedded sound in web pages.

   Reply
3. eduardo says:

   September 30, 2009 at 9:05 pm

   So we should stop audiocasting and videocasting? I don’ t think so.

   Reply
4. Impressive Webs says:

   September 30, 2009 at 9:15 pm

   @TC:

   There are exceptions to every rule. Those types of “embedding” you mentioned are under the control of the user, which is fine in most cases.

   Reply
5. NashvilEric says:

   October 22, 2009 at 11:21 am

   What about musician websites?

   As a live music lover, I go to a musician’s website for one thing: to hear what they sound like. I want it to play right away, and I want it to work.

   It infuriates me to go to a musican’s formal, official, ‘designed’ website and have an impossible time digging to the music section, selecting a track, finding out I don’t have the right codec, etc.

   Then I find the same musician on a ghetto myspace page and can actually hear what they play. And it plays immediately. Without. any. hassle.

   I was really hoping this article had some best practices for including audio across various user agents. Hell, I even bookmarked it before I started reading.

   What I wasn’t looking for was someone sharing their opinion with no explanation or caveat.

   Reply
6. Steven says:

   January 11, 2010 at 12:05 pm

   Impressive Webs not too impressive with this post.

   Reply
7. Simon Goellner says:

   March 10, 2010 at 7:12 am

   I would have to disagree.
   and here’s the reason: http://bit.ly/cCACCe
   (turn sound on)…

   I think for the majority of the web though, we should have the choice to hear sounds, not be forced to hear them.

   Reply