[ask] How to be sure that's really safe to remove the sansa fuze from the computer without wmp

@black_rectangle wrote:
But seriously, folks, the whole point of a protocol with a lot of automated choices, like MTP, is to make the process idiot proof. Not to cause more problems if someone thinks that the combined genius of Microsoft and SanDisk gave them something plug-and-play–and has it wipe out their music collection on Auto-Sync instead.

Well, MTP can be used with other programs besides WMP. When I had my Creative player ( which was MTP-only ) I used it with MediaMonkey and had no problems with it. But I also knew enough from earlier experiences with WMP to go in and disable all the auto-functions first, before I plugged in the player. 

Now that ( below ) is funny!:wink:

@fuze_owner_gb wrote:

Fact remains…99% of all consumers are idots.  No need to discourage a protocol just because they are too ignorant to understand it.

@black_rectangle wrote:
But seriously, folks, the whole point of a protocol with a lot of automated choices, like MTP, is to make the process idiot proof. Not to cause more problems if someone thinks that the combined genius of Microsoft and SanDisk gave them something plug-and-play–and has it wipe out their music collection on Auto-Sync instead.

You are blaming the protocol, when the real issue is the software using the protocol.  The protocol didn’t create the problems you listed – the software utilizing MTP did.

…and the protocol is meant to use that software…and Auto-Detect goes to MTP automatically if WMP is detected…which lets WMP screw things up with Auto-Sync…so you’ll have to pardon me if I don’t feel too much sympathy for poor misunderstood MTP. 

If I get into a car and it doesn’t have any brakes unless I make an effort to switch it to manual braking, and I find this out on a sharp curve with a tree in front of me…I don’t really care who’s to blame. 

@black_rectangle wrote:

…and the protocol is meant to use that software…and Auto-Detect goes to MTP automatically if WMP is detected…which lets WMP screw things up with Auto-Sync…so you’ll have to pardon me if I don’t feel too much sympathy for poor misunderstood MTP. 

 

If I get into a car and it doesn’t have any brakes unless I make an effort to switch it to manual braking, and I find this out on a sharp curve with a tree in front of me…I don’t really care who’s to blame. 

I couldn’t disagree more on every point.  I’ve never ever had an issue with MTP on any player, and I don’t really feel too much sympathy for anybody who does…because it is almost always due to operator error.

Default and Auto-Detect settings are supposed to lessen the possibility of operator error, to make devices “just work” with plug-and-play. 

Making default settings that need to be changed before the thing works optimally isn’t “operator error”–it’s bad software design.

If MTP is so impeccable, why, pray tell, does it change certain folder names when they are simply dragged and dropped, as in a recent post? How is that “operator error”?  

@black_rectangle wrote:

Default and Auto-Detect settings are supposed to lessen the possibility of operator error, to make devices “just work” with plug-and-play. 

 

Making default settings that need to be changed before the thing works optimally isn’t “operator error”–it’s bad software design.

 

If MTP is so impeccable, why, pray tell, does it change certain folder names when they are simply dragged and dropped, as in a recent post? How is that “operator error”?  

 

 

I don’t give a flying flip if every person on this forum switches to MSC, it’s of little concern to me.  I just get a kick to see how every problem known to mankind gets blamed to MTP.  MTP is simply the “fall guy”.  I’ve never seen it do things as people claim, as changing folder names.

But, alas…I’m not here to solve the world’s problems.

In fact, I don’t know why I’m even here…I don’t even use Sandisk products anymore!!:smileyvery-happy:

Mmmmm, mediamonkey can only see one type of file at a time, mtp or msc, so If I wanna manage both types of music files, I must insert and reinsert, while changing usb mode to mtp or msc, this is irritating, and unpractical, is there a more simplier way to manage both types at a time ?                                                                                                                                                                                                                                                                                                                                                                           Thanks

The simple practical way is to use one mode. Your computer can’t see both.

@Black-Rectangle, -----> “The simple practical way is to use one mode. Your computer can’t see both”, but we have 2 different storages, the internal and external msd card, the internal use mtp while the external msd card use msc, so we must choose only one storage ?

@paleskin wrote:
@black_rectangle, -----> “The simple practical way is to use one mode. Your computer can’t see both”, but we have 2 different storages, the internal and external msd card, the internal use mtp while the external msd card use msc, so we must choose only one storage ?

While in MTP, both internal and µSD sotareges are seen by the computer as a single virtual storage. (humm, and what happens when you remove the µSD from the fuze, then?)

But in  MSC, you see  the fuze’s internal memory and the µSD as separate drives (which they are, of course). You have to choose between MTP (and wondering which files will die if you remove the µSD, until you do, and the files on the µSd will only be usable in that single fuze, not even in another fuze) or MSC, so you can control which files are in what drive, and you will be able to see the µSD files put that way in any other SD-enabled device. If you listen to DRM’ed files, you will have to stick to the allmighty fantabulous MTP.

And my personal taste: I don’t like things which do not work  well in the operating systems I use everyday. I don’t like WMP (nor Windows, nor Microsoft products in general, as they show a very reasonable price/quality ratio [reasonable for them, no the customers]) and like to be able to use my fuze with any music player I want, or even be able to put music on it without a music player (I find the command-line and rsync much more efficient for that job, but I recognise I’m not the stereotype of user). I like to own all the data on my computer and devices. Thus, I don’t like DRM. I also like to be able to use the fuze as a expensive usb-key, and to share data with my friends between different computers. So, MTP isn’t even near to fit my needs, and I recommend MSC if someone asks to me, but I do not predicate in favour or against MTP: it  just doesn’t seem to fit the needs of a lot of people. But it does for some. The rest is sansa’s lazyness and microsoft’s legendary product quality.

And no, I’m not a pro-linux-antimicrosoft fanatic. With that I mean that my opion towards microsoft does not come from the “microsoft is evil” dogma, too many frequent in the free software community, but from personal experience. 

@Ssorgatem, the problem is, mediamonkey, and windows explorer can’t list the music in external msd, if the fuze is connected in mtp mode and vice versa, so I can’t manage both of them at the same time

Paleskin, where did you get the idea that the internal memory is only MTP?  It’s not.

You can see the Sansa as two drives–internal memory and microSD–in MSC. You have to decide what goes where, and yes, if you’re using multiple microSD cards, you have to remember what you put on each one (though you can see by the Sansa display what’s on the card and what’s internal–there’s a different symbol by the files on the card). 

The only reason for MTP, as far as I’m concerned, is for DRM files. Everything else can be done through MSC. Unless you have DRM files, you’re only making your life more complicated by using both. 

I really doubt you’re going to find a way to view both MTP and MSC on your computer, at least on a Windows computer.

Take off all your MTP files, put them back on in MSC, leave the mode switch on MSC and you’ve solved the problem.