BYE switching to JPG

[SickL]

Hi guys, tonight I did my first lengthy session with BYE. In general, I am very happy with the tool. However, when I switched from lights to darks or bias respectively, BYE saved the images as JPG from there on. The settings still read RAW only. When I selected RAW&JPG in the settings I got RAWs again. I only want RAWs, of course, so this behaviour is quite embarrassing. I attached my log, maybe it helps (https://www.otelescope.com/applications/core/interface/file/attachment.php?id=2194). Note, that I did not change the settings before the dark/bias frames were taken. Any ideas?

[astroman133]

The following fragment from the log file appears to show that a JPG image was provided when the Image Quality was RAW.

2019-02-22 22:20:02,015 [22] DEBUG - TAKE PICTURE ::: Shutter(TV) Cable(CameraUSB) Av() Duration(0,0) Iso(1600) Quality(IMAGE_RAW) Mirror(0) SaveTo(PC+CARD)
2019-02-22 22:20:02,072 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2019-02-22 22:20:02,073 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2019-02-22 22:20:02,073 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=1)
2019-02-22 22:20:03,021 [22] INFO  - Running (throw): EDSDK.EdsSendCommand(CameraRef, 4, 65539)
2019-02-22 22:20:03,113 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2019-02-22 22:20:03,113 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2019-02-22 22:20:03,113 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=2)
2019-02-22 22:20:03,114 [Main] DEBUG - ObjectEvent_VolumeInfoChanged: (inRef=239647008)
2019-02-22 22:20:03,114 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=1) (inContext=0)
2019-02-22 22:20:03,114 [OnStateEventHandler] DEBUG - Items waiting to be transfered...
2019-02-22 22:20:03,140 [22] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, 4, 65539)
2019-02-22 22:20:03,140 [22] INFO  - Running (log): EDSDK.EdsSendCommand(CameraRef, 4, 0)
2019-02-22 22:20:03,218 [22] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, 4, 0)
2019-02-22 22:20:03,793 [Main] DEBUG - ObjectEvent_VolumeInfoChanged: (inRef=239647008)
2019-02-22 22:20:03,793 [Main] DEBUG - ObjectEvent_DirItemRequestTransfer: (inRef=501195024)
2019-02-22 22:20:03,793 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2019-02-22 22:20:03,793 [Main] DEBUG - ObjectEvent_DirItemCreated: (inRef=501195792)
2019-02-22 22:20:03,794 [Main] DEBUG - ObjectEvent_VolumeInfoChanged: (inRef=239647008)
2019-02-22 22:20:04,719 [OnDirItemRequestTransfer(501195024)] INFO  - Running (log): EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2019-02-22 22:20:04,723 [OnDirItemRequestTransfer(501195024)] INFO  - Success: EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2019-02-22 22:20:04,723 [OnDirItemRequestTransfer(501195024)] INFO  - Running (log): EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2019-02-22 22:20:04,727 [OnDirItemRequestTransfer(501195024)] INFO  - Success: EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2019-02-22 22:20:04,727 [OnDirItemRequestTransfer(501195024)] INFO  - Running (log): EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2019-02-22 22:20:04,754 [OnDirItemRequestTransfer(501195024)] INFO  - Success: EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2019-02-22 22:20:04,754 [OnDirItemRequestTransfer(501195024)] INFO  - Running (log): EDSDK.EdsRelease(stream)
2019-02-22 22:20:04,765 [OnDirItemRequestTransfer(501195024)] INFO  - Success: EDSDK.EdsRelease(stream)
2019-02-22 22:20:04,765 [OnDirItemRequestTransfer(501195024)] INFO  - Running (log): EDSDK.EdsDownloadComplete(imgRef)
2019-02-22 22:20:04,771 [OnDirItemRequestTransfer(501195024)] INFO  - Success: EDSDK.EdsDownloadComplete(imgRef)
2019-02-22 22:20:04,771 [OnDirItemRequestTransfer(501195024)] INFO  - Flush Running: (501194768 501194832 501194896 501195024)
2019-02-22 22:20:04,884 [CameraTakePictureOnMessageRecieved] DEBUG - Camera BUSY flushing ObjectsWaitingToBeTransfered...
2019-02-22 22:20:04,948 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=0) (inContext=0)
2019-02-22 22:20:04,948 [OnStateEventHandler] DEBUG - Items transfered!
2019-02-22 22:20:05,352 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2019-02-22 22:20:05,352 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=2)
2019-02-22 22:20:05,885 [CameraTakePictureOnMessageRecieved] INFO  - Flush Running: (501194768 501194832 501194896 501195024)
2019-02-22 22:20:05,908 [CameraTakePictureOnMessageRecieved] INFO  - Timespan 4,706
2019-02-22 22:20:06,188 [ProcessCapture(Normal)] INFO  - Loading image file : C:\Astrofotografie\BackyardTEMP\Download\IMG_4334.JPG
2019-02-22 22:20:06,293 [ProcessCapture(Normal)] INFO  - GdPicture IMG_4334.JPG
2019-02-22 22:20:06,576 [MoveFile(Normal)] INFO  - move: C:\Astrofotografie\BackyardTEMP\Download\IMG_4334.JPG
2019-02-22 22:20:06,576 [MoveFile(Normal)] INFO  -   to: C:\Astrofotografie\BackyardEOS\NGC 1499_BIAS_Tv18000s_1600iso_CLS_20190222-22h20m03s488ms.JPG
2019-02-22 22:20:06,576 [MoveFile(Normal)] INFO  - Try move C:\Astrofotografie\BackyardTEMP\Download\IMG_4334.JPG
2019-02-22 22:20:06,577 [MoveFile(Normal)] INFO  - moved to C:\Astrofotografie\BackyardEOS\NGC 1499_BIAS_Tv18000s_1600iso_CLS_20190222-22h20m03s488ms.JPG

