Mapping parameters in Mainstage

Hey I'm having trouble mapping parameters to my midi keyboard in Mainstage.
I have an M-Audio Oxygen 49 midi controller and I tried clicking on something i want to control (reverb level) and then map parameter, and then I tried moving a fader on my keyboard to send a midi message, and then map parameter again but this did not work.
Any help would be appreciated.

First step of trouble shooting: does the keyboard actually work? Open any template concert - do you get a confirmation (An alert with "Select Preset #1" or so?) that the keyboard was recognized? Go to layout mode and check if all knobs actually react to your keyboard without any mappings.
If they work, go to edit mode and map the parameter to whatever you want. It should work. You can test this with the template concerts that are shipped with MainStage.

Similar Messages

Need help in modifying mapping parameters of out the box mapping

Hi There,
I am a new bee to dac.
Need help in modifying mapping parameters of out the box mapping, which is invoked by DAC task.
We got a requirement to edit mapping parameter. When I go and see parameter under mappings tab in a mapping, I could not see any values in it.
But when I set any value, and validate it. It is successful.
Is it right way to do it?
What my concern is, When I initially go and see parameter values under maapings tab in a mapping, they are blank.
Where is it storing these values?
Thanks,
Rag

If you modify mapping then u have to create new task in dac and dac itself craete parameter file at run time. if you want to add more parameters then do it in dac system parameters tab.
Thanks
Jay.

OWB 10.2 PARIS - How do you enter mapping parameters?

When I go to run or schedule my mapping, I can't seem to find anywhere where I can change my default parameters! I've been clicking and clicking to the point where my left mouse button doesn't work anymore. Can someone help while I go out and buy a new mouse.
Thanks
K

I am left handed so my left mouse button works the same as a normal persons right mouse button, and clicking on the mapping parameters did not work.
However, the suggestion to Tools -> Preferences -> Deployment - Process.
Set the preference Prompt for execution parameters works perfectly
I must've hovered very near that option in my frenzied clicking, but not on that exact one.
Thanks you M Boire.

Invalid map parameters

Hi!
When i'm sending to mail my world position from maps, then i can't open in my browsers on pc.
When site opens, only show me a map of the world. And sign "Invalid map parameters. Display default"
Why??

Sorry I forgot :
Database: Oracle 11gR2
GG version: Version 11.1.1.1.2
Sometimes gettin error on target side ERROR OGG-01296 Error mapping from

Mapping parameters of third party plug ins

Is Mainstage supposed to map the parameters of third party plug ins? I'm trying to map a start stop button to the play button in idrum but it doesn't work. Tried buttons on a korg polysix and that's the same. I can get it to work with apples own instruments though.

You can capture using the QuickTime player.

Pointers needed on Mapping Parameters - BAPI_OBJCL_CHANGE

Hi Gurus,
I am unable to pass correct mapping paramters to BAPI_OBJCL_CHANGE.
I need to update Characteristics in AUSP table
The paramters being passed:
Import parameters
OBJECTKEY                      - what should be the value for Object key ?
Should i concatenate Material num and Batch to build Object Key ?
OBJECTTABLE                  - AUSP
CLASSNUM                       - what is Class Num?
CLASSTYPE                      - 023
STATUS                            - '1'
STANDARDCLASS           -
CHANGENUMBER             -
KEYDATE                         -
NO_DEFAULT_VALUES   -
Tables
ALLOCVALUESNUMNEW
ALLOCVALUESCHARNEW
What should be populated in the above tables.
Please giude me with some pointers to use the above BAPI.
Please help me out in this one, its very critical.
Many Thanks,
Madan

data: numc_values type table of bapi1003_alloc_values_num with header line,
        alph_values type table of bapi1003_alloc_values_char with header line,
        curr_values type table of bapi1003_alloc_values_curr with header line,
        return type table of bapiret2 with header line,
        material type bapi1003_key-object.
if not data_record-sp_ind is initial.
    move 'spare-part-indicator' to alph_values-charact.
    move data_record-sp_ind to alph_values-value_char.
    append alph_values.
