<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Semi-Blog &#187; Quicktime</title> <atom:link href="http://semiblog.opaquedream.com/tag/quicktime/feed/" rel="self" type="application/rss+xml" /><link>http://semiblog.opaquedream.com</link> <description>By Eric Peacock</description> <lastBuildDate>Sun, 09 Oct 2011 03:45:27 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>The State of Video Playback for Mac OSX Users</title><link>http://semiblog.opaquedream.com/the-state-of-video-playback-for-mac-osx-users/</link> <comments>http://semiblog.opaquedream.com/the-state-of-video-playback-for-mac-osx-users/#comments</comments> <pubDate>Thu, 17 Dec 2009 21:15:59 +0000</pubDate> <dc:creator>Eric Peacock</dc:creator> <category><![CDATA[Commentary]]></category> <category><![CDATA[Technology]]></category> <category><![CDATA[Video]]></category> <category><![CDATA[3ivx]]></category> <category><![CDATA[codec]]></category> <category><![CDATA[Divx]]></category> <category><![CDATA[M2TS]]></category> <category><![CDATA[Mac OS X]]></category> <category><![CDATA[MKV]]></category> <category><![CDATA[open source]]></category> <category><![CDATA[Quicktime]]></category> <guid
isPermaLink="false">http://www.opaquedream.com/semiblog/?p=573</guid> <description><![CDATA[This is a quick little post inspired mostly by the comments to this news item regarding the open source VLC project. I&#8217;m sure I&#8217;ll want to refine and update it later, but right now I felt the need to jot this down. I won&#8217;t get into ripping, transcoding or conversion, this is all about playback. [...]]]></description> <content:encoded><![CDATA[<p>This is a quick little post inspired mostly by the comments to <a
href="http://www.macrumors.com/2009/12/17/videolan-considering-options-for-vlc-as-mac-developers-disappear/">this news item</a> regarding the open source VLC project.</p><p>I&#8217;m sure I&#8217;ll want to refine and update it later, but right now I felt the need to jot this down. I won&#8217;t get into ripping, transcoding or conversion, this is all about playback.</p><p>Based on the <a
href="http://forum.videolan.org/viewtopic.php?f=12&#038;t=59905#p228791">news</a> that the VLC team has had roadblocks from Apple I have only one thing to say: Apple is a corporation that has to abide by contracts and that means DRM (Digital Rights Management). VLC can ignore or remove some DRM restrictions, especially with DVDs, hence it&#8217;s usefulness. To expect Apple to openly support a product that might violate any of the undisclosed contractual obligations they must have with big media corporations is silly. Love it or hate it, that is our system. Plus, the market is still reeling from the boom in digital content delivery and it&#8217;s a mess.</p><p>Next, Apple&#8217;s long-in-the-tooth Quicktime API is finally getting a rebuild starting with Mac OS X 10.6 Snow Leopard. If you asked me I would tell you that it&#8217;s going to be transitional for a while, but this is probably a good thing given the long life that Quicktime has had with an older &#8220;Classic&#8221; Mac OS code base. That means Quicktime APIs are a moving target. That is possibly one reason Apple hasn&#8217;t published a lot of info or willingly assisted an open source project like VLC. There has to be a lot more work to do before that can happen.</p><p>I like and use VLC from time-to-time. If anything I&#8217;d congratulate the team for getting this far while dealing with so many confusing formats and APIs. It&#8217;s a little engine that could, GUI for Mac OS X aside. I hope the news of their current predicament helps rustle up more support.</p><p>In the meantime what can an OS X user who aquires a <a
href="http://en.wikipedia.org/wiki/Matroska">MKV (Matroska Multimedia Container)</a>, M2TS or any other video container do? As of this writing it comes down to these tools:</p><p><a
href="http://www.videolan.org/">VLC</a> &#8211; Well duh. Been a standby for a long time. Worth having around for more than one reason. Much buggier than the other players I&#8217;m about to mention, but still a worthy app.</p><p><a
href="http://perian.org">Perian</a> &#8211; the only one of it&#8217;s kind, a Quicktime Plug-in that adds support for MKV, DivX and a slew of other confusing and convoluted formats. Load it and Quicktime Player 7.x is your bitch for the most part. Note: I don&#8217;t have an Intel Mac, so I can&#8217;t comment on the Snow Leopard compatibility with Quicktime X and Perian, if any. This is the easiest way to start playing a whole boatload of non-Apple native codecs. Includes 5.1 surround sound or DTS passthrough if you have the hardware for that.</p><p><a
href="http://code.google.com/p/movist/">Movist</a> &#8211; nice slick player that is in a league of it&#8217;s own. Runs great and plays everything I&#8217;ve thrown at it.</p><p><a
href="http://mplayerosx.sttz.ch/">MPlayer OSX Extended</a> &#8211; a cleaned up MPlayer derivative that works better than VLC (for me). Some 1080p clips might need some tweaking of the &#8220;frameskip&#8221; pref, but otherwise this is a easy to use way to play most everything. Also includes 5.1 surround sound or DTS passthrough.</p><p><a
href="http://www.plexapp.com/">Plex</a> &#8211; A media center/player that is Intel and OS X 10.5 Leopard only. It&#8217;s designed for keyboard or Apple Remote control and is essentially Front Row on steroids. Slick.</p><p><a
href="http://www.getmiro.com/">Miro</a> &#8211; A media center/player for PPC and Intel Macs that ties into torrent networks. More features and complexity than some might want. Offers lots of subscriptions that foreshadow what TV is going to look like in a few more years.</p><p>If you&#8217;re struggling with playback on OS X these are the better tools to try.</p> ]]></content:encoded> <wfw:commentRss>http://semiblog.opaquedream.com/the-state-of-video-playback-for-mac-osx-users/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Final Cut Studio 2: Quicktime Dependancy Compressor Bug</title><link>http://semiblog.opaquedream.com/final-cut-studio-2-quicktime-dependancy-compressor-bug/</link> <comments>http://semiblog.opaquedream.com/final-cut-studio-2-quicktime-dependancy-compressor-bug/#comments</comments> <pubDate>Sun, 06 Jan 2008 23:59:02 +0000</pubDate> <dc:creator>Eric Peacock</dc:creator> <category><![CDATA[Tip]]></category> <category><![CDATA[Video]]></category> <category><![CDATA[Compressor]]></category> <category><![CDATA[Final Cut Studio]]></category> <category><![CDATA[Quicktime]]></category> <guid
isPermaLink="false">http://www.opaquedream.com/semiblog/2008/01/06/final-cut-studio-2-quicktime-dependancy-compressor-bug/</guid> <description><![CDATA[If you ever use Quicktime clips that use linked dependancy files that are missing you will hang Compressor 3.0.2 when adding these clips to a batch queue. I&#8217;ve not tested this with any other version and I&#8217;m running 10.5.1 Leopard. Compressor droplets also suffer the same problem and will hang as well. The easiest solution [...]]]></description> <content:encoded><![CDATA[<p>If you ever use Quicktime clips that use linked dependancy files that are missing you will hang Compressor 3.0.2 when adding these clips to a batch queue. I&#8217;ve not tested this with any other version and I&#8217;m running 10.5.1 Leopard. Compressor droplets also suffer the same problem and will hang as well.</p><p>The easiest solution is to keep your dependent links up-to-date by opening clips in Quicktime Player and saving them after the lengthy search.</p><p>This reminds me that the code within QT for dealing with referenced media still seems very dated when you think of OS X technologies like Spotlight, etc. Referenced file names are truncated to the Mac OS 9 31 character limit for one thing, so you can&#8217;t even be sure what the full name of the missing link is in some cases.</p><p>Perhaps it&#8217;s best to shy away from using reference clips at all if you think they will move a lot and require re-linking. If Compressor warned you or asked to find the link as Quicktime Player would this would be moot. Hanging Compressor is misleading since it might lead one to think that they have a corrupt installation to fix instead of simply relinking their source clips.</p> ]]></content:encoded> <wfw:commentRss>http://semiblog.opaquedream.com/final-cut-studio-2-quicktime-dependancy-compressor-bug/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching using disk: basic
Object Caching 300/331 objects using disk: basic

Served from: semiblog.opaquedream.com @ 2012-02-06 12:13:51 -->
