Hi All,

I am having an issue with Interplay 2.0.1 and AirSpeed Multistream 1.2 where I cannot send to playback from any of my editors. This is a brand new install and is just being tested as of now. I checked the TmClient.ini and both Studio config ASM's are there. I receive an internal dll error in the playback device which is a listed error on the Avid Knowledge Base site, but for ftp set ups. We are not using ftp. Is there a config error somewhere that I need to check out? The sequences are appearing in the send to playback folder of Interplay each time.

Thanks

What does the Transfer window show in Composer when you send?

"Internal error in DLL that sends media to the playback device: operation not allowed on receiver". This same error was on the KB for people that had misconfigured ftp transfers. We are not doing ftp transfers.

Both in the same workgroup, and the workgroup name?

Yes, they are both in the isis and the cmd workgroups, as we use command to playout. I just checked, and I got the same error when trying to send a shotlist to playback from an Assist client (using admin log on's).

Have not heard back from Support yet either........

attach a picture of your tmclient.ini config from composer...

see below. studio config.

What resolution are you Sending to playback?  HD?  Is the ASMS video server configured with the correct template (in the Service Configuration)? 

It sounds as if your attempting to send a resolution from the editor that the ASMS is not prepared to receive.

If you are sending HD, are you seeing and selecting the"aptnhdpb-HD" playback destination in the pulldown menu?

Roger Sacilotto

Avid

Also check to see that the audio you are sending matches the bit rate that is set on the Airspeed.

Hey Roger,

Thanks for the reply. This was the exact issue. It seems silly, however, there were a couple of reasons why this was not solved earlier. One, the TmClient.ini was all lower case, therefore, we thought that the lower case aptnhdpb was the correct one. Also, when trying the HD option, I witnessed the mixdown commencing followed by the exporting to ***.mxf file. I had not idea that the exporting process was actually the long gop rebuild taking place. Our upgrade was pretty rushed and not much time with Avid installer on site.

My 2 cents, is that in future editor releases, the exporting status is replaced with something like "rebuilding long gop" in the case of XDCAM which is what res we are using in HD.

Thanks again to all, very much appreciated!