OK.

@MS said:

Brett,

there is one case which can still cause a problem - and there is currently no nice way to solve this, since Kontakt does not support samplerate changes on the fly. When previously having run VE Pro server at samplerate 44.1kHz, then quitting the server - and starting it again, loading an .mframe or .viframe file from the server window itself - then connecting from a sequencer running at 48kHz. Is this the case here?

Thanks for your reply Martin - sorry, for not being as prompt but I haven't had a lot of time for testing.

No, the above scenario that you mentioned does not apply to me.  I'm at 48kHz the whole time.  This is what happens...

If the night before I have saved my cubase 4 project with all instances of VEP 'disconnected' (not preserved), then when I load the project the next morning the scripting for the leg LASS patches is broken.  However, if the night before I saved with all VEPs 'preserved' and I load the project file the next morning, then the LASS scripting works as it should (however I always get a crash with the 32-bit server this way - detailed in another thread, still not solved)

The cubase project file is a large one, encompassing many cues spread of over a 2 hour film.  Oddly, if I start a new project with only a couple off LASS legato patches, the above behaviour cannot be reproduced.  I don't know if this is to do with the complexity of the project or because I started this project using the previous VEP build, however with my current project, the above behaviour is entirely reproduceable (as are the crashes I mentioned)

With respect to the LASS scripting, I'm not entirely sure that LASS and or Kontakt is isn't at least part to blame as very occasionally the scripting breaks mid session.  There are a couple of threads on the LASS forums where this has happened to users in Bidule also.  However, the fact that here scripting 'breaks' depending on whether a project was connected or not to VEP prior to saving suggests that there is some interaction with VEP....or something....

I feel like I'm on my own with these two problems.  Any suggestions?

Brett

