<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Misterblue</title>
		<description>Not 'blue' like the mood, but blue like the sky, blue like the bird, blue like the ocean.
</description>
		<link>http://blog.misterblue.com</link>
		<atom:link href="http://blog.misterblue.com/feed.xml" rel="self" type="application/rss+xml" />
		
			<item>
				<title>WebRtc Update Grid</title>
				<description>&lt;p&gt;Some progress on WebRtc for &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus&quot;&gt;os-webrtc-janus&lt;/a&gt; has been updated with the grid connector.
This means that a region can be pointed to a grid service that implements
the WebRTC voice function. Thus, a grid can provide voice for all
the regions in  the grid.&lt;/p&gt;

&lt;p&gt;For the grid, the voice service is a Robust module so a grid can 
add it to all the other Robust modules or, to distribute the load,
a Robust service that provides only the voice service is possible.
See the description and instructions at &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus&quot;&gt;os-webrtc-janus&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;At the region level, a region can provide a spatial voice service
for just the region and send the non-spatial (group and person-to-person chat)
to the grid voice service.&lt;/p&gt;

&lt;p&gt;I have also updated the README for &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus-docker&quot;&gt;os-webrtc-janus-docker&lt;/a&gt; which is a Docker
image for running the &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt; WebRTC voice server.
The instructions include Linux and Windows operation.&lt;/p&gt;

&lt;p&gt;I also have region in &lt;a href=&quot;https://osgrid.org&quot;&gt;OSGrid&lt;/a&gt; that has WebRTC based voice. Visit &lt;a href=&quot;hop://hg.osgrid.org:80/Blueland/253/92/35&quot;&gt;Blueland&lt;/a&gt;
and see if anyone is there talking.
&lt;a href=&quot;hop://hg.osgrid.org:80/Blueland/253/92/35&quot;&gt;Blueland&lt;/a&gt; is running as a &lt;a href=&quot;https://www.docker.com&quot;&gt;Docker&lt;/a&gt; container built with &lt;a href=&quot;https://github.com/Misterblue/opensim-docker&quot;&gt;opensim-docker&lt;/a&gt;
and the &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt; server is a Docker container built by &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus-docker&quot;&gt;os-webrtc-janus-docker&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;There is still a lot of things to complete:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;spatial code modifications to Janus&lt;/li&gt;
  &lt;li&gt;voice controls (mute, volume, …)&lt;/li&gt;
&lt;/ul&gt;

</description>
				<pubDate>Thu, 09 Jan 2025 11:55:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2025/2025-01-09-webrtc-update-grid</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2025/2025-01-09-webrtc-update-grid</guid>
			</item>
		
			<item>
				<title>OpenSim WebRtc Update</title>
				<description>&lt;p&gt;I have WebRtc kinda working for &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt; and I gave a presentation
on it at OpenSimulator Community Conference &lt;a href=&quot;https://conference.opensimulator.org/&quot;&gt;OSCC24&lt;/a&gt;:  &lt;a href=&quot;https://docs.google.com/presentation/d/1WUULV5dwnAWooWtqinJGd-1h6-OT7Hvd_mlOdWc9DVU/edit?usp=sharing&quot;&gt;WebRTC Voice for OpenSim&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I also have region in &lt;a href=&quot;https://osgrid.org&quot;&gt;OSGrid&lt;/a&gt; that has WebRTC based voice. Visit &lt;a href=&quot;hop://hg.osgrid.org:80/Blueland/253/92/35&quot;&gt;Blueland&lt;/a&gt;
and see if anyone is there talking.
&lt;a href=&quot;hop://hg.osgrid.org:80/Blueland/253/92/35&quot;&gt;Blueland&lt;/a&gt; is running as a &lt;a href=&quot;https://www.docker.com&quot;&gt;Docker&lt;/a&gt; container built with &lt;a href=&quot;https://github.com/Misterblue/opensim-docker&quot;&gt;opensim-docker&lt;/a&gt;
and the &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt; server is a Docker container built by &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus-docker&quot;&gt;os-webrtc-janus-docker&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The code is in &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus&quot;&gt;os-webrtc-janus&lt;/a&gt; as an &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt; addin-module. That is,
you clone the repository into the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;addin-module&lt;/code&gt; directory of the &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt;
sources, do a &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;runprebuild&lt;/code&gt;, and then build the simulator.&lt;/p&gt;

