5DMkIV connectivity and BYE downloading JPG but not RAW when set in RAW+JPG mode

[photographybywam@gmail.com]

Caveat: I'm in Day 2 into using BYE and obviously still learning

Day 1 USB connectivity issues were resolved by switching from directly connecting to the USB 2.0 port on my laptop to using the USB 3.0 port via my card reader/hub (not sure if this is common or just masking some other issue I had with my USB 2.0).  Many thanks to Admin and Astroman133 for the guidance yesterday!

Day 2 following along with Guylain in the YouTube and successfully adjusting focus and taking test images, however when I set up the download for RAW + JPG it is only downloading the JPG (no RAW files).  If I change the settings to RAW (only) it definitely saves the .CR2 files in the BackyardEOS folder. I've attempted to find similar problem description in the forum and I've seen where many have reported exactly the opposite (they only get the RAW when attempting to download both RAW + JPG).  I also tried putting a 4 second pause between frames just in case it was a timing issue. To a large extent I dont really care about the JPG's since its the RAW that are what we want to process - this is more of a setup curiosity to determine if I'm doing something wrong or if it is a limitation within the Canon 5DMkIV SDK that limits the downloading to only one or the other but not both?  Log History and Log Files attached.

 

09:02:00  Licensed to photographybywam@gmail.com
09:02:09  Attempting to connect camera...
09:02:09  Canon drivers 'Canon\' initialized.
09:02:11  5D-MkIV CONNECTED!
09:03:03  Imaging session started.
09:03:12  BYE TEST 2_LIGHT_Tv1200s_1600iso_f9_+28c_20191108-09h03m05s444ms.JPG
09:03:23  Imaging session completed successfully
09:03:23  BYE TEST 2_LIGHT_Tv1200s_1600iso_f9_+28c_20191108-09h03m16s531ms.JPG
09:04:26  Imaging session started.
09:04:31  BYE TEST 3_LIGHT_Tv1200s_1600iso_f9_+28c_20191108-09h04m28s268ms.CR2
09:04:39  Imaging session completed successfully
09:04:39  BYE TEST 3_LIGHT_Tv1200s_1600iso_f9_+28c_20191108-09h04m36s987ms.CR2
09:06:38  Imaging session started.
09:06:46  BYE TEST 4_LIGHT_Tv1200s_1600iso_f9_+28c_20191108-09h06m40s189ms.JPG
09:06:58  Imaging session completed successfully
09:06:58  BYE TEST 4_LIGHT_Tv1200s_1600iso_f9_+28c_20191108-09h06m51s662ms.JPG

logfile-[20191108-09h01m55s840]-[4896]-2019-11-08.txt

[admin]

Please download the latest 3.1.18 pre-release in the download pre-release section and try it.  I had to make a change for a similar issue with the EOS-R and it may work.

Regards,

[astroman133]

I seem to remember a limitation where your symptoms would happen with certain memory card configurations. If you have RAW and JPG configured to go to different memory cards, your symptoms may improve if you have both image qualities going to card 1 and only switch to card 2 when card 1 is full. This is discussed in Setting the Image-Recording Quality on page 169 of the 5D Mk IV Instruction Manual.

Let us know how this works for you.

[photographybywam@gmail.com]

Sorry for the delay....I will download 3.1.18 pre-release and give it another shot! THANKS

