External Insert Offset after X1a patch

I remember checking the automatic offset delay calculation of the External  Insert in the original release of X1 and was very happy to find that it was working perfectly with my system.  I then applied the patch (and the hotfix since I have a Lynx AES16e and lost my ASIO drivers after installing the patch).  Now External Insert doesn't even do a delay offset calculation.  It's not that it does and gets it wrong.  It just do any.  The astrick appears in front of the displayed delay in the external insert window so it knows it needs to do the calculation.  It just doesn't do one.

Can someone else check this?  I filed an official problem report but I am curious if this got broke with the patch or the hotfix for the Lynx ASIO drivers.

Don

Thanks for the reply, Dave.  When I mentioned automatic delay offset calculation I wasn't really talking about a check box option.  Automatic as opposed to manual calculation or trial and error.  The asterisk sits in the delay button beside a 0ms value and no amount of clicking on the button or starting/stopping the transport will trigger a recalculation even though I assume the asterisk indicates that the External Insert function is aware that one needs to be done.

If someone else who uses Lynx ASIO drivers and has applied both the patch and hotfix could confirm that they see the same thing it would give me confidence that it isn't just something unique with my system.  If no one else sees it I will need to dig in a bit further.

I am certain that the developers will get it straightened out if it is really a bug.  Until then I guess I will need to try the values from 8.5.3 and do the offset manually.  Not the end of the world but not as convenient.

Thanks,
Don

Thanks Brundle.  I'm pretty sure everything is configured and connected correctly.  I have no trouble with External Insert under 8.5.3 or even under the original release of X1.  It's only when using the X1a patch AND the ASIO driver hotfix required for Lynx hardware.  And if I manually enter the delay everything works as expected.  So I'm pretty sure it's a bug - or something unique to my setup that is interfering with the recalc.  Since the External Insert dialog box knows that it needs to do the recalc and the audio path works perfectly with a manually entered value equal to what it calculated under 8.5.3 my money is on a bug.  My official problem report is sitting without any response but I imagine the developers are quite busy.

Don

Don I had the usual Lynx nomenclature headache ( I only see odd number I/O in Sonar all are visible in Lynx page), after actually pinging with my Lynx window up to see what Sonar was calling it, I realized that for some reason the audio engine gets knocked off sometimes in the pinging process...ping remains blank and uneventful in this case...I would never assume you would be as pedestrian in your approach as I was but...just in case...

I am running the patch for the Lynx ASIO drivers, and am using the actual A/D not the AES card I have installed...

So sorry I'm not much help I did get it to ping/manually adjusted and it works great now...

Hi Don,
I seem to remember that if you use EI on a track that is muted anywhere along the audio path the delay calc won't work.  So, if the track that it's on is muted, or another track is solo'd, or if EI is on a bus that is muted or on a bus with no tracks routed to it.  Those kinds of scenarios have caused me headache on more than one occasion with the delay compensation function.

Dean