&lt;p&gt;There is still a lot of things to complete:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;spatial code modifications to Janus&lt;/li&gt;
  &lt;li&gt;voice controls (mute, volume, …)&lt;/li&gt;
  &lt;li&gt;connection to the grid server&lt;/li&gt;
  &lt;li&gt;hardening&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want to help with the coding, join me at &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus&quot;&gt;os-webrtc-janus&lt;/a&gt; and checkout
the &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus/issues&quot;&gt;issues&lt;/a&gt; and the &lt;a href=&quot;https://github.com/users/Misterblue/projects/7&quot;&gt;project&lt;/a&gt;.
Please test the features and make some &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus/issues&quot;&gt;issues&lt;/a&gt; and this will eventually get
integrated into all &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt; regions and grids.&lt;/p&gt;

</description>
				<pubDate>Sat, 07 Dec 2024 10:44:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2024/2024-12-07-opensim-webrtc-update</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2024/2024-12-07-opensim-webrtc-update</guid>
			</item>
		
			<item>
				<title>WebRtc Voice for OpenSim</title>
				<description>&lt;p&gt;I haven’t been updating this blog lately so I thought I’d add something today.&lt;/p&gt;

&lt;p&gt;I’ve been working on adding webrtc voice to &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt; using
the &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt; webrtc server.&lt;/p&gt;

&lt;p&gt;To use the &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt; server, I’ve created a &lt;a href=&quot;https://www.docker.com&quot;&gt;Docker&lt;/a&gt; container
for running the server configured up for &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt;.
Check out &lt;a href=&quot;https://github.com/Misterblue/os-webrtc-janus-docker&quot;&gt;os-webrtc-janus-docker&lt;/a&gt; for details.
That allows the running of the voice service separate from a region or a
grid server and, hopefully, eventually allows scaling.
I’m using the &lt;a href=&quot;https://janus.conf.meetecho.com/docs/audiobridge.html&quot;&gt;audio bridge&lt;/a&gt; plugin in &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt; to create “rooms”
for group and region sessions.
That allows the mixing of audio for an area.
Initially, there won’t be spacial voice mixing but I expect future work
to add that to a fork of the &lt;a href=&quot;https://janus.conf.meetecho.com/docs/audiobridge.html&quot;&gt;audio bridge&lt;/a&gt; plugin for &lt;a href=&quot;https://janus.conf.meetecho.com&quot;&gt;Janus&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I’ve submitted a presentation for this project to &lt;a href=&quot;https://conference.opensimulator.org/&quot;&gt;OSCC24&lt;/a&gt; that happens
in early December so I have a deadline. Insert “freak out” emoji.&lt;/p&gt;

</description>
				<pubDate>Mon, 28 Oct 2024 14:03:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2024/2024-10-28-webrtc-voice-for-opensim</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2024/2024-10-28-webrtc-voice-for-opensim</guid>
			</item>
		
			<item>
				<title>Writing Down Projects</title>
				<description>&lt;p&gt;It’s been a long year and I’ve done a bunch of misc project support but haven’t
done any of the larger projects I listed last year.
No major deliverables.&lt;/p&gt;

