Chronos > Software Dev
Chronos V0.3.1 Beta - Updated Oct 15 2018 with beta-9
Buddlich:
--- Quote from: tesla500 on October 17, 2018, 12:25:57 AM ---
--- Quote from: Johnny on October 17, 2018, 12:08:50 AM ---
--- Quote from: NiNeff on October 16, 2018, 11:54:14 AM ---
--- Quote from: Johnny on October 16, 2018, 09:57:06 AM ---Is there something else missing from the CinemaDNG tags? Even Photoshop cannot open the files. No previews in macOS.
--- End quote ---
I'm having no trouble with the new beta 9 and Photoshop CS5 now.
--- End quote ---
TIFF files open with no issues. CinemaDNG does not open in Davinci Resolve or in Photoshop CC 2019. Even Lightroom CC 2015 does not want them.
And yes I'm using beta 9.
--- End quote ---
Could you upload a problem DNG file here so we can investigate?
--- End quote ---
Have the same problem... I can't open the .dng from the camera... not with lightroom, not with photoshop... with nothing :( attached one dng
patrickrebstock:
--- Quote from: Buddlich on October 28, 2018, 01:43:44 PM ---
--- Quote from: tesla500 on October 17, 2018, 12:25:57 AM ---
--- Quote from: Johnny on October 17, 2018, 12:08:50 AM ---
--- Quote from: NiNeff on October 16, 2018, 11:54:14 AM ---
--- Quote from: Johnny on October 16, 2018, 09:57:06 AM ---Is there something else missing from the CinemaDNG tags? Even Photoshop cannot open the files. No previews in macOS.
--- End quote ---
I'm having no trouble with the new beta 9 and Photoshop CS5 now.
--- End quote ---
TIFF files open with no issues. CinemaDNG does not open in Davinci Resolve or in Photoshop CC 2019. Even Lightroom CC 2015 does not want them.
And yes I'm using beta 9.
--- End quote ---
Could you upload a problem DNG file here so we can investigate?
--- End quote ---
Have the same problem... I can't open the .dng from the camera... not with lightroom, not with photoshop... with nothing :( attached one dng
--- End quote ---
try the new v9 beta i think thats fixed now
Dan D:
--- Quote ---I took a look at the pySciCam code to see how you were doing the byte unpacking and I think that our implementations agree. In the read_chronos_raw() function, you're reading the three bytes and converting them to an integer, which on a little-endian machine I think would produce a 24-bit integer of 0x23c1ab on v0.3.0, or 0xab1c23 on v0.3.1 using our example pixels of {0x123, 0xabc}.
--- End quote ---
Duh, I should have realised. That makes sense! Thanks. Nice work!
Dan D:
Hi guys
I'm trying out the 0.3.1 Beta-9 software and I've found a major bug.
Since I updated, I can't choose any IO mode other than "Record End Trigger". If I select "Frame Sync Output", "Shutter Gating" or "Exposure Trigger" modes for either IO1 or IO2 and press "OK", the UI immediately reverts to "None" no matter what recording mode I'm in. The same thing is happening on multiple cameras.
I checked on an oscilloscope and I'm no longer getting a frame sync output signal even if I choose it and hit "Apply". This is a showstopper - I can't synchronise my strobe light source without the Frame Sync Out and will have to roll back to an earlier version of the firmware. Any suggestions?
Dan D.
Dan D:
Just rolled my camera back to software 0.3.1 beta4 and the Frame Sync Out works again. Can confirm this is definitely a firmware bug and not a hardware issue.
--- Quote ---I'm trying out the 0.3.1 Beta-9 software and I've found a major bug. Since I updated, I can't choose any IO mode other than "Record End Trigger". If I select "Frame Sync Output", "Shutter Gating" or "Exposure Trigger" modes for either IO1 or IO2 and press "OK", the UI immediately reverts to "None"
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version