Audiotx Communicator



Being a freelance commercial voice talent today requires many different methods of providing product to his clients. While ISDN audio codec technology and the Internet have made the voice-over (VO) world a much smaller and faster place, the need for compatibility and dependability is paramount. To work locally and internationally via ISDN, voice talent the world over are not only the talent but also audio engineers/editors and telephone company technicians. The financial investment in equipment and its options can be quite expensive and daunting. The need for a compatible and dependable, yet affordable and easy-to-use audio codec can make the technical job of being a voice talent a great deal easier. That's what led me to AudioTX.

The AudioTX Communicator is an MPEG Layer II, III and G.722/G.711-compatible, software-based, full-bandwidth, bi-directional ISDN and IP/Internet audio codec for the PC. The user-interface operating screen is simple and straight-forward, incorporating audio metering of incoming and outgoing signals, framing indicators, input/output source selection and level controls and an easy-to-use, user created phonebook. Once connected and framed with the far-end codec, the software can also provide incoming Caller ID information if so provisioned.

My setup

Their AudioTX Communicator system will then always use that setting for the return audio, regardless of the settings used by the system on the other end of the line ie me and my magnificent bandwidth busting LOSSLESS setting. And regardless of who dialled who first. This is making me think that things are shifting. The AudioTX Communicator is an MPEG Layer II, III and G.722/G.711-compatible, software-based, full-bandwidth, bi-directional ISDN and IP/Internet audio codec for the PC. The user-interface operating screen is simple and straight-forward, incorporating audio metering of incoming and outgoing signals, framing indicators, input/output source. The Communicator can operate over Ethernet or private wide-area networks. Using a standard PC network card or other installed networking hardware, the AudioTX Communicator can provide live audio links over IP networks. Using existing installations of hubs and routers makes the scale of a given network irrelevant.

I use a P-4, 2.5MHz PC that incorporates not only AudioTX, but also an audio recorder/editor and a good word processor for reading directly from the monitor. However, an affordable Pentium-II or Athlon 400MHz (or above) system with 128MB of RAM, Windows Me and PCI bus running Windows 98-SE, Windows 2000 or XP is the minimum requirement for the host PC. Hard-drive capacity should be determined by operating system and audio file storage requirements for your needs. However, a 10GB drive will accommodate the PC operating system and AudioTX with ample storage space to spare. I also use a professional audio card with S/PDIF I/O. However, most moderately priced, full-duplex PCI audio cards, such as those from Sound Blaster, will work nicely.

Performance at a glance
Software-based ISDN and IP audio codec
Easy installation and operation
Mimimal PC hardware requirements
Phonebook entries for repeated connections
Auto-configuration capable
Integrated .WAV file transfer capabilities
Supports multiple coding algorithms

Installation of the company's software was typical of most Windows installations, and updates are posted on the AudioTX website. There is a 30-day evaluation trial version of the most recent version. When updating, the new version overwrites the old, so there is no confusion and the phonebook names and settings and all operating parameters for both operating modes are preserved. When purchased, the software is supplied with a small USB or printer port dongle, which acts as the software license.

After setting up and configuring the ISDN line or IP connection and installing the software, entering the phonebook information into a list of my most often used connections was easy. To initiate a link, I highlight the name I've programmed into the phonebook and click the dial/connect button at the bottom of the interface window. When receiving a call, the software determines the configuration of the caller (such as algorithm, audio mode and bit- rate) and adapts. The software synchronizes the path and passes audio. It takes from 2 to 15 seconds for audio delivery to begin.

The only problems I've encountered are from older codecs of varying brands that haven't been updated with their manufacturer's most recent firmware. However, in most cases, that's usually only a single parameter change on the part of the far-end device to remedy.

This software offers two separate operating modes: an ISDN mode and an IP/Internet mode. The two modes are operated from a similarly styled window switched by a tab at the top of the interface screen. The two modes share a common audio card, a unique and useful audio file transfer system and several global parameters found under the main window's pull down menu under settings. There are four headings under the settings menu. The first is global, which includes identification settings when connected, host computer speed for above and below 1GHz operation, G.711 settings for the United States or Europe and auto connect on start-up, which asks for a connection type and destination when starting the software. These need only be set once for most operations.

