Embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC) may set these third-party cookies and/or use similar technologies to store data in your browser (or other user agent) for purposes such as (without limitation) managing video settings (e.g., tailoring the playback to your connection speed), storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Such cookies and/or stored data items may be set by various domains (such as, though not necessarily limited to, youtube.com; youtube-nocookie.com; googlevideo.com; ytimg.com; google.com; accounts.google.com; www.googleadservices.com; and/or doubleclick.net, which is part of the DoubleClick advertising service, also owned by Google LLC). Not all the listed cookies and/or data items are necessarily set in all instances, and there may sometimes be others not listed above, particularly if you are logged into a Google account. Some persist for only a few minutes, or until you close your browser (or other user agent); others may remain in your browser (or other user agent) as long as your individual settings permit. To learn more about what information the YouTube platform and other Google services may collect through and/or in connection with embedded video players and how Google may use that information, see their "How Google uses information from sites or apps that use our services" page and the Google Privacy Policy. For additional information about how Google uses cookies and/or other technologies that may collect and/or process personal information, see the "Technologies" section of their Google Privacy & Terms site and the "Our advertising and measurement cookies" section of their Google Business Data Responsibility site, which includes a detailed list of cookies associated with Google advertising and measurement products. (Those pages do not currently discuss the storage of data in your browser (or other user agent) using technologies other than cookies, e.g., in web storage.) For more information about Google advertising, see the "Advertising" section of their Google Privacy & Terms site. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)
VISITOR_INFO1_LIVE, VISITOR_INFO1_LIVE__k, VISITOR_INFO1_LIVE__default, YSC, YEC, _Secure-YEC, PREF, GED_PLAYLIST_ACTIVITY, CGIC, DV, CONSENT, SOCS, AEC, exchange_uid, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, remote_sid, test_cookie, use_hitbox, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, Conversion, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE, LOGIN_INFO, Permission, yt.innertube::nextId, yt.innertube::requests, yt-html5-player-modules::subtitlesModuleData::display-settings, yt-html5-player-modules::subtitlesModuleData::module-enabled, ytidb::LAST_RESULT_ENTRY_KEY, yt-player-autonavstate, yt-player-bandaid-host, yt-player-bandwidth, yt-player-headers-readable, yt-player-lv, yt-player-quality, yt-player-volume, yt-remote-cast-available, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, application_server_key, AuthKey, DeviceId, Endpoint, HighPriorityNotificationShowCount, HomePromptCount, HomePromptTime, IDToken, IndexedDBCheck, LogsDatabaseV2, P256dhKey, Permission, PromptTags, RegistrationTimestamp, shell_identifier_key, TimestampLowerBound, yt-serviceworker-metadata
Great to know there will be more articles.
Keep up the good work!
I think that it’s wonderful that your priorities lie with the production of high quality content over high quantity content. Thank you for all of this important historical work that you do for all of us automotive enthusiasts.
Dear Aaron, I would very much appreciate a like history of the Torqueflite and Cruise-O-Matic of the similar volume as the amazing hydramatic articles. In case you did not know, the Russians built a direct copy of the Cruise-O-Matic for their Chaika limousines. I made a very brief edit on the wikipedia article, but have quite a bit of material that I can forward for your analysis and will assist with translation, should that be necessary. Best of Regards!
Alex,
I did talk about the origins of the Simpson gearset used in TorqueFlite and Cruise-O-Matic (inter alia) in an article I did on the Imperial a while back, although I didn’t get into the workings of TorqueFlite in any detail, so that might be TBD.
At present, I’m still neck deep in the revamp of the second part of the Hydra-Matic article (which I hope will be done in the not-too-distant future), so to be perfectly honest I’m not sure I’ll have the fortitude to do another transmission article any time very soon. Part 2 of the Hydra-Matic piece covers 11 different transmissions in several distinct families — plus an explanation of the operating principles of a torque converter that has come close to breaking my brain — so I’ve spent a terrifying amount of time wading through technical manuals and patent literature. This isn’t to say I won’t do similar pieces in the future, since no one has ever accused me of easily learning my lesson, but it might be nice to not be staring at schematics for a while.
If I do cover Ford automatics, I would probably want to start with the earlier Ford-o-Matic series before moving into Cruise-O-Matic. Likewise, for Chrysler, it would make sense to cover PowerFlite and, if I’m really feeling like a glutton for punishment, the earlier semiautomatic transmissions before getting into TorqueFlite. So, either would be a big project. The only potential saving grace is that I would probably understand them better now than I would have this time last year.
I had no idea the Soviets had cloned Cruise-O-Matic. That is fascinating.
Thanks for the suggestion!