&lt;p&gt;So, what’s up now? I’m still interested in the
&lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt;
virtual worlds but have been spending time supporting various spin-offs:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/OpenSim-NGC&quot;&gt;NGC&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/JennaScvl/Crystal-Frost-Viewer&quot;&gt;CrystalFrost&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So, what do I want to accomplish in the next few months? Some possibilities are:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;AIS Inventory&lt;/strong&gt;: add newer SL inventory interfaces to OpenSimulator.
  This means coding the inventory capability. It would contain the base code
  with the HTTP interface separate so that the code could be used for
  both OpenSimulator core (as a region module) and in NGC as a service.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;ASync Interface for libreMetaverse&lt;/strong&gt;: 
  Several viewer projects are using libreMetaverse as their connection to the
  simulator. The internal API needs an update from the callback form to
  the newer Task model. Along the way, I’d like to document the internal
  API and thus make it easier for new people to use.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;strong&gt;OpenSimulator interface for GLTF content&lt;/strong&gt;:
  I had the odd idea of creating a “capability” (modular API unit of the client/simulator
  interface) that returned GLTF versions of assets.
  That is, rather than inventing a new way of fetching GLTF items like I did for
  the &lt;a href=&quot;https://github.com/Herbal3d/basil&quot;&gt;Basil viewer&lt;/a&gt;
  , a viewer could see that the feature is available (in the list of available
  capabilities received at login) and thus fetch the GLTF versions.
  This is would incorporate
  &lt;a href=&quot;https://github.com/Misterblue/convoar&quot;&gt;convoar&lt;/a&gt;
  code in a way usable by different systems.
  I think this also might include adding
  &lt;a href=&quot;https://www.w3.org/TR/webtransport/&quot;&gt;WebTransport&lt;/a&gt;
  communication connection to OpenSimulator for browser based viewers.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last project is a slightly different approach to what I did for Basil.
I had created a new protocol and built region modules (Ragu, Loden, …) to
implement the protocol. I still like the idea of creating a Wayland-like
protocol for separating the viewer from world logic but that’s for another time.&lt;/p&gt;
</description>
				<pubDate>Wed, 17 Jul 2024 18:29:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2024/2024-07-17-writing-down-projects</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2024/2024-07-17-writing-down-projects</guid>
			</item>
		
			<item>
				<title>Possible Projects</title>
				<description>&lt;p&gt;I’m at a decision point – there are so many possible software projects and I can’t decide
