'Been running fine for years. Have taken a long break recently from the studio, now VEPro produces constant audio dropouts. I' getting dropouts on both the master and slave. 1 to 2 seconds or longer cutting in and out if holding down the note, often the note won't sound. During my break there were no changes to the studio, no upgrades etc. Simply had machines off for a couple months, except master machine for internet use.

I don't know where to start, any advice appreciated.

OS 10.8.5 both machines / Pro Tools 11 on mater / VEPro 5.2.12808 on both / no wifi on either machine. Network settings configured Using DHCP / IP addres same but plus 2 on slave for last digit, subnet masks, router and DNS server numbers same on both

I'm about to install RealGuitar and RealStrat and use it on my VEPro machine. Could you tell me any more details of the workaround, for example how to use it? Thanks.

What's the latest on this?

Thanks Karel.

Motu have been notified by many customers / users for a long while about this.

Might be time for me to switch to Logic like many others I know have done! Thanks for your assistance along the way with this.

UGH SCRATCH THAT. I had no problems for about 2 weeks, and now, today, every time I close a DP file I'm working on, copy it, rename and open to start working on a new file, I lose all AUX inputs again!!!!

No other crashes though, dare I say it. But the above confirms this is a DP issue although the crashes etc were resolved by going back to the old VEPro version.

I guess I MUST be doing something different from yesterdays work (for the last 2 weeks) but I don't know what. The confusion that has resulted is driving me really crazy and I'm frankly getting really tired of it.

Yes it does, and that is a motu issue. 

However I think it's important to note that since going back to the originally released version of VEPro, I have had NO issues at all.

Please also note that via personal email Vienna have been very responsive, and gave me a link to download the old version to go back. We don't know what my issues are but the response at least from Vienna is very much appreciated. 

With the latest version (and remember I skipped ALL versions between the original release and this one) I could not open an old file, nor copy a newly created DP file and rename it as a new one and continue work, without major hassles. going back to the old version of VEPro I don't have any issues at all.

Hey Chris I don't know if this has anything to do with it but always worth a try. Sorry this is such a small thing for a big problem but at one point in my studio the eLicensor would not work and I thought perhaps my dongle had fried. But the dongle worked fine on my other machine so it wasn't that.

I called apple and they asked me to shut down the machine. Disconnect ALL cables EVERYTHING. Wait 2 minutes. Reconnect and start up.

It solved that particular problem, the USB ports needed to be re-set and that's how to do it. 

Of course this might have NOTHING to do with your problem but always worth a shot I think if experiencing any USB related error messages.

Thanks, I see the reports. Do I cut and paste all the text for each report or is there a way to save it as a file and send it?

Lots of these by the way:

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bc020008

Crashed Thread:  0

etc.

Also btw, went back to the old originally released version of VEPro, no problems so far but will know more after a few saves and new file opens etc. At least I'm back to composing for today.