The second settings heading is audio, which includes audio quality for MPEG II and MPEG III (fast coding or studio quality), audio buffering for the sound card, and a sample rate conversion enable/disable setting to convert incoming sample rates.

The next heading is answer settings. The two modes, ISDN and IP/Internet, are switched by a tab at the top of the screen. The ISDN side handles incoming calls and provides a parameter to accept or deny incoming data and voice calls. It also stores the ISDN numbers to use if multiple ISDN lines are available, and the type of compression, sample rate and audio mode used to answer calls.

The IP/Internet side of this screen is quite similar, with the exception being that under a section called accept incoming calls a DNS ID is entered instead of telephone numbers. Also, an internal port for incoming data is selected. The last heading under the settings menu is SOCKS/Proxy version settings and username/password info if required.

The ISDN line requirements for full-bandwidth (20Hz to 20kHz) and full duplex (bi-directional) operation are minimal and identical to those of any other stand-alone codec; a single standard BRI (Basic Rate Interface) with voice and data activated on both B channels. Most phone companies have become quite familiar with this simple ISDN line and configuration so normally ordering, installation time and hassle is minimal.

The ISDN will connect in all modes to most all popular codecs having MPEG Layer II, III and G.722/G.711 algorithms through an inexpensive ISDN internal PCI terminal adapter/modem you install in the PC. I use the Eicon DIVA PCI ISDN modem with an external NT-1 adapter. In my case, the ISDN line is connected directly to the NT-1 via an RJ-45 connector then to the EICON ISDN TA in the PC via a CAT-5 cable. Depending on which ISDN TA/modem you choose for your system, you may not need an external NT-1. However, I found it more cost-effective for my situation to purchase an external NT-1 than one incorporated on the ISDN TA/modem itself.

The IP/Internet mode requires at least a 140kb/s broadband connection to accomplish full bandwidth, bi-directional audio across a network or the Internet. This mode works on an internal (in house) network, the Internet or ATM network and (currently) only to another Communicator software codec on the far end. When using it in IP/Internet mode, the software connects through a 10/100baseT Ethernet card directly to the Internet through an external ADSL/DSL/cable modem connection, or indirectly through an internal network. It will not work with external serial connected modems or dial-up connections.


The Phonebook screen stores the setting for all ISDN and IP connections.

Calling and receiving using the IP/Internet mode is almost the same as using the ISDN mode, except the user enters the IP address of the remote system instead of an ISDN number. The only drawback to the IP/Internet mode I've found was when I set the desired connection bit rate higher than the capacity of my ADSL connection. Occasionally, it would lose data and the audio signal would chatter a bit. However, there are three user-selectable buffer settings in the phonebook for each individual entry to help remedy such situations, but no one can predict the traffic on the Internet at any given time. Combine that with the nature of ADSL and its understandable how this can happen. A 140kb/s or higher broadband connection is the minimum required for the IP/Internet mode. Not only is it probably the most inexpensive of the ADSL connections, but it also provides a solid 128kb/s connection with some overhead. My broadband connection (ADSL) is rated at 160kb/s up and 250kb/s down.

Into action

I use the ISDN mode and the IP/Internet mode and, aside from a minor amount of additional latency in IP/Internet mode—again due to the nature of ADSL and traffic on the Internet at any given time—the operation and quality of the signal is identical, if not even slightly better to my ear as compared to the most popular stand-alone codecs. Also, the G.711 compression mode works well for standard phone patch sessions. This is possible if the ISDN line is configured for voice and data, and the software is set to receive incoming calls.

In the ISDN and IP/Internet modes, there is a useful feature that allows file transfers during a live connection. If both ends of the link are using the Communicator software, it enables either end of the link to send .WAV files across the link. When sending a file, the internal sound card is muted until the transfer is completed or aborted. The add file button brings up a browser screen so files stored on the computer or internal network can be accessed.

Audiotx communicator 1.5Audiotx communicator model

To transfer a file, add the file or files you wish to transfer to the playlist, then click the play button. To remove a file from the file list, simply highlight the file and click the remove button adjacent to the file list display window.

AudioTX
P
F
W
E
+44 121 256 0200
+44 121 256 5109
http://www.audiotx.com/
sales@audiotx.com
Communicator

