Hi,
I think I've found a bug in the pipeline init function. When using the face tracking module, initializing the pipeline can get stuck if there is no camera connected. I haven't completely narrowed the bug down, but it seems to occur only with the face tracking module and when FilterByStreamProfiles() is not called before init. When just the blob tracking module is enabled, init returns with an error code as expected.
An easy way to reproduce this bug is to take the Face Tracking C# SDK sample, comment out FaceTracking.cs line 103:
//captureMgr.FilterByStreamProfiles(set);
and run the sample with the camera unplugged (if you can, obviously you can't do this on a device with integrated camera). Calling FilterByStreamProfiles() before init somehow makes the problem go away, even if the application is not using any image streams.
Expected behavior would be that without a camera SenseManager.Init() would return always an error code and not get stuck indefinitely.
