Jump to content

amorphic8

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by amorphic8

  1. MIDI files not created by the publisher (read: the person who put them on the web or who owns the web site using them) are subject to the same copyrights laws and usage restrictions as 'audio' files.In other words, using MIDI instead of audio files doesn't solve your problem.here's an old article, but no less valid: http://members.accessbee.com/jkwasnik/copyright/copyrt.html
  2. You want it to work? use something other than Windows Media Player.
  3. Let me get this right:you've never done this beforeyou want it to be 'very professional'you want it to be 'faster to download'you want it to work in 'all browsers'you want it to be 'hopefully easy'AND you want it to be cheaper than $300?Let me ask: were you able to do this project without re-evaluating your project goals?
  4. Could it have something to do with all your tags and elements being uppercase? This is currently considered 'bad practice' as it is not valid XML. If your server is case sensitive (read: not Windows) then perhaps this could be the culprit.
  5. "veeeery old browsers" has nothing to do with it. Firefox 1.5 (Mac/Win), Safari 2.0.3 (Mac), IE Mac 5.2, all modern browsers, none work with <object> only; all work fine when using <embed> (or the nested <object>...<embed></embed></object>)Of course, the 'GOTCHA" is code that doesn't validate XHTML strict, but it's better than catering only to IE Windows!!
  6. You would want the opposite, right? Only IE Windows uses the object with classid and codebase parameters. All other browsers use the non-standard <embed>.Using <object> to play movies on any Mac browser doesn't work, unless you give up using all possible control. In other words, plain vanilla QuickTime will play using the <object> properly, but if you want to include the VR controller for a QT VR file, for example, there's no valid way to do it.There is an article here on this site that discusses this matter, but has many inaccuracies. For example, this page http://www.w3schools.com/media/media_quicktime.aspwhen discussing the <embed> element, says it is used in browsers that don't understand <object>. That is simply not true. It is used by browsers that don't need the ActiveX component of the <object> code as it is displayed in the example.And the browser that does display the media, IE for Windows, doesn't properly implement the <object> element in the first place!! The codebase and classid attributes are for ActiveX (used ONLY in IE Windows).What browsers don't need the ActiveX control? Any browser that ISN'T IE Windows...(yes, that means even IE Mac doesn't need this code and will properly use <embed>).The problem is that the <embed> tag isn't valid XHTML; in fact, the w3c never officially recognized <embed>, yet it is RECOMMENDED by Apple for QuickTime, is included in the auto-generated HTML pages to contain Flash, and other media plug-ins recommend it with a series of attributes to use to get at the plug-in's unique capabilities. It is also prescribed for use (nested in the <object>) for QuickTime, RealPlayer, and WindowsMediaPlayer in Steve Mack's "Streaming Media Bible," for QuickTime in "QuickTime for the Web," 3rd Ed., and countless others.While one can argue that the books I just mentioned are both over 2 years old, there still isn't a better solution for ensuring that most browsers in use can render the content properly.Why the w3c has never offcially recognized <embed> has never revealed itself to me, therefore, I consider my pages, and those developed by the team working under me, as valid, just as long as the media performs as intended on the major browsers that we support. This site recommends using <object> only (http://www.w3schools.com/media/media_object.asp), and none of the examples work in any browser I tested that wasn't IE for Windows, except 'Picture as Object." When given the choice, I would rather fail the Valid XHTML Strict test than lose the browsing population using Macs and IE browsers other than the 'least standards compliant champion:' IE Windows.These examples all failed using: Firefox 1.5 (Mac/WinXP), Safari 2.0.3 (Mac only) and IE 5.2 (Mac).I think a much better evaluation of the situation can be found here: http://realdev1.realise.com/rossa/rendertest/quicktime.htmlIf anyone has better information, I would be happy to know about it.--------------------------------------------------------------------------
×
×
  • Create New...