Being a voice-over talent, I most commonly transmit in mono, 128kb/s, 48kHz, MPEG Layer II but quite often receive in stereo to be able to read to a music or SFX track. I'm also often asked to do dialog with other talent on the far-end and being recorded by the far end or via a bridge link to a third studio. Also, I'm often required to be able to receive in a different algorithm than that which I'm transmitting and all with no problems.

I chose the AudioTX Communicator for several reasons. For my purposes, it was far easier to use than most stand-alone products. It incorporated everything I needed, not only for the present and all its varied requirements, but also for what I feel will be future requirements for my business. I could install and operate it from the same computer I use to read text from e-mailed or downloaded scripts and use to access the Internet. Also, even with the computer, ISDN TA/modem and professional audio card, the cost (minus the ISDN line and associated charges or a broadband Internet connection) is about a third to half of most stand-alone codecs. I like to refer it as a “codec for dummies.”

Editor's note:Field Reports are an exclusive Radio magazine feature for radio broadcasters. Each report is prepared by well-qualified staff at a radio station, production facility or consulting company.

These reports are performed by the industry, for the industry. Manufacturer support is limited to providing loan equipment and to aiding the author if requested.

System

It is the responsibility of Radio magazine to publish the results of any device tested, positive or negative. No report should be considered an endorsement or disapproval by Radio magazine.

