Replay the capture in realtime

[noitarud]

This is to complement with footage/sound so experience can be better relived in the field. Presentation as gauges is recommended (not just figures).

[Jens Noriʇzsɔɥ]

Could you give us an example of a practical application: what would this be good for – and what speaks against a screen recording?

[noitarud]

Screen recording uses the device's resources - at one time I was trying to record something that I had to wait to get (camera app wouldn't hold the exposure setting so I screen-recorded it) and after about ten long tries the device's recording performance dropped out - I suspect it began wear levelling of the SSD.

The gauge idea was with screen recording in mind. The experimenter may like to present/animate the operation of the experiment as gauges or moving zoomed-in graphs - the need to do this may not have become apparent until later. [touching zoom clears the follow setting, expected it to retain]

p.s. would that be a valid request - to record camera video to the ram and only record the buffer and subsequent video when triggered?

[Jens Noriʇzsɔɥ]

If screen recording is broken, it is likely not phyphox' task to fix it…

You could always add gauges with the editor where needed and you could revert to a saved experiment state to zoom into the details you need. With screen mirroring (also works as an alternative to on-device screen recording), you could even put these next to each other.

Are you aware that you could check “Follow new data” in the “More tools” menu?

I do not understand your request in p.s. (recording video to RAM would almost certainly trigger the OOM killer)

[noitarud]

that was a lousy joke. Screen recording uses much storage, compared to rerunning through the acquired data. If you meant "no" then say it, otherwise it's low priority.

"you can add gauges"? There's nothing about it, https://phyphox.org/wiki/index.php?searc...arch&go=Go

the ps - yes. That was assuming you wanted to record video in the app also (i have only seen apps wipe out backgrounded apps - not the present one getting wiped, so assumed no issue; assumed compressed and resolution limited also).

[Jens Noriʇzsɔɥ]

Well, it has been your first example against screen recording… Rerunning does not necessarily mean less data: there are quite some audio experiments that obtain data at 48kHz. Please note that not all data is permanently stored in an experiment run, so, yes, that would be a deep change and as such low priority.

There are plenty of meanings of “gauge”: do you mean values like in the “Multi” tabs (that's what I understood), scales like those at the axis, grids, …?

[noitarud]

Gauge: like the dashboard of your car. This would fit under what I was trying to communicate on the 'visual outputs' thread (still in progress).

Another application for replay is to work post-processing, the (reparsed, not necessarily realtime) data can be used to "build"/combine to obtain an outcome from a different aspect (see my example in my map thread for examples of creating different aspects - the images of the aspects have been removed/replaced by you)