Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - DDR

Pages: [1] 2 3 ... 7
1
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: June 06, 2019, 05:16:21 PM »
Work continues. About half the stuff we need to expose via the API has been exposed, but the UI has been delayed as I've been busy trying to work out some nasty performance issues.


(click to enlarge)

2
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: May 01, 2019, 02:58:20 PM »
Well, we're back from NAB with the Chronos 2 and the bullet-time Ring announced and successfully demoed! We're turning our attention to the camera control APIs now.

Good news/bad news: The good news is that there's actually some serious progress being made on the API - it has basic working control of the cameras, can set resolution, and take and save recordings. The bad news is that it's not the original API I had designed when I made the new UI, since the new API was developed as part of the Ring project.

Here's the current status of the API and UI:

(click to enlarge)


From left to right, we have:
  • Shell & Nav: Complete, I've designed and imported all the planned screens into the new UI's code. This is still good to go.
  • Implementation (Front-End): This is the back-of-camera interface redesign I've been working on. It makes the camera do stuff by telling the internal D-Bus API to do stuff.
  • Implementation (D-Bus APIs, v2): Turns commands from the back-of-camera interface and the HTTP API into lower-level commands to the components of the camera, such as the field-programmable gate array or the image sensor.

Most of the screens' implementations have been demoted to being "in progress", since I need to go back and change the API calls being made in all the screens I had wired in. In some cases, this is simply a matter of using a new name. In other cases, such as the recording settings screen, the API works quite differently and the screen will have to be significantly reworked.

We're still aiming to release the initial version of the API in June, so you all can give us feedback and start automating your camera!

3
Software Dev / Re: Control the camera from a pc
« on: March 11, 2019, 08:56:18 AM »
API news will be announced on this forum. The easiest way to stay up to date is probably by subscribing via RSS. (The links are at the bottom of the page.)

Development of the externally-facing APIs you need is open. The component for pc-based control is at https://github.com/krontech/chronos-web-interface. It's a HTTP-based API, which is a wrapper around two internal APIs. Those APIs are the coordinator api written in Python and the video api written in C. Neither are ready for use yet, so the http api you need doesn't work yet. The coordinator api only exists in mocked form and is (well?) [https://krontech.github.io/chronos-gui-2/D-Bus.html]documented. The video api, which actually works for realsies, is undocumented at the moment so you can't use it either.

We're hoping to have the APIs released by the end of June now. Previously, we were hoping to have them released by the end of last January.

For your second question, it sounds like setting a delay as you describe will do what you want.

Hope that helps!

4
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: March 11, 2019, 08:31:36 AM »
Any updates?
No. >_<

This is quite frustrating all around, I think.

Most of the company has been pulled off into NAB prep. Since it's at the end of this month and we are not strictly speaking ready, that has been where the attention has been.

I myself have been splitting my time between NAB work and writing the documentation for the HTTP API. The documentation is nearing completion, the API is not. To that end, I'm going to announce the dummy API soon, in the hope of gathering some useful feedback. Most APIs are terrible, and I would like this one to be the exception. The real API will be available two or three months after NAB, hopefully. :-\

Actually testing the next beta of the current software is almost done too, thanks to skronstein's efforts. :) We hope to issue a release soon. One of the issues testing has turned up that we didn't know about is that we broke white balance at some point. It now makes whites less balanced instead of more balanced.


I think the idea of the testing is that we will be able to release new betas without delaying for any new features or bugfixes, since we will know what is wrong. However, perfectionism dies hard. I will do what I can to make sure the release does happen, even with caveats such as broken white balance.

