Author
Topic: ATG Utilities not connecting to guitar (Read 335 times)

My ATG Preset and Settings Manager utilities are no longer connecting to the AT-200. I've tried on Mac OS 10.10.5 and Windows 10, to no avail. The latest drivers are installed. The MIDI interface (M-Audio Uno) is working fine - verified with MIDI keyboard. I'm using the same Peavey AT-200B box as before. The software sees the interface, but does not connect to the ATG. And yes, the guitar is powered on.

I am currently using four different midi interfaces and the only one that works with the ATG-1 settings manager is the RME UFX midi ports. The other interfaces are iconnectivity midi 4+, Roland/cakewalk UM3, and the Midisport 8x8. The other interfaces work during regular operation, but the ATG-1 needs an interface of it's own because it will respond to any incoming midi activity regardless of how it is assigned. This is pretty bizarre behavior on the part of the ATG-1. I suggest getting a single port interface for the ATG-1. I get the feeling that Antares has decided that correcting the midi wierdness is not going to be worth their while.

I am currently using four different midi interfaces and the only one that works with the ATG-1 settings manager is the RME UFX midi ports. The other interfaces are iconnectivity midi 4+, Roland/cakewalk UM3, and the Midisport 8x8. The other interfaces work during regular operation, but the ATG-1 needs an interface of it's own because it will respond to any incoming midi activity regardless of how it is assigned. This is pretty bizarre behavior on the part of the ATG-1. I suggest getting a single port interface for the ATG-1. I get the feeling that Antares has decided that correcting the midi wierdness is not going to be worth their while.

Fascinating! I had not considered that possibility. I can confirm that it also did not work with my iConnect MIDI4+.

Fascinating! I had not considered that possibility. I can confirm that it also did not work with my iConnect MIDI4+.

Quote

I am currently using four different midi interfaces and the only one that works with the ATG-1 settings manager is the RME UFX midi ports. The other interfaces are iconnectivity midi 4+, Roland/cakewalk UM3, and the Midisport 8x8.

The big issue is Antares philosophy is the ATG Manager software on the PC/ Mac should be able to auto identify and connect with Antares Auto Tune hardware platform ( ATG-1, ATG Luthier kit or Peavey AT-200 w/ AT-200B Breakout box connected to the Computer's 5 pin MIDI interface hardware.

Upon application launch the ATG Manager in the background will begin to poll every possible MIDI connection on the host computer and establish a handshake with the Antares hardware.

But the fundamental Problem is a misunderstanding by Antares regarding the number of possible MIDI devices (either real or virtual) that can be found on the typical musician's Computer today.Forget using one of these

The solution is to disable any virtual MIDI port apps, close all other apps that use MIDI, and use a simple one port high quality MIDI to USB cable (like the Roland UM-One MK II ) to make the ATG hardware MIDI connection.

It took multiple uninstall/re-installs, but now it's finally working again on my Macbook Pro with El Capitan and on my Dell laptop running Windows 10.

Elantric - I did not have any other USB/MIDI devices hooked up before because I did read the manual! That is indeed a strict requirement for the ATG utilities.

The startup sequence also seemed somewhat critical: plug guitar into AT-200B using 8-pin MIDI cable and power up AT-200B. The guitar's LED should light. Next plug the MIDI interface (in my case the M-Audio Uno) into the AT-200B and the powered-off computer. Finally power up the computer and start the software.

“Therapies administered included but were not limited to: turning things off, then on again; picking them up a couple of inches and then dropping them; turning off nonessential appliances in this and other rooms; removing lids and wiggling circuit boards; extracting small contaminants, such as insects and their egg cases, with nonconducting chopsticks; cable-wiggling; incense-burning; putting folded-up pieces of paper beneath table legs; drinking tea and sulking; invoking unseen powers; sending runners to other rooms, buildings, or precincts with exquisitely calligraphed notes and waiting for them to come back carrying spare parts in dusty, yellowed cardboard boxes; and a similarly diverse suite of troubleshooting techniques in the realm of software.”

Actually that is the MIDI interface Henrik uses at Antares. So it's a "will work".

Maybe for you, since you're working on Windows. I've found that pretty much everything they've said about what should work or not wrt midi interfaces is untrue at my house. The only interface I could get to work is the one in my Focusrite, which is class-compliant (they claim you need an interface that "uses a driver").

Maybe for you, since you're working on Windows. I've found that pretty much everything they've said about what should work or not wrt midi interfaces is untrue at my house. The only interface I could get to work is the one in my Focusrite, which is class-compliant (they claim you need an interface that "uses a driver").

Actually, I tested it on Mac OS X 10.11.6 and Windows 10. In addition the M-Audio Uno works perfectly on my other Mac systems, running on Lion, Yosemite, and El Capitan.

The problem here was not with the MIDI interface, but rather the ATG software being fickle.