Permalink Reply by VU - Founder - Zurek on July 20, 2008 at 6:38pm
Jon,
I have Audio TX and use it with IP connections, it is crystal clear like ISDN. I believe you have to have an ISDN connection, and an ISDN modem to connect to a PC/Laptop. I'd be more than welcome to test Audio TX connections.
Skype: rickpartysworld
AIM: rickparty
phone: 877-213-3600
Permalink Reply by David Seys on July 21, 2008 at 11:33am
Rick,
I have had Audio TX for 3 years, but only used it for ISDN. It works perfectly, connects with all codecs and saved a huge amount of money by not buying a dedicated piece of ISDN hardware. I required ISDN because my agent in the US requires me to have ISDN, and all sessions through them are done this way.
But......I have always looked at the IP facility that is included in my softwareand have no idea how to use it, or if any of my clients can just be dialled up to connect with me. In other words I do not know what has to be at the other end for me to connect. I would really appreciate taking you up on giving it a try if you have a spare moment.
Lastly, is this an alternative to Source Connect?
Cheers......David S
Permalink Reply by James Clamp on July 21, 2008 at 11:03am
Philip, I love your 'to be clear on this' paragraph - it's so beautifully unclear and random and as usual I'm wiping the tears of laughter from my eyes. But the point is made and it's something i've been investigating myself so it's great to hear your input. Thanks Jon for starting the discussion. James
Permalink Reply by Jon Thomas on July 21, 2008 at 11:13am
OK, now it's all making sense. I also e-mailed the AudioTX company, and the way they explained it is you can't cross connect with Internet on one end, and ISDN on the other. Before now, I wasn't totally clear on that aspect. Thanks for bringing me up to speed.
Permalink Reply by VU - Founder - Zurek on July 21, 2008 at 7:11pm
* orum Home
* My Discussions
* Start a Discussion
We're sorry, but this discussion has just been closed to further replies.
Christopher Flockton
Audio TX, ISDN, Source Connect redux
Posted by Christopher Flockton on July 21, 2008 at 4:36pm in Home Studio (Change)
Send Message View Discussions
Admin Options
* Feature
* Close Discussion
* Add Tags
* Delete Discussion
Hello all -
I missed Jon's informative discussion of Audio TX, and wanted to bring up another possibility...
It is possible to do 'ISDN without ISDN' by using Source Connect over the internet and the services of a bridging company such as DigiFon, EdNet, or Out of Hear (I believe Joe Cipriano used this company in one of his videos).
While I've never done this personally, I'd be interested in hearing from people who have, and whether this is a good strategy for doing occasional ISDN sessions without investing in an ISDN Codec.
What are the costs, technical challenges, who pays - you or the client, etc, etc?
On a slightly different subject, I'd be delighted to hear more about strategies for connecting with people without their hands :)
Discuss.
Chris.
Tags: audiotx, sourceconnect, idsn, home studio
Share
▼ Reply to This
Bold Italic Underline Strikethrough Add Hyperlink Add an Image Upload a File
Upload Files
Attach File(s):
*
*
*
Replies to This Discussion
Philip Banks Permalink Reply by Philip Banks 1 hour ago
Send Message
Delete
Creating barriers or doing things the hard way are for the big league voices. If a Voice is a MUST HAVE VOICE then producers, directors and production companies will make a way where there is now way. The alternative technology such Source Connect, using AudioTX as a VOIP or bridging one to the other via a cheese shop in Staines (cost usually around $50 to $100 or a particularly interesting Stilton) are used only as a compromise.
If you are a good voice over and have an ISDN equipped studio in your home it will make you money, in my case several pounds per week. If you say you have access to ISDN or have Source Connect or some form of native American smoke signalling system it is more likely to help you do the work you already have rather get you new clients.
For connecting handsfree people, here in Portgordon we favour the 'hook n eye' method. Men who are not handy (usually due to an accident while catching kippers the traditional way using a bicycle pump and a copy of the Old Moore's Alamnac ..sorry I digress) they have hooks and the womenfolk have eyes. Get eight couples together you'd get a signal as far away as Fochabers for a bridge we'd use Dougie Hay's 1943 Fordson tractor, it's not digital but it has a dodgy wheel which is nearly the same.
▶ Reply to This
Upload Files
Attach File(s):
*
*
*
Christopher Flockton Permalink Reply by Christopher Flockton 35 minutes ago
Send Message
Delete
Hey Philip -
Yup. Good points about getting more work vs. doing the work you already have. Thanks.
One question though... could I use an unusual French cheese, perhaps Rigotte de Condrieu, to bridge to a standard English Cheshire? Or would there be a fundamental incompatibility? I would consider this bridge a success whether my hands were free or not.
Cheers -
Chris.
▶ Reply to This
Upload Files
Attach File(s):
*
*
*
Philip Banks Permalink Reply by Philip Banks 21 minutes ago
Send Message
Delete
Remember the golden rules regarding cheese bridging, blue to blue, white to white, hard to hard, soft to soft, both Limeswold and Ilchester are no good at 128k yet delicious with Jacob's Cream Crackers.
For the sake of fellow Voice actors in two voice sessions - Bavarian Smoked cheese requires no phantom power but an open window is essential.
Are you a hook or an eye or do you just shout Fochabers?
▶ Reply to This
Upload Files
Attach File(s):
*
*
*
RSS
Follow – Email me when people reply
Permalink Reply by Mike Elmore on August 13, 2008 at 11:22pm
Beau Weaver uses it and promotes it when asked about ISDN...I would say if he uses it....(oh and Rick Party too>>>) 'it HAS to be good'.
Permalink Reply by George Whittam on August 14, 2008 at 8:15pm

Audiotx Communicator Client

I have clients who use Source Connect or AudioTX Communicator, and some even have both. Coming from someone who supports both technologies and designed outofhear.com's bridging system which handles both systems, in my experience, here is the bottom line:
1- AudioTX needs less bandwidth when using an IP connection to achieve a similar level of sound quality as Source Connect
2- AudioTX can be used with an ISDN modem and NT1 adaptor as well as in Internet connection. Source Connect is IP only.
3- AudioTX requires that at least one user has a Static IP address so that the other user will know what address to connect to and can save it as a preset. Otherwise the IP address will be different each time, a major inconvenience. Source Connect manages your contacts on their serve so either of you can use any IP address without issue.
4- AudioTX requires the user who receives the connection (usually the studio) to know how to setup Port Forwarding and possibly a dyndns.org account, should they have a dynamic IP address.
5- AudioTX will likely NEVER run on a Mac without running Windows in Bootcamp. SC runs on Mac or PC, Pro Tools or many VST compliant applications.
6- AudioTX has no way to 'Patch In' to another software the way Source Connect can. EG: If your audio chain relies on an EQ, compressor setting, or the like in Pro Tools, Source Connect will receive your audio signal post processing so your client hears your voice tweaked the way you like it. AudioTX is STRICTLY a stand alone product and has no way to 'ReWire' into another application.
7- AudioTX requires the use of a proprietary USB dongle, which if lost or damaged voids the use of your software. When purchased you must wait for it to arrive from the UK and pay a considerable shipping fee (around $75) to cover the insurance at $1200 or so. SC uses an iLok, for which you can use their 'Zero Downtime' service to keep a spare iLok USB key on hand should you lose the licensed iLok.
8- Source Connect costs only $395 for the standard version, which is adequate for most home studio users. Just get an iLok, purchase the license, and you are good to go. If you buy it from eldorec.com you'll receive free over the phone setup assistance, which is not available from SE or AudioTX.
9- Source Connect support is Europe AND US based, while ATX is only in the UK.
Did I just make the decision even harder?
Call me...
George Whittam
310-686-3746
Permalink Reply by Jon Thomas on August 14, 2008 at 10:07pm
I really do appreciate everyone weighing in on this subject. For the most part, anyone who has needed to be in on my sessions has been happy to work with me on a phone patch. So while being able to offer ISDN is a bonus, it always comes back to whether or not I'll really have a use for it. Decisions, decisions! But this thread has been incredibly helpful.
Permalink Reply by Mike Cooper on April 7, 2009 at 1:08pm
What a great thread!
For what it's worth, I re-equipped my studio a few months back and chose to put in ISDN in the form of AudioTX. For me it was a no-brainer: the software is 1/3 the cost of a second hand codec, plus £50 for an ISDN card (very much last century's news in the world of networking) and £100 for a decent M-Audio sound card. That'll do nicely, thank you. Due to space constraints, I'm forced to have everything in the booth with me, including a fanless PC. So the last thing I wanted to do was add a bit of kit with a fan to the equation, which many codecs do.
It plays nicely with most codecs (though sulks with Prontos sometimes, due - apparently - to Prontos doing some unusual things themselves) and I've yet to have a problem getting it to connect to anything, even if a bit of the usual ISDN 'fiddling' is sometimes needed.
Today I did my first session over IP using it, and it worked a treat. Rock solid for an hour, though that will depend on your internet connections at each end and the bit in the middle (just going across London it never complained).
When I re-equipped, I also took a punt on Source-Connect Pro. I work with an audio engineer here in the UK who is promoting it and who has used it lots, and was persuaded to buy in early. It's extremely impressive, but I still feel like I'm ahead of the curve. I've done one job on it so far, so it's half paid for itself.
Thing is, I can now give my clients the option of ISDN, AudioTX over IP or Source-Connect. And that might be a bit of a USP, for now. We aim to please, after all…
Permalink Reply by David Brower on April 1, 2009 at 4:28pm
Quick question if I may... will Audio TX work with 28k lines or do you need the full 64K? THANK YOU and hope you are all busy...
Permalink Reply by George Whittam on April 3, 2009 at 10:29pm

