@Karel said:

Logic sometimes needs a transport stop/start to apply AU latency changes. Does this help in any way?

No, it didn't help when bouncing externally-hosted instances - I tried it several times with the same result.  I did try it with sources on the same Mac, and those would eventually line up after a few stops & starts (I even flipped the phase on the resulting file to see if it would null).

It does feel a bit unsettling to wonder if things are being properly compensated... after all, my main interest in VE Pro is in being able to bounce my slave tracks offline.   If that doesn't work reliably, I'm back to square one unfortunately.

Hope it gets sorted... thanks!

That's strange. For the time being you could first set the VE Pro Server Interface plugins to 0 buffers of latency before bouncing. But this really shouldn't be happening.

Thanks Karel.  Yes, in further experiments today, I've found that if I switch to 0 buffers before bouncing, everything's fine for both internal and external instances.  If I leave it at 1 or 2 buffers, the resulting audio has that many samples of dead space before the actual audio starts.

Definitely something for the fix list.  It's an easy workaround, but obviously would get to be tedious every time you want to bounce a track!

The latency compensation does work for you when not bouncing?

@Karel said:

The latency compensation does work for you when not bouncing?

Yes, it works in realtime playback, although it does seem to shift around every so often (depending on track selection).  It's just offline bouncing that seems to be the problem.

Thanks for looking into it!

While certainly not identical, this problem seems reminiscent of the problem Cubase 4.x and 5.x users are having on the PC with bouncing/exporting audio.  Everything is fine on realtime playback but a large delay on rendering/bouncing the audio.  Ours was looking like a Kontakt 4.1 issue related to the latest VEP build, but not so here.  When I rolled back to the previous build (5436) everything was fine.  Perhaps you could try that?

Brett

I just built a test project to test if this occurs on my system. My answer was - no - latency compensation works fine here using OSX 10.6.4, Logic 9.1.1, VEP 4.0.6150. Everything was running at 48kHz as it always is here.

I wasn't however using Omnisphere or tempo sync. My test was simply to create 2 instances of Kontakt 4.1.1 and to load a short clicky drum sample. One of these instances was hosted locally, directly into the master Logic project, the other instance was loaded via VEP into the 64bit server on a slave Mac Pro.

I found that the clicky drum sample was properly synchronised between the local and remote (VEP) instances of Kontakt 4.1.1 during playback and for both online & offline bouncing. 

I guess your problem is either specific to your system, or to Omnisphere.

I can send you my Logic project file & metaframe if you would like to test it.

Out of interest, are you running Logic in 32 or 64bits? (32bit here as firewire video doesn't yet work in 64bit)

Thanks for the info - much appreciated.  The only apparent variables in our systems are that I'm still on OSX 10.6.3, and you're on 10.6.4.  Other than that, our systems & software versions appear identical.

FYI, I've tried this with instruments other than Omnisphere; I've also tried Kontakt, PLAY, Vienna Instruments, etc.  It happens in both 64-bit and 32-bit mode in Logic as well as 32-bit & 64-bit VE Pro servers, and also locally-hosted vs. slave-hosted VE Pro servers.  Same result no matter the combination.

Can you tell me your Logic pref settings?  I've got latency comp. set to "all" but that didn't seem to affect results either...

Thanks again - I'll keep digging further!

Protools users have no choice but to bounce in realtime.

What you hear is what it is.

Why not just bus it, and record it?

@jeremyroberts said:

Protools users have no choice but to bounce in realtime. What you hear is what it is. Why not just bus it, and record it?

Hey Jeremy,

I totally get what you're saying, but:

1. This issue is regardless of offline vs. realtime bouncing, so either way something's wrong (assuming it's not something specific to my setup, which I'm trying to rule out).

2. For archiving purposes, I render all MIDI regions as audio because change is inevitable, and recalling a project even 6 months down the road can be a nightmare if my setup has changed at all.  Even without that factor, realtime bouncing just gets to be incredibly tedious on larger projects, especially when everything starts as MIDI.

3. Even after realtime bounces, I still listen back to stems to double-check everything before delivery.  If I'm listening back either way, it would save years of my life to bounce offline first.  The feature is there in Logic, VE Pro supports it, so I'd like to use it 😉

@whinecellarstudio said:

The feature is there in Logic, VE Pro supports it, so I'd like to use it 😉

And that's all that really matters! I would feel the same way.

If PLAYBACK is good, but BOUNCE is not, then something is definitely wrong.

@jeremyroberts said:

If PLAYBACK is good, but BOUNCE is not, then something is definitely wrong.

Yep, just need to figure out where the problem lies, as it doesn't seem to happen for everyone.  I'll report back with any news...

Jim.

I've been having the same problem as you since I first starting using VE-Pro last year. 

I brought it to VSL's attention and Maya from VSL tried to replicate the problem back in November, but although a few emails bounced back and forth nothing was resolved unfortunately.

I'm using the latest VE-Pro update with Logic 9.1.1, OS 10.6.4, a Master MacPro and two slave MacBook Pros. The latency issue occurs both when using the servers on the slaves as well as solely on the MacPro.

Nick

Thanks Nick.  Good to know it's not just me!  Karel, I will send you some samples ASAP.  In the meantime, my Logic buffer is always set to 128, and as I reported previously, the problem only occurs when the VE Pro plugin buffer is set to 1 or 2.  When set to "none" everything is fine.

More info to follow...

Sounds like Logic simply doesn't do any latency compensation whatsoever when rendering. Logic is rather bad at handling dynamic latency changes, but still seems very strange that it only happens with some users while others are unaffected.

@Karel said:

Sounds like Logic simply doesn't do any latency compensation whatsoever when rendering.

I'm not so sure it's on the Logic side though, as I don't have this issue with any other plugin or instrument - just VE Pro.  And again, the issue only occurs when the VE Pro plugin is set to 1 or 2 buffers, so that makes me wonder if VE Pro is properly reporting its latency?

I'm certainly not ruling out Logic as the culprit, just that the issue only occurs with VE Pro...

Well, I just started from scratch with a new Logic 9.1.1 (32-bit) song, a new external instance of VE Pro (32 bit server) running on a brand-new iMac.  The AU I opened is U-He Zebra 2.5 with a tempo-sync'd arpeggiator patch.  Sure enough, same thing, and I took a screenshot showing the various latencies related to the VE Pro plugin buffers:

http://i751.photobucket.com/albums/xx152/whinecellarstudio/Software%20Bugs/VEProbufferbug.jpg

From the top down: original MIDI region; VE Pro plugin set to no buffers, 1 buffer then 2 buffers.  You can clearly see the buffer amount added to the beginning of each audio file as dead space.  I can't find a way around this. and it happens on all 4 of my systems (all with same specs).