device.0 versus device.1

4 views
Skip to first unread message

d.andrew STEWART

unread,
May 13, 2026, 5:40:41 AM (8 days ago) May 13
to dot_mapper
Please can anyone remind me how libmapper/webmapper assigns the suffix number to each device? On my system, I have a device, built in Max, that shows up as "DeviceName.1". Running the same Max patch on a different computer, the device shows up as "DeviceName.0"

Is there any way to force device number  ".1", please?

NOTE:  I am running webmapper from source code with the following cmd line: python3 webmapper.py --iface lo0

Joseph Malloch

unread,
May 13, 2026, 11:53:28 AM (7 days ago) May 13
to dot_m...@googlegroups.com
Hi Andrew,

This is a bit mysterious, but I think the device is somehow being blocked from registering properly. Is there any information posted to the Max console when the mpr.device object is created? Once registered it should print “Joining mapping network as ‘X’"

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/1ec9a545-a21e-4d55-873b-cc6d452b473an%40googlegroups.com.

d.andrew STEWART

unread,
May 15, 2026, 1:15:28 PM (5 days ago) May 15
to dot_mapper
Thanks for this. Sadly, this situation was on a colleague's computer (in Montreal). So, I can't debug personally with them. We'll see........  With the limited time we had (my colleague and I),  we unsuccessfully ran webmapper/libmapper; however, I think it was because he did not have a compatible version of the Max externals – he had an older version. We ran out of time, together, and were unable to verify. I can say the the "source" and "destination" Devices ".0" appeared in webmapper, but no mapping connections could be drawn.  Again, I think this was due to the incompatible Max externals.
Reply all
Reply to author
Forward
0 new messages