Notifications
Clear all

[Solved] Midi controller mapping in Massive?

10 Posts
3 Users
3 Reactions
465 Views
(@thsve)
MR
Joined: 5 years ago
Posts: 346
Topic starter  

I started to Unify some of my Massive libraries but run noticed a problem. I am not able to get Massive to open with the desired midi cc setting by default. It always opens with the same setting (se clip) and I have to change it every time. Can't find where I can change this in Massive. Do you have the same problem and have a solution?
Made a short clip to illustrate the behavoiur: https://www.dropbox.com/s/x0qtv9zo1r402qk/Massive%20CC%20Mapping2.mp4?dl=0

If this in fact is a real problem, Unifying Massive libraries seems a waste of time. 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
Quote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 

@thsve I just tried it and didn't use the MIDI SAVE option in Massive. Instead I used MIDI learn in Massive for each of the 8 cc knobs and moved the appropriate knobs in Unify. When I save the patch in Unify, change to a difference patch that doesn't use Massive and and then reload the Massive patch all of the knob assignments were recalled correctly. 


   
Robert.P reacted
ReplyQuote
(@thsve)
MR
Joined: 5 years ago
Posts: 346
Topic starter  

@zinct

Thank you for the reply. Unfortunately that is not what is happening here😢. It seems to be a Massive issue. Whatever i do, Massive always loads with the mapping seen in the clip. I’ve tried to save the setting in MyDefaultCC under File/Option/Midi to no use. Massive always opens the same mapping and I can’t find this specific map anywhere. 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 

@thsve 

When I first opened Massive the CC knobs in Massive each had "na" underneath them which I assume means that they were unassigned.

You can make it do this by right clicking on each knob and selecting "Remove MIDI cc". Try doing that for each knob and then re-learning them using the Unify knobs. Then save the patch in Unify, init and recall the patch.

I'm also wondering whether you need to delete/remove that default file somehow as maybe it is overriding whatever you may have set with other information IDK?


   
ReplyQuote
(@thsve)
MR
Joined: 5 years ago
Posts: 346
Topic starter  

@zinct

I have tried everything I can think of. According to the Massive manual, the midi assignement is not saved with the sound, so as far as I can see saving the patch shouldn’t make any difference? Saw something that the behaviour differs between Massive stand alone and plug-in. In stand alone it remembers the assignement but not when usad as a plug-in. That is exactly what happens for me. I will try to dig more into this.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
Nico5
(@nico5)
Trusted Member
Joined: 4 years ago
Posts: 52
 

I've just tested it in Cubase, and I can confirm: when used as a plugin, Massive, when originally loaded as a plugin starts with out any midi assignments.

However, when I save Massive as a Unify preset (e.g. using the Massive preset DEFAULT START, but it could be any other preset, too) after having made the midi learn assignments in Massive, then whenever I load that saved Unify patch with Massive, the midi learn assignments in Massive are recalled for me as well.

Using Massive version 15.5 (R22)

Cubase 13 Pro, Win 10 Pro (x64), several different midi controllers


   
ReplyQuote
(@thsve)
MR
Joined: 5 years ago
Posts: 346
Topic starter  

@nico and @zinct

Thank you for your input! I finally got it to work even though I still do not understand why I had the problem from the beginning.
I have now modified the unified version of PlugInGuru Massive Power Pack V1 to my satisfaction(almost). It now has the same midi cc mapping as my Unify standard and the correct macro name in Unify. To do this, I was required to open Massive for each Unify patch, change the mapping there, and save it and then save the Unify patch. Luckily I was able to script it 😀.

The only thing I have to solve is how to get and set the initial macro knob values in Unify to correspond to the values in Massive. 

Now I can proceed with unifying my other Massive libraries.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
Robert.P and Nico5 reacted
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 

@thsve Glad you got it sorted!  I don't have Massive Power Pack yet but no doubt I will pick it up at some point 🙂

This post was modified 4 years ago by JeremyH

   
ReplyQuote
(@thsve)
MR
Joined: 5 years ago
Posts: 346
Topic starter  

@zinct
I didn’t Unify it in the first place, it is from PlugInGuru. I just changed it to my likings🤗.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 

@thsve Ah yes, a misunderstanding sorry about that 😊 Fixed. 

This post was modified 4 years ago by JeremyH

   
ReplyQuote
Share: