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] 4 5 ... 7
Mm, ethernet updating would be nice…

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: September 06, 2018, 09:39:46 PM »
Hi Sam!

Instructions for compiling the UI on the camera are up at However, they assume you have a camera running Debian 7. Only our development cameras run Debian 7 at the moment, since we haven't done little things like got the camera image sensor working yet. (The 0.3.1 release is based on Arago Linux instead of Debian for this reason.) However, you can - and I am - running the new UI in a Debian 7 VM. I do have instructions for setting up the VM using VirtualBox, but they're really not very nice and I think you're much better off following the nicer camera instructions linked at the top.


As for the software, I have just finished the first real implementation of one of the screens. It's wired into the mock API for now, until we develop the real one. (I haven't implemented the real API yet, because there are several people here who could reasonably implement it, and I'm the only UI person we have, and I'm really hoping to fob it off on one of them. ;) The drivers are *almost* ready for it though! We're so close!)

As an update to the previous progress chart:

While it may be removed, a tentative motion trigger screen has been planned. This is not an official acknowledgement that such a thing will ever be made, of course - the UI plan I have will probably grow a number of things which will never be, but which I should at least leave some space for in case they do get added. The act of UI design is overly optimistic in that sense.

The Record Settings shell has been wired into the API. This is a fairly complex page, so it's been a good testing ground for the wiring process. It appears to be a verbose and somewhat error-prone process, without particularly good control over the flow of data. However, it works, and optimistically it appears each page will take about 2-3 days to put together at this point. Perhaps the whole thing will be wired into the real API by the end of October. :-\

I also made the About & Kickstarter page reflect actual camera data, rather than just my placeholders. So that's good, and it counts as done as well although it's not particularly newsworthy. :)

I've attached the full roadmap picture below as well.

I do not understand. I know neither "Kunbus" nor "piTest", nor why this is posted as a reply to this UI design thread.

Software Dev / Re: Updating the UI: Battery
« on: August 28, 2018, 03:27:36 PM »
I just noticed that in the current UI there's no way to see your battery level while you are saving videos.

Yessss, that would be a really good one to fix. I've added a battery level readout to the play & save screen mockup, so the issue will be fixed when I get the UI redesign in. (In general, I think I need to take another whack at the play & save screen design. I don't think it's very intuitive at the moment. 😒)

More generally, I'm hoping the battery will be more accessible through the (eventually) upcoming remote control app. The back-of-camera interface is somewhat constrained by size and mode of interaction, but with the app I'm hoping we'll be able to be a little bolder.

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: August 14, 2018, 02:25:39 PM »
Work on the shell and nav section continues; work on the main screen continues.

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: August 11, 2018, 12:19:44 PM »
Oh -- if anyone's curious about the gritty details, the UI is open-source. There's a commit log up at, for example. :)

Software Dev / Re: Monitoring value on IO trigger
« on: August 11, 2018, 12:00:49 PM »
Hi Matom.

The CPU isn't really fast enough to record trigger inputs on a per-frame basis. We're currently working on a metadata system which will capture the inputs on the FPGA side, so you'll have access to timing information and trigger information on a per-frame basis. This is tentatively scheduled for the 0.4.x software release, iirc.

Reading from the analog inputs is not currently supported. There is a chance the FPGA may not expose it to the CPU yet. However, I hope you are able to figure something out. Getting all the inputs working is something we'd all really like to do here as well. :-[

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: August 07, 2018, 04:32:46 PM »
This looks like a gold mine! We'll have to see what's available in quantity, but it all looks very promising. :D

Thank you, NiNeff!

Software Dev / Re: Deploying camApp from Qt Creator
« on: August 07, 2018, 04:22:38 PM »
Im running Windows 10 and using Qt Creator. I installed Qt 5.8.0.

Hi Michael, I'm afraid Windows 10 is not a supported development platform. In addition, Qt 5.8.0 will not run on the Arago linux, the operating system of the camera.

Your best bet is to install Ubuntu in a VM such as VirtualBox and modify the existing QT 4 camapp, as per these instructions.

We have a version of the camera running Debian that can compile for itself, but I do not currently have video capture working on it. That will be brought together after my colleagues return from DEF CON, and hopefully documented not long after.

Best of luck!

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: August 03, 2018, 11:48:08 PM »
ooo, if you could do that, that would be great. It would be great to have one known option, regardless of what happens. :)

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: August 01, 2018, 03:57:25 PM »
Small update - after about a month of work, we've got all our core requirements compiling for our hardware architecture. This vastly increases certainty that my last three months of work will actually... work. :D

Next step is to see if this can be copied to the camera and run. Will it pick up and use the Framebuffer?

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: August 01, 2018, 03:12:23 PM »
When it comes to the "basic remote control", will that be via Ethernet and an app you will provide?

