Path: csiph.com!goblin2!goblin.stu.neva.ru!newsgate.cuhk.edu.hk!news.netfront.net!.POSTED.157.158.68.60!not-for-mail From: Krzysztof Mitko Newsgroups: comp.sys.mac.system Subject: Re: WWDC 2018 Date: Wed, 6 Jun 2018 08:45:00 -0000 (UTC) Organization: Netfront http://www.netfront.net/ Message-ID: References: Injection-Date: Wed, 6 Jun 2018 08:45:00 -0000 (UTC) Injection-Info: adenine.netfront.net; posting-host="157.158.68.60"; logging-data="16674"; mail-complaints-to="news@netfront.net" User-Agent: slrn/1.0.3 (Darwin) Xref: csiph.com comp.sys.mac.system:117113 On 2018-06-06, JF Mezei wrote: > On 2018-06-06 02:46, Your Name wrote: >> >> "Quicktime Player 7" was replaced by "Quicktime Player X" a while back. > > > > Question still stand: does Quicktime (ciurrently Quicktime X) still rely > on the Quicktime framework to render videos, or did it evolve to > avfoundation as the underlying engine? otool -L /Applications/QuickTime\ Player.app/Contents/MacOS/QuickTime\ Player is your friend. You'll see all the frameworks linked in QT X binary - there is no QuickTime.framework. There is QuickTime.framework if you run the same command on QT 7. > If it is still relying on quicktime as engine, would Apple update the > app or produce a new media player app? -- Chemical engineers do it in packed.