Posts: 4.125
Threads: 138
Joined: Jul 2017
Reputation:
247
OK, this is one of the last issue I have before I can finally release V2.0:
The screen is called mapping where you can map a source to a destination. And you can do much more by combining these up to the point that you can let it execute the lines in an algorithmic way.
The issue I got is how to name these (or lets say a block of it since you can have multiple ones within one project).
My idea would be simply:
map
Other possibilities would be: 'sketch', 'script', 'lines of mapping rows that create together a new function'
Let me know your ideas and why 'map' is maybe the best one :-)
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help! 
Posts: 140
Threads: 29
Joined: Oct 2018
Reputation:
3
I would like to know more
1. Are lines or group of lines selectable and then able to be exported and saved with name.map
or does it save the whole contents of the mapping screen?
2. when you say "multiple ones within one project" does this mean having differing blocks - so a few lines of midi to cv, a few lines of functions etc within a single mapping screen?
Instinctively I like the word "map" because it's simple and reflects (I suspect) on how most will use this "anything mapped to anything". - Script and sketch put me off as they are way too much like computing language.
Posts: 24
Threads: 10
Joined: Sep 2023
Reputation:
0
‘Map’ sounds good. Maybe something like ‘link’ ‘chain’ ‘chaincmd’ ‘cmdchn’ could work
Posts: 30
Threads: 15
Joined: Nov 2020
Reputation:
1
Exporting a “map” that can be imported into another mapping setup sounds right.
Posts: 478
Threads: 58
Joined: Dec 2020
Reputation:
35
I've been thinking about the proper naming for a while.
I remember when I first saw the new features @SB23 I thought "Why is this called 'mapping'? That clearly only covers some parts of this incredibly versatile new feature...hmm...probably it started as mapping for the I2C functionality and then Thomas saw a way to make it even better".
For me this is very much a scripting environment. It has great potential for generative processing and algorithmic manipulation of patterns and sequences in general. I therefore find "Script" a much better name as "Map" covers only a part of the functionality.
That having said:
In the end I can live with either "Map" or "Script" but my preference is clearly with "Script".
Kind regards,
Michael
Posts: 5
Threads: 0
Joined: Dec 2020
Reputation:
1
I'd prefer 'map'. It's just the nicer and more accessible word. Although the things you can possibly do in this screen is better described with 'script' people won't start with scripting logic functions. The first things people would like to do in this screen is something very basic like mapping a fader to an envelope decay or something like that.
If i imagine being a fresh Nerdseq user i would be so overwhelmed with all the possible features i would definitely ditch a chapter/screen that is called 'script' for later, because i am still trying to wrap my head around patterns, tables, automators and patches (and i am one of those people who finds joy in reading the fukking manual). But if it is called mapping i would give it a glance as mapping features is something every DAW, Hardware Synth, Midi, DIN, modular user is used to
