Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly

[Phil Housley]

Binary package hint: hal

From lsusb -vv

idVendor 0x0781 SanDisk Corp.
idProduct 0x74d1

The device is an extended version of the Sansa Clip, which I assume is recognised, as 10-usb-music-players.fdi says "Sansa Clip and Fuze versions 1 and 2."

[Jonathan Blackhall (johnny-one-eye)]

My Clip+ product id is 0x74d0, however, even after adding that to the .fdi file, my player is still not detected. Does adding your product id to the .fdi file fix this problem for you?

[Jonathan Blackhall (johnny-one-eye)]

I added Rhythmbox to this bug report since at least the player shows up in nautilus (listed as a regular USB device). However, it is not properly detected in Rhythmbox unless a .is_audio_player file is placed in the root of the device. This is a bug. If you'd like me to create a new bug report for Rhythmbox or if you feel the problem is just with hal and not rhythmbox, let me know.

[Sebastien Bacher (seb128)]

the issue there doesn't seem to be a rhythmbox one, there is also no reason to mix tasks this way

[Jonathan Ernst (jonathan.ernst)]

@Phil Housley
This should work in Maverick as it is now correctly handled by media-player-info.

@Jonathan Blackhall
0x74d0 is the ID of your player in MTP mode (not msc). Your player should work fine in msc mode in Maverick. If you still encounter problems in mtp, please fill a new bug agains libmtp (run "ubuntu-bug libmtp").

[Jonathan Blackhall (johnny-one-eye)]

@Jonathan Ernst
Thanks for following up on this. However, something is still wrong. I just deleted the ".is_audio_player" file from my Sansa Clip+. I ejected and replugged my Sansa, and now Banshee and Rhythmbox no longer detect it as a media player (i.e. an icon doesn't show up so that I can sync music to it). The player is in MSC mode. When I plug the player in, Nautilus recognizes it as a USB drive (actually 2 separate USB drives because my player also has an optional additional uSDHC card). But when I open Rhythmbox or Banshee, I can't access the drive.

I'm using Banshee 1.9.2 and Rhythmbox 0.13.1.
$lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 0781:74d1 SanDisk Corp. Sansa Clip+ (msc)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

On a side note, with the .is_audio_player hack, I was able to get Banshee to sync with my Sansa, but the syncing wasn't perfect (some of my meta data was garbled, truncated, blank, etc). I wonder if something didn't get messed up with Banshee when I upgraded from 10.04? No need to answer this, but if you have any thoughts let me know.

[Jonathan Blackhall (johnny-one-eye)]

@Jonathan Ernst
It looks like: http://cgit.freedesktop.org/media-player-info/tree/media-players/sandisk_sansa-clip-plus.mpi
is different from the contents of
/usr/share/media-player-info/sandisk-sansa_clip_plus.mpi on my updated
Ubuntu 10.10 machine.
The freedesktop site lists:
[Device]
Product=Sansa Clip+
Vendor=SanDisk
AccessProtocol=storage
DeviceMatch=usb:0781:74d1;

My machine's file has:
[Device]
AccessProtocol=storage
DeviceMatch=usb:0781:74d0;
Product=Sansa Clip+
Vendor=SanDisk

Maybe that's the reason it's not detected?

[Jonathan Blackhall (johnny-one-eye)]

I also wonder if there may be 2 device IDs (0781:74d1 and 0781:74d0) for this device, since it appears that the original poster had a different ID than I did.

[Jonathan Ernst (jonathan.ernst)]

Hi Jonathan :-)

0781:74d0 : mtp mode, handled by libmtp
0781:74d1 : msc mode, handled by media-player-info

Your lsusb from Comment #5 shows that you are now using msc mode (you were using mtp in Comment #1). So is the original reporter.

But in Comment #6 you have shown that you have an outdated mpi file (which is normal as it is the one currently in Maverick).

Please update to the version currently in proposed and let me know if it works :

1) https://wiki.ubuntu.com/Testing/EnableProposed
2) sudo apt-get update;sudo apt-get install media-player-info
3) remove proposed repo

[Jonathan Blackhall (johnny-one-eye)]

Yes, that works as expected now, thanks. Will this update be pushed to
Maverick at some point?

[Chris Cowan (macil)]

I'm on Ubuntu 13.10, and my Sansa Clip+ is only detected by rhythmbox if I put a ".is_audio_player" file in its root with "audio_folders=MUSIC/,RECORD/" in it. It was detected perfectly fine automatically in Ubuntu 12.04.

some lsusb output:
Bus 002 Device 011: ID 0781:74d1 SanDisk Corp. Sansa Clip+ (msc)

Content of /usr/share/media-player-info/sandisk_sansa-clip-plus.mpi:
```
[Device]
Product=Sansa Clip+
Vendor=SanDisk
AccessProtocol=storage
DeviceMatch=usb:0781:74d1;usb:0781:74d0;

[Media]
InputFormats=audio/x-wav
OutputFormats=audio/mpeg;audio/x-ms-wma;audio/audible;application/ogg;audio/ogg;audio/flac;audio/x-wav;audio/x-pn-audibleaudio

[Playlist]
Formats=audio/x-mpegurl

[storage]
RequiresEject=true
PlaylistPath=
AudioFolders=MUSIC/;PODCAST/;PODCASTS/;RECORD/FM/;RECORD/VOICE/;AUDIBLE/;AUDIOBOOKS/
```

[Martin Pitt (pitti)]

Chris, can you please run

  udevadm info --export-db > /tmp/udev.txt

while the player is plugged in? Please attach /tmp/udev.txt here.

[Ian Nicholson (imnichol)]

Martin -
I've run the command you requested that Chris run, and the following entry was in udev.txt:

P: /devices/pci0000:00/0000:00:10.1/usb8/8-1
N: bus/usb/008/002
E: BUSNUM=008
E: DEVNAME=/dev/bus/usb/008/002
E: DEVNUM=002
E: DEVPATH=/devices/pci0000:00/0000:00:10.1/usb8/8-1
E: DEVTYPE=usb_device
E: DRIVER=usb
E: ID_BUS=usb
E: ID_MODEL=Clip_Sport
E: ID_MODEL_ENC=Clip\x20Sport
E: ID_MODEL_ID=74e7
E: ID_REVISION=0100
E: ID_SERIAL=SanDisk_Clip_Sport_244093A7D422D948
E: ID_SERIAL_SHORT=244093A7D422D948
E: ID_USB_INTERFACES=:080550:
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk
E: ID_VENDOR_FROM_DATABASE=SanDisk Corp.
E: ID_VENDOR_ID=0781
E: MAJOR=189
E: MINOR=897
E: PRODUCT=781/74e7/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=1617077006

Do you need the rest as well?

[Martin Pitt (pitti)]

> E: ID_MODEL_ID=74e7

That one is indeed now known. Which formats can it handle and which are its playback/record folders? It's very likely that it's identical (or sufficiently similar) to one of the existing Sansa Clip models, check in /usr/share/media-player-info/sandisk_sansa-clip*

[Ian Nicholson (imnichol)]

The following relevant files are in /usr/share/media-player-info/:
sandisk_sansa-clip.mpi
sandisk_sansa-clip-plus.mpi
sandisk_sansa-clip-v2.mpi
sandisk_sansa-clip-zip.mpi

According to http://www.sandisk.com/products/music-video-players/clip-sport/, it supports: MP3, WMA (NO DRM), AAC, Ogg Vorbis, WAV, FLAC, and Audible (DRM only). The playback folder seem to be "/Audible/", "/Audiobooks/", "/Music/", and "/Podcasts/".