Pro Tools not seeing Carbon

[wickett]

Thanks. I have removed carbon central.
I've also reset the firmware + reinstalled HD drivers a few times now.
I get an error message when starting Pro Tools saying it cannot communicate with the carbon. It asks me to select the audio device in Hardware setting but the carbon is not in the list even though the system can see it and it is detected and ticked in Audio/midi setup.
I restarted Pro Tools. while holding down the 'n' key and I was able to select the carbon in the hardware list. Not sure if this was because I held down the key or because I restarted Pro Tools.
ISome times when I power the carbon of and on or restart pro tools It works again but after I restart my mac I get the same problem again

[wickett]

The 'N' key does the trick until I restart my Mac. Then the same issues occur.

[massivekerry]

Originally Posted by wickett

Thanks. I have removed carbon central.
I've also reset the firmware + reinstalled HD drivers a few times now.
I get an error message when starting Pro Tools saying it cannot communicate with the carbon. It asks me to select the audio device in Hardware setting but the carbon is not in the list even though the system can see it and it is detected and ticked in Audio/midi setup.
I restarted Pro Tools. while holding down the 'n' key and I was able to select the carbon in the hardware list. Not sure if this was because I held down the key or because I restarted Pro Tools.
ISome times when I power the carbon of and on or restart pro tools It works again but after I restart my mac I get the same problem again

I'm completely spitballing here, but I believe you do not need the HD drivers if you're using Carbon. I got a new computer when I bought my Carbon and have studiously avoided the HD drivers since then. Maybe (fully?) remove them?

[Darryl Ramm]

Correct, HD Drivers are totally unneeded, they are for HD Native and HDX only.

[dominicperry]

Originally Posted by wickett

I then Re-install the carbon central app and it 'sees' the carbon is an expansion unit.

I think this might be the problem. Have you accidentally designated your Carbon as an Expansion unit rather than Primary? I'm not sure how you'd manage this if you only have one unit, but Carbon Central is the place to assign this value.

Sounds like you might need to re-install Carbon Central, change that value and then try again.

The other boring but worthwhile thing to do when troubleshooting connectivity problems is try another known good (Ethernet) cable.

Dominic

[K Roche]

Originally Posted by wickett

Thanks. I have removed carbon central.
I've also reset the firmware + reinstalled HD drivers a few times now.
I get an error message when starting Pro Tools saying it cannot communicate with the carbon. It asks me to select the audio device in Hardware setting but the carbon is not in the list even though the system can see it and it is detected and ticked in Audio/midi setup.
I restarted Pro Tools. while holding down the 'n' key and I was able to select the carbon in the hardware list. Not sure if this was because I held down the key or because I restarted Pro Tools.
ISome times when I power the carbon of and on or restart pro tools It works again but after I restart my mac I get the same problem again

This is could be your problem. Carbon does not use HD drivers

[wickett]

I've uninstalled the HD drivers.
I reinstalled carbon central and checked that it was not configured as an expansion unit.
Same issue occurs.
Uninstalled carbon central again.
Same issue occurs.
Tried other known good ethernet cables.
Same issue occurs.

Thanks anyway.


Thanks anyway.

[wickett]

Same issue after uninstalling the drivers.
2 weeks of this and I'm now looking at good old RME interfaces.
Sigh..........

[wickett]

After connecting the carbon by holding the 'N' key I got the AVB internal error AAE -6123

[[email protected]]

No one asked, and I don't see it in your posts..



What are the specs of your computer. You said Mac.. but Macbook/Pro? Mini? Studio?

If you're on a macbook what ethernet interface are you using?