<div class="gmail_quote">On Mon, Jun 15, 2009 at 12:49 AM, Michael Dale <span dir="ltr"><<a href="mailto:dale@ucsc.edu">dale@ucsc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have requested that a few times as well... Some went so far to even make a mock up page: <a href="http://people.xiph.org/~j/apple/preview/" target="_blank">http://people.xiph.org/~j/apple/preview/</a><br>
<br>
It would or course be much more ideal if we could get the component into quicktime codec lookup system. Is there any criteria or process that has been made publicly available? Are there any guidelines or special request mechanisms that we have missed? Eric or anyone at apple reading this list: if you have _any_ information as to how a codec component gets into the quicktime codec lookup system; it would be great if you could inform us.<br>
<font color="#888888">
<br>
--Michael Dale</font><div><div></div><div class="h5"><br>
<br>
<br>
Silvia Pfeiffer wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm sorry, but there is quite a bit of frustration from the past<br>
hidden in my paragraph. For the last 4 years we have been trying to<br>
get XiphQT added to the list of QuickTime components on Apple's<br>
external components webpage at<br>
<a href="http://www.apple.com/quicktime/resources/components.html" target="_blank">http://www.apple.com/quicktime/resources/components.html</a> . We have<br>
seen proprietary codecs added one after the other but Xiph codecs<br>
continuously being ignored even though we requested addition multiple<br>
times and through different people. I'm sorry to say but that has<br>
indeed caused a feeling of being rejected on purpose. We would love to<br>
see this situation rectified.<br>
<br>
Regards,<br>
Silvia.<br>
<br>
On Mon, Jun 15, 2009 at 2:48 AM, Eric Carlson<<a href="mailto:eric.carlson@apple.com" target="_blank">eric.carlson@apple.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Silvia -<br>
<br>
On Jun 13, 2009, at 7:02 PM, Silvia Pfeiffer wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As for Safari and any other software on the Mac that is using the<br>
QuickTime framework, there is XiphQT to provide support. It's a<br>
QuickTime component and therefore no different to installing a Flash<br>
plugin, thus you can also count Safari as a browser that has support<br>
for Ogg Theora/Vorbis, even if I'm sure people from Apple would not<br>
like to see it this way.<br>
<br>
<br>
</blockquote>
Speaking of misinformation and hyperbole, what makes you say "people from<br>
Apple" want to hide the fact that Safari supports third party QuickTime<br>
codecs? We *could* have limited WebKit to only support QuickTime's built-in<br>
formats, but did not specifically so customers can add other formats as they<br>
choose.<br>
<br>
We have never tried to hide this, it is ridiculous to imply otherwise.<br>
<br>
eric<br>
<br>
<br>
</blockquote></blockquote>
<br>
</div></div></blockquote></div><br><div>I don't even think QuickTime has a codec lookup system. For codecs that are unavailable, it just points me to the page, even if the codec doesn't exist on that page. I remember that either QuickTime 4 or 5 had a codec lookup and download system... Not sure about QuickTime 6. Definitely not QuickTime 7. Maybe QuickTime X will have one again?</div>