ATG Utilities not connecting to guitar

Started by GuitarBuilder, March 19, 2017, 11:09:04 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

GuitarBuilder

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.

Any suggestions?
"There's no-one left alive, it must be a draw"  Peter Gabriel 1973

admin


BBach

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.

GuitarBuilder

Quote from: BBach on March 20, 2017, 07:45:41 PM
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+.
"There's no-one left alive, it must be a draw"  Peter Gabriel 1973

drbill

It does not work with my M-Audio Midisport 1x1, nor my MOTU 828 mk3 Hybrid.
GP-10, KPA
BM i2.13p, '76 Les Paul Deluxe w/GK-3, MiM RRS, Ibanez RG420GK, Charvel strat copy w/GK-2a, FTP

Elantric

#5
Works with Roland UM-One MK II

But it was on a laptop computer with no other USB Devices (important)


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


QuoteI 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.

However the ATG manager application typically "times out", never locating the correct 5 pin hardware MIDI interface which the ATG hardware is connected.

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




Multichannel MIDI interface hardware  and Virtual MIDI Cables (MIDI -Yoke, LoopBe30 ) yield problems with the ATG Manager
http://www.soundonsound.com/sound-advice/pc-notes-0

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.   


and read the ATG Manager Manual

http://www.autotuneforguitar.com/mediafiles/online_help_records/77_ATG_Software_Manager_v1.1.0.pdf


GuitarBuilder

I got confirmation from Henrik at Antares that the M-Audio Uno should work with the ATG software.  I know that mine used to about 6 months ago.
"There's no-one left alive, it must be a draw"  Peter Gabriel 1973

drbill

Quote from: GuitarBuilder on March 21, 2017, 04:35:30 PM
I got confirmation from Henrik at Antares that the M-Audio Uno should work with the ATG software.  I know that mine used to about 6 months ago.

Lol. "Should." Maybe it will, maybe it won't, but I'm sure they have no idea.
GP-10, KPA
BM i2.13p, '76 Les Paul Deluxe w/GK-3, MiM RRS, Ibanez RG420GK, Charvel strat copy w/GK-2a, FTP

Elantric

QuoteI got confirmation from Henrik at Antares that the M-Audio Uno should work with the ATG software.  I know that mine used to about 6 months ago.

Be sure only the M-Audio Uno is connected to your computer - remove ALL other Audio / MIDI Interfaces

GuitarBuilder

Success!

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.

;D ;D
"There's no-one left alive, it must be a draw"  Peter Gabriel 1973

GuitarBuilder

Quote from: drbill on March 21, 2017, 04:44:13 PM
Lol. "Should." Maybe it will, maybe it won't, but I'm sure they have no idea.

Actually that is the MIDI interface Henrik uses at Antares.  So it's a "will work".
"There's no-one left alive, it must be a draw"  Peter Gabriel 1973

mooncaine

Sounds like the 1990s. My life with PCs.


  • "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."

           ― Neal Stephenson, The Diamond Age: or, A Young Lady's Illustrated Primer


[Source: http://www.goodreads.com/work/quotes/2181158-the-diamond-age?page=2]

drbill

Quote from: GuitarBuilder on March 22, 2017, 10:00:21 AM
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").

GP-10, KPA
BM i2.13p, '76 Les Paul Deluxe w/GK-3, MiM RRS, Ibanez RG420GK, Charvel strat copy w/GK-2a, FTP

GuitarBuilder

Quote from: drbill on March 22, 2017, 11:33:52 AM
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.
"There's no-one left alive, it must be a draw"  Peter Gabriel 1973