10.5.3 Problems with Au validation

best to check here first b4 doing a major os upgrade. 3rd party manufacturers always lag behind the os, even going from v1 to v1.1 causes problems. It's the reason I ditched m-audio Ozone.

That's the thing, I did check here, as well as the Logic Pro Help forums, and didn't see anything but hig praise for the upgrades.

I've downgraded back to 10.5.2 and LP 8.0.1 and everything validates correctly. Amplitube Metal still causes Kernel Panic in standalone mode, but seems to be working fine in plugin mode. Haven't loaded up X-Gear yet, but I'm assuming it'll work fine, as it did before I tried upgrading.

Ya know, it's kinda BS that IK and other plugin authors have to scramble to find out why their product isn't working, just because Apple decides to issue a point upgrade. Chances are, it's the smallest little thing too, like a misspelled term or version check in the AU process causing it, cause A2 worked fine, even after failing validation in 10.5.3/LP 8.02. I doubt it'll happen, but to me, it seems Apple should be the one fixing this.......

esta es la dirección
www dot fxpansion dot com

<Edited by Moderator>

Well I try it with VST2AU and work amplitube 2 only, no metal or xgear, work but detect interface problems in the plugin, isn't a real solution for me.

Only have to wait update from Ik or the next 10.5.4 next week.

JemmX

That's odd,

I upgraded to Logic 8.02 and OS10.5.3 last week and never went through the AU validation at all, it didn't even run, all plugins and VI seem to work fine.

pancenter

it worked for me at first too, but then i got curious and tried re-validating. that's when it said all amplitube plug-ins, except jimi hendrix, failed the validation.

is there a way to disable the au validation tool so i dont get a message everytime i open logic saying im using uncompatible plug ins?

Noisenet wrote:

Ya know, it's kinda BS that IK and other plugin authors have to scramble to find out why their product isn't working, just because Apple decides to issue a point upgrade. Chances are, it's the smallest little thing too, like a misspelled term or version check in the AU process causing it, cause A2 worked fine, even after failing validation in 10.5.3/LP 8.02. I doubt it'll happen, but to me, it seems Apple should be the one fixing this.......

At least some of the developers are getting sick of it, everyone gripes at third party developers for not having their plugins immediately compatible with Apple but that's only half the story. I swear Apple would like their user base to only use Apple products.. of course, then we would be using a closed system. On a positive note, Logic upgrades don't come out that often.

I didn't have any problems with the upgrades, however, I didn't run the AU validation.

pancenter-

THe bottom line is that something, God knows what, changed in the upgrade and, apparently, all the developers were left high and dry until the actuall update release. SO now, there's fols like us, left with plugs which won't validate. Yeah sure they'll work, but ****, I don't wanna HAVE TO select a plug in from a list specifically marked as having not passed validation.

Sorry, but this is an Apple thing. They need to fix it.

Hi All,

So there is a way to get it working.

Even if AU validation FAILs, you can still open it. I have done this kind of thing before. just make sure you check the first box it may fail. but make sure it's checked before closing the au manager.

The plugin will then appear as Audio Units>-Incompatible>IK MULTIMEDIA>Amplitube 2

It still works. haven't tested it much though.

Best of luck one and all.

F

Spectrasonics Trilogy and Atmosphere crash validations on my dual G5 10.5.3 LP 8.0.2 and 8.0.1 too!

😟

Atmosphere fails here too. Have you contacted Spectrasonics about it yet?

No... but I will (I'm on a hard recording session at this time.. and I post something on my favourite discussion forum... when I have free time 😉 )
I think it is a problem related with 10.5.3... because I've just have the Audio Units cache that was made on Leopard and 10.5.2...

I just try by moving the caches for reply to the many question of my friends about that.

Now I just put again my previous Audio Unit caches and all the only PPC Spectrasonics works correctly...

It is one of the first great alarms that make me think that Apple could be forgetting to support leopard for PPC machines!

😟

In any case you can manualy force Logic to load Atmosphere and Trilogy... because they works fine as always with 10.5.3!!!
they work as usual (with realease restricion when stopping and start play)

Maybe is this issue that make them unsupported? because they are only PPC?
It is very strange because in a previous system release they PASS AU validation... bah!

AU validation app is an unnecessary waste of time in professional studios. (it could be bypassed with a preference setting... please don't show AU validation pop up... I am the owner of my computer and I want to be empowered to decide what I use under my responsibility... THANKS)

G

Hi All
I email Ikmultimedia about the au validation problem and this was their reply

+Thank you for your request.+
+Yes we are aware of issues with Logic 8 and are currently investigating the+
problem.
+However you should still be able to use the software if you 'force'+
validation.

So fingers crossed they will solve the problem soon.
TTFN
Subcoustic

If you don't care about "actually" validating the audio units, you can trick logic into thinking it's validating a plug-in, when it's just automatically passing everything. The way I did this was, if you show hidden files and navigate into usr/bin, you'll find a combination of auval and auvaltool. What happens when you run auval, is it effectively forwards to auvaltool, and this is the new validation tool being used. You can delete auvaltool (or rename it or move it to keep from permanently losing the file), and this will solve all your problems. The only caveat to this method is that logic can no longer scan audio units being used, so if there are any that will crash logic, you won't be able to scan to prevent that.

What will happen is logic will launch AU Manager, it will scan the plug in(s), wait for the process to start, and instantly pass the audio unit. Amplitube will now be located where we all want it to be, no longer under "incompatible", once you pass these audio units, you can replace the auvaltool, and all will be back to normal, with AU Manager capable of scanning for serious problems.

very good to know that

Thanks

🙂