• Welcome to the General Discussion forum for UAD users!

    Please note that this forum is user-run, although we're thrilled to have so much contribution from Drew, Will, and other UA folks!

    Feel free to discuss both UAD and non-UAD related subjects!

    1) Please do not post technical issues here. Please use our UAD Support Forums instead.

    2) Please do not post complaints here. Use the Unrest Forum instead. They have no place in the the General Discussion forum.

    Threads posted in the wrong forum will be moved, so if you don't see your thread here anymore, please look in the correct forum.

    Lastly, please be respectful.

UAD Card does not work in my new G5

johnnyspy

New Member
I have had this card in a G4 since the beginning. I love it.

I heard about the new 3.6 version and said time to buy a G5
(G5 system specs below question)
I go to open a song I have created. It opens. When I play it, it immediately stops, gives me a core audio error. Sometimes it stops the song, while others, it stops the song at first, reports the first error and then pops up that the UAD card is not responding and that the plug ins have been shut off and then it plays again.

I have tried rebooting, reinstalling the plugs etc. I took out the Powercore core (did not work), took out the UAD in put it in other PCI slots (did not work), turned off the motu and used the built in audio drive (did not work), tried Peak (did not work in peak either).

Is there a possibility that I have an early UAD card that does not work with the G5? Do I need to format the drive and start over again (something I don't relish but will do as a last result)?

I have not repaired the permissions yet and I am about to do this but I am not sure this will help.

Any ideas?


Dual 2.0 ATI 9600, 1.5 gigs of ram, 4x DVDRW
I have a MOTU MOTU 828 MK II plugged into a fire wire system port directly
I have the latest version of Logic Pro 6
The latest version of MOTU drivers
The latest version of UAD drivers
A Powercore Element with the latest drivers
I run OX 10.35 with the latest updates
I run the operating system and logic from a firewire drive that is plugged into a separate firewire port from the motu.
 

johnnyspy

New Member
Ok here is an update

I decided last night at 1:00am that although this forum is awesome and people tend to respond very quickly , I decided to not wait for a response since I knew everyone was sleeping.

The drive that came with the g5 I loaded Logic, Uad software, etc etc.

The songs work great. I wonder if my old system had some G4 files or attributes to it that made it not work correctly with the g5. I attached everything to the g4 (before I loaded everything one the g5) and everything worked on the g4.

Anyway, everything works awesome and boy does the G5 smoke the g4 (duh), the power is just amazing.

I would still like feedback to see if there is something I could do to fix the previous situation. I tend to have six drives, one for each task I do (one for games, one for word processing, articles, research, one for film/dvd editing, and one for graphic editing/scanning, etc. and then one drive for backups of the working drives (image files) in case of a crash, software bug, screw up etc.

I would hate to have to reformat all the drives and start again, but perhaps it is a good idea. Backup time!.

PS sorry for some pc jargon, I converted years ago but I still speak Windoze lingo :)
cheers
Johnnyspy
 
If you were using the drive/files from your G4, then most likely the problem was that AMD-8131 mode was not enabled in the UAD-1 Meter configuration window. This *MUST* be enabled for current G5 models (except for the newest dual 1.8 G5, which does not use the AMD-8131 PCI-X controller). This is described in the manual, and the online tech notes page. When you install from scratch, the first time you run the Meter or one of the plugins, it automatically detects what machine you're running on and sets this appropriately... but if you were using a previous install from a different machine, it will use those settings.

I'm 99% sure that was the problem, so try checking that setting and see if it fixes your problem.

Jim
 

johnnyspy

New Member
Thanks Jim Wintermyre

That was the problem Jim. Thanks for the advice, it sure was better advice than the email I got from UAD. They blaimed it on using firewire. Funny how firewire is one day the solution and the next day the problem. Now some people are saying go to scsi, which I just dumped because I had so many problems with scsi. Ah opinions.

It is weird that when I reinstalled the sofware it did not auto detect the G5. It must be an issue with OSX. I know people always say with a new computer reformat all the boot drives and start again.


At least I know what the issue is. I wonder if most of the problems in this forum are do to these issue. By the way the system runs much better on the g5 drive than the originally formated for g4 drive so I suspect there are other issues.

So I am going to format all my old drives (once I back them up) and start fresh.

Thanks for the advice.
cheers
Tom
 
UAD Bundle Month
Top