Hey Martin,

I haven't installed my copy of PT11 yet, but in v10 it works for me if I uncheck the second and third boxes in;
Preferences/Midi - Delay Compensation for External Devices.

I don't think it's a bug, but we need to see an update in which PT can tell the difference between midi tracks for internal vs external devices.

Maybe this is a remnant from an ancient version, when the developers presumed that all midi in a session was intended for external sources.

In this case, I have a solo cello with slot x-fade between perf-leg and sus_Vib_espr.

Both those "articulations" have a lot of resonance in the body of the instrument, the epressivo patch even more so.

When I crossfade rapidly, I get an bump of low/mid frequency resonance.

As for now, I have to turn off the release samples to get rid of this.

If I could lower/control them on an articulation basis, that would help.

Is it possible to control the release samples more than on/off?

I'd like to be able to adjust the level and/or release time for only the release samples.

Thanks,

Hakan

Sorry for the late answer, I use IAC to route midi to/from Transmidifier.

I use VE Pro on the same computer as Pro Tools, and I use another IAC bus from Transmidifier to VE Pro to avoid a midi loop, don't know/remember if you have to do that using a slave.

Thanks Karel, I see, of course.

The path (OS X) is: Home/Library/Audio/Presets/

There is Channel Sets and in most VIs you can store your user presets. So, could anybody explain the idea behind the "Presets..." menu above the left top corner of 3rd party VIs. Where are those presets stored (OS X), and do they bring someting else to the table?

Thanks,

Hakan

Exactly, Martin - thanks! Keyboard shortcut assigned, too!

The way to trigger a note to activate an instance would be appreciated in VE Pro itself, to bring an instrument to ther front! (If the feature's not already there, and I've missed it)

Thanks, Karel!

+1

1. A collaboration with AVID and other DAW developers, creating an equivalent to the Expression Map feature in Cubase that can handle the complexity of the matrixes in VI Pro.

Or an integrated sequenser that handles this and more, synced to the main DAW.

2. Transmitting of the VEP Bus/Output names to DAW.

3. Visual feedback in DAW for the VEP-outputs that have been used already in the current Metaframe.

Thanks Karel,

Good to hear!

I'm asking because there was this dialog window when I first activated an external midi port. Something like; "Use on your own risk, this feature is an experiment." ;-)

There is no offline bounce in Pro Tools, so that's no issue.

Regarding midi sample accuracy, you're right, in most cases this won't matter - and I'll keep the midi for material that needs the most rhythmical tightness on the VE Pro network, then.

Q: Jitter free midi?

Hi, since Pro Tools lacks an equivalent of the Expression Map feature in Cubase, I'm experimenting with third part midi apps between PT and VEPro. (TransMIDIfier / Midi Pipe)

When I activate devices in the External MIDI page of VEPro prefs I get a warning, but so far it seems to work just fine. Anybody knows if the External MIDI is reliable?

Thanks, Hakan

+1

Thanks, Philippe!

Please report back your results if you use VEPro, Kontakt and/or Play.

I'm on Pro Tools, and I often miss some visual feedback of what articulations my keyswitches calls up. The only way that I know about is to use program changes. That way you can name the patches, and they are visible in the event editor etc. Logic Pro used to have a function where you would name the notes in a "mapped kit". You could then see the names of (some of the) notes in the pianoroll on the left.

One drawback of using keyswitches to change articulations appears when you transpose something in your DAW and the keyswitches in that region/clip are transposed, too.

Thanks, Martin!

Thank you, cgernaey. Windows7 it is.

I'm getting a PC for VEPro/VIPro/Play/Kontakt etc as a slave to my main DAW.

Thoughts on O.S. appreciated. (Windows 7 Pro vs Windows 8)

Thanks,

Hakan

Thanks a lot Martin, very informative! Such a huge difference between mechanical and SSD! The Caviar eco-drive, on the other hand, is not far from the Caviar Black. Luckily, when doing orchestral stuff, I hardly quantize at all.

Ok thanks, I'm gonna go for an extra SSD for some of the Hollywood Strings and EW Pianos. I'm also putting some of my VSL libs on this PC on a 7200 HDD. On Mac it's obvious that Play is less efficient than VIPro and Kontakt. As far as I know, all three engines reads partly from a buffer kept in RAM, so I guess with a large memory buffer, the performance has a lot to do with how well the software is written. That's why I thought that on the PC platform with at least 32 GB RAM, I could get away with a 5400...

I got an offer from the company that builds my PC. They suggested a SSD for the system and a Caviar Green drive (5400). Since I don't know how the Play engine works, I thought I'd ask if that was good enough. Now I've gotten the advice to put the samples on another SSD, so I guess Play isn't very efficient. On my Mac Pro I seldom hit the roof, using Vienna Instruments and Kontakt, all samples stored on 7200 rpm HDDs.

Regarding the memory server in Play, with 32GB RAM, will I need a 7200 SATA or will a 5400 be good enough? (Guess not)

Great, thanks! Good luck with solving your problem.