Q: I Have a device that is supposed to be MTP based but does not work with libmtp, what do I do next?
A: First be sure to read our New Device? page. If that doesn't work, join the discussion list and tell us your story.
Q: How does libmtp differ from libgphoto2?
A: libgphoto2 is very file-listing oriented, everything is a file (the unix way). It abstracts away details of the underlying protocol this way and represent any camera device (MTP devices are regared "cameras" in libgphoto2) this way. libmtp is closer to the actual protocol and does not provide the same abstraction, instead it relies on numeric identifiers for "objects" on the device, 32bit numbers that are unique for each object/file. This has the side effect that libmtp can handle two files with an identical path (folder+filename) whereas libgphoto2 will be confused by this.
We hope that all of this will be fixed in libgphoto2 so we can obsolete libmtp some day. BTW: this is not nagging, we work closely with the libgphoto2 guys and love what they do.
Q: Doesn't Microsoft hate your guts?
A: No. On the contrary we have heard some positive things from Redmond through the grapevine. (MS guys, please join our mailinglist and say hello.) They are working with the USB Implementors Forum to standardize MTP and when that spec is released we will hopefully be the first conforming implementation outside of Redmond, or something like that. (Alas, their business problem is with Apple and the iMusic stuff, not with us.)
Q: Any manufacturers helping you guys out?
A: Not really, with the exception of Microsoft who gave us a Zune through a proxy. Creative has been positive though. If you work for a MTP device producer, please help.
Q: A device is missing on your compatability chart / You're missing a downstream application that uses libmtp
A: There's more information out there then we can possible find ourselves. If you see something out of date, or find something that should be added to the page, please contact our content manager who will figure out what to do next.
