unwanted midi to controlsurface

Here is an update from SSL that i just found.. They will be fixing the problem according to this....

http://solid-state-logic-en.custhelp.com/app/answers/detail/a_id/3707/~/nucleus- and-logic-x-10.2

Why is Nucleus behaving erratically with Logic X 10.2?

We have received a number of reports about random, erratic behaviour of Nucleus after a Logic X upgrade to v10.2. The symptoms include flashing lights + fader movements which render the console unusable.

We are currently investigating this issue and aim to have a solution as soon as possible. In the meantime we suggest not upgrading to Logic X 10.2 until this FAQ states that the issue is solved.

It may also affect other SSL controllers such as Matrix, AWS and Duality.

So until SSL release a fix... roll back, using your backups, to 10.1.1

No backups? Lesson learned I hope!

There's a few discussions across various forums about this issue.

Apparently if you still have 10.1 (or even Logic 9) installed, opening that 1st 'solves' the issue....possibly something to do with ipMIDI startup - seems that previous versions of Logic set it up correctly but 10.2 doesn't.

Proper butt pain (especially as I don't have previous versions of Logic installed as 10.2 installed over the top of them).

I've found that it also causes a regular/repeating 'durge' of MIDI notes to trigger on some of my hardware synths too.

Apparently if you still have 10.1 (or even Logic 9) installed, opening that 1st 'solves' the issue....possibly something to do with ipMIDI startup - seems that previous versions of Logic set it up correctly but 10.2 doesn't.

From what i understand, that is actually incorrect...

What has really happened is SSL used a 'workaround' instead of the correct way.... as per the Dev Guidelines... to get their system to work.. This worked with previous versions of LPX

However in 10.2 the 'workaround' no longer works as the Logic Devs updated some routines... Had SSL followed the correct procedures, there would be no issue but because they used a non standard 'workaround' it has now broken.... which is why they have already announced they need to fix it themselves...

In most (Though not all) cases.. it is these sorts of reasons why certain 3rd party hardware/software fails after an update.... because programmers either fail to follow the correct methods or they use workarounds to "improve' the performance of their gear in one way or another... and then it gets tripped up when an official routine or lib is changed that would work fine with properly designed/written hardware/software/drivers but fails when some 'backdoor' is used by 3rd party devs.. in a routine/lib.. gets altered or removed...

Again.. I did say in most and not all cases as there have been a few examples where its an error by the Logic Devs that has caused the problem.. but in most cases.. it is typically an error or poor design... bad implementation or even an attempt to do something that Logic isn't designed to do... by the 3rd party hardware/software devs that causes these kinds of issues.

I've found that it also causes a regular/repeating 'durge' of MIDI notes to trigger on some of my hardware synths too.

Through which midi interface?

I cannot replicate that here using various different Motu and iConnect interfaces to external hardware synths...

Thanks for the note and the clarification, makes much more sense :-)

Poor SSL are having a nightmare with Nucleus compatibility lately (audio interface and now everything else!)

In terms of the additional conment re MIDI durge...

The MIDI notes are coming from a Yamaha baby grand piano which is connected to Logic via a pair of MOTU midi timepiece AVs. They time pretty much exactly with the fader movements on the Nucleus (hence the initial thought it was a dodgy midi command being 'looped'...HOWEVER...reading between the lines from your previous note this is probably related to the SSL issue as the MTPs are connected via the USB hub on the Nucleus (as they weren't too happy working directly via usb3, known issue).

Guess we'll just have to wait for SSL to update their s/ware.....in the meantime I've reinstalled 10.1 ho hum

Cheers again for the note, appreciated.

Nick

Hey Nick...

Yes.. the 'durge of notes' sounds like the SSL related issue.... rather than anything else.... based on the reports I've been reading....

Anyhow, hopefully SSL will get their act together and release a stable fix soon.. as it must be quite frustrating for Nucleus, Matrix, AWS and so on owners.....

I'm glad to hear you are apparently one of the small number of people who actually do make backups before upgrading to a new version of an App or OS X.... so you could roll back...

If only more people got this same 'clue'..... 🙂

Regards!

Nigel

Definitely...fingers crossed n all that!

Timemachine means it's a piece of pee just restoring the old Logic App - just need to remember to rename the new one so the restore doesn't wipe over it :-)

Seems to work fine.

Thanks again for the info Nigel. Take it easy squire.

Nick

MIDI over IP / Solid State Logic, Mackie MCU/HUI issue