Did you ever fix this? 

I'm running into the same issue with VEPro 6, Kontakt 5 and the latest version of Logic, but it seems to happen even if I restart VEPro. I think it started when I began using Logic's disable tracks without midi data function. Before that, I had regions on each track which enabled/disabled the VEPro instance, but that was causing my large Logic template to CPU overload as all of the tracks were considered 'active' in Logic. Deleting the enable/disable shortcut regions more than quartered my CPU usage, but then I started getting this issue in my local VEPro server on my MacBook Pro. My PC server doesn't seem to have the issue.

Screenshot attached. I've batch resaved many of my Kontakt instruments, including the ones in the screenshot, but it's still happening.

So I think it's linked to Logic trying to connect to the VEPro instance (locally) when I click on the track. Are you using Logic?

Hi Paul,

It's a bit disappointing that a bug like this has been present for 3 years (probably longer, but that's when it was first reported in this thread), and there's no plans for a fix. It makes managing big templates far more difficult without different colours. I do hope VSL will have a rethink and look at getting this fixed in the next update.

I did check out VEPro 7, but as the issue with Play VST & Logic is not specific to VEPro 6 (or 7) and therefore that issue won't be resolved by updating, and because I don't particularly need any of the newer features for my workflow, there isn't much incentive for me to upgrade. Especially when you consider that the upgrade from VEPro 5 to 6 was a reasonable 85 Eur - for me to get the same number of licenses for my machines in VEPro 7 would cost me 225 Eur.

Originally Posted by: Paul

Hi, 

No plans there right now. Did you check out VE Pro 7 yet?

Best,
Paul

Hi,

I've just come across this issue in VEPro 6 v6.0.18442. Any word on when this will be fixed for VEPro 6?

I've solved issue no. 2, which was the button only disabling - it was a setting on my midi keyboard where the button only output a set value rather than a range/toggle.

Still not sure about questions 1 & 3, though.

I'm trying to set up a button, not a slider, on my midi keyboard (M-Audio Oxygen61) which toggles the selected track in Logic to enable/disable the corresponding channel in VEPro. I'm using Automation Mapping in VEPro 6 for this, 'learning' the button's CC number (in this case CC26) and 'learning' the enable/disable feature by clicking the power button to the left of the channel in VEPro. It seems to learn the command fine, showing '... Controller 26' as the Source and '2 Play 1/Disable' as the Destination. There isn't a dropdown option for Enable in the Destination section, and clicking the CC26 multiple times only enables the channel from a disabled state - it can't return it to a disabled state (despite the destination actually being disable rather than enable).

If I set the Source to one of the sliders, 127 (max) disables the channel, and 0 enables it. So, the feature seems to work in reverse and only on sliders, not buttons.

So, my questions:

1. Can the direction be reversed of the feature, so 127 is enable and 0 is disable?
2. Can the command be set to toggle from a button, rather than a slider?
3. Can I also just check that there isn't a feature in VEPro 6 that loads the channels in an unloaded state, and only loads the samples into RAM when midi notation is received?

Originally Posted by: Paul

As a quick check, I'd also suggest to test with VE Pro 7, I just send you fully functional demo licenses. 

I've just tested it with VEPro 7 and the issue is still there. AU bounces in place fine, VST drops out. And just to be safe, I tested a Kontakt instrument in AU and VST, and both worked fine so it's just Play that's having issues.

Hi Paul,

Thanks for getting in touch. I've spent most of today trying to fix this and every test is slowly narrowing it down but still not quite sure what the issue is  

Since my last post, I also tried running a local server (64 bit) on my Macbook Pro in Logic, and the exact same thing happens. This was with everything up to date, and a clean install of Play 6 and VEPro 6.

The way I tested it was:

1. Open VEPro Server 64-bit
2. Add New Instance
3. Right click>Insert Plugin>VST>EastWest>Play (Stereo)
4. Add instrument and set the Midi Channel to 1 in the Instrument Panel Popout within Play 6
5. Right click>Insert Plugin>AU>EastWest>Play (Stereo)
6. Add instrument and set the Midi Channel to 2 in the Instrument Panel Popout within Play 6
7. For this example, I set each VEPro plugin in to Midi Port 1 & Midi Channel All
8. Open LPX>Add Track>Software Instrument>VEPro (Stereo)
9. Under the Track panel on the left, select MIDI Channel 1, then hit Cntrl + Return on a Mac to create another track with the next midi channel.
10. Record some midi chords, duplicate the region onto the 2nd track and shift to the end of Track 1's midi track so there's no overlap and it'll be clear which is which when it's bounced
11. Right click, bounce in place.

I'll give VEPro 7 a go now.

So it seems it's an issue with Play in VEPro 6 when it's hosted as a VST (on the PC this is the only option, and on Mac I have a choice of VST or AU).

Realtime & offline bouncing, bounce in place, freezing - all of these work fine if the Play instance is AU. If I have the exact same setup but with Play loaded in VEPro as a VST plugin, I get the dropouts.

Freezing the track also results in the dropouts

My PC Slave machine is cutting off the tails of EWHO samples when hosted in VEPro 6 (latest versions of both Play and VEPro). They play back fine in real time, but as soon as I either Bounce in Place or Bounce the Project offline, it cuts each sample. This doesn't happen with Orchestral Tools' Metropolis Ark 1 hosted in VEPro on the PC, nor does it happen with Spitfire's Albion V Tundra (both of which are Kontakt instruments), which makes me think it's something specific to VEPro and Play.