which one to choose. Here is a possible list:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Basil viewer&lt;/strong&gt;: this is advancing the features of the viewer.
  It includes implementing avatars, adding scene rendering features (water, …),
  and updating the UI to be the WASM modules that run in the client to provide
  world and UI operation.
    &lt;ul&gt;
      &lt;li&gt;Avatar movement&lt;/li&gt;
      &lt;li&gt;Avatar implementation&lt;/li&gt;
      &lt;li&gt;Shaders for water, lighting, scene&lt;/li&gt;
      &lt;li&gt;Child/adjacent regions&lt;/li&gt;
      &lt;li&gt;WASM UI implementation&lt;/li&gt;
      &lt;li&gt;Reactor into peoperty updates and optional sync back to server&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Loden&lt;/strong&gt;: work on creating the assets for the browser viewer.
  These things are also useful in other projects (like Convoar and Unity viewer).
  There are some refactoring (textures) but mostly is creating the 3d tiles version
  of the region. Also use the real asset database.
    &lt;ul&gt;
      &lt;li&gt;Integration with grid asset server (solve the access key (capabilities?))&lt;/li&gt;
      &lt;li&gt;Move texture resizing out of the GLTF generator&lt;/li&gt;
      &lt;li&gt;S3 asset storage&lt;/li&gt;
      &lt;li&gt;Create individual GLTF assets on demand&lt;/li&gt;
      &lt;li&gt;Create region 3dTiles down to the individual assets&lt;/li&gt;
      &lt;li&gt;Create avatar to GLTF
        &lt;ul&gt;
          &lt;li&gt;Close to VRM format and can be used with https://github.com/vrm-c/UniVRM and Unity&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;OpenSimulator 3d voice service&lt;/strong&gt;: OpenSimulator needs a spacial voice replacement.
  On candidate is the voice mixer from HiFi/Overte. The work is figuring out
  how the scalable service is invoked and then adding a Vivox API to the mixer
  (that already has a WebRTC-data and Overte interface). Probably should have a
  plain WebRTC interface also. That could make it generally useful for other VWs.
    &lt;ul&gt;
      &lt;li&gt;Research the Overte voice service&lt;/li&gt;
      &lt;li&gt;Research the Vivox protocol (viewer to server)&lt;/li&gt;
      &lt;li&gt;Research the avatar position protocol (simuilator to audio server)&lt;/li&gt;
      &lt;li&gt;Understand OS capabilities: how generated and passed around&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;GLTF Avatar for OpenSimulator&lt;/strong&gt;: Related to the Loden work, making a GLTF
  version of the OS avatar would be useful in many places. The avatars could
  be used in other VWs as well as the CrystalFrost viewer (see (UniVRM)[https://github.com/vrm-c/UniVRM] ).
    &lt;ul&gt;
      &lt;li&gt;Research VRM format&lt;/li&gt;
      &lt;li&gt;Research OS avatar format
        &lt;ul&gt;
          &lt;li&gt;Seems to be Bento bones but a lot of work on mesh modes with sliders&lt;/li&gt;
          &lt;li&gt;(Viewer-Character)[https://github.com/vrm-c/UniVRM]&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Convoar&lt;/strong&gt;: Based on the changes to Loden, add GLTF extensions that contain
  all of the OpenSimulator asset information (creator, transferable, …).
    &lt;ul&gt;
      &lt;li&gt;Add GLTF extensions that includes the raw OS prim information&lt;/li&gt;
      &lt;li&gt;Add GLTF extension to hold ownership, etc&lt;/li&gt;
      &lt;li&gt;Add Identity to creator
        &lt;ul&gt;
          &lt;li&gt;This might include DIDs or some other identity info&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There could be more.&lt;/p&gt;
</description>
				<pubDate>Tue, 30 May 2023 18:29:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2023/2023-05-30-possible-projects</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2023/2023-05-30-possible-projects</guid>
			</item>
		
			<item>
				<title>TIL (Today I Learned) About c++filt</title>
				<description>&lt;p&gt;I’ve been working on this project&lt;sup id=&quot;fnref:1&quot; role=&quot;doc-noteref&quot;&gt;&lt;a href=&quot;#fn:1&quot; class=&quot;footnote&quot; rel=&quot;footnote&quot;&gt;1&lt;/a&gt;&lt;/sup&gt; where I’m compiling different C++ libraries
and statically linking them together.
I had problems with undefined symbols.
And the undefined symbols were mangled C++ symbols.
If you didn’t know, C++ creates “mangled” symbols for all your human readable
symbols to solve the global namespace problems that C++ inherited from C.
The article &lt;a href=&quot;https://blog.oakbits.com/how-to-mangle-and-demangle-a-c-method-name.html&quot;&gt;How To Mangle And Demangle A C++ Method Name&lt;/a&gt; explains it well.&lt;/p&gt;

&lt;p&gt;The problem I had was that one library had the symbol 
&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;_ZNK16btCollisionShape17getBoundingSphereER9btVector3Rd&lt;/code&gt;
and another library referenced
&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;_ZNK16btCollisionShape17getBoundingSphereER9btVector3Rf&lt;/code&gt;
.
What was different?&lt;/p&gt;

&lt;p&gt;Well, the above referenced article references the “well known” tool of &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;c++filt&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Of course!!&lt;/p&gt;

&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;user@ubuntu ~&amp;gt; c++filt _ZNK16btCollisionShape17getBoundingSphereER9btVector3Rd
btCollisionShape::getBoundingSphere(btVector3&amp;amp;, double&amp;amp;) const
user@ubuntu ~&amp;gt; c++filt _ZNK16btCollisionShape17getBoundingSphereER9btVector3Rf
btCollisionShape::getBoundingSphere(btVector3&amp;amp;, float&amp;amp;) const
user@ubuntu ~&amp;gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Looks like I am building one library with double precision turned on
and the other was referencing it with double precision turned off.
Now I know what to fix.&lt;/p&gt;

&lt;p&gt;There are just so many tools in Linux.&lt;/p&gt;

&lt;hr /&gt;

&lt;div class=&quot;footnotes&quot; role=&quot;doc-endnotes&quot;&gt;
  &lt;ol&gt;
    &lt;li id=&quot;fn:1&quot; role=&quot;doc-endnote&quot;&gt;
      &lt;p&gt;BulletSim in &lt;a href=&quot;http://opensimulator.org&quot;&gt;OpenSimulator&lt;/a&gt; &lt;a href=&quot;#fnref:1&quot; class=&quot;reversefootnote&quot; role=&quot;doc-backlink&quot;&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
    &lt;/li&gt;
  &lt;/ol&gt;
&lt;/div&gt;
</description>
				<pubDate>Sat, 24 Dec 2022 07:35:21 +0000</pubDate>
				<link>http://blog.misterblue.com/2022/2022-12-24-TIL-cppfilt</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2022/2022-12-24-TIL-cppfilt</guid>
			</item>
		
			<item>
				<title>Loadable Abilities for Basil</title>
				<description>&lt;p&gt;Had this idea the other day.&lt;/p&gt;

&lt;p&gt;The Basil protocol is built around &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;entities&lt;/code&gt; and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;abilities&lt;/code&gt;.
The SpaceServer creates entities in the Basil viewer and adds abilities
to that entity.
The abilities add attributes to the entity and the values of the
attributes effect the entity’s actions in the rendered world.
So, there would be abilities like “camera follow” which would be
added to a camera entity to cause the camera to follow something
(usually an avatar). Or maybe “instance” which adds “pos” and “rot”
properties to an entity and makes it appear somewhere in the view.&lt;/p&gt;

&lt;p&gt;One problem with that design would be that  the abilities need
to be embedded into Basil. That is, abilities would have to be part
of Basil’s protocol definition (this are the abiltities that are defined)
and thus would be rather static.&lt;/p&gt;

&lt;p&gt;Also, abilities could get very complex. Like adding an animation
to a boned entity. Or just adding the bones. There might be scripted
behaviors for entities that is required to be implemented in the viewer for
latency issues.&lt;/p&gt;

&lt;p&gt;So, the idea I had was: what if I could upload abilities? I could
define an API to the Basil entity internals and then individual
ability behaviors could be coded separately and dynamically added
to Basil.&lt;/p&gt;

&lt;p&gt;Since the first Basil is for the browser, the abilities could be
Javascript code. But then I thought, what about [WebAssembly]?
That has the advantages of making other languages available as
well as not being tied to the browser since there are engines
for different languages and OS’s.&lt;/p&gt;

&lt;p&gt;An interesting idea. It would mean cleaning up the intefaces inside
Basil (which is a good thing in any case). Standardizing an internal
API. And then figuring out [WebAssembly].&lt;/p&gt;

&lt;p&gt;Hummm. I wonder…&lt;/p&gt;

&lt;p&gt;[Basil]: 
[WebAssembly]: https://webassembly.org/&lt;/p&gt;
</description>
				<pubDate>Tue, 08 Feb 2022 17:08:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2022/2022-02-08-loadable-abilities</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2022/2022-02-08-loadable-abilities</guid>
			</item>
		
			<item>
				<title>OpenSim Docker V2 to V3</title>
				<description>&lt;p&gt;Since I’ve started playing with &lt;a href=&quot;https://herbal3d.org&quot;&gt;Herbal3d&lt;/a&gt; again (more on that later), I need to have an easy way of running my modified &lt;a href=&quot;http://opensimulator.org/&quot;&gt;OpenSimulator&lt;/a&gt; instances.
Thus, I’ve gone back and updated my old &lt;a href=&quot;https://github.com/misterblue/opensim-docker/&quot;&gt;opensim-docker&lt;/a&gt; project.&lt;/p&gt;

&lt;p&gt;I first updated from V1 to V2 by updating OpenSimulator configuration files to the latest versions and then reworking the code so it is easier to understand.&lt;/p&gt;

&lt;p&gt;That last problem was that it was a muddle of which image was being created and which runtime configuration was to be used. So now there are clearly two images (found in the directories &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;image-opensim&lt;/code&gt; and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;image-herbal3d&lt;/code&gt;) and there are multiple configurations for those images in the image directories.&lt;/p&gt;

&lt;p&gt;I also debugged the SQL version so it properly creates a standalone region and connects to the separately spun up database container.&lt;/p&gt;

&lt;p&gt;After working on V2, I have come to feel that the idea of putting the configuration and the secrets for the configuration into the &lt;a href=&quot;https://www.docker.com/&quot;&gt;Docker&lt;/a&gt; image is wrong.&lt;/p&gt;

&lt;p&gt;Thus version 3 is born.&lt;/p&gt;

&lt;p&gt;The plan is to fix &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;docker-config&lt;/code&gt; to mount the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;config&lt;/code&gt; directory in the user’s space. The process then becomes to clone the repository, build your image, edit the configuration information in the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;config&lt;/code&gt; directory, and finally start the container.&lt;/p&gt;

</description>
				<pubDate>Fri, 04 Feb 2022 11:22:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2022/2022-02-04-opensim-docker-v2-to-v3</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2022/2022-02-04-opensim-docker-v2-to-v3</guid>
			</item>
		
			<item>
				<title>Notes on v-web Metaverse</title>
				<description>&lt;p&gt;There has been some discussion on adding metaverse selection to &lt;a href=&quot;https://github.com/vircadia/vircadia-web&quot;&gt;Vircadia-Web&lt;/a&gt; (here after “v-web”) and this note talks about how the existing code could be modified.&lt;/p&gt;

&lt;p&gt;Currently (as of Feb 4, 2022), v-web has a default metaverse URL that is used to fetch the metaverse information and is used as the metaverse to log the user into.
This default metaverse is specified in &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@Base/config.ts&lt;/code&gt; and is connected when the main view is mounted (in &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;App.vue&lt;/code&gt;).&lt;/p&gt;

&lt;p&gt;The real work connecting to a metaverse is in &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@Modules/Utility.metaverseConnectionSetup()&lt;/code&gt; which calls &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;MetaverseMgr.metaverseFactory()&lt;/code&gt; to create a new metaverse connection class instance. This operation also has the side effect of making the network connection to the metaverse, setting the “active” metaverse, and updating the metaverse information in the Vue variable $store. So the overall effect of calling &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;metaverseConnectionSetup()&lt;/code&gt; is to change the active metaverse and update all the display variables. The only work needed here is that the previous metaverse class instance is not saved or freed.&lt;/p&gt;

&lt;p&gt;Looking at the user interface, there is a “Click to log in to metaverse” text at the top of the page. Clicking this opens the “Metaverse Login” dialog (&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@Components/dialogs/Login.vue&lt;/code&gt;). This dialog has fields for username and password. If this dialog has a “metaverse” field added that had the default metaverse URL preloaded then the user could enter a new metaverse URL if logging into a different metaverse. The action would be, when the user pressed “Login”, the code would check if the metaverse URL had changed and, if so, call &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;metaverseConnectionSetup()&lt;/code&gt; with the new URL before logging in the user. This would change the active metaverse and set up  the application to use the new metaverse (Explore and other operations use the active metaverse).&lt;/p&gt;

&lt;p&gt;As a side note, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@Base/config.ts&lt;/code&gt; has code to save some variables in the browser’s local storage. If the user is specifying a different default metaverse, there should be some place that does a &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Config.setItem(DEFAULT_METAVERSE_URL, newURL)&lt;/code&gt;.&lt;/p&gt;

</description>
				<pubDate>Fri, 04 Feb 2022 09:12:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2022/2022-02-04-notes-on-v-web-metaverse</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2022/2022-02-04-notes-on-v-web-metaverse</guid>
			</item>
		
			<item>
				<title>ROS2 Sending Image</title>
				<description>&lt;p&gt;I don’t know why this is not documented better but…&lt;/p&gt;

&lt;p&gt;While I was porting my
&lt;a href=&quot;https://github.com/Misterblue/ros2-looker&quot;&gt;old ROS2 Python test application&lt;/a&gt;
to the newest ROS2 Foxy
on my Raspberry Pi’s, I discovered that I needed to use OpenCV
to capture images because
&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;picamera&lt;/code&gt; does not work in 64 bit](https://github.com/waveform80/picamera/issues/540)
.&lt;/p&gt;

&lt;p&gt;What’s not documented very well (and I spent several days figuring out)
is that, after one has ported to OpenCV,
converting an OpenCV image into a ROS2 message is not obvious.
After a bunch of Google’ing, one discovers that the ROS2 folks
have packaged all the magic into a module called &lt;a href=&quot;http://docs.ros.org/en/lunar/api/cv_bridge/html/python/index.html&quot;&gt;CvBridge&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;OpenCV keeps images in &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;cv:im&lt;/code&gt; structures
and converting that into a byte array that fits into the ROS2 message
is tricky. Actually, what’s expected in a ROS2 image message is not
documented very well so what works is hard to figure out in the first
place.&lt;/p&gt;

&lt;p&gt;The ROS2 developers have created some tools for the OpenCV users
and one is a tool that converts OpenCV images into ROS2 image messages.
So, the code ends up looking like:&lt;/p&gt;

&lt;div class=&quot;language-python highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;&lt;span class=&quot;kn&quot;&gt;from&lt;/span&gt; &lt;span class=&quot;nn&quot;&gt;sensor_msgs.msg&lt;/span&gt; &lt;span class=&quot;kn&quot;&gt;import&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;Image&lt;/span&gt;
&lt;span class=&quot;kn&quot;&gt;import&lt;/span&gt; &lt;span class=&quot;nn&quot;&gt;cv2&lt;/span&gt;
&lt;span class=&quot;kn&quot;&gt;from&lt;/span&gt; &lt;span class=&quot;nn&quot;&gt;cv_bridge&lt;/span&gt; &lt;span class=&quot;kn&quot;&gt;import&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;CvBridge&lt;/span&gt;
&lt;span class=&quot;p&quot;&gt;...&lt;/span&gt;
&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;bridge&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;CvBridge&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;
&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;camera&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;cv2&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;VideoCapture&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;0&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;
&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;frame_num&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;mi&quot;&gt;0&lt;/span&gt;
&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;publisher&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;create_publisher&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Image&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;&quot;topic&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;mi&quot;&gt;10&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;
&lt;span class=&quot;p&quot;&gt;...&lt;/span&gt;
&lt;span class=&quot;n&quot;&gt;ret&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;frame&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;camera&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;read&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;
&lt;span class=&quot;k&quot;&gt;if&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;ret&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;==&lt;/span&gt; &lt;span class=&quot;bp&quot;&gt;True&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;
    &lt;span class=&quot;n&quot;&gt;msg&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;bridge&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;cv2_to_imgmsg&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;frame&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;&apos;bgr8&apos;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;
    &lt;span class=&quot;n&quot;&gt;msg&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;header&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;frame_id&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;nb&quot;&gt;str&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;frame_num&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;   &lt;span class=&quot;c1&quot;&gt;# &apos;msg&apos; is a ROS2 sensor_msgs/Image.msg
&lt;/span&gt;    &lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;frame_num&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;+=&lt;/span&gt; &lt;span class=&quot;mi&quot;&gt;1&lt;/span&gt;
    &lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;publisher&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;publish&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;msg&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;That is, don’t try to create the image message yourself.
Instead, rely on the &lt;a href=&quot;http://docs.ros.org/en/lunar/api/cv_bridge/html/python/index.html&quot;&gt;CvBridge&lt;/a&gt; package to create the whole message
and then fill it in with other information.&lt;/p&gt;

</description>
				<pubDate>Sat, 29 May 2021 21:51:20 +0000</pubDate>
				<link>http://blog.misterblue.com/2021/2021-05-29-ros2-sending-image</link>
				<guid isPermaLink="true">http://blog.misterblue.com/2021/2021-05-29-ros2-sending-image</guid>
			</item>
		
	</channel>
</rss>
