Thanks @MylesT ,
Good to know, thanks! So it's necessary to run this branch (for now) for multi-stage inference:
And note that it it currently only has the post processing for parsing the
landmarks-regression-retail-0009 as the second stage.
Other networks are -probably- running behind the scene, but we haven't written the host-side processing of the metadata for display yet - so they won't work/display properly.
I'll check into what is required to get the processing working for running other second-stage networks parsing/displaying properly (like
So speaking longer-term, we have been refactoring our build system and our pipeline builder for significant improvements, including a visual editor where one can drag/drop the networks which are desired to be run in series/parallel and/or in a loop.
This will improve the UX for doing multi-network systems like this (including CV functions/rules in-between). This is part of the reason the current flow isn't what it should be - as we've been focused on a longer-term more capable pipeline builder, which requires a re-architecting, instead of focusing as much on extending the current pipeline builder.
From the fact that you are running on Windows, I think you are using the
refactor branch, which lays the initial groundwork for this new build system (which will include PyPi.org support - so
pip3 install depthai instead of having to clone a Github repo) and sets the stage for the v2 pipeline builder (which is in progress now and we expect to have initially released mid-July).
So the branch w/ the current multi-stage pipeline support is actually in the old build system (and I don't think it's been brought over to the new build system, so I'm actually thinking it will not be supported on Windows yet).
So the latest Windows-supporting branch is
develop (here) which actually has in-progress documentation (here) corresponding to how the build system will change.
I haven't yet tried develop on Windows (although I did try it on Mac and it worked).