I have looked high and low on their website and unable to find it. Does anyone know if OMT offers a download of the manual to the imediatouch v4 somewhere?
-
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 manual
- Thread starter Bengalsfan
- Start date
They used to, but do not seem to any longer. Probably need to have a current support contract to be able to access the manual. (A shame)
Sweet! ;D
Thanks VoR. I looked all over the freaking website and could not find that.
Thanks VoR. I looked all over the freaking website and could not find that.
Good luck, however, getting solutions to issues from OMT. Josh was upset about a low-cost automation. Imagine spending $40k and two years later still having "latency" problems after going through numerous hoops based on advice from the techs at OMT.
I just added my fifth station and you would think that I would add my fifth OMT system. Wrong!
I just added my fifth station and you would think that I would add my fifth OMT system. Wrong!
Bill Wolfenbarger said:
After taking over a station with BSI's Simian, I have become a fan of their system. I understand no system is perfect. but after reading Simian's manual one night, I was able to get in and troubleshoot it when they had problems and do stuff like build rotators and such. If I ever own another station, it will be automated with Simian.
Bill Wolfenbarger said:
Wow... We've had recent problems with OMT support as well. It seems that their tech support is getting worse, and that they don't wish to jump in and correct problems. Too bad as I like the system.
Hey Bill, if you don't mind, what did you get for the fifth station??
N
Neal
Guest
I just installed OMT into a small 2 station group. its Running Flawless... 2 On -air packages
1 logtools 1 Production, and 2 channel I-Logger to log both stations..
I had One issue Tech support was great. the Problem was I used the 2 internal NIC Cards. on the Motherboard. one for local Network. one for outside control Both used the same Driver which.Kept swapping Ip's.... I added a 3Com NIC Card with its own Driver. that solved the problem. Never had a Problem with OMT Support.
1 logtools 1 Production, and 2 channel I-Logger to log both stations..
I had One issue Tech support was great. the Problem was I used the 2 internal NIC Cards. on the Motherboard. one for local Network. one for outside control Both used the same Driver which.Kept swapping Ip's.... I added a 3Com NIC Card with its own Driver. that solved the problem. Never had a Problem with OMT Support.
just call me Ralph said:
Are you using a server? Are you satellite or voice-tracking? Our problems have centered around latency issues between audio cuts, and ending up with 4 minute stopsets perhaps .5 to 1 second long, as well as delays in files transferring from server to local drive, inability to insert cuts quickly such as when doing an "almost live" remote.
Voice-trackers would never know if their is a tiny little latency problem.
Bill,
Were your machines turnkeyed?
What sound cards are you using? Some of the recent m-audio drivers are horrendous.
I assume you've checked for IRQ conflicts? Ours does very strange things if the network and sound card end up on the same shared IRQ (thanks Microsoft...NOT). I've had them randomly reboot, and had audio playing 2x normal speed due to IRQ's.
If you haven't, you may want to try to move the sound card on one to a different slot as a test.
Were your machines turnkeyed?
What sound cards are you using? Some of the recent m-audio drivers are horrendous.
I assume you've checked for IRQ conflicts? Ours does very strange things if the network and sound card end up on the same shared IRQ (thanks Microsoft...NOT). I've had them randomly reboot, and had audio playing 2x normal speed due to IRQ's.
If you haven't, you may want to try to move the sound card on one to a different slot as a test.
While I don't use mediatouch as my automation, I have had experience with m-audio. I have never got one of those cards to work reliably with anything. I remember a couple of years ago saying something like "I will never buy another m-audio card again"... which I have not. I have also replaced them all with Digigram cards and guess what? No more problems.
If you use older drivers, the Delta series are workhorses. Anything after 5.10.00.5057v3 seems to have issues with latencies, processor timing, etc.
That said, I don't think that series is going to be sustainable much longer. And many say that once Avid bought M-Audio, all bets are off.
Back to iMediaTouch, we have 8 on-air workstations, 5 production workstations, and 2 VT workstations running 2.6.x and streaming Layer II 256 audio directly from the server and have no issues outside of the few quirks of actually using the software that we've learned to deal with.
Their audio engines (pta.exe) are built on DirectX.
One other thing that can cause issues is that the on-air app "talks" to the PTA via IP on the localhost. On Windows, any network irregularities on the actual physical LAN will cause the localhost communications to slow down too, causing lags in element starts. Sometimes the system will go haywire if it doesn't receive confirmation back from the PTA within a period of time. It tries to restart the PTA app, which is already running, just lagged.
That said, I don't think that series is going to be sustainable much longer. And many say that once Avid bought M-Audio, all bets are off.
Back to iMediaTouch, we have 8 on-air workstations, 5 production workstations, and 2 VT workstations running 2.6.x and streaming Layer II 256 audio directly from the server and have no issues outside of the few quirks of actually using the software that we've learned to deal with.
Their audio engines (pta.exe) are built on DirectX.
One other thing that can cause issues is that the on-air app "talks" to the PTA via IP on the localhost. On Windows, any network irregularities on the actual physical LAN will cause the localhost communications to slow down too, causing lags in element starts. Sometimes the system will go haywire if it doesn't receive confirmation back from the PTA within a period of time. It tries to restart the PTA app, which is already running, just lagged.
- Status