XPost: misc.phone.mobile.iphone, rec.photo.digital
From: winstonmvp@gmail.com
On 2/21/2026 9:27 AM, Maria Sophia wrote:
> Frank Slootweg wrote:
>>> iTunes(no Quicktime)
>>> Why does it work? I know
>>> Maybe the op can figure out(why), too!
>> Those are indeed the defaults.
>
> Thanks Winston & Frank for reporting what your observations are, so that
> everyone on the team (Windows, iOS and digital photos group) benefits.
>
> For the sake of those who don't know, iTunes is an Apple product.
> It's not natively installed on Windows. The user usually installs it.
>
> Once iTunes is installed, the system is no longer "indeed the defaults".
> a. Apple iTunes is not "just a music player."
> b. Apple iTunes installs a huge Apple media subsystem on Windows.
>
> Hence, it's impossible for anyone to say with certainty that the "defaults"
> are what the settings happen to be at any given moment *after* iTunes has
> been installed, for example, even without QuickTime, iTunes installs a
> large
> portion of Apple's media framework on Windows such as ... a. Apple
> Application Support (32-bit, 64-bit)
> i. CoreFoundation.dll
> ii. CoreGraphics.dll
> iii. CoreMedia.dll
> iv. CoreAudioToolbox.dll
> v. ImageIO.dll
> vi. Apple-specific proprietary MOV/MP4 parsing libraries
> b. Apple Mobile Device Support
> i. Libraries for reading iPhone/iPad media bundles
> ii. Components for handling Live Photos and HEIF/HEVC assets
> iii. Apple File Conduit (AFC) services
> c. Apple QuickTime compatibility shims
> i. Not the old QuickTime player
> ii. But compatibility layers that mimic parts of the old API
> iii. These can change how Windows selects decoders
> d. Apple HEIF/HEVC support modules (varies by iTunes version)
> i. HEIF parsing libraries
> ii. HEVC decoding helpers
> iii. Sidecar metadata handlers
> e. Apple Photo Stream and iCloud hooks (optional)
> i. Additional media handlers
> ii. Additional codecs for HEIC/HEVC
> And probably a few things that I omitted in this quick response.
>
> In short: iTunes is effectively a codec pack. It installs Apple's media
> stack, which can change how Windows and DirectShow handle MOV files,
> Live Photos, and HEVC/H.264 content.
Clueless, again.
Installing iTunes does not change Windows and Direct Show handling of
MOV and Live Photo files. Nor does it's presence enable Windows or
Irfanview to play MOV and Live Photo files.
>
> This means Winston's test environment was not a "clean" Windows install.
> It was a Windows system with Apple's media framework already present,
> which might explain why his IrfanView behaved differently from mine did.
Incorrect again. The presence of iTunes installation does not impact how
Irfanview behaves on my, your or anyone's device with respect to Windows
and Irfaniew default and untampered settings. Nor would the results
change if iTunes was not installed(Win10/11 untampered by the end user
and Irfanview with its default video settings will play MOV and Live
Photo files 'and' without the need to install a 3rd party codec.)
Maybe you'll figure out it out eventually, but until then you're just
grasping for straws on how Windows and Irfanview plays MOV and Live
Photo files(without a need for additional codecs.
>
> But I do wish to momentarily point out Winston's theatrical performance was
> duly noted, so I simply refer to his comments as... well... unhelpful.
> Winston's unhelpful theatrical performance that he knows the "secret" and
> that I don't notwithstanding, I'm not trying to "win" silly games here.
As noted above, the reason(someone with your claimed experience and
troubleshooting should be capable of understanding) why an untampered
Windows 10/11 install with or without iTunes presence and Irfanview 4.72
or 4.73(latest release) default install settings works/plays MOV and
Live Photo files.
--
...w¡ñ§±¤ñ
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
