Anyone Automating with iMediaTouch and Axia Pathfinder?

[Kate C]

We are in the process of upgrading from iMediaTouch v4 to Enterprise, and along with that upgrade, we purchased the licensing for the Axia audio routing interface (not the IP Drivers, though- we are still using analog audio outputs from OnAir) for our two OnAir machines. The interface is supposed to work with our Axia Pathfinder PC to provide feed-based audio routing for automation, but I've had no luck actually getting it to do that. iMediaTouch is trying to help, but...

So far, I've established that the connection between OnAir and Pathfinder is good. OnAir will respond to GPIs sent from Pathfinder to advance the log. I just haven't had any success with getting OnAir to communicate to Pathfinder that it needs to route audio. Just wondering if anyone has had any experience/success using these two systems together.

 

[Kelly A]

I haven't worked with the iMedia Touch and Axia combo, but have quite a bit of experience with the same sort of interface for Enco and Axia. In the case I'm familiar with, your automation workstations communicate with Axia nodes and Pathfinder via IP over the Telos Axia network. If not already a Livewire device, it must have the Axia drivers installed in order to communicate as a Livewire device. If not purchased from Telos, the drivers are supplied (usually at a price) from your automation software provider.

 

[Kate C]

I haven't worked with the iMedia Touch and Axia combo, but have quite a bit of experience with the same sort of interface for Enco and Axia. In the case I'm familiar with, your automation workstations communicate with Axia nodes and Pathfinder via IP over the Telos Axia network. If not already a Livewire device, it must have the Axia drivers installed in order to communicate as a Livewire device. If not purchased from Telos, the drivers are supplied (usually at a price) from your automation software provider.

Thanks, Kelly- That's what I was afraid of. I think iMediaTouch was assuming I had the IP driver installed. I explained to them yesterday that I was using the ASI card, and the tech said he'd have to reach out to the Dev team for an answer. I'm waiting to hear back.

 

[Kelly A]

Thanks, Kelly- That's what I was afraid of. I think iMediaTouch was assuming I had the IP driver installed. I explained to them yesterday that I was using the ASI card, and the tech said he'd have to reach out to the Dev team for an answer. I'm waiting to hear back.

No problem. Sure, if your playout workstations have the correct drivers installed, they will appear as just active devices in Pathfinder. Once the drivers are installed, you'll need to probably close and restart Pathfinder for the machines to be discovered on the network, but that's pretty standard for any new device being added.

 

[Kate C]

Here's an update on this issue for anyone who might stumble across this thread later... The iMediaTouch OnAir system has a 15-character limit for the source and destination names it can send to the Axia Pathfinder. My source and destination names were over 15 characters long, so the OnAir system was essentially sending the Pathfinder abbreviated commands that it couldn't undersatnd. I shortened the source and destination names and the system is routing properly now. No IP drivers needed!

 

[Kelly A]

Interesting. You must have LiveWire drivers installed already. Otherwise, there's no way for Pathfinder to recognize your workstations as valid virtual sound cards.

 

[Kate C]

No Livewire drivers on those machines. The iMediaTouch interface is just sending routing instructions to Pathfinder. The audio outputs feed into an AES node.