Nucleus Logic

[Benita Vandervoort]

Thesite is secure.

The ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Signaling from synapse to nucleus is vital for activity-dependent control of neuronal gene expression and represents a sophisticated form of neural computation. The nature of specific signal initiators, nuclear translocators and effectors has become increasingly clear, and supports the idea that the nucleus is able to make sense of a surprising amount of fast synaptic information through intricate biochemical mechanisms. Information transfer to the nucleus can be conveyed by physical translocation of messengers at various stages within the multiple signal transduction cascades that are set in motion by a Ca(2+) rise near the surface membrane. The key role of synapse-to-nucleus signaling in circadian rhythms, long-term memory, and neuronal survival sheds light on the logical underpinning of these signaling mechanisms.

I recently bought a used Nucleus 2 knowing it was discontinued last summer, but it still seems like the best choice for the way I'll be working - live acoustic guitar and vocal basics, additional instruments in ones and twos, and drum machine tracks in most cases - primarily building arrangements and likely finished recordings.

I'm looking for resources to help me get on top of that. I've searched here but most (or all) of those posts are, understandably several years old and about specific issues. It took 3 weeks to get SSL to clear a Support login problem I had, which just happened yesterday, so I have not been into their stuff, but I will certainly look.

Thanks David, but I have a newer version of that. I used it and SSL support to configure Nucleus 2 and Dante routing to the extent it is now, which is fine for the multi-track mix. But I found even that much of the Users Guide to be vague and confusing, and I'm perfectly willing to admit that getting farther into it without clarity is intimidating, since guessing my way thru that process can result in a mistake that takes days to recover from, which has already once.

It took a while cause I'm still so ignorant of Mac world, but I deleted the file and reinstalled Nucleus 2, which is now configured horizontally, but is not yet loading to the controller. That is not entirely surprising, I've been dealing with a number of issues recently, and did it load a mix sometime overnight after I'd given up on it for the evening. That is not typical, it's usually instantaneous, but nothing appears to be wrong in its configuration so I suspect it will appear when it's ready.

A further update... The controller is still not loading, and there is now a Mackie listed along with the Nucleus 2 in Preferences -> Control Surfaces -> MIDI Controllers. That may be correct but was not there before when it was working.

It took a while cause I'm still so ignorant of Mac world, but I deleted the file and reinstalled Nucleus 2, which is now configured horizontally, but is not yet loading to the controller.

After uninstalling the Nucleus form Logic and your Mac, did you clear all its mapping entries in the Controller Assignment window? That is highly recommended to avoid double conflicting entries upon re-installation. There is a specific procedure to do so correctly.

The controller is still not loading, and there is now a Mackie listed along with the Nucleus 2 in Preferences -> Control Surfaces -> MIDI Controllers. That may be correct but was not there before when it was working.

The Controller assignment windows is where the controllers' mappings are stored. It gets automatically populated when installing a supported controller. The Mackie's (aka MCU, C4) and those using the same protocol are supported MIDI controllers which provide such mapping presets.

I'd intended to quote the file name I'd deleted (com.apple.logic.pro.cs) but between that message and the one I was replying to from des99, almost all of our previous messages were moved to another forum and I was running out of time then and could not remember. Now you have that.

I did not re-install Nucleus 2 Remote (its software) since I didn't know I should. After deleting the file above, I re-entered the Nucleus L/R devices and their ipMIDI I/O ports. And yes, BEFORE that I had learned that the R/2 device could be moved, but that did not cause it to start working, so I proceeded to delete that file.

After re-loading the devices and re-entering their ipMIDI ports I took everything down, rebooted the Mac, and brought it back up to find the Control Surface devices and configuration appeared as expected now.

