Merging Technologies

Hi,
I have a brand new turn key system from Merging and a HAPI. Ravenna Easy connect is not populating on the Host side, and on the Device side the HAPI is grayed out.

The system was tested and working at the factory. Anyone have a solution for this? What changed?

Just because I've done it before, I have to ask... Are you connected to the correct Ethernet port on the Hapi? If you connect it while standing in front of the unit, it's very easy to accidentally connect it to the top "Sec" port instead of the lower "Pri" port.

Yes, I have made sure the connection is in the primary, not the secondary.

There won't be anything on the Left side until you launch Pyramix.....
-mark

mpdonahue wrote:There won't be anything on the Left side until you launch Pyramix.....
-mark

When launching pyramix, it's not communicating with the hapi, and it gives us this error:

VS3 error: Failed to attach to ASIO driver

Warning: Initialization error
failed to init VS3

Some essential initialization has failed
Sorry, can't continue...

Is the Hapi showing up in MT Discovery?
Is Ravenna ASIO set in VS3 control panel? This shouldn't change, if it was all working before transport, but is still something to check.
Upon launching the ASIO panel, you should be able to see the Hapi, change input & output numbers, etc.
You can do all of these steps before starting Pyramix. By the way I recommend adding MT Discovery to the startup folder. Then you'll always be sure the device is attached and 'seen' by the computer.

On my MassCore systems, each Horus is grayed out and in italics for about 2 minutes 15 seconds. Then they change to solid, non-italics and Pyramix can be run. This is because I have DHCP enabled on the Ravenna NIC. At home (Native system(s)), my Hapi always shows up immediately if the network connections are correct.

Yes, HAPI shows in MT Discovery, but the ASIO in VS3 does not show it, so there is a disconnect somewhere there.

Update: I thought I would try Ravenna ASIO Driver to see if it would allow the connection, and that was a mistake. It actually voided the Hapi all together. So I removed that application, rebooted a few times, reinstalled my license, and now I have no Hapi at all - not in MT Discovery, not in VS3, ... nowhere.

Thoughts anyone? Complete remove / reinstall of Pyramix?

Update: See screen shot.

It seems we were able to retrieve the Hapi in MT Discovery / ASIO / and we see it in Ravenna Easy Connect but it is still grayed out. Based on what you see on Ravenna ASIO Panel, I think this error means the IP address of the Hapi/merging is not in range of the native Network IP. IS this correct? Anyone have suggestions on this problem?

The screen shot isn't coming through. Have you contacted Merging about this? It is highly recommended to do so and soon, before they're gone for the weekend.

Contact the dealer where you purchased the unit. They are the appropriate channel for support. In turn the distributor.

What IP adress do you have in Windows and Hapi?

Please give the specifics of your system.
Masscore or Native
Is the Hapi connected to the computer directly, through a switch or a DHCP router?
MOBO or add on card NIC?
Version of PMX and Windows software?
I have the feeling this is a case of RTFM.

Hi Everyone,

I have very similar problem!
This is NATIVE system: Two HAPIEs, switch Dell (recomended) WIn 10 1803, onboard ethernet card, Pyramix 11
I've install, by the instruction, Merging Ravenna ASIO Driver 11.1.5, ANEMAN, Pyramix 11.

When I open VS3 Controll, and choose Driver name: Merging Ravenna ASIO Driver, appear window with: "The Driver is not properly configured. Please, configure it from the Control Panel. VS3 Control Panel."

But there is nothing else to configured ???

Also when try to lunch Pyramix 11, I can't do this. Next windows with communicates thats something wrong. No chance to open Pyramix!

I will just add that when in VS3 the controller will be replaced with, for example, RME ASIO, Everything working excelent. Pyramix starts and see inputs on RME devices.

I will be grateful for any help!

Seem to be a driver issue. Have you set up yor ethernet card and firewall according to Merging spec?
There are very specific instructions in the Knowledge Base area from Merging.