Sorry for the delays. :-[

5
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: February 08, 2019, 12:00:40 PM »
Well, it's been a while since I updated what was going on behind the scenes here. While we've all been working hard, it's been a lot of behind-the-scenes sort of stuff. Nothing very showy, really.

So, some background is in order.

We decided about a year ago that we did not want to keep using the original version of the software, camApp, which ships with the camera and is updated via the betas on this forum. One of the main reasons for this is that we wanted a web api and remote control app. Embedding a web server in original camApp was impractical. An external web server could not reasonably be hacked together with the tools available¹.­ Some infrastructure needed to be built.

So, Foobar ported a newer linux kernel to our CPU, and we got access to much better tools. Porting a linux kernel is generally not considered a one-man job, so it took him a few months. During this time, I put together a virtual machine to develop the new UI, called gui2, on. After I'd completed that, Foobar promptly delivered an early version of the new linux to me. While it lacked drivers for all the camera-y parts, I was able to get a modern tech stack up and running and I used this to develop the app for the next half-year.

As this progressed, it became apparent that the tech stack I'd compiled was not one that we could safely upgrade and maintain. Foobar completed his port of the linux kernel, giving us Debian 8 as the underlying operating system, and we decided to backport the infrastructure I was using from Debian 9. This was completed, but we were still several versions behind what I'd developed the new UI on. I am currently finishing porting everything from my new tech stack to the older, maintainable versions of the tech we had. While a few bugs remain, I got the app running in it's entirety, on it's final tech stack, this afternoon.

Near the beginning of all this, Johan was hired to extract the startup logic from the current camApp. (I was hired to do the mobile app promised in the Kickstarter, which was deferred due to the technical issues mentioned above, so I wound up extracting the graphical user interface from the camApp.) Extracting the startup logic to initialize the sensor proved to be quite difficult. This was completed this morning, and the camera can now start and show the new UI entirely without having to run the current camApp!

The camera can now also run a nascent HTTP API, which plays well with the new UI. If you update a value via the API, the new value is reflected in the UI running on the camera. However, both the new UI and the alpha HTTP API are still largely disconnected from the hardware of the camera. They are running against dummy values. Since Johan has managed to bring up the camera, he is now implementing the dummy values so the HTTP API and the new UI can actually make changes to the camera. Some tasks are expected to be easy to tell the camera to do, while others will require a bit more work. This implementation is represented by box in the last progress chart posted in this thread³.

While all this has been going on, Loial has been making significant improvements to the firmware of the camera's FPGA. This has been appearing in the forum betas. We are currently in the midst of working on a testing plan for the next beta, since we'd like it to actually work this time. Unfortunately, there turns out to be quite a lot to our software, so while skronstein has been working on the testing plan it is still a work in progress. I myself may be pulled aside for a few days to complete that, so we can test and release next beta here. 🙂

If you'd like to talk to us in person and see some cool stuff, we'll be at NAB. It's April 6th through 11th in Las Vegas, though we'll be around a few days longer for setup and teardown.



¹ These tools were Ash² scripts being called via CGI.
² Ash is like Bash, but awful.
³ There has been no real progress on the chart since then since both Johan and myself have been been dealing with the underlying work of making our respective technologies run. Since this work was unforseen and unpredictable, it was uncharted.

6
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: January 23, 2019, 04:19:09 PM »
Hi JamesB.

I've asked around, and the backend guys have told me that saving/restoring black cal images would be "very hard". I'd like to see that feature myself — I've had a lot of difficulty around changing temperature and black cal — so I'm still going to push for it.

There was some unrelated work done to improve the vertical banding problem, however. It should land in either the next 0.3.x beta or 0.4.x, and should help that issue quite a bit. :D

7
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: January 17, 2019, 01:17:38 PM »
Hi Thomas. As it stands, @skronstein is working on a test plan for verification of 0.3.x. So that should be coming in a few weeks, once we've actually checked it does what we say it does. @tesla500 is working on an improved version of the power-down feature for your use. A more configurable version will be released with the new UI, on the power screen. I myself am busy with 0.5.x UI, which will be served by the API Johan is working on for 0.4.x. (We've experienced difficulty extracting the sensor initialization logic from the old camApp code.)

I hope that helps explain what we've been working on. There haven't been any major milestones to announce, so I'm afraid we've been pretty quiet.

8
Chronos User Discussion / Re: Time Stamps
« on: January 02, 2019, 05:16:12 PM »
Hi all,

Thanks for the feedback. I'm glad to see the overlay is getting some use!

Going forward, the new UI I'm working on will have some minimal overlay configuration settings. It will be a small improvement over what we have now.

After the new UI is released, I'm planning to add fine-grained stamp settings. These will include the ability to choose a font (and thus font-size) and some formatting options for the data. Including what the timestamp and frame numbers are relative to. :)

