Transfer from EOS M50 Mark II to computer - best workflow?

[Pontus54]

First, I have to ask this: All Canon Software that I have downloaded to my new EOS M50 MARK II are painfully slow. It's like a present day application running on a PC from the 1980s. Takes about 10 seconds for every click to register and move on to the next screen. Is this a well known fact that you (or Canon) can't do anything about, or is it something wrong on my side?

I have a Win10 Pro running on AMD Ryzen 5 2600X Six-Core Processor  3.60 GHz.

I'm not too knowledgeable about the network side of things, but somehow I manged to get the two first test pictures transferred to my computer.  After that, I thought that when I turned off and on the camera next time, the transfer would start automatically, but it didn't. I had to start it manually, and didn't really know what I was doing. (Didn't have to set up the router side of things again, though.) What got me believing that it would start without my intervening was some setting saying "Download automatically next time the camera is turned off and on again" or something to that effect. Did I misunderstand that?

So what are the correct settings and workflow if you want the transfer to run as smoothly and magically as possible?

[Pontus54]

Yes, copying or photographing or scanning. Since it's a thing that has devolved from scanning, I assume that's why the most used term is scanning.

[Waddizzle]

Your best option for “scanning” images is to use an actual scanner, not a camera.  A camera will not give the resolution that a scanner can achieve.

However, if you really wish to use your camera and view each image after it has been scanned, then I suggest that you use a remote shooting mode so that the image files are transferred immediately after they are captured.

[Pontus54]

Thank you so much for this. I actually bought a Canon BR-E1 Wireless Remote Control together with the camera so that I don't have to touch it when taking the shot.

I'll come back to why I don't want to use a scanner when the main question is sorted out, but I don't want to risk this thread going off in the wrong direction again.

As for the problem with the slow Canon software, I'll open a separate thread for that. Not always a good idea to ask two different questions in the same thread.

I will look into your suggestion, but it will perhaps take a couple of days before I can report back.

[Waddizzle]

Be aware of the fact that just because the camera has “Wi-Fi” does not mean that it is fully networkable or communicate at Mbps speeds.  For example, once you connect the camera to your local wireless router, you cannot browse the files stored on the meory card in the camera.

The camera uses the Wi-Fi technology in combination with a smart device because it has more range than Bluetooth.  On a PC, you must use a Canon app to access the files stored in the camera, just like you would use Canon Connect on a smart device.

There is nothing wrong with your camera.  

Canon sells a separate adapter that can make cameras truly networkable.  The built-in Wi-Fi is not fully networkable, and does not communicate at typcical network speeds.

[JamesHarvey]

If your main aim is to scan using the camera, & I understand why you might be doing that rather than using a flatbed, have you tried connecting the camera to the PC using EOS Utility for Remote Shooting?  That way you should be able to generate the image files directly on the PC.  I have done that with several cameras over USB to a really old 4 core I7 machine very successfully.

I'm curious about your statement that you get very slow response to inputs, clicks.  Are you talking about when DPP is actually processing an image, so you are seeing the spinning wheel in the corner of the image while, for example, the editor opens the image or applies noise reduction; or what?  On an older 6 core machine DPP would be seem very slow in that regard, as it only uses the CPU for basic processing; on my newer 10 & 20 core Intel based machines it works acceptably fast, and the new Neural Processor uses the GPU like LR/PS and executes acceptably quickly (a few seconds to generate the 150MB enhanced file).