search

microsoft / HoloLensForCV

Sample code and documentation for using the Microsoft HoloLens for Computer Vision research
MIT License
472 stars 156 forks source link

Recorder App: All sensor streams frames are null #141

Open rustycandlewick opened 3 years ago

rustycandlewick commented 3 years ago

Hi Everyone,

I've been having a problem with the Recorder app, where it doesn't run properly on my Hololens device. The Start menu does not show up when the app is deployed and run, and when I check the output console, the MediaFrameReaderContext::FramedArrived keeps saying the frame is null for all the sensor streams. The app deploys without any errors, so I was wondering if anyone knew why this problem is occurring and how I can fix it. I've tried retargeting the solution and recloning the repository in a new project, and my other apps such as StreamerPV and StreamerVLC seem to be working.

Thanks!

emeraldy commented 3 years ago

hello,

You just need to do an air tap after the app runs to start recording and air tap again to stop. The app doesn't seem to have any UI but I saw some voice feedback in it logic in it, not sure why it doesn't work. The recorded files can be found under LocalAppData\CV:Recorder\TempState by default when you select File explorer in the device portal.

rustycandlewick commented 3 years ago

Hi,

Thanks for the response! The problem is my screen is black and there is no air tap option and the files are not saved to the file explorer. Therefore, I think there is a problem with either the device itself or the app itself.

emeraldy commented 3 years ago

hello,

I built the app from a freshly downloaded zip of the repository and it worked. Yes, when i ran it, there was nothing shown in HoloLens view and there were frame null messages scrolling out in the output window of VS but if you just do an air tap regardless, the recording will start and after you are done, do another air tap to stop the recording and then if you go to that path I mentioned in my last post, you will find the files there. I think that's just how the app works, a barebone demo for recording. As for why there are frame null messages pumping out, I am afraid you will need to go through the code to figure it out if you have the time. On a side note, if you want the user interaction to be a little fancier, you can uncomment the #define at line 15, which should activate the voice command feature but i haven't tested that.