God, but I hate being paranoid, though. If we can put a man on the moon, as REM says, surely we can have safe autosaves. Surely

Mahlon

P.S. Cubase always seems to do fine with autosave for me, but I've got it on a separate machine and it's decoupled.

DG,

Number 2. I run decoupled for the reason you mentioned. For sure, I wouldn't want to be locked out as it takes about 40 seconds or so to save the metaframe. Normally I'll save the project or the Kontakt multi while I'm tweaking, (since they save much faster, and I can reload them individually if things go South),  then save the whole metaframe every 20 minutes or so. I messed up last night, though. Thunderstorms.

Thanks,
Mahlon

I wonder if there could be introduced a timed "autosave" for Metaframes in VE Pro. I just lost a bunch of changes because my battery backup blew when the elecricity went out.

Just made me think --- that would be a nice feature.

Would VSL consider it?

Thanks,
Mahlon

Sorry folks. User error I forgot that you also have to set the MIDI Preferences for the master machine, too.

Mea culpa,

Mahlon

I've recently rebuilt my main DAW. Cubase 7.5.2 is on the main DAW, and I have a slave running VE Pro. On the slave I have VE Pro connections settings for 32 MIDI ports, 32 Audio INS and 32 Audio OUTS. When opening a previous Cubase project Cubase tells me I have unmapped midi Ports. Where previously (before rebuilding) I had 16 MIDI OUTS in Cubase, now it's only show 8 for the instance of VE Pro, and it's showing 9-16 as missing.

Also, when I connect to VE Pro from Cubase, I'm getting two instance of VE Pro available (see Pic).

http://lutanian.com/temp/VE-Pro.jpg (for some reason I can't insert this image in the post)

Anyone have an idea as to why I'm not seeing 16 MIDI OUTS in Cubase? Could it have something to do with the two instances of VE Pro?

Thanks for any and all help!

Mahlon

Thanks Fred; I never thanked you for that.

Mahlon

Thanks, guys. Much appreciated.

Mahlon

Any thoughts on this would be appreciated.

Thanks,
Mahlon

I've downloaded the MIDI file for J Bacal's Syrinx tutorial. Which Flute matrix should I use to get the correct patches playing? I couldn't find this information.

Thanks,

Mahlon

Yeah, I think this is a Berlin Strings issue. I also have it with a few of Project SAM's instruments.

Thanks for the help.

Mahlon

Thanks. No, VE Pro is connected to the DAW. I'm going to do a few experiments to see if I can narrow it down. Haven't heard back from Orchestral Tools tech support yet.

Mahlon

I have multiple Berlin String patches loaded into an instance of Kontakt. The Kontakt instance resides in VE Pro which is on a slave machine -- separate from my master DAW. I save the Kontakt instance within the VE Pro metaframe.

In Berlin Strings, you can adjust the different mic levels to suit your needs, but when save the metaframe and I reload that instance of Kontakt, the Mic levels are not remembered. They show as having been changed, but the actual audio output sounds at the default level, not the level I changed it to. I've tried saving the individual patches as custom patches in Kontakt, but when these reload -- same thing.

I've also noticed that in one of my Symphobia patches, the "Attack" level  for the patch was not remembered when I adjusted that either. However, it did not show that the knob was adjusted -- both visual and audio signal were set back to the default.

So, it seems like I may be doing something wrong -- or expecting something else. But shouldn't VE Pro remember all settings --even when it is saving the Kontakt instance inside?

Has anyone else experienced this? If so, is there an answer I'm overlooking?

Thanks,
Mahlon

P.S. I have no idea why the above has a blue background.

Thanks. That's very clear. I keep my signals peaking for individual tracks at about -15 dB. Final output peaks about -6 dB. Appreciate the help on understanding this.

Now, to the other part my first post. Is the output slider functioning correctly when I set the slider to 2dB using one preset, then after loading a new preset -- the slider remains at 2dB, but the ouput slider's output is actual at unity?

Mahlon

