Chrome having issues opening .JSON mapping file

[d.andrew STEWART]

Hi everyone,

I'm working with Benjamin Lavastre, trying to SAVE and OPEN mapping files in Webmapper. We can successfully build the mappings and save, but when we open the saved mapping file (JSON), Webmapper is not re-drawing the connections.

To be clear, after creating some mappings manually – the regular way – connections between Source and Destination are working.  However if we then start from scratch – quitting and re-opening the Source and Destination patches, and then, try loading our JSON file,  Webmapper is not re-drawing.

I'm wondering if this issue is about Google Chrome, which is prohibiting access to JSON for some reason?

Context:  Benjamin is trying to do this with a computer in the DCS, McGill.  On my own system, everything is working fine.

Thanks for any suggestions you may have

AA

[d.andrew STEWART]

I may be making some headway debugging, but I'm not sure.  I'm not working on the underlying programming of Webmapper, of course – I don't know how to do this. However, I am working on scripting connections with /map and /unmap from Max.  I've used this technique for dynamic mapping during a performance a lot.  The challenge is that the syntax gets changed (I think), which plays havoc with my scripting.  Here are some questions:

(1) Scripted a connection with:

/map dascontroller.1/fuchsia/twirl -> dascontroller.1/red/calibrate @mode expression @expression y=x

When I /subscribe maps I get this:

dascontroller.1/red/calibrate <- dascontroller.1/fuchsia/twirl @id 14 @expression y=x @mode expression @muted @num_inputs 1 @process_location source @protocol unknown @status 31 @version 0 @scope dascontroller.1 @src@length 1 @src@type i @src.0@bound_max none @src.0@bound_min none @src.0@calibrating @src.0@causes_update @src.0@max 127 @src.0@min 0 @src.0@num_instances 1 @src.0@use_instances @dst@length 1 @dst@type i @dst@bound_max none @dst@bound_min none @dst@calibrating @dst@causes_update @dst@max 127 @dst@min 0 @dst@num_instances 1 @dst@use_instances

Is it normal that the Destination is listed before the Source? This is new, yes? Also, looks like operator is reversed.  No longer using ->  Instead, use <-  correct?

(2) Is muting still possible?  I tired /map/modify … @muted True.   but not luck

(3)  Is there any command for [oscmulticast] to report the number of mapping connections

(4) When I   /subscribe maps, [oscmulticast] only reports the first 52 connections

(5) In Webmapper, we can now change the direction of the signal from Destination to Source? (i.e., Graphically, the arrowhead of a connection pointing to the Source). What does this do?  Forgive me if this is an older feature; I don't fully understand the logic of going from Destination to Source. 

For now, I'm going to try reversing the order of devices in my scripting – a lot of copy/paste

Thanks for any tips, here.

[d.andrew STEWART]

Yet more headway

I've discovered that the order of attributes in my scrip is important

This doesn't give me the correct scaling:

70, /map karlax.1/instrument/knead -> ritual.1/1_channel/makenote/velocity/01 @id 148 @expression y=x*(102)+(25) @mode expression @muted @num_inputs 1 @process_location source @protocol unknown @status 31 @version 0 @mute 0 @scope karlax.1 @src@length 1 @src@type f @src.0@bound_max none @src.0@bound_min none @src.0@calibrating @src.0@causes_update @src.0@length 1 @src.0@max 1. @src.0@min 0. @src.0@num_instances 1 @src.0@type f @src.0@use_instances @dst@bound_max none @dst@bound_min none @dst@calibrating @dst@causes_update @dst@length 1 @dst@max 127 @dst@min 25 @dst@num_instances 1 @dst@type i @dst@use_instances;

This gives me the correct scaling:

70, /map karlax.1/instrument/knead -> ritual.1/1_channel/makenote/velocity/01 @id 148 @mode expression @expression y=x*(102)+(25) @muted @num_inputs 1 @process_location source @protocol unknown @status 31 @version 0 @mute 0 @scope karlax.1 @src@length 1 @src@type f @src.0@bound_max none @src.0@bound_min none @src.0@calibrating @src.0@causes_update @src.0@length 1 @src.0@max 1. @src.0@min 0. @src.0@num_instances 1 @src.0@type f @src.0@use_instances @dst@bound_max none @dst@bound_min none @dst@calibrating @dst@causes_update @dst@length 1 @dst@max 127 @dst@min 25 @dst@num_instances 1 @dst@type i @dst@use_instances;

@mode must come before @expression

Could someone look through the rest of these scripts/attributes and report anything that needs to be changed, please?

It would be really helpful , if these changes were documented somewhere – excuse me , please, if these changed get logged on the Google Group (do they.......?)

[Joseph Malloch]

Hi Andrew,

What version of libmapper / max objects are you using?

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 on the web visit https://groups.google.com/d/msgid/dot_mapper/99875b36-0448-471e-a0b8-94d29b29ea26n%40googlegroups.com.

[d.andrew STEWART]

Hello,

WebMapper20191211.zip

From https://github.com/libmapper/webmapper/releases/tag/20121211

mapper-osx-max-pd-max8-20190702.zip

Okay, I guess I'm behind here. I should be using the following, correct:

v2.1 at <https://github.com/libmapper/libmapper/releases>

I know Benjamin is using "mapper-osx-max-pd-max8-20190702.zip", too.  And I've asked him to make sure his Webmapper is up-to-date.

NOTE:  He's working on a computer in the DCS.  And they are still running macOS 10 and a slightly older version of Max.

…versions…versions…

Thanks for any tips you can give

D.N