I would make 2 suggestions:

1- Upgrade to the latest pre-release version
2- Save only to the PC

See if you can re-create your issue.

[SickL]

Thanks for the swift answer. I will try as suggested. Seems to be a bug, however. Maybe devs can look into it sometime.

[admin]

If a JPG image was saved then that is what the camera provided.  BYE saves the image provided by the camera as-is without any alteration.

Try with the dial set to "M" instead of "TV" for BIAS frames.

 

[admin]

Oh, I just released and uploaded BYE 3.1.17 a few minutes ago.  Try that new release.

[SickL]

Wilco. Btw, I set the camera to C1, which in my case is a custom setting based on "M" with bulb mode. Works fine with bulb selection in BYE, as long as I do not change it to specific shutter times. When I do this once, images are saved as JPG without me changing any settings.

[admin]

I wonder if this could be the cause.  I've never tested nor design BYE to use the C1 custom user define modes.  In theory it should work but I wonder if this plays a role in all of this.  It should be worth a try to use the native modes and see if you get the same result.  What I do know without any doubt is that BYE will save the image as-is provided by the camera so if BYE saved a JPG this is what the camera provided.  We need to figure this out.  

[SickL]

I will look into the settings of the camera, but since lights were saved as RAW only and switching to darks/bias frames in BYE changes saved format to JPG all in a sudden, I do not think I will find the cause of the faulty behaviour in camera settings.

[admin]

Did you move the dial physically from C1 to TV for your bias?

[admin]

22 minutes ago, SickL said:

I will look into the settings of the camera, but since lights were saved as RAW only and switching to darks/bias frames in BYE changes saved format to JPG all in a sudden, I do not think I will find the cause of the faulty behaviour in camera settings.

There is no logic in BYE when you select LIGHTS/DARK/BIAS.  This dropdown is informational only (aside from skipping dithering for anything but light frames) and it only serves as additional information to be inserted in the file name.  Changing that value has no baring on image quality.

[SickL]

I did not physically touch the camera after initially setting it up. I switched settings in BYE exclusively. When I wrote that I switched to dark/bias frames, I of course changed shutter settings from bulb to 1/8000 to shoot the bias frames. This somehow seemed to trigger the change from RAW to JPG.

[admin]

Ok, thanks.  I've looked at the log files again and I'm stumped.  The camera is reporting that it is set to RAW image, the take picture command is also set to RAW image, yet when the image is ready for download the camera event is providing a .JPG image.  I'm not sure where to go from here, I have no clue why the camera would provided a reference to a JPG image instead of RAW.

Go to Settings -> Advance Settings and check the option "Camera Force Read Properties".  With this enabled, BYE will force read all properties before each image is taken, maybe this will 'wake' something up in the camera.

If this does not work my only other recommendation I can think of now is to do a camera factory reset and see if you get the same behavior.

Keep us posted,

 

[SickL]

Thanks for you input. I will give your suggestions a try on my next session and will report back.

[s3igell]

On 2/26/2019 at 12:53 PM, SickL said:

Thanks for you input. I will give your suggestions a try on my next session and will report back.

Remember, you don't need to waste a perfectly good Dark Sky Night in order to test your DSLR with BYE.

You can set the Camera and a Lens up on a Tripod or the Kitchen Table, and attach to your Laptop.  Fire up BYE and Test what is needed...

[SickL]

Hi, sorry for the long time off. Real life happened...

So, today I did a little test session and came to the conclusion, that the custom modes C1 and C2 are obviously confusing BYE. I attached a log that recorded the following steps (I hope I recall the order of actions correctly):

1. Connect camera

2. Switch to C1 mode

3. Change settings to RAW via BYE settings

4. Take 5 photos -> all photos were stored as JPG (I selected store to PC only)

5. Switch to Bulb

6. Change settings to RAW again in BYE settings

7. Take 5 photos -> all photes were stored as RAW

8. Change Frame Type to Dark

9. Take 2 photos -> alle photos were stored as RAW

10. Change shutter time to 1/8000 and description to Bias

11. Change Frame Type to Flat

12. Take 2 photos -> alle photos were stored as RAW

Conclusion: When I use Bulb instead of a custom mode with my 80D everything seems fine. C modes would be nice, since I use them to store my settings for different scenarios, but I can live with that.

logfile-[20190330-16h24m13s175]-[8160]-2019-03-30.txt

[s3igell]

2 hours ago, SickL said:

Conclusion: When I use Bulb instead of a custom mode with my 80D everything seems fine. C modes would be nice, since I use them to store my settings for different scenarios, but I can live with that.

The Issue would seem to be between Canon's Implementation of the Custom Shooting Modes and Canon's SDK, as BYE doesn't interface directly with the Camera but only with the SDK.