Do you want the application “Neuron Plugin Scanner.app” to accept incoming network connections?
If you’re on a Mac running a contemporary1 version of OS X with the Firewall engaged and trying to fire up RX 5, you might encounter the following error.
Do you want the application “Neuron Plugin Scanner.app” to accept incoming network connections?
What is Neuron Plugin Scanner? The alert dialog box warns: “Clicking Deny may limit the application’s behavior. This setting can be changed in the Firewall pane of Security & Privacy preferences.”
The only solid reference to this app that I could find is a tiny thread on this forum. A guy named Jonah (possibly this guy?), who claims to work for iZotope Inc. (software developers of the amazing RX 5, Ozone, Iris, etc.), states that Neuron Plugin Scanner is a “helper application to scan your host for plugins to use” and that “it never connects to any other computer, iZotope, the internet, or anything else!”
That seems harmless, but I wanted better proof that Jonah was legit and the app wasn’t something more malicious. I contacted iZotope customer service and got this reply:
Thank you for reaching out! Yes the Neuron Plugin Scanner is related to RX 5. RX 5 has the ability to host 3rd party plugins. Those plugins have to be scanned by the Neuron Scanner before they are instantiated. Allowing this functionality is recommended.
Thank you for your time!
iZotope Customer Care
Verdict: Neuron Plugin Scanner is safe. Simply click Allow and keep making music.
It turns out the app is harmless. But clicking Allow every time you open RX 5 is a pain. Shutting off the Firewall is not wise. So if you want to make this dialog box go away forever, here is what to do.
1. Open Security & Privacy panel in System Preferences
You can find System Preferences under the Apple logo () on the far left of the menubar. Click on the Security & Privacy icon.
Click the Security & Privacy icon
2. Unlock System Preferences
If your System Preferences are locked, unlock them. Enter your system account password when prompted.
Unlock to enable changes to the Firewall
3. Open Firewall Options
Once you enter your password, the Firewall Options button will no longer be grayed out. Click it.
Click on Firewall Options
4. Find the app Neuron Plugin Scanner in the list
Scroll down until you see Neuron Plugin Scanner. It will have a red dot and the words “Block incoming connections” beside it.
Find the Neuron Plugin Scanner.app
5. Allow Incoming Connections
Toggle the setting for the Neuron Plugin Scanner app to read “Allow incoming connections” and exit out by pressing the OK button.
Set the Neuron Plugin Scanner to “Allow incoming connections”
That should fix the problem. The alert dialog for Neuron Plugin Scanner will no longer pop up…at least until iZotope updates their software or Apple changes their operating system. This is what worked for me with RX 5.00.135 running on OS X 10.10.5. Not all systems are the same. YMMV.
1Contemporary = a version released within the last few years prior to this article being publish. If these issues still exist at some point years from the publish date, I would be surprised. If so, well hello dear reader from the future. Do we have flying cars in the time you are from?
No Comments >
Make that Waves Preferences pop up dialog window go away forever WITHOUT having to uninstall and reinstall your plugins.
After doing a fresh install of Pro Tools and my Waves plugins, this Waves 9.2.100 Preferences dialog window (pictured below) kept popping up every time I fired up Pro Tools.
Checking the “Don’t ask me again” checkbox didn’t seem to be working.
I searched for some solutions on the Google machine and found some forums were recommending a complete uninstall and reinstall of all Waves plugins. This didn’t seem necessary. Here’s the fix I used:
- Quit Pro Tools.
- Trash the entire Waves Preferences folder. The folder is located in the Preferences folder in your user Library folder, not your system Library folder. A quick way to locate the folder is to switch to the Finder and hit Shift+Command+G. A Go to Folder dialog window will pop up. Copy and paste the following line in that field and hit enter.
Put that folder in the trash and empty the trash.
- Start Pro Tools.
- A window should pop up asking you to select the Waves 9.2 Plug-Ins folder. By default, it should be located in the Waves folder in your Applications folder.
Once you’ve located the folder, click Open.
- The Waves 9.2.100 Preferences dialog window should pop up again. The “Don’t ask me again” box should be checked. If not, check it and hit OK.
- To test if everything worked, quit Pro Tools and start it again. The Waves dialog window shouldn’t reappear.
About the Fix
I adapted this solution from a somewhat unrelated problem I found on Sweetwater Sound’s SweetCare Knowledge Base. The fix definitely works for the following system set up. YMMV
- OS X Mavericks 10.9.3
- Pro Tools 9.0.6
- Waves 9.2.100 plugins
Please leave a comment below if this helped you or not.
15 Comments >
An alternate method that might make your Bluetooth device connect with your iOS device.
Can’t get your Apple Bluetooth keyboard to pair with your iPhone, iPad, or iPod touch? I couldn’t either. My A1255 keyboard wouldn’t connect at all. The iPhone would find the keyboard, but wouldn’t update the name of it, nor ever present the four digit code for pairing. I could only get this error:
Make sure “Keyboard” is turned on, in range, and is ready to pair.
I tried a bunch of fixes I read about online and none of these worked in any combination nor configuration:
- turning Bluetooth off and on
- rebooting the iPhone
- holding the power button on the keyboard
- deleting other Bluetooth device pairing from the iPhone
- clicking ‘Forget This Device’
- connecting to another device and then my iPhone
- replacing the batteries
- holding the V, A, and R keys while powering on the keyboard
- turning off Bluetooth on any other nearby devices
It seems Bluetooth under iOS 7 is broken. Lots of people are having issues with Bluetooth on iOS 7 that weren’t there in older iOS versions. Unfortunately, Apple is apparently ignoring this problem.
Here’s how I finally connected my keyboard to my iPhone.
- Switch off Bluetooth on iOS device under Settings > Bluetooth.
- Shut off the keyboard by pressing and holding the power button for 3 seconds.
- Switch on Bluetooth on iOS device.
- Turn on the keyboard by pressing and holding the power button until it green light blinks.
- The keyboard should appear listed under the DEVICES heading in the iPhone Bluetooth settings screen with “Not Paired” in gray next to it.
- Now at this point you’re supposed to just tap on the listed device on the iPhone to begin the pairing process, but when I would do that it would time out with the “Pairing Unsuccessful” alert. Here’s the trick: repeatedly tap on the listing (maybe 5-6 times) and hopefully the “Bluetooth Pairing Request” alert will appear with the four digit code you’ll need to enter.
- The pairing may fail the first time. Try again.
- I also found that subsequent attempts to connect after forgetting the device worked much better after that initial connection.
I hope this fix works for you. Let me know if it does.
7 Comments >
A friend gave me a Pro Tools session on a thumb drive. I copied the entire session folder to my external hard drive and opened it. After changing the routing to work on my system, everything played back fine. Then I tried to clean up the session.
Every time I attempted to cross fade or consolidate an audio or MIDI region, I would get an error like this:
“Could not complete your request because You do not have appropriate access privileges (-5000)…” Why do you build me up, Buttercup? Capitalize ‘You,’ then award me negative five thousand points…pssh.
Seeing the “access privileges” bit, I figured the problem was probably an operating system issue, not a Pro Tools thing. The session files were indeed set to ‘Read Only,’ which is why I could play back the session, but couldn’t do anything to the regions or fades.
Here’s how to fix the issue.
- Close the session. You shouldn’t have your Pro Tools session open while changing its permissions.
- Select the session folder in Finder. Make sure the session folder is highlighted, not the files inside the session.
- Get Info. Hit Command-I (capital i) or from the Finder menu select File > Get Info. An Info window will pop open.
- Change all privileges to ‘Read & Write.’ At the very bottom of the Info window is a box with a list of users and their privileges. They should all be set to ‘Read & Write.’ You may be asked for user password to unlock and verify the change.
Not listed are NSA permissions, which by default are set to ‘Collect All,’ but, like, totally isn’t a violation of your privacy.
- Close the Info window. After making the privilege changes, try reopening your Pro Tools session and editing some regions. If you can, this fix worked for you.
Why does this error occur?
Many common problems that Macs develop are related to file permissions errors. Files are given various permissions to maintain privacy between computer users and prevent users from easily messing up the operating system.
Permissions can get wrecked when disks are removed without being ejected and during unexpected shut downs. That’s why it is important always to try to eject disks and shut down your Mac properly.
Permissions can also get messed up during copying and moving of files or while installing software. That appears to be why I experienced this error. During the copying of the files, the permissions were never changed to grant me access. Simple problem, simple fix.
After encountering this problem on several other sessions, I tried another method and found a better (and probably more proper) solution. Try this in addition to or instead of the above fix:
In the problematic Pro Tools session, pop open the Disk Allocation dialog (Setup > Disk Allocation…).
When the dialog window opens, you’ll be presented with a list of all the tracks in your session and the location where that track should be located. If you’re having problems creating fade files and getting the sort of error that brought you to this page, then you’ll probably see something like the picture below.
As you can see, not all of the tracks had their disk allocation pointing to the right place. To fix them, select all of the incorrectly allocated tracks, then click and hold the little up/down arrows on the right hand side. A little window will appear and ask you to select a folder. In my case, the session file was looking on my internal system drive instead of my external audio drive. Choose the correct location of your session files and click OK. That should solve the issue. Let me know if this worked for you.
29 Comments >
This might be the solution.
An unexpected authorization error 14051 occurred.
ID: ePAY : 14051 / Dngl : 1595
I got this error a few days ago. It’s a new one for me. What caused this? Good question. I have no idea. Pro Tools wouldn’t really start after this.
As usual the Avid forums weren’t very helpful. Which led to this tweet…
For the record, at the time the error occurred I was running OS 10.8.4 and Pro Tools 9.0.6 on a Mac Book Pro with an iLok 2.
I had to force quit Pro Tools. Then I unplugged my iLok 2 and plugged it into a different USB jack. Presto. Working again. Not sure what caused it, nor if switching USB jacks was actually the fix, but I did get it working again after doing so. Hope this helps somebody.
I confirmed again that switching which USB jack the iLok 2 was plugged into made the difference. I would think that this is a problem with that particular USB jack, but all other USB devices work just fine plugged in there. Hmm…
5 Comments >
After upgrading to the newly released Pro Tools 9, I couldn’t open sessions or create new ones. I got this error: “Could not complete the Open Session… command because Pro Tools could not set sample rate to specified value..” I hunted around on the web and various forums, but couldn’t find a solution that fit. […]
After upgrading to the newly released Pro Tools 9, I couldn’t open sessions or create new ones. I got this error: “Could not complete the Open Session… command because Pro Tools could not set sample rate to specified value..” I hunted around on the web and various forums, but couldn’t find a solution that fit. I found several items relating to Windows and Pro Tools 8, but nothing for a Mac running Pro Tools 9. After messing around a bit I figured out the problem was with my playback engine. Here’s how I solved it. Let me know if it works for you too.
Open the Playback Engine dialog under the Setup menu item.
From the menu bar select Setup > Playback Engine… to open the Playback Engine dialog window.
The problem is with the Pro Tools Aggregate I/O.
By default, my current engine was set to “Pro Tools Aggregate I/O.” It’s odd that this Pro Tools would leave it that way after an installation since AVID states that it is not supported in OS X.
Select your current playback engine.
The fix is easy. Simply select the right playback engine. Your options may differ based on your setup.
In my case, I usually would edit with my Mbox 2 Micro, but since Pro Tools 9 gives us so many more options for hardware compatibility, I selected Built-in Output. I was able to edit some vocal takes using my Macbook Pro’s speakers instead of pulling out my headphones. Nice!
29 Comments >