Jump to content

Plugin "Not Available" - Red Circle Shows Up


RoyFan

Recommended Posts

I believe a similar topic was covered but I think mine is a bit different.

I AM able to start a project and create some SW tracks. Then all of a sudden (usually it starts with creating an additional track)

whatever SW track I create has a Red Circle and says either "can't find" or "unavailable" - regardless if it's ES2 or third party.

I believe at this point even previously create SW tracks are unresponsive with the same circle msg etc.

 

Then all of a sudden it works again. So far I've been lucky it only stays like that for short periods of time, but it's scary and I'd love to solve it. midi driver maybe?

Link to comment
Share on other sites

AFAIK, the only way to have a Logic plug-in such as ES2 be disabled is when the audio engine is not unabled under Logic Pro X > Preferences > Audio, so next time this happens, have a look at that? What equipment are you working with?

 

Click this link to your signature and add your system information:

 

• Logic version and sub-version (e.g. Logic 10.0.7)

• OS X version and sub-version (e.g. OS 10.9.3)

• Computer (e.g. MacBook, Mac Pro, iMac)

• Processor (e.g. 2 GHz Intel Core 2 Duo)

• Memory (e.g. 2GB)

• Audio interface manufacturer and model (e.g. Presonus AudioBox USB)

• MIDI Controller manufacturer and model (e.g. M-Audio Axiom Pro 49)

 

(most of that information can be found by choosing Logic Pro X > About Logic Pro X, and  > About This Mac)

Link to comment
Share on other sites

Thanks Dave! I updated my signature. Yes you were right about core audio being disabled. So the question is:

Have you heard of problems with interfaces losing touch temporarily with Logic cause of any reason

-Faulty Interface? (focus rite scarlet solo)

- Faulty usb/firewire ports? (tho it's a new computer)

- Computer being a pc parts computer running Logic SW?

-Faulty overall driver scheme or configuration of the computer?

or Any other reason?

 

So far it's been resolving itself, but I worry that it might get worse, and it worries me that I don't know what it is that's causing it..

 

Thanks in advance!

Roy

Link to comment
Share on other sites

thanks - so you mean whenever it happens, since i'm using midi anyway, just by pass the focus rite right?

 

ever hear of a situation where a certain i/o port works better than another for an interface?

you know of a good forum for focus rite..or do they have customer service that's helpful with these bugs?

I'm gonna google it..just wondering..thanks again!

Link to comment
Share on other sites

thanks - so you mean whenever it happens, since i'm using midi anyway, just by pass the focus rite right?

No, that's not what I had in mind. What I'm saying is: for troubleshooting's sake, try to work without the Focusrite for a while: if the issue disappears, then you can clearly point to the Focusrite (and its driver) as the culprit.

 

ever hear of a situation where a certain i/o port works better than another for an interface?

No, unless one of them is damaged.

 

you know of a good forum for focus rite..or do they have customer service that's helpful with these bugs?

I'm gonna google it..just wondering..thanks again!

There's a Focusrite employee who comes and help right here on Logic Pro Help, I'll try to see if I can ping him.

Link to comment
Share on other sites

Thanks Jakob I will. This computer was assembled for me by someone. Some of the components weren't so good like 1 of the hard drives. Do you think it might be the actual usb ports themselves?

It could be many things however at this point in the troubleshooting process, what I suggested in my last post is the first thing you should test. Then, depending on the results you get, we can determine what's at fault and what isn't, or move on to more tests.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...