I am the original poster of this thread, and I wish I could report that everything is running smoothly for me, but two slight problems remain.  (I'm on OS 10.5.8 running PT 8.0.1 on a 2X2.66 Quad Mac Pro).
 

LASS seems fine now.  For the Trumpet and Mr. Sax T I've noticed that cc11 breaks very frequently.  The other scripts seem to work.  Sometimes I can reload the instrument or press "reset" on the Sax GUI and it fixes it.  Other times it doesn't.  Last night I ended up taking the Sax out of VE Pro and putting the Sax directly into ProTools.
 

Also, in two projects now, toward the end of the projects (say in the last 20% of the song) I'm getting crackles when the Trumpets play.  They are intermittent and inconsistent, but I have to bounce to audio files a few times until I can get it clean.  Odd that the crackling only occurs at the end of the piece, even if the Trumpet is playing at the beginning.

No, LASS does not work correctly at all on PC.

I noticed from what other users said that on MAC the problem seems to have disapeared. Maybe it has somthing to do with Kontakt's memory server??

But on PC - Xp64 - the issue is still there. I tried this on three different systems, plus it seems that other PC users have the same problem with LASS (and possibly with other kontakt libraries). The only workarounds that I know of are:

1. Only work at 44.1 KHz sample rate. This is a disaster for the TV/Film composers. What I do though at the end  of a gig (when I do the music Delivery) is use Voxengo R8brain pro converter to convert everything to 48 KHz and then submit the audio. Otherwise, for director's approval, I use MP3's anyways.

2. After loading a preserved VEP metafile (or VEP instance), link it to Cubase, then reload the LASS MULTI in Kontakt. This takes a lot of time. Then I need to remember to disconnect that instance of VEP everytime I save a Cubase project. Then connect back. This way the Kontakt multi remains uncorrupted. It only take a few seconds (disconnect/SAVE/connect) but if I forget then next time I open that cubase project I corrupt the scripts.

I am happy for John and the others (on Mac) who stopped experiencing the problem, but I hope the issue (on PC) will eventually be fixed.

Agreed Catalin! There are very few of us according the the response on this forum.  I think the majority here are on Mac.  I wonder if it's an XP problem?  I'm on Cubase (32-bit) in XP64 running both VEP32 and VEP64 servers.  I generally don't work in 'preserved' mode which seems to help for me although I lose the benefits of preserving which is great swapping projects or recovering from a crash.  I will port to W7 in time to test there but until then...

Hi,

As you know, XP64 is not a supported platform for VE PRO. We are mainly working with Win7 here, it´s a great OS.

It could well be that your troubles are OS-related.

Best,

Paul

You may be right Paul, however at least one of my problems (the crashing of the 32-bit server upon loading a cubase project) appeared only in the latest build so may not be entirely XP64 related.  Karel said he could not get VEP32 to crash following my repro, but perhaps he wasn't testing in XP64?

W7 isn't released for another week, and many musicians using PCs have leapfrogged Vista for many well documented reasons, so W7 isn't a realistic option right now.  Soon though!

Brett

Hello Brett,

I´m not sure how Karel tested, but why should he test VE PRO on an unsupported platform in the first place? I assume he was referring to XP32.

Best,

Paul

Dear Wolfsterik and Nick Harvey,

which version of Vienna Ensemble PRO do you have installed exactly? With the latest build (Vienna Ensemble PRO build 4536) and Kontakt 3.5 (OS 10.5.7) I cannot reproduce the problems you encountered.

/Regards,

Maya,

I have 4.0.4536 installed on all machines. slaves run on OS 10.6.1; master runs 10.5.8. Kontakt is version 3.5.025.

It's seems to be an intermittend bug. It remember it to happen like this: fresh reboot of all MAcs - load template, things run fine for a while; closed Logic project - opened same template - some Kontakt channels won't play any more. I did try it with a new Logic project to rule out an error in my template, but encountered the same problem (but the bug might have already been in the system by then). And I think it happened when I left the VE PROs connected.

I'll try to determine the steps to reproduce it as soon as my schedule permits.

Hi Maya.

I'm using the latest version of VE-Pro (4536) on all computers. My two slaves are OS10.6.1, my main DAW is OS10.5.8 and the Kontakt version is 3.5.0.025.

The small template (5 Kontakt tracks and 3 Omnisphere) that I emailed you as an example of the midi tracks not working is still problematic. Even when setting it up I wasn't able to trigger the last two Omnisphere tracks 7 & 8 and have reloaded it numerous times to no avail. I've tried taking the second slave (unused in this example) out of the network but it doesn't make any difference unfortunately.

My ethernet hub is a 5 port 10/100 mbps switch. Not sure if this is relevant...

Thanks.

Nick

Edit: Just bypassed the hub altogether and plugged the MacPro directly into the MacBook Pro. Still the same problem, so I guess the 5 port switch isn't at fault.

So before I go through the trouble of upgrading to Windows7...Is it confirmed that LASS/Kontakt 3.5 don't have the "Broken script behaviour" on Windows 7 and VEpro 4536?

Thanks.

Incidentally I've just tried to create a new template omitting Kontakt altogether. Only using Omnisphere, when I reached the fourth midi track the 'no sound but obvious triggering' problem occured.

This obviously indicates that the problem doesn't actually lie with Kontakt at all.

Nick

OK. Getting somewhere now.

I took my main MacPro out of the equation and used one of my MacBook Pro slaves as the DAW and the other as its slave. I then loaded up numerous Kontakt midi tracks and they all worked fine.

I guess that this means that the problem is probably at the MacPro end of the chain. Obviously this still needs to be my main DAW, so until a fix can be found (wherever the fault lies) VE-Pro is sadly unusable for me.

@Nick Harvey said:

Incidentally I've just tried to create a new template omitting Kontakt altogether. Only using Omnisphere, when I reached the fourth midi track the 'no sound but obvious triggering' problem occured.

This obviously indicates that the problem doesn't actually lie with Kontakt at all.

Nick

As posted here: http://community.vsl.co.at/forums/t/23126.aspx

Also having troubles with LASS

We need a fix for this as soon as possible...

Mac Pro 2 x 2,93 GHz, 16 GB RAM

OS 10.6.1

Logic 9.0.2

Thanks for the link to the other thread. Yep, that's what's happening my end too.

Sorry to hear you're having problems, but glad that Wolfsterik and I aren't the only ones encountering these issues.

Nick

hanging notes here:

LASS +

Ensmeble 3 pro +

Kontakt 3.5

Driving me up the wall.

Getting stuck notes on bank changes....a lot.

I am also using VST expression maps.

I'm happy to stand corrected on this point but as I understand it, Steinberg has Cubase send out a 44.1kHz 'ping' upon startup (why???), which if you're working at 48kHz is confusing for Kontakt (which is already open in VEP) which interprets this as a sample rate change.  If you just click OK on the message all will be well. 

For what it's worth, LASS and The Trumpet are mostly behaing here, but I'm still on v4686!

Brett