An enhancement of features within mitkNDIProtocol is needed to read out supported tracking volumes and dimensions of the volumes (NDI API: SFLIST). This allows to change the tracking volume (NDI API: VSEL). Also reading out the revision number would be nice to differ between tracking systems.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Restricted Maniphest Task | ||||
| Resolved | None | T3272 refactor TrackingVolume | ||
| Resolved | None | T3261 Aurora Tracking Volume seems to be wrong | ||
| Resolved | None | T5297 Add support of changing tracking volumes for NDI Aurora (++) |
Event Timeline
Comment Actions
because NDI API lists several tracking volumes in Polaris API and Aurora NDI at section SFLIST, I will adapt enum NDITrackingVolume. right now I used the names given by NDI (see below). Any suggestions for better names?
enum NDITrackingVolume
{
Standard,
Pyramid,
SpectraPyramid,
VicraVolume,
Cube,
Dome
};The modification will then support SFLIST from Polaris and Aurora
Comment Actions
[SVN revision 26019]
ENH (#5297): Adding APIREV (revision number), SFLIST (supported tracking volumes) and VSEL (select tracking volume) to NDIProtocol. Add methods GetFirmwareRevisionNumber, GetSupportedVolumes and SetVolume to NDITrackingDevice to use previously mentioned methods. Adding volume types to enum.
Comment Actions
fixed. future steps will be using the information to display featured tracking volumes in gui and to enable displaying the selected tracking volume.