nosy-b/holography

Not working so debugged: This version apparently not finding resources?

Opened this issue · 2 comments

evaristoc commented

Hi @nosy-b,

I was curious about your project but it was not working. I debugged a bit and found the following:

  1. An issue with tensorflow.js? In DevTools:
DevTools failed to load SourceMap: Could not load content for https://cdn.jsdelivr.net/npm/@tensorflow/tf.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for https://cdn.jsdelivr.net/npm/@tensorflow-models/body-pix.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
  1. getCapabilities points to an object that might not be the same in all devices?
getCapabilities() error:  TypeError: Cannot read property 'max' of undefined

where max is property of zoom which doesn't shows in my device.

Hopes this helps?

I haven't tried to make any correction yet so I don't know. I will post if find something. I will fork yours.

evaristoc commented

I got a better debugging and found that:

  1. The eventListener of the controller might take some time - not really a big issue actually...
  2. In my case, I got the following error after select: grabFrame() error: DOMException: The associated Track is in an invalid state. . This is probably affecting the image capture.

A possible solution for the second issue might be found at: https://stackoverflow.com/questions/60693519/javascript-domexception-the-associated-track-is-in-an-invalid-state. Wondering if there is a conflict issue between mediadevices and xr APIs? Probably solved with more than 1 camera?

nosy-b commented

Hi! Thanks for the comments!
I'll update the code, Tensorflow new version changed the sources structure and I've to update camera handling, got a pixel phone to test that