October 25, 2021, 08:24:40 am
Welcome, Guest. Please login or register.
Did you miss your activation email
News:

Arturia Forums



Author Topic: V Collection Perameters Changing When Recalling MainStage Patches  (Read 1135 times)

badhabit2112

  • Apprentice
  • Apprentice
  • *
  • Posts: 6
  • Karma: 0
Good evening,

I purchased the V Collection last month and really LOVE the classic instruments.  I have slowly been programing and incorporating the new VI's in my system, trying to incorporate the actual instruments that were used in the studio when many of the songs I'm doing were recorded.  But I find I'm having an issue that I don't quite know how to address.

The information for my rig is included in my signature.  I use MainStage 3.2.4 as my VI "carrier".  The set up runs as follows:

  • Korg Kronos is the master keyboard.  Nearly all songs are done using Combinations.  Channel 16 is used to send patch change information to MainStage.
  • My MainStage concert has all of my songs in it.  The patch change from the Kronos changes to the corresponding patch in MainStage, which calls all of my channel strip VI's, then also sends patch change information to my Yamaha EX5 on channel 14.
  • My VI's (see long list in signature) are typically used on either channels 1, 2 or 3.

When changing patches which include Arturia V Collection VI's, I find often times the sound has changed.  Usually the volume on the instrument has increased to maximum, or one of the ADSR levels have changed, or some other perimeter has changed significantly changing the sound from what was programmed.  When I open the VI, I can see the " * " after the program name, signifying that something has changed the sound.

I have not experienced this type of occurrence from any of my other VI's (Korg Legacy bundle, GSI's VB3, Miroslav Philharmonic, or any of MainStage's stock VI's).  So far the Modular V, Mini V, and SEM have reacted this way. 

In order to find a work around, I have many times opened up the MIDI configuration for each of these instruments, removed the midi assignments from the various controls, and have created a MIDI Control Config of "NO Control".  However, I have found that there are many times when reopening my MainStage Concert, the configuration I've created is missing entirely and all of the original configurations have returned.

While troubleshooting, I've used Midi Monitor to see what has been sent to the Computer from the Kronos.  There are some instances of General Control 5 and General Control 6 with values of "0" reported coming from 2 of the programed switches on the Kronos, but that would certainly not explain the volume going full on (which would be 127, no?).  I have eliminated as many occurrences of that as I could, but I do need those buttons to send controller data to MainStage on occasion, so I cannot eliminate them completely.

The end result is that I cannot depend that the sound I have created in my Arturia VI's will be the sound I play when I call up the song and start it.  It makes the Arturia V collection basically unusable for my live rig until I can find out why this is occurring and terminate it.  :(

Any suggestions or help would be greatly appreciated.  :)

-  Jim  -
MacMINI 2.3 GHz Intel Core i7 Quad Core, OSX version 10.11.6, 16 Meg Ram, 1TB SSD, Mainstage 3.2.4, Korg Kronos X 88, Yamaha EX5, Korg RK100, Arturia V Collection, Korg Legacy Bundle, Miroslav Philharmonic, GSI VB3, AI-Studio D50 VR, Sound Radix 32 Lives.

badhabit2112

  • Apprentice
  • Apprentice
  • *
  • Posts: 6
  • Karma: 0
Re: V Collection Perameters Changing When Recalling MainStage Patches
« Reply #1 on: March 10, 2017, 09:55:45 pm »
Perhaps I have to chalk this problem up to "everything can and will work a little differently than everything else"...

On some of my Kronos Combi's, it would send out volume controls on various channels.  All of my other VI's ignored them, but for some reason the changes effected the volume of the V Collection synths that were called up in active channel strips, even though MainStage is supposed to prevent the information from going through to the VI (it stops at the volume control), and even after I've removed the control mapping at the VI itself.

Live and learn I guess.  :)
MacMINI 2.3 GHz Intel Core i7 Quad Core, OSX version 10.11.6, 16 Meg Ram, 1TB SSD, Mainstage 3.2.4, Korg Kronos X 88, Yamaha EX5, Korg RK100, Arturia V Collection, Korg Legacy Bundle, Miroslav Philharmonic, GSI VB3, AI-Studio D50 VR, Sound Radix 32 Lives.

 

Carbonate design by Bloc
SMF 2.0.17 | SMF © 2019, Simple Machines