Chronos V0.5.0 Full Release
- Thread starter sanjay
- Start date
Hi Sanjay,
I'm using Chronos with Matlab over network connection and it works good so far. I was waiting for the official software update to get rid of some bugs that i mentioned before in anther posts. Parameter disableRingBuffer, which will stop the recording when the buffer is full, is still in V0.5.0 not responding even if I change the state to true.
Can you suggest me a switch or router that is not going to cause an issue with the camera while starting up?
I'm using Chronos with Matlab over network connection and it works good so far. I was waiting for the official software update to get rid of some bugs that i mentioned before in anther posts. Parameter disableRingBuffer, which will stop the recording when the buffer is full, is still in V0.5.0 not responding even if I change the state to true.
Can you suggest me a switch or router that is not going to cause an issue with the camera while starting up?
JamesB said:
There are no plans to implement the horizontal top/bottom bars in the UI. We're sticking to the sidebar to keep things unified and predictable across updates.
Regarding the manual, look out for one in the coming (3ish) weeks. We're taking the time to rewrite the entire thing to make it easier to understand, but for urgent needs, I'd say about 95% of the V0.4 manual is still valid for V0.5 operation.
ieSe said:
Hmm, I'll give the disableRingBuffer parameter a try on my side and see what happens. Any gigabit switch or router should be fine.
If you're looking for an unmanaged switch, something like this would work: https://www.amazon.ca/NETGEAR-8-Port-Gigabit-Ethernet-Unmanaged/dp/B07PFYM5MZ
If you're looking for a router, something like this would work: https://www.amazon.ca/Netgear-Nighthawk-Routeur-intelligent-R8000/dp/B07R169MXR
Other folks could probably also chime in on what router/switch works for them.
Thank you for the update! The development is coming along very nicely.
I am not sure if I was not able to find it, but is there a place where 'bugs' can be reported?
For example, saving the file using python/json confuses the camera, where it needs to be restarted. Frame number starts jumping around wildly.
post = requests.post(c_ip+'control/startFilesave', \
json = {'format': 'h264',\
'device': 'nfs',\
'filename': 'test',\
'start': 0,\
'length':0})
I am not sure if I was not able to find it, but is there a place where 'bugs' can be reported?
For example, saving the file using python/json confuses the camera, where it needs to be restarted. Frame number starts jumping around wildly.
post = requests.post(c_ip+'control/startFilesave', \
json = {'format': 'h264',\
'device': 'nfs',\
'filename': 'test',\
'start': 0,\
'length':0})
gcp5017 said:
Hmm, thanks for pointing this out. I'll investigate further and see if I can replicate it. Bugs can be posted here: https://github.com/krontech/pychronos/issues
CS223 said:Could you keep the link to the builds in the original posts when posting new updates?It makes it easier to keep track of things for those of us who are still using Balena Etcher to update.
http://debian.krontech.ca/builds/
Ah yeah, good point. Will keep this in mind for future updates.
It is still being written, but please let me know via PM or through our official support email if you need help with anything specific in the mean time.hodu84 said:
坦丁
New member
NoDak said:
Camera is shipped with OS on 32gb card novadays.
Ist an update mainly for the 2.1 of the New batch which have some issue at higher gain-Values.I allready updated, and while i never did a direct comparison, the new update improoved Image Quality a bit from What i can tell and removed a bunch of issues with no image at all beeing displayed at some Resolutions/ Framerates at Very high gain.I dont think the Update does anything to the 1.4 or the older batch of 2.1?s but is mainly for the New 2.1?s.CS223 said:
DDR said:Must say, I love what you did with the interface. Very nice!
Thanks DDR! Hope all is well with you.
Yes, the 0.5.1 update was minor and only affects Chronos 2.1 cameras. We noticed some variance when our production team started building Chronos 2.1s with a new batch of image sensors, and so an analog voltage was updated via software to mitigate the issue while slightly improving the old batch of sensors already in the field. Thanks for providing some info in lieu of my late response, Nikon1.Nikon1 said:
just helping out where i can. Thanks also for all the work you guys put into this.sanjay said:
While we are here, can you maybe give me some info or at least a hint at how the Color-Matrix and White-Balance Settings on the Chronos work.
I see nine Values for the Color matrix, and three for the White-Balance. Guess for the Color it would be amounts of Colors from something or Contrasts at Shadows/ Highlights or....?
Have no real idea how to set the White balance based on color values (guess the three values would be R,G,B).
Can you or someone else give any info about this, i cant find anything about this anywhere.
Thanks
I need to spend some time trying to reproduce this, as of now it is unpredictable.
I have had my Chronos 1.4 'overshoot' the end point when saving h.264 videos. I mark my start and end points and the save begins as expected but passes the end mark. The touchscreen then becomes unresponsive, the "abort save" button does not respond nor do any touches in on any other part of the screen. All that I can do after that is to restart.
I had it happen 3 times out of ~20 videos that I shot today, I have not run an online update since the summer (maybe a month after v0.5.0 was released) so I will try that and see if I experience the same.
If I ssh in, is there a way to get debug info on what is going on, or manually unlock-up the UI? Just curious, thanks.
I have had my Chronos 1.4 'overshoot' the end point when saving h.264 videos. I mark my start and end points and the save begins as expected but passes the end mark. The touchscreen then becomes unresponsive, the "abort save" button does not respond nor do any touches in on any other part of the screen. All that I can do after that is to restart.
I had it happen 3 times out of ~20 videos that I shot today, I have not run an online update since the summer (maybe a month after v0.5.0 was released) so I will try that and see if I experience the same.
If I ssh in, is there a way to get debug info on what is going on, or manually unlock-up the UI? Just curious, thanks.
I tried to do some Single-Frame Saves (or to just save a very small number of frames) in the past an noticed that too. Seems to always save a bunch more than Selected, but havent figured out whats happening there Exactly....nik282000 said:
#EDIT#: forgot to say, but for me thats on my 2.1
That may have been the same issue I was having. I was saving a large number of frames but it was a relatively small portion of the full recording, less than 5%. I'll try leaving more lead in and out.
Thanks.
edit: Updated my camera, tried saving both long and short segments but had the same issue and I was unable to cause it to happen on purpose,
It seems to happen more with low resolutions/high frame rates (>30kfps) but, again, I am unable to cause it to happen predictably so it may just be that I have been recording more high frame rate video recently.
Thanks.
edit: Updated my camera, tried saving both long and short segments but had the same issue and I was unable to cause it to happen on purpose,
It seems to happen more with low resolutions/high frame rates (>30kfps) but, again, I am unable to cause it to happen predictably so it may just be that I have been recording more high frame rate video recently.