axiom-recorder icon indicating copy to clipboard operation
axiom-recorder copied to clipboard

Software to record moving images from Apertus° AXIOM cameras via USB3 or ethernet

Results 13 axiom-recorder issues
Sort by recently updated
recently updated
newest added

Adding my config so you can test. You'll need to adjust the hardcoded file path for images.

This refactors the gpu node code so that shaders are assembled and compiled during runtime. This is a first step that could later allow us to fuse gpu nodes together...

debian11 latest kernel & software. Cargo installed from cli Compiling sz3 v0.1.0+3.1.5.3 (https://github.com/apertus-open-source-cinema/sz3-rs#7e227cd1) error[E0308]: mismatched types --> /root/.cargo/git/checkouts/sz3-rs-763d189c3e7f1e3d/7e227cd/src/lib.rs:400:13 | 399 | ) -> *mut i8 { | ------- expected `*mut...

how to benchmark and prevent dropped frames in axiom-recorder recorded image sequences? there are integrated benchmarking tools (benchmarkSink) but I want to benchmark write speed Would the CLI output indicate...

As the CinemaDngReader doesn't have the --fps parameters that the RawDirectoryReader has how to specify playback FPS?

The rawdirectorywriter path defines the folder structure only currently and the written files are hardcode to be called *.data Would be handy to be able to use a syntax like...

pressing ESC button while in _Display --fullscreen true_ closes the currently running task

Some nodes don't really care what output format they write (rgba / rgb / fp16 / uint8, ...). Thus the next node may wish for a specific output format

So that we have a `FileReader` or a `DirectoryReader` and a `RawParser` or a `CinemaDngParser`. This would allow us to have a CinemaDNG Frameserver and a CinemaDNG writer without the...

this would allow to optimize rendering and to split the plot and display nodes