Audiotx Communicator Manual

It works with ISDN lines, at least one 64kbps B-channel.
Not POTS lines, however...

Audiotx Communicator Network

Permalink Reply by Beau Weaver on April 7, 2009 at 3:31pm
I have used Audio TX for years, mostly to bridge to ISDN sessions while on the road. Digifon and Outahear do Audio TX bridge. But with an ISDN line from the telco and a (100 bucks) USB adapter, it will replace the Telos Zelphyr or CDQ Prima.
(Don't ever buy a Prima!). 1300 bucks vs 4000 plus?
I use AudioTx on my macbook pro, with a bootcamp windows xp installation. It works flawlessly. When the MBP is running windows via bootcamp, it is a native windows machine, and is actually the best windows machine I have used.
Do not try to use AudioTX with a Windows virtual machine, as in Parallels or VM Fusion.....they do not access the hardware naively, and it won't work. But a bootcamp windows installation is golden.
And, if you want to use it as a bridge, or connect direct over IP with another AudioTX user, it beats the pants off Source-Connect......SC requires waaaaay too much upstream bandwidth to be reasonable for most home users. And it is still finicky and crash prone. AudioTX has been totally bulletproof for me under some challenging conditions.
I have used it for years, and never had a problem. Dave Immer at Digifon is a dealer for AudioTX and will tech support you through your instalations. Can't go wrong here.
Beau Weaver
  • ‹ Previous
  • 1