Hi DG,

I have done as you described, however, upon loading a matrix into the VEPro server the settings default to the factory settings.

Firstly, you can't load a matrix in the server, so I think it's best that we go through this one step at a time, to make sure that we agree on the terminology..

1. Have you set up your Preset?
2. Have you checked that when you load the Preset, it works as you wish?
3. Startup is the last step of the puzzle.

DG

Ok. Here's what I'm trying to do:

I would like some way to make the assignment of the velocity crossfade parameter to be midi control 12 (for example) for all instruments that are loaded into my orchestral template in VEPro 64bit. I would like to have some way to do this without having to go into each of the 60 odd matrices individually and changing this setting.

You suggest that this is possible, however when I created an empty setting with vel-crossfade set to midi control 12 (using VI standalone) and called it startup it did not have any effect.

When I start up VI standalone the settings are standard. When I load the startup preset it does change vel-xfade to midi ctrl 12. The startup preset is in the correct folder for VSL custom data (directory manager points to the correct folder also).

What could be going wrong I wonder?

Cheers,

Tom

 OK, it's obviously still not 100% clear so I'll try to explain again.

These settings are not stored within the matrices. They are stored within the Vienna Instruments Preset system. Therefore in order to get this to work you need to load your matrices into the Startup Preset. You can't change these settings en masse in retrospect. You need to:

1. Create your Preset and save it
2. Load your matrices and save that Instrument
3. Load a new Instrument with your startup preset
4. Ass matrices to this one for the next Instrument
5. Save it etc.etc.etc.

As far as getting your default Preset to be the startup one, it needs to be in the correct folder. I can't explain in more detail now, as I have no time to check, but will post back later today.

DG

This is not what I'm looking for then.

I was hoping there was a way to set up controller values for the map page in the instruments globally so I don't have to rebuild my entire template yet again.

So... this would be a pretty important feature request then. I'm surprised this hasn't come up before. Are people just resigning themselves to the laborious process of rebuilding their template each time they want to make such changes?

We should be able to:

1. Design our own templates which load as the default instrument when you create a new VI in VEPro.

2. Retrospectively edit sections such as the map control page on a global scale (for that viframe).

3. Copy and paste the whole map control page from one instrument to another.

Right now it seems the only way to achieve what I want to do is to go through each of the 60 odd instruments in my VEPro template and manually edit the fields on the map control page that I wish to have assigned. Very tedious indeed, especially if you want to assign a midi controller to several of the functions like attack, vel-xfade switch, filter etc.

Or does anyone knowledgeable on VEPro have a different solution?

@inwinterhesleeps said:

... We should be able to:

1. Design our own templates which load as the default instrument when you create a new VI in VEPro.

2. Retrospectively edit sections such as the map control page on a global scale (for that viframe).

3. Copy and paste the whole map control page from one instrument to another.

 

Hello Mr. Wintersleeper 😉,

according to my knowledge and to what I did in the past your wish-points 1. and 3. can be accomplished with DG's suggestion - as long as your instrument-setups consist of patches or matrices.

Here's a step-by-step instruction:

1. Start VEpro with a new session. There should be the master bus and the instrument 1 bus available.

2. set up instrument 1's controllers the way you'd like to have them set for all your instruments.

3. save that setup as a preset ("startup").

4. Load one of your patches or matrices into that instrument (e.g. "first violins")

5. Save that patch/ matrix as a preset, now called "first violins"

6. Repeat steps 4. and 5.  for your other patches/ matrices

7. for future use load the newly created presets into VEpro

Did that help?

Sebastian

P.S.:

I would like seeing your wish "2. Retrospectively edit sections such as the map control page on a global scale (for that viframe)." realised by the VSL-team.

Thanks, Sebastian, for the step by step tutorial. The VI interface is not very clear when it come to this stuff. The save option is merely a disk icon. No dialog as to what you are saving. So I'm assuming when the Patch button is selected it will save a Patch and when the Matrix button is selected it will save a Matrix. Perhaps they should have named Patch an articulation instead of throwing another term into the pot.

In any case, I can see no way to load up my custom patches or matrices using VEPro. There is simply no option for it. All I get is the factory content. I have set up a custom directory with Directory Manager, but none of what I save in there seems accessible.

There must be something obvious I'm doing wrong. I am quite comfortable with technology, however, I find VSL software to suffer from programmers' syndrome. I'm sure it's all crystal clear and obvious to the programmers themselves, but there has not been enough consultation with an interface designer.

So you are saying that when you load VEPro the (blank) instrument has your customised startup settings already loaded? Because that's what DG implied.

First of all I have to solve that problem with not getting access to my custom data.

@Another User said:

So you are saying that when you load VEPro the (blank) instrument has your customised startup settings already loaded? Because that's what DG implied.

This is how startup works. However, if VE Pro can't "see" the VSL Custom Data folder, then it won't work.

Regarding your original point (now that I understand that it is retrospective assigning that you want) I agree that it would be a good option.

However, you should be able to assign all faders (and on/off buttons) on the Perform page for 60 Instruments in about 10 minutes (or less, if you're fast), so at least it's not like building a template from scratch again.

DG

@inwinterhesleeps said:

First of all I have to solve that problem with not getting access to my custom data.

Hello Wintersleeper,

how about:

1. Start VEpro

2. Rename "instrument 1" into "Woops that worked!"

3. Save this setup as a preset called "Find me"

4. Search for the preset-file "Find me"

5. Copy your custom patches and matrices into the folder where you found "Find me"

6. And let me know whether you can load your patches and matrices into VEpro now! [:)]

Sebastian

I have solved the problem with custom data. Although the path looked correct, resetting it and then restarting finally did the trick. So now the startup file works for me too. I'd like to now where the documentation for this is. I could find no reference to it in either the VI or the VEPro manuals.

Now I am faced with either rebuilding my orchestral template with this new startup patch or rebuilding the template by going through and changing the map settings for each instrument individually. Both are a pain and could be avoided if there was a way to load or paste the map settings (or the startup patch settings for that matter) into an already established instrument within VEPro.

I think there is a strong case for requesting this as a future feature of VI/VEPro.

Who supports this idea?

Tom

@inwinterhesleeps said:

however, I find VSL software to suffer from programmers' syndrome.