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 - BiduleOhm

Pages: [1] 2 3 4
1
The main problem is in the debayering method but the last firmware update (0.3.0) has greatly improved it (but 99.9 % of the videos on the internet are videos from before the update was available).

The raw data is very good since the beginning: http://forum.krontech.ca/index.php?topic=132.msg1115#msg1115

2
Software Dev / Re: Updating the UI: Main Screen Edition
« on: July 24, 2018, 03:35:00 AM »
You have very good ideas :D

Of course if we can have all the buttons as customizable soft buttons it would be great.

And I think the battery icon should always be displayed (even when there's buttons on the top row).

3
I like the second one, good job on that. I'd only add the possibility to write custom text in addition to the presets (%frame%, ...) and the possibility to have the timings as 01:23:45.678 for example (because following a dozen digits number when you are editing or even just watching the video is not super easy) or even better: to be able to specify our own format (like the date() function in PHP for example) with something like h:m:s.M (or %h%:%m%:%s%.%ms% so we can have prettier tags (ms instead of M...)) for example.

4
Chronos User Discussion / Re: Trigger can just stop recording
« on: July 18, 2018, 04:45:19 AM »
It'll not save anything to the SD card until you press the trigger. It's not like a classic camera, the Chronos record in RAM in a ring buffer so it'll no take any space on the SD card unless you save the buffer to the SD.

5
Software Dev / Re: Deploying camApp from Qt Creator
« on: May 22, 2018, 03:27:51 AM »
Yep; photodiode, phototransistor, LDR, CDS, ...

But yeah, given your use case it's best if it's in software ;)

6
Do:
Code: [Select]
sudo chmod +x pyraw2dng.py
Then retry your command (without sudo, shouldn't be needed here).

7
Software Dev / Re: Deploying camApp from Qt Creator
« on: May 20, 2018, 03:16:56 AM »
Why not a hardware trigger? Just a few components would do the trick.

8
Software Dev / Re: Updating the UI: Input Methods Edition
« on: March 29, 2018, 03:03:27 PM »
Just some ideas:

Maybe a white on black UI would be less violent than the black on white.

Let the user choose the fore and background colors (colors can be just a gradient of a dozen of grays, no need to be really fancy).

Maybe the font 'clearview' would be a good idea, it has been especially designed to be the most readable possible.

NB: as for most other UIs I prefer something simple and functional even if it's not that pretty than something pretty but more or less unusable; but that's just my personal opinion.


9
Software Dev / Re: Updating the UI: Input Methods Edition
« on: March 24, 2018, 05:13:32 AM »
Thanks for your work ;)

Personally I prefer this one for the text:




And this one for the number (that must be the most perfect layout you can do, very good job on that :D):




Quote
The jog wheel can do two things: spin and click.
I figure the logical thing to do is keep having an unpressed spin cycle the value a little, and a pressed spin cycle the value a lot. Like on the Play screen. However, if you just click the wheel without spinning it, it'll pop you out of the control you're editing so you can select a different control or button. Click the jog wheel again to edit the new control or click the button.
I think this is the most natural and intuitive way to do it, so looking forward to it. However please try to keep the different option windows (recording, saving, trigger settings...) somewhat consistent in their design and orientation. For example a general left to right or preferably up to down direction for the user inter-actable items. You should not be surprised which input field is going to be selected next by rolling the wheel and they should not jump around too much :)

I agree, basically wheel click working like the tab key on a PC and spin = increase/decrease the value, can't do better than that I think ;)

10
Chronos User Discussion / Re: Type of RAM
« on: March 16, 2018, 12:03:49 PM »
The creator of the camera (David) has made a complete teardown. If I recall correctly it's on his main youtube channel (tesla500).

11
Software Dev / Re: Updating the UI: Main Screen Edition
« on: February 28, 2018, 02:21:51 PM »
Right now, we've got it down to 4 seconds for max resolution, and more or less instantaneous at low resolutions.

We've got a few ideas to make it effectively instantaneous, at which point we'll remove the little reminder popup and just perform software black cal when we need to. (This probably won't make it into the next release though.)

Wow, that's impressive! Good job on that ;)

12
Software Dev / Re: Updating the UI: Record Settings Edition
« on: February 27, 2018, 11:27:32 AM »
Version B is my favorite (and with vertically aligned inputs it would even better) :)

13
Software Dev / Re: Updating the UI: Main Screen Edition
« on: February 27, 2018, 11:25:17 AM »
I don't see any problem with pinch to zoom and drag to pan; with all the smartphones and tablets now it's pretty much "touch screen + image = pinch and drag" in everyone's brain, and there's also the manual for the few % who might have missed that.

And we can always add a click to toggle the zoom level, it's not mutually exclusive with the pinch to zoom AFAIK.

14
Software Dev / Re: Updating the UI: Record Settings Edition
« on: February 24, 2018, 01:47:19 AM »
I prefer version A mainly because it's more clear, version B is more cluttered.

15
Software Dev / Re: Updating the UI: Main Screen Edition
« on: February 23, 2018, 03:43:45 AM »
Definitely version C :)

What would be awesome is to be able to chose which buttons are assigned to which functions (like top button 1 = ... top button 2 = ..., etc...).

Pages: [1] 2 3 4