Vienna Symphonic Library Forum
Forum Statistics

182,938 users have contributed to 42,265 threads and 254,952 posts.

In the past 24 hours, we have 4 new thread(s), 8 new post(s) and 46 new user(s).

  • One VEP fader goes down on each instance when loading a Logic project?

    This is a strange problem I can't solve:

    I have a VEP Server loaded with several multi channel instances of VEP in it.

    Whenever I load a current Logic 9 project that has any VEP instantiations loaded, one fader on each VEP instance drops down to infinity (off).

    it's usually the 4th or 5th fader on each.  This also happens when I load an empty template configured with VEP instantiations.

    Can anyone help me solve this?

    Thanks


  • I will venture a guess, somehow you have -∞ automation written somewhere in Logic. The fader instructions per se will come from Logic.

    Now, I haven't worked much in Logic, but another guess: there may be some corruption in the files where there is inexplicable behavior. In Cubaseland, we trash/rebuild the preferences when this kind of thing happens.


  • Well, something in Logic is sending a message, but I don't see how it could be automation.  This problem has followed me on two different machines, also running VEP locally as well as on a slave. Preferences have been trashed and rebuilt more than once along the way.


  • Which version of VE Pro are you using?


  • does this happen only with the one project?


  • I think I finally figured it out.  The Template I made must have been corrupted in some way.  I tried rebuilding the template from scratch and it seems to be ok now.  Thanks all.


  • I am having a similar problem.  VE Pro 4.1.8008 (64 bit), Logic 9.1.3 (64 bit), local machine.  One of the faders in a VI Pro instance within VE Pro jumps without any corresponding automation change in the Logic track for the VI Pro instance in question.  You can clearly see the fader moving.  Other channels on the VE Pro are well behaved.  I tried deleting the Region and deleting all automation on the track in question, then reintroducing automation on the track (without the region at the location where the unexplained jump in the fader occurred) and the jump still happens.  I will try rebuilding the VE Pro template to see whether that helps.  It only occurs in one spot in Logic composition.

    Steve