9
Chronos User Discussion / Re: Dual Cameras over Ethernet
« on: December 17, 2018, 04:24:36 PM »
Hi mcknight. You're right, you'll need to configure one of the cameras to use a different IP address than the other. To do this, edit the /etc/network/interfaces and /etc/udhcp.conf files on one of your cameras, changing 192.168.12.1 to 192.168.13.1. This should put the camera on a different subnet, which will keep them from fighting each other.

Hope that helps!

10
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: December 12, 2018, 04:22:41 PM »
Will 0.3.x ever see the light of day?
We discovered last weekend, during testing here, that the internal candidate we had for release was outputting a solid green video and nothing else. This ultimately ended up being an upgrade script error, which we since fixed. The only thing we know of that's broken now is an off-by-one column gain error which Loial is currently working on fixing. Hopefully, if nothing else breaks, we should be able to release beta 0.3 in the next week or two. Fingers crossed.

We might still make the January release date for 0.4.0. 🤞 0.3.x has been a real pain in the neck, but we've continued work on 0.4.x as 0.3.x has been going through testing. We should have a release candidate out for 0.4.0 by Jan., at least. (This will probably include better sensor calibration, a better operating system, and however much of the HTTP API we have implemented by then.)

11
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: December 04, 2018, 03:50:46 PM »
Hi, Sam. We could get the new UI and OS up and running as-is now, they just wouldn't be able to do anything. I think you'd find the old, C++-based camApp running on Debian to be much more useful. What do you want to do with the camera?

[edit]
We should have 0.4.0 by January. Possibly February if things go really badly.

12
Chronos User Discussion / Re: Chronos 1.4 Footage Thread
« on: November 29, 2018, 02:34:39 PM »
That's super-cool, Dan D. :D

We don't get to see lab use that often. Thank you for taking the time to put the video together.

13
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: October 22, 2018, 04:17:59 PM »
In the software update roadmap I do not see audio recordings for the video, what's going on? It looks like this feature will be available on version 1.0 ?
Audio will be one of the later features to be added. It should be in by 1.0.

14
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: October 17, 2018, 09:28:32 PM »
Hi SamL. I'm not sure when the HTTP API will be released. However, for you and everyone else curious, an explanation is is order.

Here is a map of the tasks we're working on. (Click for larger version, or see attachment 1.)


Green = done
Yellow = in progress
White = not started

The blue circles denote areas we're actively working on. In order:

One of our engineers, Johan, is implementing the underlying D-Bus API right now. The HTTP API (not pictured) will act as a wrapper for the D-Bus API, so as the timing works out, when the D-Bus API is done the HTTP API should be done as well. Johan has so far implemented reading the power controller for battery charge, and is currently porting reading/writing to our FPGA. Soon, we can do actual useful stuff with the API, but how soon is unknown. Johan hasn't done this before, and therefore can't produce an accurate estimate. I'm guessing it will take him at least few months to work through everything. Assuming we can get out some sort of gimped HTTP API built on that work, which won't run simultaneously with the touch-screen user interface on the camera, I would very roughly estimate "late January" for basic HTTP control. This should not include video streaming, but should include video download and basic file management.

I am continuing work on the new back-of-camera user interface. I've spent the last two weeks working on one of the two great unknowns of the process, jog wheel input. The other great unknown, the software keyboards, I will start work on tomorrow. I don't know how long the software keyboards will take. They could take a few days, or they could take a few weeks. The jog wheel still needs roughly a week or two of work, as each widget needs its own behaviour implemented. (Menus are going to become a heck of a lot easier to select. :D)

Foobar has effectively ported the current UI forward to our shiny new Debian-based operating system. This is a major milestone for us! It means we can abandon our old operating system, which was sucking up a lot of our time. It also means we can do a more piece-wise release of the new features as they're built out, so we may see useful parts of the HTTP API available well before the full HTTP API is finished.

15
Software Dev / Re: Updating the UI: Network / Remote Control Screen
« on: October 05, 2018, 04:03:39 PM »
ARIN says they're reserved for private use. I'm not sure what the implications are, though.

Quote from: ARIN link=https://www.arin.net/knowledge/address_filters.html
Note that only a portion of the "172" and the "192" address ranges are designated for private use. The remaining addresses are "public," and routable on the global Internet.

I figure it'll be fine in most cases - anyone setting up a nonconforming network either knows what they're doing or have larger security issues.

Pages: [1] 2 3 ... 7