How do I obtain the crash reports? Please note due to deadlines I must proceed with finding a way through this and getting back to work. As such I have rolled back to the original version of VEP, and this I am hoping now to not experience further crashes when I do. (Today is the first day of going back to the original version so we'll see.)

Thanks.

By the way, a complete restart (shut down both machines, start VEPro machine, load up the 32 and 64 bit metaframes, start DP machine and fire up teh sequence again) results in the 32 bit instances being loaded TWICE. The set up was all de-coupled during the crash.

If I disconnect all instances from teh 32 bit server, then reconnect to the correct instances, then start work again, it all crashes again soon after.

Interestingly, I don't ever have a problem with teh 64bit server. It's always the 32bit one that crashes, or reloads twice etc.

What is the correct procedure I should follow when VEPro crashes?

2 machines: VEPro on its own machine, DP7.21 on my main machine (both Mac OS 10.5.8, both with the very latest VEPro and VI software).

The 32 bit server (metaframe) on the VEPro machine crashes a lot (it has 10 instances inside) and I am never certain what the correct procedure should be to bring it all back online. If I simply reload the metaframe with the 10 instance template, it crashes again upon playback of lots of tracks. I guess I need to restart everything (both machines)? This happens a lot so I was wondering it there might be a quicker solution to restarting. Thanks.

And while we're at it just have a button added to the interface for:

"Fix any and all other studio issues".

I know Vienna can do this, I have full confidence in them.

Thank you!

Hi,

Is there a way to quickly "DECOUPLE ALL"?

For those of us using AU and thus having to have multiple instances, it'd be great if we could hit one button to de-couple all, and un-decouple all when needed instead of having to click through each and every one every time.

minor update:

Started VEpro machine, started and loaded 32 and 64bit metaframes. (Song 1)

Started DP7.21 machine, started DP and Song 1 from example above. Aux in channels are in italics, thus lost.

However, as it tries to complete fully loading the following happens:

VEPro machine now attempts to load AGAIN song 1 metframe material, this will result in a memory crash. So this time I FORCE QUITTED the VEpro 32 but application on the VEPro machine. I know it's headed for a memory crash so I thought I'd see what happens.

After it force quitted, THE DP MACHINE DE-ITALICIZED THE AUX INPUT CHANNELS. 

This is very interesting. Of course I don't know what to do next. But once the 32 bit server was force quitted on the VEPro machine, DP found the aux inputs and returned to "normal".

I would like to go back to my original version of VEPro which is the version that was initially released, and also the version of Vienna Instruments that would be compatible with that. At this website, in the ARCHIVE version dated 2010-08-27 is the oldest available. Is any access available to much older versions? I know that the version that worked for me was before the de-couple feature was released, and I think it was the very first release of the software.

So instead I went back to how I usually start up. Started VEPro machines first and loaded the metaframes.

Started the DP7 machine, opened the Song 2 file. All Aux inputs had been lost. 

Recreated the aux input bundles in DP, Hit SAVE in DP.

DP froze / not responding, and I'll have to force quit and start all over again.

(Force quit DP, restart DP song 2 file, and VEPro machine now tries to load the instances all over again in addition to the stored ones, resulting in a memory error and crash of the VEPro machine).

This has left me with no way it seems right now on my system with these versions, to access VEPro!!!! I am going to have to try un-installing the software and going back to my original purchased version. However I don't recall if it was discs or download? I'll check this site for available versions to re-download if possible.

Hello again, an update.

Today I thought I'd try something that I thought would be fool proof: Instead of loading the metaframes up at the beginning of the day and risk them being re-loaded and twice, I did the following thinking DP7 would tell VEPro what to load in and not make any mistakes:

Started VEPro machine, started the 32 and 64 bit servers. Left them empty ( I don't usually do this).

Started the DP7 machine, started DP7 and loaded SONG 2 from last night (and previous post above).

As expected DP7 pushed the info to the VEPro machine and began loading the servers / metaframes.

The 64 bit version appeard to successfully and fully load it's instances.

During the 32 bit version loading, VEPro 32bit crashed.

EDIT: I tried this again and the same result. The above procedure is repeatable. This is now an additional issue I have.

ALSO please note although the 64bit version push-loaded, in DP7 all aux in assignments are once again, lost. They can only be recreated all over again by creating new stereo bundles for each aux track (one per instance, I have a total of 13 instances).

HI again Paul,

For the moment may I outline my procedure that occurred last night:

Start up Ve Pro machine, start 32bit and 64bit servers. Load my metaframe template for this project (a movie) into each. (each contains several instances, with labels like "LASS strings 1, LASS strings 2, pianos, drums, bass, EWQLSO GOLD PLAY, Orchestra FX etc)

Start DP7 machine, start DP7, open a file I had been working on.

DP7 had lost it's aux inputs (which were labeled VEPro LASS strings 1, VEPro LASS strings 2, VEPro pianos etc as above to reflect what is in the metaframes).

Re-created new aux inputs (new stereo bundles in DP7) etc to get it working again.

Continued writing and recording the music. SAVED the metaframes (32 and 64) (not save as). SAVED the file (DP7).

Closed the DP7 Song 1 file. Copied it. Renamed the copy (eg "Song 2"). Open Song 2.

This time VEPro metaframe attempted to load new instances. Crashed due to memory error (probably overloaded).

The day before, I had worked on a (lets say) SONG 1 file, completed it. Saved it. Re-opened it 4 hours later (after leaving the studio) and all of the VEPro Aux tracks in DP had lost their input assignments. In that particular case all I had done was saved the DP file after completing work. Closed it. No other work on either computer whatsoever. RE opened that same file 4 hours later to discover the above.

Please note this is not a "one off" event, for about a week now opening files has resulted in similar results but in previous cases I am not 100% sure what I did or didn't do that might have been user error in terms of saving the metaframes etc. I outline the 2 particular events above because I am sure of my step by step procedure there. But opening DP7.21 files this past week usually results in lost aux input assignments, disconnections from VEPro, and sometimes re-loading of the metaframes again, resulting in memory errors on the VEPro machine as it attempts to load large files on top of the material already loaded. Reading the mainal very carefully about how that can happen but I thought I had done everything correctly.

I will provide more info as I work further, and when I am sure of what I have done or not done. Thank you.

Thank you Paul.

I will update with any further info especially if I can clarify the exact course of events. Please understand I am busy with composing and deadlines so sometimes my info is not as detailed as you could benefit from in reproducing. Once it works I tend to just try to get my work done and record and move on to the next cue. Allow me to refrain from posting further details until I am sure of what I am saying in terms of procedure. I've looked closely at the manual especially the "song 1, song 2" info which is great, but for me, and I'm trying to notice any user error, it isn't as simple as that it seems. Thanks.

I have another thread here about losing aux inputs every time I close a DP7.21 file and open a new one. It's getting to the point where I really would rather not work like this as I have to reconstruct it every time I create a new cue.

Is there a way to uninstall the program, then I could re-install the original version that I purchased when VEPro was first released? I didn't have this problem before upgrading to the latest versions of VEPro and Vienna Instruments. I assume I will need to go back to both VEPro original release version and Vienna Instruments might also have to be rolled back?

Hi 

What is the correct procedure to undertake for when Vienna Ensemble Pro crashes? (In terms of I now have my sequence sitting open on my DP / sequencer machine, but I've lost the 32 bit metaframe (with multiple instances within it) on the VEPro machine. What to do next for a smooth recovery?

The latest manual clearly spells out how to handle a sequencer crash. But what about when it's VEPro that crashes instead? I'm not sure what to do in terms of what is saved or not in the sequencer if I restart everything, or if there is a best way to handle it. Currently my sequence probably contains the VEPro info because it has been saved during working on it. But now VEPro has crashed, if I close or save the sequence will the VEPro information be lost? Just not sure what to do as I'm still wrapping my head around the connection between the two machines and what is saved and not saved when EITHER machine performs a save!

BTW when I start DP, the old interface shows up trying to examine AU, it can only be "skipped for now" to proceed, then after DP starts, the old interface (the black and dark blue one) keeps spinning and must be forced to quit in Mac finder to get rid of it.

When clicking on a VEPro instrument track in the track list in DP, the new version does show up and appears to work (but I have other issues with it as mentioned in the first post above).

Hi,

I needed to trash Digital Performer prefs due to some issues. When restarting DP I noticed it tried to load up a very old version of VEPro to examine the Audio Units. This of course failed. I know it's an old version because I could see the old interface come up (the very dark blue one).

Should I have some how removed the old version before upgrading to the latest VEPro and VEPro instruments?

(As a side note, a lot of problems with VEPro channels in DP7 for me at the moment since upgrading, not at all sure yet of my solution but wondering if this might have something to do with it. Any suggestions appreciated, thanks).

Hi,

Using VEPro (latest versions downloaded and installed) and DP7.2 on a Mac 8-core, VEPro is on a 2nd Mac 8-core.

Since upgrading recently to the latest versions of VEPro (on both machines, updated VEPro and Vienna Instruments) I keep losing my Aux in assignments in DP that are connected to VEPro. Please note I have been using VEPro since its release. This issue started since using the latest update (my previous version was quite old, before the decouple feature was released).

I can't nail down what I'm doing wrong. THe most obvious example is that last night I worked ona DP file, I have both 64bit and 32 bit servers running. The 64 bit has 3 instances and the 32 bit has 9 instances in the metaframe. Usually I can close and save the DP file, return the next day, open it and continue working (the machines do not get shut down, and VEPro always stays up). Today, again, in DP all of my aux tracks connected to VEPro instances are italicized, meaning no longer available. I click on it, and can select "create new stereo bundle" and choose from a list and re-create the VEpro coming in. But it seems I have to now do this almost every time I open a file. I'm not quite sure but last night I did test it and created this new file, opening and closing and it was fine, but not today, it has lost SOME of the aux ins.

So at the moment I typically now have to always recreate the aux ins (12 of them) every time I re-open a DP file. 

I had been wondering perhaps along the way I've added an instrument or two to the metaframe and I'm not going through the procedure of saving etc correctly to keep everything updated. I usualy work by creating a DP file for the first cue of a TV show with a template etc, but might add an instrument or two along the way half way into the show. I'm fairly certain when I've done this before this update I haven't had problems. I would save the new metaframe and didn't seem to have issues.

But this latest example from last night, I did not change anything since closing it (and re-opening and closing to tesst last night) and now today the auxes have gone.

Please, any suggestions? I must admit I do get confused by VEPro and what you need to do or not do regarding my usual workflow which is as follows:

Start VEPro machine, start 32/64 servers, load the shows metaframe for each

Start DP7 machine, open first file for the show, compose, save close.

Copy first file for show, rename to 2nd file (1m2), open, delete contents, compose 1m2, save and close.

And so on, done this many many times

Sometimes I've had to add an instrument or several, and in the past what I've done in that case is I save the metaframe (on the VEPro machine) with a new name., Then saved the DP file. I don't recall having issues with this.

Any ideas why I'm losing auxes?

Any suggestions for workflow given my usual workflow above (something I've been doing for 15 years, including ever since VEPro came out).

Any help at all would be appreciated. Thanks.

Thanks

(now if only East West could respond to my problems with getting it to work!! This re-installation to the new machine has taken an entire day of troubleshooting with no results. It's a PLAY problem though, not VEPro).