• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

iMediatouch problems

C

ChiefOperator

We use the iMediatouch system (V3.1.9) and have it configured with four machines: onair, production, logger, traffic. The onair machine acts as the server. Currently, we record two programs on the logger for time shift playback. We've been running this way for two years without issue.

Now, we find that many of the recordings segments are truncated--that is, the closures properly split the recordings into segments but the eom and length times seem to shift back, which shortens the segments.

We seem to be the only station having this issue. Support thinks that the problem *may* be resource conflicts and is suggesting we add a server or add RAID 5. However, I'm guessing there are other stations configured the same as ours and they seem to not have issues.

Before we go the route of adding a server or RAID 5, I'm wondering whether anyone else has these same problems. Or are there stations that are configured similiar to ours where everything works okay?

Thanks

PS: Also, as a side note, many ask about the *best* automation systems. I have come to learn that the best system is the one with the best tech support.
 
If the audio is actually recorded, but the EOM marker is incorrect, I wouldn't guess that it could be a resource problem.

Are you sure that it isn't related to updating iMediaTouch versions?

We've stopped using logger since our satellite receivers natively support delaying programs. Last used it with iMT 3.1.2 or so.
 
Thanks. Actually, it's difficult to determine whether audio is present or not, since it won't play past the EOM/stop times. It looks as if the EOM and Stop times have shifted back. Yes, we did recently upgrade and I'm wondering whether we have a faulty update.

I'm stopping all feed recording tomorrow, with the exception of a single feed recording at one time. In addition, I won't allow any production work to be done. If it is a conflict, then a single feed should record without issue.

PTBoardOp94, what type of set-up are you using? Are you using a separate server or using onair as your server?
 
There is no separate server.

When I hear you say "The EOM and Stop times have shifted back", here's what I'm thinking:
Logger starts recording program at 0506.
Network sends a local break closure at 0517.
Rejoin network at 0521.
Network sends a local break closure at 0529.

Segment A should have length of 11 minutes, with EOM and Stop time to match.
Segment B should have length of 8 minutes, with EOM and Stop time to match.

What I understand from your description:
Segment A has a length of 11 minutes, with EOM and Stop time to match.
Segment B has a length of 8 minutes, but with EOM at 4 minutes (as if the timer never stopped for the local break).

If this is the case, I would consider it an iMT software problem.
 
Thanks for the reply.

Close. Segement B would have length, stop, and EOM at :04mins, although the machine shows recording times of :08mins.

Yes, we have no separate server either. Are you running a RAID 5 on your onair machine?

iMediatouch believes it may be a problem with "delayed cueing." I now have it enabled to see whether this function will solve the problem.
 
OMT seems to have a "workaround" for everything. The system has quirks.
 
Hey Guys,
Just reading the thread.

Did you ever figure out what the problem was??

Sounds like the database isn't getting updated. It has been a while since I have used iMT, but I am sure they still use a "Production" program (like they used to).
Are you able to go into production and edit the EOM on the cuts?? If so, then sounds like an issue with the delayed cueing (trying to play back before it has finished recording).

I have used a lot of other systems, and I am glad that iMT has at least a work around for their issues. Others just say "sorry, call again"
 
It does sound like the database is not updating for some reason. We're on 2.6.X. Our traffic reporter uploads and imports her cuts and sets the EOM. Occasionally, the cuts will "end" early and start the next event. Refreshing the database solves that issue for awhile. Sounds similar to your situation.
 
The problem was a combination of "delayed cueing" and a faulty install. We reinstalled the software and added delayed cueing. All is working fine now...

Thanks!
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom