Search
1000 results for “localjoost”
-
#MRTK3 has a subsystem implementation for speech commands that is supported by #HoloLens2. #MagicLeap2 supports voice commands as well, if only someone had taken the trouble of making a KeywordRecognitionSubsystem implementation of it, it would have had MRTK3 support for speech commands as well.
Well, guess what - someone just did. Me. So now you can have voice commands on *both* devices using the same API, and you only need to flip a checkbox in the MRTK3 settings.
https://localjoost.github.io/An-MRTK3-KeywordRecognitionSubsystem-for-Magic-Leap-2/
-
#MRTK3 has a subsystem implementation for speech commands that is supported by #HoloLens2. #MagicLeap2 supports voice commands as well, if only someone had taken the trouble of making a KeywordRecognitionSubsystem implementation of it, it would have had MRTK3 support for speech commands as well.
Well, guess what - someone just did. Me. So now you can have voice commands on *both* devices using the same API, and you only need to flip a checkbox in the MRTK3 settings.
https://localjoost.github.io/An-MRTK3-KeywordRecognitionSubsystem-for-Magic-Leap-2/
-
#MRTK3 has a subsystem implementation for speech commands that is supported by #HoloLens2. #MagicLeap2 supports voice commands as well, if only someone had taken the trouble of making a KeywordRecognitionSubsystem implementation of it, it would have had MRTK3 support for speech commands as well.
Well, guess what - someone just did. Me. So now you can have voice commands on *both* devices using the same API, and you only need to flip a checkbox in the MRTK3 settings.
https://localjoost.github.io/An-MRTK3-KeywordRecognitionSubsystem-for-Magic-Leap-2/
-
#MRTK3 has a subsystem implementation for speech commands that is supported by #HoloLens2. #MagicLeap2 supports voice commands as well, if only someone had taken the trouble of making a KeywordRecognitionSubsystem implementation of it, it would have had MRTK3 support for speech commands as well.
Well, guess what - someone just did. Me. So now you can have voice commands on *both* devices using the same API, and you only need to flip a checkbox in the MRTK3 settings.
https://localjoost.github.io/An-MRTK3-KeywordRecognitionSubsystem-for-Magic-Leap-2/
-
#MRTK3 has a subsystem implementation for speech commands that is supported by #HoloLens2. #MagicLeap2 supports voice commands as well, if only someone had taken the trouble of making a KeywordRecognitionSubsystem implementation of it, it would have had MRTK3 support for speech commands as well.
Well, guess what - someone just did. Me. So now you can have voice commands on *both* devices using the same API, and you only need to flip a checkbox in the MRTK3 settings.
https://localjoost.github.io/An-MRTK3-KeywordRecognitionSubsystem-for-Magic-Leap-2/
-
When debugging problems after-the-fact, you can always use UnityPlayer.log. On #HoloLens2, that is. On other devices - for instance #MagicLeap2 - that's not available. So I wrote a little #ServiceFramework service to dump #Unity logfiles in a file for an app running on a device. While I was at it, I included filtering on keywords and log type as well.
-
When debugging problems after-the-fact, you can always use UnityPlayer.log. On #HoloLens2, that is. On other devices - for instance #MagicLeap2 - that's not available. So I wrote a little #ServiceFramework service to dump #Unity logfiles in a file for an app running on a device. While I was at it, I included filtering on keywords and log type as well.
-
When debugging problems after-the-fact, you can always use UnityPlayer.log. On #HoloLens2, that is. On other devices - for instance #MagicLeap2 - that's not available. So I wrote a little #ServiceFramework service to dump #Unity logfiles in a file for an app running on a device. While I was at it, I included filtering on keywords and log type as well.
-
When debugging problems after-the-fact, you can always use UnityPlayer.log. On #HoloLens2, that is. On other devices - for instance #MagicLeap2 - that's not available. So I wrote a little #ServiceFramework service to dump #Unity logfiles in a file for an app running on a device. While I was at it, I included filtering on keywords and log type as well.
-
When debugging problems after-the-fact, you can always use UnityPlayer.log. On #HoloLens2, that is. On other devices - for instance #MagicLeap2 - that's not available. So I wrote a little #ServiceFramework service to dump #Unity logfiles in a file for an app running on a device. While I was at it, I included filtering on keywords and log type as well.
-
I get a lot of questions from developers about #MixedReality in general and #MRTK3 in particular. One developer wanted to know how you could find the actual *position* of an air tap. I found out, and of course blogged it: https://localjoost.github.io/Getting-raw-air-taps-and-their-positions-with-MRTK3/
-
After successfully updating #HoloATC to #MRTK3 GA, I felt confident I could upgrade the #Augmedit #Lumi #HoloLens app as well. I was successful indeed - but there were some more *interesting* things I ran into. I updated my blog post from September significantly with my new findings. https://localjoost.github.io/Upgrading-to-MRTK3-GA-from-a-pre-release-some-assembly-required/
-
For my second blogpost of the day ;) one of my more infamous and far-fetched experiments encompasses the combination of #MachineLearning combined with a Spatial Map to recognize and locate objects in 3D space, using a #YoloV8 #computervision model. This worked pretty well on #HoloLens2. I got it to work on #MagicLeap2 as well, but it was quite a rocky road. The #RealityCollective #ServiceFramework to the rescue :). Explanation, sample and full code at: https://localjoost.github.io/Running-a-YoloV8-model-on-a-Magic-Leap-2-to-recognize-objects-in-3D-space/
-
For my second blogpost of the day ;) one of my more infamous and far-fetched experiments encompasses the combination of #MachineLearning combined with a Spatial Map to recognize and locate objects in 3D space, using a #YoloV8 #computervision model. This worked pretty well on #HoloLens2. I got it to work on #MagicLeap2 as well, but it was quite a rocky road. The #RealityCollective #ServiceFramework to the rescue :). Explanation, sample and full code at: https://localjoost.github.io/Running-a-YoloV8-model-on-a-Magic-Leap-2-to-recognize-objects-in-3D-space/
-
For my second blogpost of the day ;) one of my more infamous and far-fetched experiments encompasses the combination of #MachineLearning combined with a Spatial Map to recognize and locate objects in 3D space, using a #YoloV8 #computervision model. This worked pretty well on #HoloLens2. I got it to work on #MagicLeap2 as well, but it was quite a rocky road. The #RealityCollective #ServiceFramework to the rescue :). Explanation, sample and full code at: https://localjoost.github.io/Running-a-YoloV8-model-on-a-Magic-Leap-2-to-recognize-objects-in-3D-space/
-
For my second blogpost of the day ;) one of my more infamous and far-fetched experiments encompasses the combination of #MachineLearning combined with a Spatial Map to recognize and locate objects in 3D space, using a #YoloV8 #computervision model. This worked pretty well on #HoloLens2. I got it to work on #MagicLeap2 as well, but it was quite a rocky road. The #RealityCollective #ServiceFramework to the rescue :). Explanation, sample and full code at: https://localjoost.github.io/Running-a-YoloV8-model-on-a-Magic-Leap-2-to-recognize-objects-in-3D-space/
-
For my second blogpost of the day ;) one of my more infamous and far-fetched experiments encompasses the combination of #MachineLearning combined with a Spatial Map to recognize and locate objects in 3D space, using a #YoloV8 #computervision model. This worked pretty well on #HoloLens2. I got it to work on #MagicLeap2 as well, but it was quite a rocky road. The #RealityCollective #ServiceFramework to the rescue :). Explanation, sample and full code at: https://localjoost.github.io/Running-a-YoloV8-model-on-a-Magic-Leap-2-to-recognize-objects-in-3D-space/
-
I wanted to see if I could run one of my more far-fetched #MRTK3 #HoloLens2 samples on #MagicLeap2. Step one was getting a Spatial Map. It was dead easy on HoloLens 2, but less so on Magic Leap 2. I managed to make it work, but there were more challenges than I had anticipated. I blogged my findings to help others avoid the same pitfalls as me.
https://localjoost.github.io/Using-a-Spatial-Mesh-with-MRTK3-on-Magic-Leap-2/
-
I wanted to see if I could run one of my more far-fetched #MRTK3 #HoloLens2 samples on #MagicLeap2. Step one was getting a Spatial Map. It was dead easy on HoloLens 2, but less so on Magic Leap 2. I managed to make it work, but there were more challenges than I had anticipated. I blogged my findings to help others avoid the same pitfalls as me.
https://localjoost.github.io/Using-a-Spatial-Mesh-with-MRTK3-on-Magic-Leap-2/
-
I wanted to see if I could run one of my more far-fetched #MRTK3 #HoloLens2 samples on #MagicLeap2. Step one was getting a Spatial Map. It was dead easy on HoloLens 2, but less so on Magic Leap 2. I managed to make it work, but there were more challenges than I had anticipated. I blogged my findings to help others avoid the same pitfalls as me.
https://localjoost.github.io/Using-a-Spatial-Mesh-with-MRTK3-on-Magic-Leap-2/
-
I wanted to see if I could run one of my more far-fetched #MRTK3 #HoloLens2 samples on #MagicLeap2. Step one was getting a Spatial Map. It was dead easy on HoloLens 2, but less so on Magic Leap 2. I managed to make it work, but there were more challenges than I had anticipated. I blogged my findings to help others avoid the same pitfalls as me.
https://localjoost.github.io/Using-a-Spatial-Mesh-with-MRTK3-on-Magic-Leap-2/
-
I wanted to see if I could run one of my more far-fetched #MRTK3 #HoloLens2 samples on #MagicLeap2. Step one was getting a Spatial Map. It was dead easy on HoloLens 2, but less so on Magic Leap 2. I managed to make it work, but there were more challenges than I had anticipated. I blogged my findings to help others avoid the same pitfalls as me.
https://localjoost.github.io/Using-a-Spatial-Mesh-with-MRTK3-on-Magic-Leap-2/
-
With the arrival of #MRTK3 GA, a fellow developer reported my #Quest passthrough sample appeared to be broken after upgrading. I did some investigation, and fixed it. https://localjoost.github.io/Full-underlay-passthrough-transparency-with-MRTK3-GA-on-Quest-2Pro/
-
To my surprise there is no Store for #MagicLeap2. So how do you alert users to new versions and help them update? I made a little #ServiceFramework Service and some #MRTK3 UI to do just that. https://localjoost.github.io/A-ServiceFramework-Service-to-help-update-Magic-Leap-2-MRTK3-apps/
-
After getting my app running with #MRTK3 on #HoloLens2, I of wanted to try it running on #MagicLeap2 as well. Turned out the Magic Leap MRTK package wasn't quite ready for that, so I hacked a bit around until it was. Or almost entirely was. And blogged about my findings, of course. https://localjoost.github.io/Using-MRTK3-GA-on-Magic-Leap-2/
-
After getting my app running with #MRTK3 on #HoloLens2, I of wanted to try it running on #MagicLeap2 as well. Turned out the Magic Leap MRTK package wasn't quite ready for that, so I hacked a bit around until it was. Or almost entirely was. And blogged about my findings, of course. https://localjoost.github.io/Using-MRTK3-GA-on-Magic-Leap-2/
-
After getting my app running with #MRTK3 on #HoloLens2, I of wanted to try it running on #MagicLeap2 as well. Turned out the Magic Leap MRTK package wasn't quite ready for that, so I hacked a bit around until it was. Or almost entirely was. And blogged about my findings, of course. https://localjoost.github.io/Using-MRTK3-GA-on-Magic-Leap-2/
-
After getting my app running with #MRTK3 on #HoloLens2, I of wanted to try it running on #MagicLeap2 as well. Turned out the Magic Leap MRTK package wasn't quite ready for that, so I hacked a bit around until it was. Or almost entirely was. And blogged about my findings, of course. https://localjoost.github.io/Using-MRTK3-GA-on-Magic-Leap-2/
-
Last Wednesday, the #MRTK3 became GA. An important milestone for the XR community. Today, I subjected my app HoloATC to an upgrade, using it as a guinea pig to get an idea of the issues involved (rather than using my employer's app for that :grin:). I got it to work, but it wasn't entirely smooth sailing. Upgrading from a pre-release requires two steps you would not expect outright, but... anyway, read about it in my blog https://localjoost.github.io/Upgrading-to-MRTK3-GA-from-a-pre-release-some-assembly-required/
-
I just blogged: "#HoloLens AI - training a #Yolo V8 model locally on custom pictures to recognize objects in 3D space" #MRTK3 #AI #Machinelearning
https://localjoost.github.io/HoloLens-AI-training-a-YoloV8-model-locally-on-custom-pictures-to-recognize-objects-in-3D-space/