Will the initial implementation of that effectively allow us to use the Chronos 'tethered', so we can effectively start, stop, save, play clips and see the camera's live output remotely on a laptop?

Yes. The initial version of the basic remote control will be via Ethernet. Visiting the camera's network address from a laptop or cellphone will bring up a basic web-based UI. It will support start/stop/save and live video display. It should support playback of saved files as well. You may make your own HTTP API calls as well if you want to write scripts to control the camera.

If we can find a wireless USB dongle for sale that is supported by Debian 7, then wireless remote control will work as well. We haven't found a compatible dongle yet, the ones which do work are no longer for sale. However, something may yet turn up.

One feature I would love to see implemented is having shutter speed (EXPOSURE) in 1/60 1/100 1/500 1/1000 1/XXX instead of it being in Micro Seconds (us) as an option.

… That is an excellent suggestion. I've added it to the mockup for the new UI, so it should make it into 0.4.0.

Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« on: July 31, 2018, 06:01:29 PM »
It is a thing that we would like to play with in the future, after 0.5. There's a handful of stuff like that we'd like to do at some point.

Software Dev / Software Roadmap - 0.3.1, 0.4.x, etc.
« on: July 31, 2018, 05:35:13 PM »
What is happening with the Chronos' software? What is in the works, and when will it be available?

Keeping in mind "The best laid plans of mice and men will often go awry", here's what we have planned:

  • 0.3.1 (expected late August)
    • Improved image demosaic for .mp4 (less colour-fringing around high contrast areas)
    • Overlay frame number on video.
    • Save .dng for raw video.
    • HDMI port supports video out.
    • Basic remote video control. (play, pause, seek)
    • Save more than 45 videos.
    • Possible raw video save speed increase.
    • Additional minor bugfixes and tweaks.

  • 0.3.x (expected mid-September)
    • Power controls (turn on when connected to power, turn off when not)
    • Basic overlay controls. Maybe.

  • 0.4.0 (expected late October)
    • Debian replaces Arago as the camera operating system.
    • Python is available to script the camera.
    • External HTTP API available for custom scripting. (may be delayed)
    • Internal D-Bus API available for custom scripting. (may be delayed)
    • UI is ported to Python, prettied up, and made to use the D-Bus API.

  • 0.4.1
    • Bugfix release for 0.4.0.
    • APIs, if delayed.

  • 0.5.0
    • Remote control app, using the HTTP API.

Behind the scenes, the main delay is that we've discovered that it's impractical to continue development using our current operating system, Arago Linux. It lacks some basics such a C compiler, a scripting language, and several basic Linux debugging utilities. Arago's video subsystem also crashes after saving 45 videos.

For example, developing the back-of-camera user interface using Arago entails a ~5-minute delay between making a change and seeing the change in the UI. Using Debian, changes made to the UI are live in seconds.

We've been working on getting Debian running, on and off, for the past year. However, a few months ago a combination of near-success and issues with Arago's video system meant we decided to officially devote engineering time to the problem. This, naturally, delayed the progress we were making on the internal D-Bus API for 0.4.0, because now we were working on something else.

Currently, from my user-interface-centric perspective, here is how our progress is looking for version 0.4.0. The new UI and APIs will be debuted when this is complete.

tap for full resolution ↗️

Green means "completed", yellow is "in progress". Arrows show what depends on what. For example, the final implementation on the right depends on the D-Bus API, which has had the video control component made, and the D-Bus API Mock, which is currently being developed. Implementation is done by adding behaviour to a laid-out UI (labelled "Shell & Nav"), which I sketch up in Designer as a separate step. Each screen can be done more or less independently.

I hope this helps clear things up. I'll try to keep this thread updated as things progress. One of the big reasons we don't like to announce things is that they frequently turn out to simply be untrue. For example, we thought we'd fixed raw save speed, but then it turned out we hadn't a few times. We really don't want to promise something we won't deliver on, so we keep to ourselves quite frequently. What are your thoughts on this?

Software Dev / Re: Updating the UI: Main Screen Edition
« on: July 26, 2018, 06:31:44 PM »
Well, I can't leave anything alone, so I've whipped up a ~modern touch display~ version. (It's based loosely on Krita's radial menu style.) I think it looks pretty, but it's also kind of mysterious what things do.

Tap anywhere on screen to bring up the radial menu. Buttons are the same as mockup 8, and do the same thing. Tapping the resolution in the corner brings up the list of presets, because it might as well.

I personally think it looks good, and it makes much better use of the screen space for image preview, but I don't like icon-only navigation which I think is confusing. I think zooming in on the video will help fix the focus issue we've got now, which is the main reason we wanted to make better use of the screen space in the first place.

Pages: 1 2 [3] 4 5 ... 7