Thanks for your help. Maybe (probably) I'm using incorrect terminology. Initally, I was trying to just understand a technical aspect of the output slider's function and whether it is working as it should when changing presets. Then there's also the conceptual/practical workflow you are mentioning.

So, as to the workflow question, here's a simple example of a situation where I must not understand the function of the output slider (this is a different problem from the technical question I asked in the first post about the output slider showing a different value than what is being heard): Say I have a bunch of stems which have been mixed to the correct levels without reverb. I insert Hybrid into an output buss and send the stems to that bus. I load one of VSL's presets into Hybrid. If I leave it as is, the final output signal is reduced by about 3 dbs. Now, I was thinking that the way to make up for this is to raise the output slider about 3 dbs. But you're saying that 's not what the output slider is for? How would you compensate for the loss of dbs? I don't want to raise the main output and I don't want to change any of the stems, groups, busses or what have you.

Remember, this is the most basic example just to show what I'm talking about.

Thanks, again.

Mahlon

Thanks jasensmith,

I'm using it both as an insert on some stems and on the Master Out in different situations. I had assumed the output slider was there to make up for the gain loss when dry is not set to 100%, as most of the VSL presets are not.

Mahlon

There's a significant attenuation at the output of the reverb when I apply one of VSL presets (using Hybrid as an insert by the way). Raising the output slider just brings the whole signal level back up, right? It doesn't only raise the reverb level by itself. I assumed that's why the output is there. But I don't know.

How do you account for the gain loss? If you're just wanting to use a preset, I mean.

Thanks for the help,
Mahlon

I've noticed that the Vienna Hybrid Reverb presets usually need a little boost to the output -- around 4db to keep the same level as the signal before going through the reverb.

Many times I'll test out patches back to back, loading one, listen, then load another, etc. If I change the output slider to +4 db for a patch and then load another patch, the output slider remains at +4db for the new patch but the actual sound is really at 0 db. Is this a bug? Shouldn't the slider jump back to 0 db to show the true output of the new patch?

Thanks,
Mahlon

P.S. Or is this the best way to deal with gain in the first place? Should I be raising the Dry and Wet signals instead of changing the Output?

I'm trying to understand how much RAM I've used on my Window 7 slave computer. On the slave, I've got 64 gigs of RAM and am hosting multiple Kontakts, Plays, and VIs inside 4 instances of VE Pro.

When I first boot the slave and load the metaframe template, Windows Resource Monitor shows I've used 54 GBs physical memory. The Memory tab processes in Resource Monitor, shows VE Pro using about 31 GB.

Now, if I close down VE Pro, emptying the samples, and then relaunch VE Pro, Windows shows that I'm using about 36 GBs of physical memory. Which seems in line with the Memory tab stats from before because Windows and other process would be taking up about 5 GBs. Physical mem usage only goes back up to 54 GB if I reboot the computer.

So what gives? How does this work? I sure would like for the latter case to be the real memory usage, but somehow I doubt it. I suspect VE Pro is not showing all the RAM used.

Thanks
Mahlon

Just wanted to say that, in the end, it was user error. I had the buffers set too low. Raised them and everything is fine.

Thanks,
Mahlon

It's across several instruments, but yes, I think bassoon I suffers. I know Oboe II does, and Flute I and Clarinet I exhibit this behavior with the Upbeat Repetition patches.

Thanks, for the help. I've sent a support ticket to VSL and they've responded.

Mahlon

This may be elementary, but did you launch VE Pro Server on the slave? Before, when it hasn't shown up on my slave, I've forgotten to actually launch the VE Pro Server app.

Just a thought.

Mahlon

I've posted on EastWest forum in Dave's original thread that I'm having a similar problem with Cubase, Play and VE Pro -- but as far as I've tested it's happening after loading the marcato patches for Solo Trumpet in th 16th midi channel of a Play instance. Haven't gotten further with testing.

I'll send EW the crash info tomorrow.

Just wanted to let you guys know.

M.