add site
services
publishers
database
health videos
toolbar
stats
live show
health store
more stuff
JOIN/LOGIN
| advertise add site services publishers database health videos
| | about toolbar stats live show health store more stuff JOIN/LOGIN |
Huggins Protocol | Dental Protocols | Protocol For Amalgam Removal and biologicaldent.com | PROTOCOL FOR THREE SEPARATE VED?S WITH SMALL MEDIUM AND LARGE CYLINDERS, peyroniesforum.net | Fat Transfer NYC, Fat Transfer Manhattan, Fat Transfer New York City marczimblermd.com |
The Media Transfer Protocol is a devised set of custom extensions to the Picture Transfer Protocol (PTP).[1] Whereas PTP was designed for downloading photographs from digital cameras, Media Transfer Protocol supports the transfer of music files on digital audio players and media files on portable media players, as well as personal information on personal digital assistants. Media Transfer Protocol (commonly referred to as MTP) is part of the "Windows Media" framework and thus closely related to Windows Media Player. Windows Vista has built-in support for MTP. Support for Media Transfer Protocol in Windows XP requires the installation of Windows Media Player 10 or higher.[2] Mac and Linux systems have software packages to support it. The USB Implementers Forum device working group standardized MTP as a fully fledged Universal Serial Bus (USB) device class in May 2008.[3] MTP is since then, an official extension to PTP and shares the same class code.[4]
[edit] OverviewThe main purpose of this protocol is to facilitate the transfer of media files and associated metadata to/from devices, the management of media files and configuration data on these devices, and to allow the remote control of these devices.[5] The protocol was originally implemented for use across USB but extended for use across TCP/IP and Bluetooth. Windows Vista supports MTP over TCP/IP. Windows 7 and Windows Vista with the Platform Update for Windows Vista also support MTP over Bluetooth.[6] The host connecting to an MTP device is called an MTP Initiator whereas the device itself is an MTP Responder.[5] A main reason for using MTP rather than for example the USB mass storage device class (MSC) is that the latter operates at the granularity of a mass storage device block (usually in practice, a FAT block), rather than at the logical file level. In other words, the USB mass storage class is designed to give a host computer undifferentiated access to bulk mass storage, such as compact flash, rather than to a file system, which might be safely shared with the target device (except for specific files which the host might be modifying/accessing). In practice, therefore, when a USB host computer has mounted an MSC partition, it assumes absolute control of the storage, which then may not be safely modified by the device without risk of data corruption until the host computer has severed the connection. MTP and PTP specifically overcome this issue by making the unit of managed storage a local file rather than an entire (possibly very large) unit of mass storage at the block level. Additionally, the MTP allows MTP Initiators to identify the specific capabilities of device(s) with respect to file formats and functionality. In particular, MTP Initiators may have to provide passwords and other information to unlock files, or otherwise enable restricted capabilities. Nothing specific of this nature is in the core standard but the possibility is allowed via Vendor extensions. MTPZ, the Zune Extension to MTP specifically denies access to files until authentication has been processed, which is only capable using Windows Media Player 10 or higher. [edit] AdvantagesMTP can be seen as using a variable storage block size as it stores media files of varying sizes, usually in the megabyte range. Standard filesystems like FAT-32 have fixed file blocks, the media file taking up sufficient blocks for storage, with the leftover space going unused. In a collection of thousands of files, this can add up to a considerable amount of wasted space.[citation needed] [edit] DrawbacksBy design, MTP devices (like PTP devices) are not treated as a traditional removable drive. The actual file system is implemented by the device, not by the computer's operating system. In theory the operating system may hide this difference, but this is not the case on Windows or Mac OS. This also means that conventional file system recovery tools will be of no use if the drive is corrupted, or crashes. Neither the MTP nor the PTP standards allow for direct modification of objects. Instead, modified objects must be reuploaded in their entirety, which can take a long time for large objects. With PTP/MTP, the file size must be known at the opening stage.[5] [edit] Windows MTP supportOn Microsoft Windows, MTP is supported in Microsoft Windows XP if Windows Media Player 10 or later versions are installed. Windows Vista has MTP built-in. Most MTP-compatible devices do not appear through drive letter assignment in Windows Explorer, instead they will appear as "devices" in Windows Explorer. Additionally, on Windows, MTP-compatible devices support a feature called AutoSync, which lets users configure Windows Media Player to automatically transfer all newly acquired or ripped content to devices whenever they are connected. AutoSync is customizable so that the player will transfer only content that meets certain criteria (songs rated four stars or higher, for instance). Changes made to file properties (such as a user rating) on a device can be propagated back to the computer when the device is reconnected. Windows 7's sensor platform supports sensors built into MTP-compatible devices.[citation needed] [edit] Support for legacy Windows versionsFor downlevel operating systems, specifically, Windows 2000, Windows 98 and Windows Me, Microsoft has released the MTP Porting Kit.[7] which contains a MTP device driver for these legacy Windows operating systems. Some manufacturers, such as Creative Technology, also provide legacy MTP drivers for some of their players; these usually consist of MTP Porting Kit files with a customized INF file describing their specific players.[citation needed] [edit] Market acceptanceMicrosoft's partners, including Creative Technology, Intel, iriver and Samsung, who manufactured devices based on Microsoft's "Portable Media Center specification", popularized this protocol. These devices were lined up at the 2004 Consumer Electronics Show. After an initial period of uncertain reactions, several large media player producers such as Creative Technology and iriver have opted to embrace the MTP protocol and drop their own custom device protocols. The general perception is that these companies are happy that they no longer have to develop their own protocols and device drivers for their products. The current device makers and device lines supporting MTP are:
Note: [edit] PlaysForSureThe Microsoft certification mark PlaysForSure was commonly used to distinguish devices that support MTP or USB mass storage device class (MSC), or both, and Windows Media Audio. However, only MTP devices received the PlaysForSure "Subscription" mark, which denoted support for Janus DRM. The PlaysForSure program has been terminated and replaced by a Certified for Windows Vista[8] program instead. [edit] ImplementationsMTP Basic has been proposed for standardization and shall become available on multiple platforms.
[edit] See also[edit] References
[edit] External links |
| ↑ top of page ↑ | about thumbshots |
