55 links is the "cap" (maximum) - please help

[d.andrew STEWART]

Hello everyone

55 links is the "cap" (maximum) when loading into Webmapper. 

I can create more than 55, in Webmapper, and save the JSON file.  I currently have a mappings file with 56 "Destinations", which I can verfiy by opening the JSON and counting then number of "Destinations". However, when I load the file into Webmapper (GUI), it caps at 55?

Suggestions?  I will try saving 56 mappings in separate JSON files

D> 

[d.andrew STEWART]

I went back to an earlier mappings file (53 Mappings) and then, rebuilt – gradually adding one mapping at a time. It seems I can surpass 55.  I now have 57 mappings; however, there is some inconsistency.  When I load the 57-mapping JSON, sometimes it works, sometimes I only get 56 connections realised.  I'll keep monitoring the situation to try to find a consistent pattern. Could this issue be related to speed limits and timing of messaging within the programming? Please advise

[Joseph Malloch]

Hi Andrew,

I responded to this question on Friday but perhaps you missed it – the file you provided contains 1 map where the destination is the webmapper “monitor” input. This map should not have been saved and it is the correct behaviour for the map to fail to load since this destination is handled privately by webmapper when you click the monitor button for a signal. This map is used only for webmapper to display the signal values.

The next version of mappersession will have better tests to exclude monitor maps from being saved, but for now they may be included if the monitor is open when you save the mapping.

There is NOT a cap of 55 maps :)

Cheers,

Joe

--
You received this message because you are subscribed to the Google Groups "dot_mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dot_mapper+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dot_mapper/fc2ee05f-06d2-48e6-abed-053909bc7466n%40googlegroups.com.

[d.andrew STEWART]

Thanks for reply, regarding "monitor input".  I'm not exactly sure what this is and , thus, I do not fully understand; however, I'll look at this weekend. Send screenshot to help, if that makese sense to do. 

I guess the question is: how did I `accidentally` map to the monitor input?

 I do know, however, that on sevearl occasions, one mapping connection was missing (consistently).....I'll keep exploring... Thanks again.

[Joseph Malloch]

Hi Andrew,

Briefly: Webmapper also registers itself as a hidden device with one signal named “monitor”. If you click one of the little mouseover eye icons on a signal in list view it will open a rudimentary signal visualizer and show live updates of the signal’s value. In order to get these values webmapper creates a map from the signal you want to view to its own “monitor” signal. This map shouldn’t be included in saved files but in your case it was… the next version of mappersession will include better checks to ensure the map is not included.

Cheers,

Joe

To view this discussion visit https://groups.google.com/d/msgid/dot_mapper/9699b572-2b4b-4d37-8c81-99e65919252an%40googlegroups.com.

[d.andrew STEWART]

Okay this is making some sense. I recently created a Source:  mpr.out /cooked/lefthand/button/front/top/left/tap.  In Webmapper, the final container is "tap" and, thus, visually, the box created for tap is small. As a result, it's easy to accidentally click on the eye icon. Is the "monitor" signal mapping created by clicking on the eye?

[Joseph Malloch]

Yes clicking on the eye should create the map from the signal you clicked to webmapper.n/monitor. It should also open the monitor pane:

Clicking the “close” button on the monitor pane or clicking outside the pane should dismiss the pane and destroy the hidden map.

Cheers,

Joe

On May 22, 2026, at 1:15 PM, d.andrew STEWART <dandrew...@gmail.com> wrote:

Okay this is making some sense. I recently created a Source:  mpr.out /cooked/lefthand/button/front/top/left/tap.  In Webmapper, the final container is "tap" and, thus, visually, the box created for tap is small. As a result, it's easy to accidentally click on the eye icon. Is the "monitor" signal mapping created by clicking on the eye?

<eye.png>

To view this discussion visit https://groups.google.com/d/msgid/dot_mapper/0018c130-f97d-431c-b144-81d8fe206fe6n%40googlegroups.com.
<eye.png>

[d.andrew STEWART]

Hello there.  

An update to say that I continue to see this `odd` loading issue. My mapping .JSON file has 57 connections. Each time I use Webmapper GUI, the system only reads 56 connecitons. The "fix" is simply to reload the same .JSON file - actually, firstly, I delete all 56 connections from withint the GUI and then, reload. At this point, the system does instantiate all 57 connections. 

If this issue concerns one "map where the destination is the webmapper monitor input", is there a way I can verify that the missing connection is, in fact, this hidden monitor input? Should I read the output/log of Terminal.app?  Will that tell me?

This whole issue started becaus I could literally hear that some of my synthesis was behaving differently, because the missing mapping connection was fundamental to the control of timbre. And, in at least one instance, the missing mapping connection was responsible for actually starting a sound.   

I'll do my best to track this and see if I can find a pattern.  

All the best

[Joseph Malloch]

Hi Andrew,

An easy way to check for these stray maps is to open your .json file in a text editor and search for “webmapper” – any maps involving the signal “webmapper.N/monitor” will likely not load and shouldn’t since they have nothing to do with your actual mapping.

So if your file contains 57 maps but one of them has "webmapper.1/monitor” as the destination you should only expect 56 maps to load.

If you can hear a difference the problem is definitely not the monitor maps since they have no effect on you synth. Perhaps we should add a feature to mappersession that displays any differences between the current state and a mapping file? In my tests your mapping file loaded perfectly every time (with the exception of the monitor map) but I wasn’t using your Max patches – I just created mock devices that had all the signals featured in the mapping file. Feel free to DM me the patches if you want me to try more testing.

Cheers,

Joe

To view this discussion visit https://groups.google.com/d/msgid/dot_mapper/d0534cf0-bfee-4b82-bf53-7a907c37ed25n%40googlegroups.com.