Merging Technologies

The setup:

- AES out 1 > AES in 1 - I can play digital audio through this loop just fine

- add AES out 2 > Weiss eq > AES in 2 - as soon as this loop is made all AES inputs mute

At first I thought it was the Weiss eq at fault, but I tried a few different pieces of gear in that spot and get the same results each time. If I remove the gear and just connect AES out 2 > AES in 2 it works fine.

HAPI is on internal clock. Seems to me it is experiencing clocking problems as soon as the 2nd AES loop is connected and that's why it is muting, but I can't for the life of me figure out why.

As best as I can tell, this problem seemed to manifest after upgrading HAPI to the 3.0.70 build 28889 firmware and v10 ASIO driver. Prior to these updates I was using this same setup daily for months with no problems.

I tested with both Pyramix and Samplitude, same results.

Anyone else seen anything like this?

Best,

- J.

Hi J.

What are the buffer settings in the Merging Ravenna ASIO Settings Control Panel? Try 64 or 128 smpls if it is currently higher.

We have had a number of intermittent AES issues with both Horus and Hapi similar to what you describe. Multiple reboots seem to eventually resolve it. However, please report these to Merging as I suspect there is still something not ironed out here.

-Silas

Hi Silas, I had the buffer at 256. I just tried 128 and 64, no change.

I just did some further testing too - it seems that plugging in the 2nd AES loop to the Weiss eq actually does allow signal to pass on the AES 2 input, but it mutes AES input 1 as soon as the AES 2 loop is connected.

So strange! I have reported it to Merging via the tech support form.

Best,

- J.

And I just went back to the last v9 ASIO driver, in case that was somehow the problem - but no, same behaviour with the v9.1.6 ASIO driver.

As far as I can tell, the only other thing that changed before this behaviour began was the HAPI firmware update to 3.0.70b28889.

archive wrote:As far as I can tell, the only other thing that changed before this behaviour began was the HAPI firmware update to 3.0.70b28889.

Figured I might as well try rolling back the HAPI firmware while I'm at it, so I went back to 3.0.3_26178 and lo! it works normally again.

Does this mean I've discovered a problem with the 3.0.70_28889 firmware?

Is there an download archive somewhere with all the firmware versions?

archive wrote:Figured I might as well try rolling back the HAPI firmware while I'm at it, so I went back to 3.0.3_26178 and lo! it works normally again.

Does this mean I've discovered a problem with the 3.0.70_28889 firmware?

It looks like you have. You had better get on to Merging and update them on what you have discovered.

Heard back from Merging, this is now a confirmed issue with the Hapi firmware. The last firmware version that does not show the issue is 3.0.5_28606.

Best,

- J.