Another reason why I did not reload Nucleus 2 Remote is because it establishes the fixed Dante IP for the software and the DHCP IP for the controller. But as far as I've seen and been told, that does not affect Logic Pro as long as it knows the correct devices, with the correct ipMIDI ports, in the correct horizontal L/R positions. And it has been connecting to the Nucleus controller and appearing correctly and instantaneously in Dante controller the last couple of days, which it had not been doing for the last week or so.

Yes, we definitely need to have all the discussion on a subject to stay within one single thread. We're here to help you first, and that's great if you can keep track of two different threads. However it's not necessarily easy for us to keep track of two threads for a subject. For example in one thread you may have tested something and reported the resulted, but if we're reading the other, we don't know that. So that's inefficient.

But really where it's most important to me, is that after we've helped you, the thread stays forever in this huge database of Q&A that Logic Pro Help really is, that people will search when they come to this site, or get a link as a result when they search Google. And if they get only half the information we've shared, then they're missing out. So we're here also to help everybody else with the same problem that is reading this now or that will stumble upon this in the future. I'm always mindful of that.

Since my last message I deleted and reinstalled Nucleus 2 Remote, and along with that, Control Surfaces -> Setup is coming up configured correctly, and the file I deleted com.apple.logic.pro.cs is back again, I assume because the Setup was done again.

Understanding that the Nucleus communicates with your Mac via ip, I suspect there might be a problem with the ip setting/attribution. Sometimes the powering-up (turning On) order of the connected devices could affect such ip configuration.

That's a legitimate question. I went thru that with SSL support last week to get it right, but I think the quickest way to answer your question would be with a few screen shots, and then you can ask about anything that hasn't covered.

The address in the Nucleus 2 Remote must be a fixed address, but the Mac and the sound card in the Controller are DHCP. But I will turn off WiFi after I send this message, which is recommended, to see if that helps. I'm sure I've had it running with that on before, but stand by...

To address the start-up issue, what seems to work best is to bring the controller up first, and then the Remote software. Sometimes I have to "Find" the controller, which means selecting the correct 1 of 2 addresses that are offered, but this time they connected immediately, all by themselves.

After that I can check Dante controller, because (almost) everything else is dependent on that, and again this time, that locked in immediately, including the errant latency lights shown in the previous screen capture.

One other thing to mention - again - is that the L/R halves of the Controller selected at Control Surfaces -> Setup must be placed next to each other horizontally - NOT vertically - even if they land there to start off with as they did in my case.

I would like to constrain the ring region within the boundaries of the cytoplasm. I am able to segment the cytoplasm but unsure how to crop the ring region/expand the nucleus region within the cytoplasm boundaries.

Note I am already able to calculate a nucleus to whole cytoplasm ratio but have found better readings in other image analysis software in using the ring region, due to large differences in cytoplasm shape between and within lines.

Not a Nucleus user myself, but sorry to report, it's a known issue, (with Logic only). Seems to stem from the way Logic deals with MCU &/or Dante. It was supposedly fixed in Logic 10.2.1, so might be worth upgrading if you haven't already, (although some users are still experiencing the issue in later versions of Logic).

yes, that really seems to be a pure apple problem. as already mentioned, under cubase pro and pro tools the peak meter indicator works great. I also have an original mackie hui and even that does not work properly under logic. just pitiful what apple has screwed up here !! ?

I know this doesnt help you! Just saying it seems like having a DAW controller is just something else to wrong, they work for a while, then the latest DAW version isnt compatible, or the firmware update doesnt work etc etc, nightmare.

not only with the ssl nucleus is that the same with the faders. I have an original mackie hui here in the studio and also there fidget the faders, the meters freeze and some buttons like the wheel / scrub do not work. everything only under logic !! Apple sabotages these standard protocols such as HUI and MCU in favor of their logic remote! it's a shame what apple aud logic did !!!!

Nuclei is a fast, efficient, and extensible vulnerability scanner. It can scan thousands of hosts in just a few minutes.

The Nuclei engine uses YAML-based templates to define the steps required to detect a vulnerability.

3a8082e126