Also regarding my issue with USB 2.0 vs USB 3.0 connectivity issue I heard back from Canon Professional Services (where I have "professional" status--mostly because of all the $$$ I've spent LOL but their support is good) and they've indicated that they've seen a similar issue before.  They were guessing but they think it could be that my ASUS laptop either doesnt have enough voltage on the USB 2.0 output to support the connection or that perhaps my particular laptop has a low voltage issue on that port.  I'm going to try it with a powered USB 2.0 hub just to test their theory and will report back.

[photographybywam@gmail.com]

Good news and interesting news...

the 3.3.18 pre-release is definitely saving both RAW and JPG files from my Canon 5D MkIV.  That's the good news.  The interesting news is the date stamping meta data as displayed by Windows vs the metadata captured in the file name (btw...your file names are brilliant).  The RAW images appear to be picking up a different time stamps...see attached screenshot.  The RAW date stamps are "acting" differently than the JPG date stamps...and depending on which date stamp you look at in File Exlporer it appears to be writing different information.  Is that a function of BYE?  Or do you think I might have something buggered in the system date/time settings on my machine?

07:55:05  Licensed to photographybywam@gmail.com
07:55:05  BackyardEOS 3.1.18 RC12
07:55:10  Attempting to connect camera...
07:55:10  Canon drivers 'Canon\' initialized.
07:55:11  5D-MkIV CONNECTED!
07:55:14  Unable to set LiveviewAutoFocusMode, current setting is assumed!
07:59:24  Imaging session started.
07:59:33  Imaging session completed successfully
07:59:39  LIGHT_Tv160s_100iso_f13_+27c_20191118-07h59m26s357ms.CR2
07:59:39  LIGHT_Tv160s_100iso_f13_+27c_20191118-07h59m26s357ms.jpg
08:02:15  Imaging session started.
08:02:21  LIGHT_Tv160s_100iso_f13_+27c_20191118-08h02m17s776ms.CR2
08:02:21  Imaging session completed successfully
08:09:08  Imaging session started.
08:09:13  LIGHT_Tv160s_100iso_f13_+26c_20191118-08h09m10s229ms.CR2
08:09:13  Imaging session completed successfully
08:12:27  Imaging session started.
08:12:37  LIGHT_Tv160s_100iso_f13_+26c_20191118-08h12m29s440ms.CR2
08:12:37  LIGHT_Tv160s_100iso_f13_+26c_20191118-08h12m29s440ms.jpg
08:12:37  Imaging session completed successfully

[photographybywam@gmail.com]

I forgot to mention that in this test as well as in all previous tests, I was only using the CF card and did not have the SD card installed in my camera.  It might be "bad form" but I generally on use the SD card as an "overflow" if I'm out shooting wildlife/birds and my CF card fills up the camera will roll over to the SD card without me having to interrupt my shooting/move to grab my gear.  If it would be helpful, I could reinstall and BYE 3.1.17 and see what happens if I put an SD card in the second slot and send the JPG's to the SD and the RAW to CF and let you know if there's any difference.

[admin]

The date used in the file name is a timestamp at the start of the image exposure.  All other dates are either coming form the camera itself or windows at different time during the image download, file creation, or what ever other event is used by either the camera and/or computer.  The only date BYE stamps the file with is the file name; beyond that nothing is done.

Thanks for the detailed report, it's always nice to see how quickly users are able to turn the table and be productive almost right out of the gate.

Regards,

[photographybywam@gmail.com]

You're welcome! I've heard nothing but good things about BYE from a colleague and I'm happy to report that it definitely doesnt disappoint in any way.

On a side note I read in another thread that a user was able to successfully use the WiFi function to connect BYE to his Canon 5D MkIV (or maybe it was his 6D?) ...In any event I was able to recreate that result.  It does require going through the WiFi pairing process and you have to remember that the camera is the WiFi hub and disconnect laptop from home WiFi to connect to the camera's WiFi and, just like with the cable, make sure the EOS remote utility is closed and select Camera within BYE and bada-bing bada-boom it connects right up (the first attempt I deliberately left the EOS utility connected) log files and screen shot of imaging thru BYE connected to 5DMkIV via the camera's WiFi.  The downloading is definitely a little slower but it didnt appear to be so slow as to be an issue.

 

09:58:57  Licensed to photographybywam@gmail.com
09:58:57  BackyardEOS 3.1.18 RC12
09:59:07  Attempting to connect camera...
09:59:07  Canon drivers 'Canon\' initialized.
10:00:18  Attempting to connect camera...
10:00:18  Canon drivers 'Canon\' initialized.
10:00:19  5D-MkIV CONNECTED!
10:00:42  Unable to set LiveviewAutoFocusMode, current setting is assumed!
10:01:02  Imaging session started.
10:01:22  Imaging session completed successfully
10:01:22  LIGHT_1s_1600iso_f4-5_+30c_20191118-10h01m04s529ms.CR2
10:01:22  LIGHT_1s_1600iso_f4-5_+30c_20191118-10h01m04s529ms.jpg
10:02:05  Imaging session started.
10:02:34  LIGHT_Tv1100s_100iso_f13_+30c_20191118-10h02m07s947ms.CR2
10:02:34  LIGHT_Tv1100s_100iso_f13_+30c_20191118-10h02m07s947ms.jpg
10:02:34  Imaging session completed successfully

[admin]

If you need to maintain wifi connection with your home network, you might want to consider getting a small USB wifi dongle so that you have 2 wifi networks on your laptop, one to your camera and one to your home network.

Caution:  I do not officially support wifi because I have found over the years to be somewhat unreliable at times.  If the Canon SDK looses connectivity to the camera, even for 1 millisecond, the camera will disconnect and all bets of off as far as where BYE is concerned. 

Regards,

 

[photographybywam@gmail.com]

thanks for the info re the dongle (great idea) and the note of caution...both points well taken!

[astroman133]

I am sure that your info about WiFi usage will be very useful to users with cameras that have that capability. Thanks for sharing!

In my experience with BYE, even with a wired connection, what Guylain means with "all bets are off" is that the Canon SDK can lock up which causes BYE to lock up. This requires you to use the Task Manager to kill BYE. 

I mention this because if you have a Premium license you should keep a saved copy of your capture plan so that you can be up and imaging more quickly after you have restarted and re-connected BYE with the camera.