Thought maybe someone here could help me setup my nucleus as Im having issues So after lots of trouble, I now got ipmidi working AND the nucleus is showing up green and connected in my ssl remote but it still doesnt have proper contact I had the wifi off as well Also the internal display of the Nucleus is showing squares Any ideas??? Attached Thumbnails. Hoping for help. Originally Posted by Mr.
Reason: Fixed. My Studio. Hi, I'm having the same problem here Did you find a solution? Thanks, regards E. Hi, I've been fighting with my nucleus2 for 4 months. I think your issue is related to WiFi. You need to remove Wifi from your network profile - turning it off will not fix the problem - it needs to be removed completely.
My Nucleus2 profiles all disappeared and doing the above worked for me a couple of days ago. Nucleus2 is not the most friendly device to configure - I have yet another support job logged with SSL see my other posts for details. Last edited by Herc; 8th September at AM..
Everything worked fine. I had Nucleus soundcard and control surface both working perfectly Its gotta have something to do with TotalMix having an IP address. I just don't know how to fix it.
TotalMix doesn't have any IP address, that's nonsense. All of those options are deactivated by default, so it shouldn't interfere with anything else. I don't have any particular experience with Nucleus setup. So if remote control from Nucleus works, when RME interface is turned off, and stops working, when your power it on and appears in the system..
For example when particular remote layer is set to ports number 3 and 4, then new ports appears and original ones gets shifted to 5 and In that case remote layer stops working and you need to set it up again like in a DAW or some control panel, where you select right ports again according to new port ordering.
Generally that shouldn't happen, because good programs doesn't rely on fixed port order, but rather on ID of port or at least its name. However I've seen programs, which behaved like that.. Besides of that, SSL has support, which should help you out with Nucleus setup.. Hi, hard to guess, what's really happening there.
However oddities you mentioned with regards to setup in the DAW, seems to be right according to manuals. You need to enable six of them to use all three DAW remote layers. Weird, but apparently that's how they designed that. With the rest I really don't know, I played with Nucleus 1 somewhere, but it was already set, so I didn't have any reason to mess with setup.
There is few other elements though.. Also with regards to stuttering or some apparent loosing of communication, I'd double check correct network setup in your computer. You've touched elsewhere, there is a WiFi dongle for internet access and likely some fixed ethernet network port NIC , which you're using for direct connection to the controller. If you left all IP settings in the system and in setup Nucleus at default eg.
Also I'd disable software firewall in Windows, this can mess up with network communication between devices MIDI ports 2 and 1 , layer 2 if ports 4 and 3 are used etc. CC Default. So with RME interface connected although I'm still not convinced, there's some interplay between those.. If there's Quick controls remote layer not sure, whether it is still there, but it was in Cubase before years , I'd set its input and output MIDI ports as "Not connected", which should disable that. IP port 2 and 1.
If that won't be working, I'd likely push on SSL support to give some further assistance.. That's all, which come to my mind without actual hardware.. Unfortunately, the stuttering is an issue. The buffer was at when it started, I moved it up to the next highest value which is the highest for the Fireface You referred to generic DAW playback issues.
There can be multitude of issues causing this.. In general I didn't have issues with RME interfaces at driver level.. Cards with Texas Instrument XIOB chipset were the least problematic for me, but for instance I've never used those with more recent AMD boards and systems generally because almost nobody use firewire interfaces with newer systems, so I haven't any chance to try it.
Cool, but it's still bit weird to me.. At least that's how it always worked for me.. I had tons of setups with RME interfaces. Anyway, it's good, it's working for you.
I got it wrong, I though you're referring to stuttering of the Nucleus during playback. Like some glitches in fader movements for automation passes or so. A bit has changed since I last posted. Nucleus 2 provides a complete set of dedicated and assignable hardware controls that is easily customised to suit individual user preferences, for all major DAW and plug-in parameters.
It also features a USB connection and appears to your host computer as a standard keyboard enabling key command emulation. A standard jack footswitch connection is also included and there is also an SD card slot for Profile storage.
Configuration and mapping of Key commands and DAW Commands is via a remote "SSL Logicitivity" browser, which allows differing control profile sets to be stored and recalled. We could have stopped there but because we can, we chose to endow Nucleus2 with one final killer feature; it includes the SSL Native Essentials Bundle. Console grade processing for your DAW. Get the precision, advanced feature set, and legendary tonal characteristics of SSL in affordable plug-in….
New colours from the masters of analogue: Fusion is the all-analogue 2U stereo outboard processor expertly designed for the modern hybrid studio. We know how to make audio sound amazing. Create professional standard music and audio — at home, in the studio, or on the road.
Find out why musicians have trusted SSL for over 40 years. The ultimate desktop mixer. SiX has a feature set driven by an obsessive desire for total flexibility and to encompass every creative eventuality. Help Centre. Media Careers Events. Our History Legal. DAW Control.
0コメント