Version 0.5.2

Features:

• Display progress when acquiring a z-stack
• Add experimental 3D stack accumulation function
• Display acquisition progress in main window, instead of progress window

Bugfixes:

• Ensure correct framerate is set for AVI containers
• Enable sync pulses / recording mode even if we aren't recording

Miscellaneous:

• py: Explicitly set video filename, rather than implicitly

---

Please check out the information for users for using the
prebuilt binaries and solutions to common issues users may encounter.

Version 0.5.1

Features:

• Update to more modern image rendering code from Syntalos
• Add option to highlight image saturation
• Allow building for OpenGL ES, making arm64 builds easier
• Implement a device hard-reset feature for developers

Bugfixes:

• Clean up V4L buffers after OpenCV release for clean future device reconnect

Miscellaneous:

• ci: Build for Debian 12 by default
• cmake: Stop using PythonInterp, use Python3 module instead in FindNumPy

---

Please check out the information for users for using the
prebuilt binaries and solutions to common issues users may encounter.

Version 0.5.0

Features:

• Implement BNO read support (if DAQ firmware version is high enough)
• Perspective-warp BNO indicator according to received BNO data
• Check firmware ABI when connecting to device
• python: Update API to include the new BNO settings
• zstack: Speed up acquisition by waiting for frame counts, not durations

Bugfixes:

• Optimize PoMiDAQ SVG
• Make "Stop recording" button more obviously clickable

---

Please check out the information for users for using the
prebuilt binaries and solutions to common issues users may encounter.

Version 0.4.5

Features:

• Display device name for camera ID on Linux
• Don't store data in temporary location by default
• Update screenshots
• Add Flatpak bundle build recipe
• Validate & augment metainfo file using appstreamcli

Bugfixes:

• Prevent in-tree builds
• Give a better error when trying to build against GLES instead of OpenGL
• cmake: Find more recent FFmpeg versions as well

---

Please check out the information for users for using the prebuilt binaries and solutions to common issues users may encounter.

Version 0.4.4

Features:

• Implement z-stack capture feature for Miniscopes with an EWL
• Run display image rendering as event loop callback

Bugfixes:

• Resolve a few compiler warnings

---

Please check out the information for users for using the prebuilt binaries and solutions to common issues users may encounter.

Version 0.4.3

Features:

• Make build instructions a bit more beginner-friendly

Bugfixes:

• Give video display container a minimum width
• Don't use deprecated FFmpeg API
• Save view splitter sizes as byte array, instead of variant (#8)

---

Please check out the information for users for using the prebuilt binaries and solutions to common issues users may encounter.

Version 0.4.2

Features:

• Add spin boxes for sliding values, in addition to slider widgets
• Start Miniscopes on highest framerate by default

Bugfixes:

• Tell DAQ board when we are recording data
• Consistently sort Miniscope controls
• Save & restore main window splitter position

Notes for Users

On Linux

• The packages were built on Ubuntu 20.04 and Debian 11. They may run on other Debian-based distributions as well, but in case they don't, compiling the application from source is pretty easy to do (refer to the README.md file).
• You need at least an OpenGL 3.0-capable graphics driver on your system to run this application.

On Windows

• You will need at least an OpenGL 3.0-capable graphics driver installed, otherwise the application will not start.
• You will need to trust the executable from an "Unknown Publisher" as it is not signed.
• Some users reported they can't start PoMiDAQ on Windows because MF.dll/MFPLAT.dll are missing. In this case, you will need to install the Mediafeaturepack from Microsoft for your Windows version to resolve the problem.

Version 0.4.1

Features:

• ci: Switch to GitHub Actions for CI
• Build Win64 build with MSVC by default
• Add ability to hotplug Miniscopes to DAQ board
• Add reset button for display limits settings

Bugfixes:

• Emulate timestamps on Windows if backend doesn't provide accurate ones
• Update Miniscope hardware definition from upstream

Notes for Users

On Linux

• The packages were built on Ubuntu 20.04 and Debian 11. They may run on other Debian-based distributions as well, but in case they don't, compiling the application from source is pretty easy to do (refer to the README.md file).
• You need at least an OpenGL 3.0-capable graphics driver on your system to run this application.

On Windows

• You will need at least an OpenGL 3.0-capable graphics driver installed, otherwise the application will not start.
• You will need to trust the executable from an "Unknown Publisher" as it is not signed.
• Some users reported they can't start PoMiDAQ on Windows because MF.dll/MFPLAT.dll are missing. In this case, you will need to install the Mediafeaturepack from Microsoft for your Windows version to resolve the problem.

Version 0.4.0

This is the first release of PoMiDAQ supporting both the v3 and v4 Miniscope variants, as well as a few other models. In order to use this new version, you need to make sure that your Miniscope DAQ board is flashed with the latest firmware version (supporting v3 and v4 Miniscopes). You can find the new firmware at Aharoni-Lab/Miniscope-DAQ-Cypress-firmware.

Features:

• Supports a lot more Miniscope devices, including the new Miniscope v4!
• Drop dependency on Boost
• Add Miniscope device type listing
• Implement dynamic loading of scope controls
• Implement the new DAQ board communication API
• ui: Jump to the next useful toolbox page automatically
• Simplify logging, write more detailed log in GUI
• Add callback to be notified of control value changes
• Don't call the raw encoding "No codec"/"None" in the UI
• Drop background division, make background diff a display mode
• Display storage location next to directory select button as well
• Save & restore window geometry
• Remember user data storage directory choice
• Remember last Miniscope device choice
• Add build instructions to README
• Use newer compiler and libs on Windows
• Update Python bindings

Bugfixes:

• Convert more pixel formats in video writer
• Only show tested and suitable codecs in selection box
• Reset control value UI to device values upon reconnect
• Remove explicit framerate delay code
• Avoid sending lots of packets to the DAQ device in a short time
• Make amount of permitted broken timestamps framerate-dependent
• Auto-disconnect on device type change
• Fix Python module build and switch to pybind11
• Show GUI error message when failing to initialize OpenGL

Notes for Users

On Linux

• The .deb package was built in an Ubuntu 20.04 (Focal Fossa) container. It may run on other Debian-based distributions as well, but in case it doesn't, compiling the application from source is pretty easy to do (refer to the README.md file).
• You need at least an OpenGL 3.0-capable graphics driver on your system to run this application.

On Windows

• You will need at least an OpenGL 3.0-capable graphics driver installed, otherwise the application will not start.
• You will need to trust the executable from an "Unknown Publisher" as it is not signed.
• You may need to install the VC++ runtime to run this application. An installer is included with this release, just run "bin/vc_redist.x64.exe".
• Some users reported they can't start PoMiDAQ on Windows because MF.dll/MFPLAT.dll are missing. In this case, you will need to install the Mediafeaturepack from Microsoft for your Windows version to resolve the problem.

Version 0.3.0

Features:

• Use the improved OpenGL image view widget from MazeAmaze/Syntalos
• lib: Add callbacks to retrieve the current raw and displayed frames
• Use C++17 as baseline
• Add AppStream MetaInfo file
• Simplify & improve time keeping code
• lib: Permit API users to intercept & modify timestamps

Bugfixes:

• Lower required OpenGL version, and fail if we can't initialize GL
• Never even try to use dark mode on systems where it doesn't exist
• Perform sanity check on timestamps before initializing timer with them
• Do not expose clock details in API
• Don't resend settings when framerate is low, this only causes the problem to get worse
• Prefer V4L as camera API on Linux
• Prefer DirectShow as camera API on Windows
• Improve locking code and handle dropped init frames better