There is no additional processing within LPX on the host machine. Reverb is turned off in Play on the PC.

As an additional test, I've just loaded the latest version of Play on the Mac host with a cello sample from Goliath (plugin in Logic without VEPro) and this does not cut off the samples early when offline exporting, but if I run a local VEPro server on the Mac and hook it in that way, I get the same issue as I was getting for instruments hosted on the PC. So it only happens if Play is hosted in VEPro (locally or on a slave machine, on Windows and Mac).

Is this a known bug, or has something not quite been set up right at my end?

Play, VEPro & Logic are all running the latest versions.

Same here, except with VEPro 6.

VEPro 6.0.18442
Logic Pro 10.4.7
OS 10.14.6

Anyone?

Does anyone know a way to automate it globally so it's not on a per instance basis?

Is there any update on this?

Is there a way to assign this as a global parameter? So that in my DAW, when I select a track and press the assigned button, it'll disable/enable whichever track is selected. At the moment, it's only applying to any instances that I've manually set it up on.

I would have just commented on the old one but for some reason it wouldn't let me. Think it might be closed.

Does anyone know how to resolve the issues posted about in this thread:

http://vsl.co.at/community/posts/t32838-incoming-network-connections#post207269

I've removed all authorised connections and re-added them all in the firewall, but VEPro still comes up with this when I open it every time. It doesn't happen when the firewall is disabled.

This would be a great new feature :)

I also get this on OS 10.11.1 (had it before that too). Usually I noticed it when I'd quit logic completely, my windows slave would disconnect fine, but more often than not, my localhost server connection would stay active, even though logic had completely closed! If I reopen logic, those instances don't reconnect, it's like they've frozen. To resolve this I have to force disconnect all in the local server, and then just reload my logic template and it all reconnects fine. 

Very odd indeed!

I recently upgraded my systems so I've got the slave pc and a 4GHz iMac 5k host now. The problems have mostly gone away, although I occasionally get crackles and pops and a popup saying 'error while trying to sync audio and midi: sample rate ..... not recognised'. I don't know what causes this, but for the most part a quick pause and then play sorts it out. The main issue I was having before has been resolved with the upgrade, partly because I'm now hosting some of the smaller samples/ones I don't use as much on the new host, so the slave can focus all its power on the more system intensive samples (I use VEPro on both machines for ease of project management). I have yet to try a full template with the new systems, but I found on the old system it became bearable if I only kept the instruments I absolutely needed connected. I'm still getting about 90% cpu usage on the 3.5GHz 6-core slave though when I hit play (10-12% idle), so I'm not completely it's totally set up right, or if it is, these samples are just very system intensive, even for my specs!

Hi,

I've copied across some files for templates (M-Frames and channel strips etc.), but when I try to open them on my mac, I get this message (see screenshot).

I also can't load channel strips properly, it only loads the right number of channels with the name, but doesn't load any samples and the play instance isn't showing in the V-instance.

Is it not possible to transfer them across from PC to Mac?

Hi,

will any e-licenser key (eg. http://www.gear4music.com/Recording-and-Computers/Steinberg-USB-Copy-Protection-eLicenser-Key/64T?origin=product-ads&utm_campaign=PLA+Shop+-+Steinberg&utm_medium=vertical_search&network=google&adgroup=*All+Products.+Steinberg&merchant_id=1279443&product_id=7949d1&product_country=GB&product_partition_id=87577298599&gclid=CNL1mZ6Z4cgCFWnkwgodUA0BGA#full-des) work with licensing my VEPro? Or is the only one that works the one that is on the website here?

Peter

Originally Posted by: Cyril

Use KeySwitching on one track for each violin

Get rid of Play instrument if you can, VSL have beatifull strings (I was a QLSO client)

I don't think play offers the functionality to load them all into one channel and switch via keyswitches sadly (unless you know of a way!)

Don't think I can afford VSL right now (I'm a poor student :p ) and I really like the libraries I've got, even if I can't quite work out the best way to set them up!

I've also noticed that the midi chase function in logic does not appear to work when using this template.

Originally Posted by: Cyril

Originally Posted by: pmjbaumann

Originally Posted by: marnix

Hello Sunny,

Can you please send me screenshots of your Logic MIDI Environment, so I can see how things are set up on your system?

And perhaps it would also be helpful if you could re-save the project on your computer and send me a zipped copy of this, so I can try and reproduce the problem you are experiencing.

Best, Marnix

Attached are some MIDI environment screenshots I've just taken. From the looks of it it's actually set up identically to the 2x48 template. VEPro 1-3 are hooked up to midi ports 1-48, and 4-6 are hooked up to a second set of 1-48.  Although I may be totally misreading the data as I have never seen anything like that before ha!

 

This setup is totally crazy !  it is adressing 1536 midi channels ! ( 2 x 48 X 16)

Why do you need 1536 instruments ?

it is quite normal you are having problems !

My Orchestral template is using 100 instrument so 100 midi channels and it is using all the Levell II articulations of those 100 instruments

I don't need that many, but I need more than the basic one for my Hollywood libraries (ie. Violin 1 sustained, legato, portamento, pizz, staccato, staccatissimo, bartok pizz, col legno), and then violin 2 etc. When I set these up on 1 v-frame each (violin 1, violin 2), my CPU went through the roof on the slave pc. I'm now trying to add instruments to 6 v-frames (each with 10-16 play instances in them - ie. strings, woodwind, brass, etc.) to see if that helps to resolve my CPU issues.