SSL nucleus incompatibility

[Slis]

Hello there guys,
I have some problems with the SSL nucleus and pro tools.
Before I get started and I need to tell you that I have already sent mail to the SSL support and they told me that the problem is not from them and said to ask avid. I already tried the DHCP and the static IP setting and the problem remains the same.
The controller is connected correctly and works fine for some minutes, but as I continue working on a project, the controller is not working interactively. I cannot move the faders from the controller and listen or view e changes on the pro tools faders. From the other side now, if I move e faders on the protools with the mouse, I can see movement on the controller faders. Can you please tell me what's going on? To be honest with pt10, nucleus works fine.
Thank you in advance.

[musicman691]

Is this the new Nucleus 2 or the older one? I know there's an extensive setup routine with the new one that could quite frankly be easier on the end user. You would think that PT being one of their main targets they'd have functionality perfect between the two.

Have you tried a new Ethernet cable? Sometimes a crossover cable is needed instead of a straight-through one.

[Slis]

I own the old nucleus. No I didn't try a new Ethernet cable but I will.
But if it's not it then what? As I said the controller works fine with pt10 but I cannot install it anymore and don't know why. Anyway, that's not the point. Do you have any new ideas?

[Southsidemusic]

Check under peripherals (in Pro Tools menu) and make sure that Ethernet is checked there so PT can read. That option gets unchecked when trashing preferences and or installing a new PT version for some reason.

[Slis]

I can't see any other option in peripherals menu.
Setup/peripherals/midi controllers
This is how I am connected now:
Type hui 01 Ethernet midi on both receive and send, channels 8
Type hui 02 Ethernet midi on both receive and send, channels 8

[Southsidemusic]

Aha, sorry, thought that SSL used ethernet cable and protocol.

[Slis]

I believe that this is some kind of bug or something and I am thinking to work with another daw from now on. Please if you have any ideas or one of you can speak directly to avid for some bug fixes with a light update it will be nice. Maybe I am asking too much but you never know. I am very disappointed because I have paid 5000€ for the controller and 560€ for protools and I cannot make them work together. I don't know what else I can do.

[Emcha_audio]

Have you seen these?

http://www2.solidstatelogic.com/vide...ucleus-2-setup

and

http://www.solidstatelogic.com/nucleus2network

[musicman691]

Originally Posted by Emcha_audio

Have you seen these?

http://www2.solidstatelogic.com/vide...ucleus-2-setup

and

http://www.solidstatelogic.com/nucleus2network

Those are for the new Nucleus 2; op has the original. Found this video on YouTube that shows how to do the setup in PT.

https://www.youtube.com/watch?v=n1DJ0_7qXXo

Amongst other things ipMIDI has to be installed.

[darkfader]

So I have this issue since I got my Nucleus as well. I run Pro Tools on Windows as admin, so it's not that known other pesky issue.

By any chance, does Pro Tools freeze when you try to close it after your controller stop responding? Also does it tend to happen more often with bigger sessions?

If so, this is definitely a problem with Avid, but I wish SSL wouldn't bounce the ball around, investigate, and get Avid to fix their software. I haven't personally called support yet, but someone else on this forum did and Avid / SSL were bouncing the ball at each other.

I have been trying different things to get to the bottom of this issue before calling support, and I suspect this may be machine-specific or there is a conflict with another piece of software or driver installed. What's your machine configuration?