Support and General Use > Recording

what do you want on the recording screen?

<< < (4/8) > >>

linuxstb:
Why display the "Time:" and "File:" labels at all?  Isn't it obvious what they are?  If you remove at least the File: label, then the filename could easily be made to scroll.  Even with the label, the filename could scroll using a viewport.

Benway:
Would it be possible to have some flashing sybol to indicate that the unit is actually recording? I think this would be extremely helpful as the increasing of the filesize is just too hard to see with this tiny font.

GodEater:
Isn't that what the peakmeters do?

Or do they run even when the unit isn't recording ?

(Spot the recording novice...)

LurkAzusa:
The peakmeters run in pre-recording mode.  I've missed many a recording because I couldn't see the filename (too small a font).  A flashing recording symbol or larger font would be nice. (H340)

jhMikeS:
I had the idea of actually separating the recording functionality such as control, AGC, etc. from the display code so that various pages of information could be displayed and even custom screens easily added (debugging, custom builds, etc.) without getting in the way of control of the low-level recording code.

It wouldn't need multiple threads but just a layered structure with display code called by functional code similarly to how peakmeters function. State machine-based design is the way to go to make that simple.

Just my $.02 to have maximized flexibility.

Navigation

[0] Message Index

[#] Next page

[*] Previous page