Jul 5, 2012 8:55 AM in response to angelruiz85
You might have to re-install OS X, if you are not able to extract it from the packages. How did you accidentally delete a system file?
Jul 20, 2012 11:33 AM in response to angelruiz85
hey there i done this too but luckily i have another mac with lion so i copied it from there to my other computer here is the link to download it i had to zip it in order to keep it the exec kind:
http://www.mediafire.com/download.php?966iju00do9vck7
now to put the auvaltool back in its place follow this first, this is to find the hidden folder:
Show hidden files Mac OS X 10.7, 10.8, 10.9 and 10.10 Yosemite
now once done you will want to go onto the finder to macintosh hd and find the usr click it then click bin open the zip and drag it in it worked for me and it should you too !
cheers,
Ollie
Mar 10, 2015 8:34 AM in response to oliver49
Hello Ollie, this line was a little confusing.
«now once done you will want to go onto the finder to macintosh hd and find the usr click it then click bin open the zip and drag it in it worked for me and it should you too !»
Where exactly am I dragging this file into? I’m running Yosemite 10.10.2, Logic Pro and X
Mar 10, 2015 8:41 AM in response to coolrunnings
Note:
The version of auvaltool provided with an earlier OS X version, may not be compatible with the version included with Yosemite because of changes made in Yosemite and in fact could cause all kinds of issues if used with Yosemite… that could easily be hard to track down and in trying to troubleshoot those, you could end up wasting more time than it would take to do things properly in the first place.
I would recommend, to prevent such possible issues… you simply start again from scratch and install a fresh copy of Yosemite and LP… and not try the method suggested above….
Also, for what it is worth…. supplying a copy of an OS X file to another person via a link to a remote storage system….is actually illegal…. and is against the OS X/Apple’s T&C/Agreement/License….
|
Hello, I’m currently running both the old and new Final Cut Pro applications on my MacBook Pro. The new, Final Cut Pro X, was just recently installed. Every first time that I launch the app after my computer is booted, AuvalTool icons appear in the dock momentarily. After that, if I were to quit and launch the app, they don’t show up. However, if I were to restart my computer, and relaunch the app, then they show up again. So far as I know, they shouldn’t be doing this, as they’re only supposed to show up when FCP X needs to validate new Audio plugin. The strangest part is that I haven’t even installed a single plugin, but it does this every time the app is launched for the first time after booting up. If anyone else has this issue, please tell me. Is it normal? If not, how can I fix it? Thanks, |
|
|
Please Log in to join the conversation. |
|
This is not normal. If the problem persists delete the following cache file: ~/Library/Cahes/com.apple.audiounits.cache Quit FCPX, put the cache file to the trash (don’t empty the Trash yet), then relaunch FCPX. Normally you will see the AuvalTool appear once again, but then never again until you add a new Audio plugin of you update an existing one. If everything works well you can empty the trash. Like dgwvideo says there is a specific installation method recommended by Apple, but FCPX and FCP also work perfectly together on the same drive without partitioning. |
|
|
Please Log in to join the conversation. |
|
Unfortunately, I just tried it, and it did nothing. Any other ideas? |
|
|
Please Log in to join the conversation. |
|
I have solved the problem. It would seem that it was ESET Cyber Security causing the problem, as it erased the cache files at startup. |
|
|
Please Log in to join the conversation. |
|
Here’s two long standing rules for video editing, any NLE, any OS. Then that stuff off when you need to edit. And if ESET is trashing cache files, you need to get that garbage off your Mac, contact them and let them know it’s doing stuff that is dangerous to your system stability. It’s like that MacCleaner crap, I know half a dozen people who bought it and it left them with systems so trashed nothing was recoverable, and the developer never lifted a finger to help, refused refunds. I hate that anti-virus crap. If you feel you really need it, get a long time known name brand. |
|
|
Please Log in to join the conversation. |
|
I agree 100% with NOT USING the anti-virus software. Never used it and never will on my Mac. I make sure (although it would be a headache) that I can always be in a position to completely restore my mac if a virus completely took over, but in 8 or 9 years using a mac I never had the problem. I do, however, use Time Machine (and so far without any problems affecting FCPX)…but I know BenB has a different opinion on this. Creating history….one edit at a time ! |
|
|
Please Log in to join the conversation. |
|
It’s because TimeMachine eats up a lot of CPU time and drive bandwidth and RAM that I’d rather have available for doing my editing. Remember that it monitors changes at all times. Not to mention the many users that have had problems running it at the same time as FCP. That’s all. |
|
|
Please Log in to join the conversation. |
|
Thanks, Benb. I didn’t realize it did continual monitoring. I thought it just saved snapshots every hour. But I will turn it off at my next editing session and see if there’s some improvement. Every little speed boost helps! Creating history….one edit at a time ! |
|
|
Please Log in to join the conversation. |
|
It has a deamon or two running in the background. |
|
|
Please Log in to join the conversation. |
|
I completely uninstalled Eset. As for Time Machine, I don’t have it set to back up regularly, automatically anyways. I always do it manually, when I’m not running anything. |
|
|
Please Log in to join the conversation. |
Recommended Posts
-
- Share
Since I upgraded to Lion, the auvaltool tool is crashing with some of my 32 bit plugins. They actually still work, but there are listed in the plugins menu in an «incompatible» category.
Has anyone experienced this problem?
I am using the latest version of Logic in 32 bit mode.
Link to comment
Share on other sites
-
- Share
Which plug-ins and versions?
Link to comment
Share on other sites
- Author
-
- Share
The following plugins have crashed the au validation:
Altiverb 6.3.7
Melodyne Plugin 1.04
Melodyne Bridge 3.2
PSP 608 Multidelay 1.1.2′
I somehow have the impression the auvaltool is corrupted, but I’m not sure. Again, these plugins do work, even though they say «failed» or «crashed» validation in the AU manager.
Link to comment
Share on other sites
-
- Share
The following plugins have crashed the au validation:
Altiverb 6.3.7
Melodyne Plugin 1.04
Melodyne Bridge 3.2
PSP 608 Multidelay 1.1.2′
I somehow have the impression the auvaltool is corrupted, but I’m not sure. Again, these plugins do work, even though they say «failed» or «crashed» validation in the AU manager.
I have the latest version of Melodyne (1.30) and that validates perfectly in Lion.
I can not comment on the others.
Link to comment
Share on other sites
- Author
-
- Share
Thanks for your feedback. I think what all of these plugins have in common (except PSP) is they are the latest versions of software that has since been revisioned or in the case of Altiverb, is about to be upgraded.
It is just strange, because there are no error messages from Ableton Live or Digital Performer or Final Cut Pro, etc., just Logic. So it seems the auvaltool is the problem, because again the plugins do work.
Link to comment
Share on other sites
- 3 months later…
-
- Share
Hi, I have a similar problem.
I recently upgraded to Lion, and now one my my plug ins also dont work. I am using Logic Pro 8.
For me it crashes when loading the PLAY plug in (with east/west Symphonic Orchestra).
The AU manager says, crashed during validation.
I have tried in both 32bit and 64 bit.
Anyone help please? This is a fairly vital piece of kit for me!
Thanks
Link to comment
Share on other sites
- 2 months later…
-
- Share
I am getting the same problem as aidenfry. Any solutions found yet? can people update this tread please..?
Link to comment
Share on other sites
-
- Share
I am getting the same problem as aidenfry. Any solutions found yet? can people update this tread please..?
Please add your Logic version and system info to your signature: Forum Rules — please READ THIS before posting (#5)
And add what version of Play you are using to your post.
Link to comment
Share on other sites
-
- Share
That probably doesn’t help, because auval is part of Mac OS X, not Logic. Logic Pro is just calling auval to — duh — validate AudioUnits. You can therefore receive a new version auval with any Mac OS X update.
Link to comment
Share on other sites
-
- Share
That probably doesn’t help, because auval is part of Mac OS X, not Logic. Logic Pro is just calling auval to — duh — validate AudioUnits. You can therefore receive a new version auval with any Mac OS X update.
Of course that information helps.
He is having problems with Logic 8 and Play.
System info means OS, Computer…
Link to comment
Share on other sites
-
- Share
I was having the issue after upgrading to L9.1.7 as documented here: viewtopic.php?f=1&t=82495
Unchecking the offending auto mapped plug-ins in the Audio Units Manager stopped the crashing and rescanning process with each start up.
It’s not uncommon for one DAW to be cranky with some plug-ins while another DAW does not.
Link to comment
Share on other sites
Archived
This topic is now archived and is closed to further replies.
I ran into the very same issue:
So I digged a little deeper and I found the reasons for it:
-
auvaltoolexecutable can’t be found / or is not reachable to Xcode for execution (maybe security considerations) -
the schema is configured to debug
auvaltoolbut it doesn’t contain the correct debug symbols! -
the build step to build the AU in XCode is set up with dummy data to call
auvaltool. -
Option A: Disable the «Run» task in Xcode and run
auvalin a terminal on your own like this with the correct arguments that match your plugin id’s: auval -v aufx $PLUG_UNIQUE_ID $PLUG_MFR_ID, i.e.:auval -v aufx Lapa AHVI
- Option B: Fix the schema config in Xcode like this:
-
Open a terminal and run:
cp /usr/bin/auval /Applications/auval. This will copy the binary ofauval(auvaltool is only a symbolic link) — and place it into a place your user can reach without any security limitation. -
We gonna fix the schema config:
-
Take a look into your
resource.h. Note the values ofPLUG_UNIQUE_IDandPLUG_MFR_ID:
- Then select the build target in the menu:
- Go to: «Edit Scheme…»:
-
Select «Run» and:
-
Disable the «Debug executable toggle»
- Click on the combobox that says «auvaltool»-> Select: «Other…» and select the «auval» executable you just copied to /Applications
- Now select «Run» -> Switch to «Arguments» tab:
- Instead of
-v aufx Ipef Acme, which is dummy data and totally wrong, put-v aufx $PLUG_UNIQUE_ID $PLUG_MFR_ID, i.e.:-v aufx Lapa AHVI
=> FINALLY, run the task again, and…
IT WORKS!
@olilarkin Maybe we can improve the duplicate.py by adding two more arguments to specify set the PLUG_UNIQUE_ID and PLUG_MFR_ID and replace them automatically in resource.h and the Xcode schema config. Maybe I could take a look at it and pull request. Because: If new users start using this project they even might think it doesn’t work «at all» when the first thing that happens after clicking «Build» is an «Internal error» :))
non-Apple AUs to be specific — they’re there in /Library/Audio/Plug-Ins/Components, but auvaltool says then can’t be opened. Strange is that the version of auvaltool is still 1.6.1a1, so that’s not changed.
output from auvaltool below for v2.2 of Omnisphere from Spectrasonics, but all non-Apple AU plugins are reporting this. Of course the Apple plug-ins are in the app package Logic Pro X itself and not in the directory above.
thinking perhaps this was a permissions issue, ran Disk First Aid but that didn’t change anything.
previous command line options to repair permissions also not working on Sierra such as below:
To verify
Code:
sudo /usr/libexec/repair_packages --verify --standard-pkgs
To Repair:
Code:
sudo /usr/libexec/repair_packages --repair --standard-pkgs==================================
validating Audio Unit Omnisphere by Spectrasonics:
AU Validation Tool
Version: 1.6.1a1
Copyright 2003-2013, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options
—————————————————
VALIDATING AUDIO UNIT: ‘aumu’ — ‘Ambr’ — ‘GOSW’
—————————————————
ERROR: Cannot get Component’s Name strings
ERROR: Error from retrieving Component Version: -50
* * FAIL
—————————————————
TESTING OPEN TIMES:
FATAL ERROR: didn’t find the component
validation result: couldn’t be opened