Hello,

We are using Interplay Capture with 3 Airspeed 5500 to record in 10 channels configuration.

Usually when we record, the editor is able to edit while recording, but two days ago we were recording around 5 channels and the editor was not able to edit, not until the recording was done. Is this normall and is this a limitation?

Also, in one of the Airspeeds we are using, which has 4-channel configuration, only one channel is not usable and we can record on that channel, the rest of the channels are working fine. Does anyone has any idea how to tackle this?

Thanks.

HI,

I might be able to help. But more info is needed.

Regarding the airspeed not being able to use 1 channel. Do you get any error messages? Have you checked the recording profiles and that the incoming signal is the correct format or that the channel can perform up/down conversion? 

Regarding the EWC, have you checked if the transfer manager is checking in the device clip after a few seconds? Is Interplay capture creating the master clip correctly? This could be time sync related. 

In a Interplay capture setup licenses come in groups of 5 while airspeeds have 4 channels (go figure). So in your case is the 10 channel recording a license limitation leaving 2 channels unused or a feeds limitation where you currently only use 10 out of 12 channels?

I have attached a PDF file that explains the problem.

I am attaching the error messages from the Health Monitor. Hope it is informative enough.

HI,

Open Mediacentral (or Interplay) capture Monitor and login. (it's a different app that is installed on the capture server)

Open the channels window and right click the channel that is stuck and select release.

Hello,

I did that and released the channel. However the error remained and in the transport status. I tried to release the channel as you advised but it doesn't release. And still I'm unable to record on that particular channel.

however, I noticed a single service on the Airspeed called "Avid multi stream devices" which is disabled in this Airspeed while enabled in another Airspeed and nonexistent in the 3rd Airspeed. Not sure if this is related.

Hi,

In that case I would first check on the airspeed if you can still start a manual recording using the airspeed remote console. If so, you have to either restart the capture server or at least the airspeed API Device service and probably the Capture service. However depending on the version of Mediacentral/Interplay capture you are running your recordings on the airspeed might stop and/or not start/resync with capture again.

(You might want to update capture to the latest version regardless of the rest of your system to be able to restart without disrupting airspeed recordings).

But it is always better to stop all recordings and restart all systems, airspeeds and capture if yourecording schedule allows it.

Thanks a bunch.

Hello,

We finally got to fix this issue. It was not straightforward to me. Basically, as explained by Avid, it seems that there was a conflict in services between API from the Capture side and the AMS device service from the Airspeed side, as both were running which should not be the case. I hope I got that right.

The AMS device service is an optional service you can install on your airspeed for it to communicate with Interplay capture or iNews command. Several years ago Avid introduced the API device service for Interplay capture which makes the AMS device service obsolete although Avid says it can still be used. The API device service is automatically enabled on the airspeed but needs to be installed on the capture side. But you have to choose and can't have both installed!

So typically with the latest versions of Capture you normally use the API device service. With the older versions and iNews command you use the AMS device service.

Finally. On a recent setup I have seen the AMS device service not working correctly with capture. There is an issue with the timecode source not being able to use the local clock of the airspeed and only accepting LTC causing recordings to start at 00:00:00:00 instead of time of day.

Yes, but the AMS device service is intalled in some of out Airspeeds which are used for capture, although we are using API. I think the AMS device should have been uninstalled by our system integrator as it might start running in one of the Airspeeds which might repeat this issue. Our capture is relatively old but seems to have API installed.

Hi,

Which version of capture are you running?

I would make sure all 3 airspeeds are running the same version of airspeed. If the API service is installed on capture I would remove the AMS device service from 1, 2 (or 3) of the capture airspeeds by you or your integrator. Be aware you will probably have to reconfigure capture for those airspeeds.

That said, I'm not sure how this would affect your initial edit while recording problem.