Vienna Symphonic Library Forum
Forum Statistics

196,182 users have contributed to 43,014 threads and 258,396 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Cubase 5.5 Export Audio and VEP 4.0.6150
  • S
    S

    I use two systems, one with Win7 64 and one with Vista 64. My Cubase project uses an instance of VEP locally and one on the remote system.  It all works fine when composing and playing back even with 6150 and Cubase 5.5.  If I export at real time it doesn't lose anything off of the front of the song.  If I export faster than real time it loses the first 3-5 seconds of each track. 

    In my case I use MEAP to export one track at a time have this problem, so I know it's not too much data or anything.  The export starts from the beginning of the midi track but you can see there is no meter movement in Cubase or the VE Pro mixer until it is part way into the export.  At real time, the meters begin immediately and you don't lose anything.

    I even tried just exporting one of my tracks manually and moving the midi data farther down but still starting the export area at the front of the timeline so as to give it a few seconds to start up -- but it still loses the first part of the music.  I just assumed this was a Cuase 5.5 issue.  But now beatpete makes me think it was introduced in the new VEP pro.  For me it's just an inconvenience now.
  • K
    K

    Do you experience this also without Kontakt in the VE Pro instance? Thanks.
  • S
    S
    last edited
    last edited

    @Karel said:

    Do you experience this also without Kontakt in the VE Pro instance? Thanks.

    Karel,

    Just tested it. You may be onto something.  With only the Vienna Instrument it exports properly.  But with only a Kontakt 4 instrument, it misses almost the first nine seconds of the audio data.
  • B
    B

     I'm wondering if this might have something to do with the new Kontakt 4.1 "quick load" feature. I'm not sure how it works but it could be the culprit (however, again it works fine in VEP 4.0.5436). CSTeam, are you using Kontakt 4.1?
  • S
    S
    last edited
    last edited

    @beatpete said:

    CSTeam, are you using Kontakt 4.1?

    Yes, I am.  The test Karel suggested seems to narrow it down to Kontakt.  And you may be right about the quickload feature.
  • B
    B

     Karel: Are you testing with Kontakt 4.1? I'd rather roll back VEP than either Cubase or Kontakt (I love the new quick load feature btw).

    CSteam: did you try rolling VEP to 4.0.5436?
  • K
    K

    Strangely enough I haven't been able to reproduce this behavior even with Kontakt 4.1 in the VE Pro instance. Will keep trying to find out what makes the difference.
  • S
    S
    last edited
    last edited

    @beatpete said:

    did you try rolling VEP to 4.0.5436?

    No if I may if I have the chance.

    Karel, my happens when I don't have any Vienna Instruments in the VE Pro instance, just Kontakt 4.1.
  • K
    K

    So having a Vienna Instruments in the VE Pro instance actually fixes the behavior?
  • S
    S
    last edited
    last edited

    @Karel said:

    So having a Vienna Instruments in the VE Pro instance actually fixes the behavior?

    It seems.
  • B
    B

    Karel, I was finally brave enough to migrate from v4686 which has been working well for ages, due to the lure of PLAY compatibility (I try not to update if everything is working!).

    However, I've just encountered the same problem as the original poster.  The severe delay while bouncing seems only to affect those instances of VEpro that have K4.1 loaded.  I haven't discovered a fix and so am going to have to roll back to 4686.

    Unlike the OP I'm on Cubase 4.5 in XP64.  I'd love a solution or an update if you have one.

    Regards
  • B
    B

    fwiw I took the OPs advice and rolled back to 5436 (rather than my old fave 4686!) and so far so good.  Export Audio (bounce) is working again and even PLAY seems to be behaving.  Seems to be an issue with the new release and K4.1.  Hopefully PLAY 2.018 behaves with 5436.

    Disclaimer - I've only been working 20 min or so.  I'll post back if I get probs with either exporting or PLAY.

    Brett
  • B
    B

    So far so good.  5436 is working better than 6150.  PLAY is behaving, and audio export is fine.  fwiw (and this prob belongs in another thread) but I noticed that 6150 would take a while to "let go" of Cubase once Cubase was shut down.  6150 also wouldn't let the computer shut down without force quitting on occasion.  5436 is fine in both regards.

    Brett
  • B
    B
    last edited
    last edited

    @brett said:

    So far so good.  5436 is working better than 6150.  PLAY is behaving, and audio export is fine.  fwiw (and this prob belongs in another thread) but I noticed that 6150 would take a while to "let go" of Cubase once Cubase was shut down.  6150 also wouldn't let the computer shut down without force quitting on occasion.  5436 is fine in both regards.

    Brett

     

     Exactly! Not only does 5436 export properly but it's much quicker to "let go" (as you said) of the VEPro plugin. Fortunately this is an acceptable workaround but a workaround none the less.
  • K
    K

    I've already fixed this for the next update release, which still needs to go through beta testing though.
  • B
    B

    Thanks for the acknowledgement Karel.  Great news.

    Thanks once again - Brett
  • S
    S
    last edited
    last edited

    @Karel said:

    I've already fixed this for the next update release, which still needs to go through beta testing though.

    Karel,

    For clarification, did you fix the export problem or the VE Pro not letting go of Cubase problem?
  • K
    K

    The problem when rendering where up to a couple of seconds of the beginning of the resulting audio file would be silent. I haven't been able to reproduce the letting go thing.
  • S
    S
    last edited
    last edited

    @Karel said:

    The problem when rendering where up to a couple of seconds of the beginning of the resulting audio file would be silent. I haven't been able to reproduce the letting go thing.

    That's great news, Karel.  Thank you.