Setup in Logic

The Moog Forum Moog Beta Forum
1

Hi,

I’ve previously been playing with this in standalone, which appears to be quite stable. It’s been a pleasure to work with so congratulations to the team so far.

I’ve just tested it in Logic X 10.1.1 this morning and it’s left me scratching my head…

There appears to be an issue with changing presets. This may have been flagged previously but I haven’t seen anything, so apologies if I’m repeating something.

Just to check I’m not doing anything foolish… I’ve set it up with an instrument track with the editor as an effect (can’t see any other way of loading it). The synth is played through an external MIDI track set to MIDI channel 1. Local control is OFF. I’ve also set PGM CHANGE to receive only, as I’d hoped it may solve any MIDI routing issues. Image attached.

loading hardware presets from either the editor or the synth…

the MIDI LED flashes on/off red.. on the synth, and continues to do so.

A note appears to be latched. Playing the keyboard triggers new notes, but the drone remains after key off. I need to perform a full midi reset from logic for ‘all notes off’ to stop the sound, but the red LED continues to flash.

Setting the instrument track to record for a couple of second stops the MIDI LED flashing, but a full MIDI reset is needed from Logic to stop the drone. By doing this, however, Logic will record the value of the current preset, and changing/loading new presets again causes the problem to re-occur as the instrument track ‘records’ the current preset value. (check under ‘additional info’ in the Event list). So using this technique only makes matters worse.

In other words, he behaviour is different depending on which Logic channel is selected (the software instrument or the external MIDI), which is what leads me to believe it could be a routing problem. Perhaps there is something we need to add to the environment?

This is not such an issue when loading presets from the centre panel of the librarian or from the preset list on the main page (i.e. loading into the current Bank/Preset slot), but does appear to occur after loading seq patches which tend to ‘latch’ although it could be just as common for other types of patches - I’ve not done exhaustive testing… the issue with the preset list ‘moving’ to random positions after loading makes this too time consuming. A full MIDI reset in this case stops the MIDI LED from flashing (without the need to record on the instrument track)

I may well be setting it up incorrectly and could have a MIDI loop, but it’s not obvious.. I’ve looked again at the standalone and the issues are only when using as an AU within Logic.

FYI the MIDI input is always active on the editor, no matter what channel is active in Logic. I’m assuming this is as expected.

I’m using OSX 10.9.5
The Sub37 is USB MIDI direct without a hub.

Cheers.
Screen Shot 2016-01-06 at 11.38.43.png

2

Thanks for the detailed report.

This is a know issue which is set as high priority. The problem seems to be that midi loop is created when the synth is set as both Midi In and Out on a DAW’s midi channel and the channel’s midi monitoring is active. Selecting a preset on the hardware triggers a program change message which is then sent back as a midi input message to the synth, causing the patch to be reselcted and sending the program change message over as midi out, and so on. Does this case match your scenario ?

3

Hi,

Following your suggestion I’ve had another look using MIDI monitor to check what’s being sent where…

It appears that I had SMPTE generated somewhere, which may have been affecting MIDI clock messages, which could be why the seq programs were particularly troublesome.

I noticed my Midiman Midisport was writing SMPTE so turned SMPTE OFF on the unit which seems to have resolved the problem (I haven’t used SMPTE since to golden days of tape! so had no idea it was sending). Attempting to recreate the problem I turned it back on and received a message in Logic re MTC FPS being inconsistent (23.976 or 24 FPS with Logic set at 25). It was actually sending at 24.

Anyway.. this seems to have sorted the problem. I’ve tried to recreate it, but no problems as of yet.

I have, however, discovered some unusual responses when selecting the presets from the top panel..

If the right hand panel is chosen in the librarian, the presets can be selected by the top panel as expected (except for the ‘up’ button moving down the list and vice versa, which is counter intuitive).

If the middle panel is selected so the preset is loaded into the current slot then clicking on the up/down buttons or choosing from the drop down list doesn’t work properly… The first 10 presets can be ‘clicked through’ via the drop-down list or the buttons, but continuing through the list does not work, and the remaining presets can not be loaded via the to panel.

The list is alphabetical in the centre panel and starts with numbers then A-Z. In the box at the top the names with ‘spaces’ appear first e.g. Dorian Electra, Percuss Dub, Analogue Native Dance (all os which start with at least one space). The spaces are ignored in the panel in the centre, which is confusing, as the list appears to be different.

So, to clarify which are the first 10 that can be selected: those with spaces followed by patches with numbers. The last one that can be loaded is ‘5th in Line’

Hope this helps.

4

I Spoke too soon..

I was using it with Local on, playing the instrument track in Logic. All worked fine.

When then changing to the external midi track in Logic I experienced the issues again. The midi monitor shows that the preset is continually changing (hence the flashing MIDI LED).

changing the PGM Change send/receive parameters does not seem to help much. Even when turning both off, the synth latches.

5

Hi,

Navigating the preset list on the middle pane does have some issues, which are now reported.

Thanks.

6

I wonder if this is related to the problems I’m having in Logic. If I switch to a “sequence” preset like “Bomb Bass Tick”, triggering the Sub 37 from Logic just plays 1 repeating note instead of the sequence. Then it is stuck holding a note down no matter what preset I switch to. I have to turn the Sub 37 off and on to clear.

7

this matter needs some work, but it’s worth mentioning that you don’t need to cycle the power to resolve a stuck note. Just press and hold both the KB Octave Up and Down buttons at the same time, for about a second, and it will clear stuck notes.

8

Thanks - the “clear stuck notes” shortcut is a huge help!