endif.
    call function 'BAPI_OBJCL_CHANGE'
      exporting
        objectkey          = material
        objecttable        = 'MARA'
        classnum           = 'SPARES'
        classtype          = '001'
      tables
        allocvaluesnumnew = numc_values
        allocvaluescharnew = alph_values
        allocvaluescurrnew = curr_values
        return             = return.
the above is a code snippet from a program we use to maintain chracteristics of a class on material masters.
The object key is indeed the object that is being classified. in this case, the material number. you must first move it to the work field to make sure there is no typing issues with the BAPI. The object table is the table which stores the OBJECT (not the classification table AUSP). The classnum is actuall the NAME of the class, and the class type is the class type (for materials, this is '001' for example.
the internal tables store the values for the characteristics, and each characteristic goes into one of the three tables, depending on its data type. in the snippet is an example of loading a "character" characteristic.
actually create a classification manually, and then check it in AUSP, and you will see how the data is stored, and this might also help you. ausp is one of about a dozen or so tables used in classification.
this comes from a working, active program, but of course, you use this at your own risk (end of disclaimer)
i hope this helps. we do a lot of classification, so if you need any further help, just ask.

Mapping parameters binding gets removed in process flow

Hi All,
whenever i import a mdl file from development to production
parameters binding of few mappings and pprocedures in process flow get removed automatically.
for example Map1 in PF1 has input parameter p1 binding set to Pf.p1.
this binding is getting automatically removed when i import the mdl file from development to production.
I am in big trouble bcz of it.
could anyone plz help.
Thanks in anticipation,
RD_RBS

This also happend to us when we moved from dev to prod. We really didn't find any good way to bypass this but just rather enter the binding values again manually. You might wanna check a few other things that got lost during the move. Such as DB Link(DB Connections on stage tables) and Outgoing Transitions in the process flows.

C# Class and Oracle Mapping Parameters

I have a type declared in an Oracle Database:
CREATE OR REPLACE TYPE t_project_code_changes AS TABLE OF obj_project_code_change;
I map to this type in C# like so
[OracleCustomTypeMapping("DEV_SCHEMA.OBJ_PROJECT_CODE_CHANGE")]
class ...
The above code works without error, however if I remove the schema name 'DEV_SCHEMA' from the attribute, it fails:
[OracleCustomTypeMapping("OBJ_PROJECT_CODE_CHANGE")]
class ...
Generates the following error:
Unhandled Exception: System.InvalidOperationException: Custom type mapping for 'ProjectCodeChangeDTO' is not specified or is in valid.
at Oracle.DataAccess.Types.OracleUdt.GetUdtName(String customTypeName, String dataSource)
At some point I will want to ship the code past 'DEV_SCHEMA', but this will result in the code failing.
The schema name comes from the connection string User Id:
"Data Source=DBNAME;User id=DEV_SCHEMA;Password=pwd;Pooling=False;"
Is there anything I can do onm the Oracle of C# side to help me with this. I.e., somehow:
1. Pass the schema name as the attribute parameter
2. Define the type in Oracle in a way that I don't need to use the schema
As a further bit of information, this problem presents itself when I use the ODP.NET client version 11.1.0.7. The 11.2 version of the DLL works perfectly without the schema name in the attribute.
Any help would be much appreciated.

What is the actual statement you're executing in the System.Data.OracleClient code? The one you've pasted right underneath SQL:? And that's exactly how you're executing it? No bind variables, etc? Just a hard coded literal statement and that's it?
Are you sure you're connecting as the same schema when you execute the same statement via Toad? I see ora-942 in the error stack, which is frequently a permissions issue. You're connected as MitSchema in both cases?
Can you reproduce this with a small test app that does nothing but execute that statement, similar to the code in this post for example?
Performance issue with ODP.NET 11.1.0.7.20
System.Data.OracleClient is generally supported by Microsoft rather than Oracle if the behavior is specific to their provider. Do you see the same behavior when using Oracle's data provider? If so, it may be more appropriate to post this in the ODP.NET forum ( ODP.NET ), as this forms is specifically for the Oracle Developer Tools for Visual Studio
Hope it helps,
Greg

Automatic mapping bug in mainstage slave mode

Recently we have a setup with ableton (and which we control with a BCR-midi controller).
As rewire slave we have mainstage 2.1.1 with USB garagekey and a novation remote.
While we are using the BCR-knobs in Ableton, mainstage seems to have automapped the knobs and buttons to some of our ffx in the ES and B4. Also the main-fader in mainstage seems to be affected. Is there any change to avoid this serious problem? We havnt found a way to turn the BCR off in mainstage.
Thx!

in short:
Is there a way to turn usb-controllers OFF in mainstage?

Parameterized mapping in PI 7.31 Dual Stack

Hi All,
I am working on PI 7.31 Dual Stack. I am getting the below exception in parameterized mapping:
com.sap.aii.utilxi.misc.api.BaseRuntimeException; com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter TestVal does not exist.
I could test in MM test tab but facing the issue in runtime. Please suggest me where I am going wrong.
Thanks,
Madhurima

Hi Madhurima,
Have you checked if your PI version and patch level is being affected with this note 1933139 - Errors during execution of operation mapping with message mapping parameters names different from the operation mapping parameter names?
Regards.

What are mapping variables & parameters ?

1.In real time scenario where can we use mapping parameters and variables?
2.what are mapping variables & parameters ?

http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10577/d_xplan.htm#CACICEDJ]
BPS@xe>explain plan for
2 select sysdate from dual;
Explained.
BPS@xe>select * from table(dbms_xplan.display());
Plan hash value: 1388734953
| Id | Operation        | Name | Rows | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |      |     1 |     2   (0)| 00:00:01 |
|   1 | FAST DUAL       |      |     1 |     2   (0)| 00:00:01 |
8 rows selected.
BPS@xe>select * from table(dbms_xplan.display('PLAN_TABLE',null,'BASIC'));
Plan hash value: 1388734953
| Id | Operation        | Name |
|   0 | SELECT STATEMENT |      |
|   1 | FAST DUAL       |      |
8 rows selected.

Execute mapping thro sqlplus - parameters

Dear all,
I am new to owb
I have a mapping with two input parameters(MAPPING_NAME & MODULE_NAME), if i execute from control center it is executing
i want to execute it from sqlplus
the command i am using to execute from unix prompt is
sqlplus username/password@connectstring @/opt/oracle/product/10.2.0.1-OWB
/owb/rtp/sql/sqlplus_exec_template.sql repouser mapping_location PLSQL mappingname , MAPPING_NAME=mappingname,MODULE_NAME=HRMS
Log file after execution
Stage 3: Overriding Parameters
| MAPPING_NAME%CUSTOM='mappingname'
| MODULE_NAME%CUSTOM='HRMS'
Stage 4: Executing Task
| l_audit_result=3 (FAILURE)
Stage 5: Closing Task
Stage 6: Processing Result
| exit=3
how to give the mapping parameters
Thanks in advance
S. Sathish Kumar

For string parameters In 10.2, you need to use four apostrophes on both sides.
sqlplus username/password@connectstring @/opt/oracle/product/10.2.0.1-OWB
/owb/rtp/sql/sqlplus_exec_template.sql repouser mapping_location PLSQL
mappingname MAPPING_NAME=''''mappingname'''',MODULE_NAME=''''HRMS''''

Using Guitar Rig 5 in MainStage

Hello all!
I'm just getting started with MainStage, and so far quite liking the possibilities.
However, I've hit one thing which seems to be an issue for me, assuming I've understood it correctly. Each patch seems to have it's own channel strips, with it's own AU instruments etc... which to me seems a bad idea. Surely in this state, I will end up having hundreds of AUs running for the same software, which would slow things down?
On top of that, I'm running keyboard, guitar and vocal through Mainstage. All for me, as I switch what I'm doing depending on the song we're performing (and sometimes mid-song). However, this means I may sometimes want to change a guitar patch while keeping my keyboard the same, or vice versa.
So, to my question; is there a way to change AU presets without changing MainStage patch? I mainly need to do this with Guitar Rig 5 from NI, but I'd also quite like to do it with Massive and Reaktor too.
Not quite sure I've worded that very well, so an example:
I have a MainStage layout set up, which has my vocal going through clean with maybe some EQ etc. I've also got a guitar running through Guitar Rig 5, and my keyboard into Massive. During a song, I start off on keys playing Fat Bass 1 on my keys in Massive for the intro, switch to a distortion for the verse with my guitar, then Fat Bass 2 for the chorus in Massive. Maybe later I'll want a clean guitar in a bridge or something too, with some string hits thrown in from Massive again.
The way MainStage is set out currently, I'd need a patch for each combination, which would leave me with at least 3 "patches" for one song and three instances each of Massive and GR running. I'd much prefer to just send in a control message to change the presets in Massive and Guitar Rig.
Running on a 2014 15" MacBook Pro, 2.2GHz i7/16GB RAM/256GB SSD.
Thanks

I haven't been able to find a way to get it to work with Guitar Rig yet, but for Massive (and presumably Reaktor) I have found a solution. First, create an instance in MainStage, load it with Massive and load the presets you would like to use into Massive's preset bank. Turn it on so that it will respond to patch changes.
Navigate to the 'Assignments & Mappings' tab of the edit page. Find the device you want to use to send the MIDI CC messages. If it isn't in the list, click on 'New Assignment', which usually creates an Unmapped assignment in the 'All Devices' list. Click the area where it says No Assignment to bring up the Hardware Input popup menu. Choose your device, assign channel to 1-16, and change Type to absolute. From the number menu, choose the CC number you want to send the patch change. Set MIDI thru to Automatic. Name the input to something like CC to PG01.
Click on it to highlight the mapping info. In the far left side of the Control Inspector, you'll see a list of items such as Same as Input, Block, etc. You will also see the name of the instance containing Massive. Select it to bring up a list of control parameters, such as Volume, Mute, etc. From the list, choose MIDI Controller. The third item down in that menu is Program Change. Select it.
You'll see the Parameter values for Program Change. For saved value, select the Program Change number you want to send. Number scheme is 0-127. Now, here's the tricky part that nearly drove me mad before figuring it out. For NI instruments, one of the Range Max or Min numbers must be set to zero and the other to a non zero number. If you want to select PG 0, set saved value as 0, range max as 1 and range min at 0. For any other patch number, set saved value and range max to the same number and set range min to 0.
Also, make sure that the device thats sending your CC control message is configured as a toggle switch, not a momentary, or else it will send the range min program change number when you lift your foot or finger from the button. If you want to send multiple patch changes, add more mappings and assign different CC numbers to select the patch number you desire.
An additional benefit is that you can load up a single instance of Massive with as many presets as it can hold and use aliases of that instance for other songs. In this case you would create a new MainStage patch and populate it with an alias of your Massive instance. Set up a separate hardware input (I use logic remote) and rather than setting the number to a CC controller, set it to Any. By entering the same NI mapping parameters as above, it will send the correct PG info to Massive when you select the MainStage patch containing the alias. If you need to select multiple Massive patches from the new MainStage patch, simply assign the CC controllers to select new patch assignments. All that info is freely assignable and saved on a per MainStage patch basis, so your first instance could select the patch (say 0) and use three CC controllers to set patches 1-3. On the next MainStage patch containing the Massive alias, you could set the PG to select patch 4 and those same controllers can be set to select patches 5-7.

MainStage 2.2.2 released

MainStage 2.2.2: Release notes
Products Affected
MainStage 2.2
Symptoms
MainStage 2.2.2 is a software update for MainStage 2.2. MainStage 2.2 is a feature upgrade for MainStage 1.0 and 2.0 customers available for purchase on the Mac App Store. MainStage 2.2 includes several new features and fixes.
Resolution
About the MainStage 2.2.2 Update
Stability and Usability
Resolves an issue in which MainStage might quit unexpectedly on OS X Lion v10.7.4.
Resolves an issue in which MainStage sometimes quit unexpectedly when loading certain concerts.
Resolves an issue in which MainStage quit unexpectedly when a second mapping was assigned to a screen control that already had a mapping assigned.
Fixes an issue in MainStage 2.2.1 in which assignments and mappings could be inadvertently deleted by removing a screen control in Layout Mode.
Resolves an issue related to the download and installation of basic and additional content.
The menu item for Release Notes now opens the correct URL.
Compatibility
Compatibility with the VAX-77 keyboard is improved.
Resolves an issue in which patch lists were not updated to VAX and Axiom keyboards if the keyboard lost and then regained connection to the computer after launching MainStage
General
Resolves an issue with MainStage 2.2 and 2.2.1 in which EXS instrument files were not available if they were in aliased folders.
Fixes an issue in MainStage 2.2 and 2.2.1 in which the I/O Plug-in did not route audio to outputs.
When mapping a Screen Control to a parameter already mapped to another Screen Control by using the plug-in GUI, MainStage now correctly maintains independent mappings for each Screen Control.
Resolves an issue in which using the Command key in conjunction with up and down arrows in Edit mode with Map Parameters enabled caused MainStage to assign the mappings to Next Patch and/or Previous Patch.
Fixes an issue in MainStage 2.2 and 2.2.1 in which mapping a Screen Control to jump to a patch or a set no longer worked.
Screen Controls mapped to more than one parameter now operate smoothly over their entire range with all range scale settings.

Grabbed MS 2.2.2 last night, loaded, started and promptly crashed. Switched to 64 bit mode and it runs but my 32 bit plug ins (inc apple plug ins) dont work properly (causes crackles). Switched back to 32 bit mode and MS crashes after about 30 secs with no action on my part. I've looked for any special instructions concerning 2.2.2 but have not found any. Has anyone else out there used 2.2.2 yet in 32 bit mode?

Mainstage Crash during live use after OS X 10.7.4 install.

I am a semi-pro musician and I have added Main-stage to my set-up, in line with my hardware synths, as I transition into the soft synth world in a live situation. Up until the latest OS X install, Main-stage has been stable, which is critical for live use, and my confidence moving forward is growing. However now, my Main-stage set-up hangs up and or crashes in performance mode after about 15-20 minutes. This is not acceptable, anyone here that is invested in Main-stage for live use, understands this. 30% of my show is dependent on this too,l but crashes cannot happen on stage.
I have read that the new OS X update 10.7.4 may be responsible, as this is the only thing that has recently changed. If so, what is the solution to resolve?, is it possible to back out a OS X update and if so, how?
This is my first post, which for me, means I am desperate for an answer quickly, thanks.

And there is your reply from Apple:
MainStage 2.2.2: Release notes
Products Affected
MainStage 2.2
Symptoms
MainStage 2.2.2 is a software update for MainStage 2.2. MainStage 2.2 is a feature upgrade for MainStage 1.0 and 2.0 customers available for purchase on the Mac App Store. MainStage 2.2 includes several new features and fixes.
Resolution
About the MainStage 2.2.2 Update
Stability and Usability
Resolves an issue in which MainStage might quit unexpectedly on OS X Lion v10.7.4.
Resolves an issue in which MainStage sometimes quit unexpectedly when loading certain concerts.
Resolves an issue in which MainStage quit unexpectedly when a second mapping was assigned to a screen control that already had a mapping assigned.
Fixes an issue in MainStage 2.2.1 in which assignments and mappings could be inadvertently deleted by removing a screen control in Layout Mode.
Resolves an issue related to the download and installation of basic and additional content.
The menu item for Release Notes now opens the correct URL.
Compatibility
Compatibility with the VAX-77 keyboard is improved.
Resolves an issue in which patch lists were not updated to VAX and Axiom keyboards if the keyboard lost and then regained connection to the computer after launching MainStage
General
Resolves an issue with MainStage 2.2 and 2.2.1 in which EXS instrument files were not available if they were in aliased folders.
Fixes an issue in MainStage 2.2 and 2.2.1 in which the I/O Plug-in did not route audio to outputs.
When mapping a Screen Control to a parameter already mapped to another Screen Control by using the plug-in GUI, MainStage now correctly maintains independent mappings for each Screen Control.
Resolves an issue in which using the Command key in conjunction with up and down arrows in Edit mode with Map Parameters enabled caused MainStage to assign the mappings to Next Patch and/or Previous Patch.
Fixes an issue in MainStage 2.2 and 2.2.1 in which mapping a Screen Control to jump to a patch or a set no longer worked.
Screen Controls mapped to more than one parameter now operate smoothly over their entire range with all range scale settings.

Mapping parameters in Mainstage

Similar Messages

Maybe you are looking for