Why does my synth or arpeggiator not follow Nome II’s tempo?

Connect Nome II’s OUT 1 or OUT 2 to the instrument’s MIDI IN and configure the instrument to follow external MIDI clock. A setting that merely enables MIDI notes is not necessarily its clock-source setting. Check the receiving instrument’s manual for the exact option. Arpeggiators usually require you to play a note; following the tempo does not mean they start from Nome II’s Play button. Sequencers and drum machines must also support and accept MIDI Start/Stop to follow transport.

See Nome II Quick Start: all setup answers and Buttons & Connectors. A MiniNova setup discussion illustrates the distinction between MIDI input and clock-source settings.

Why is my sequencer running at a different musical rate from the click?

First distinguish the tempo from the number of notes or steps played on each beat. Check the receiving sequencer’s clock division and step length, and Nome II’s SIG time signature and click settings. For analog clock, match the pulses per quarter note expected by the receiving device using An.1 or An.2. For MIDI OUT 2, also check Mi.2, which can divide its MIDI clock rate. Do not assume one sequencer step must occur on every audible metronome click.

See Settings. A Moog Messenger discussion shows why clock rate, cable type and sequencer divisions must be checked separately.

Can I connect a MIDI output to an analog clock input with an adapter?

A passive cable does not convert MIDI messages into analog clock pulses. Use OUT 1/OUT 2 for MIDI inputs and ANLG for compatible analog clock inputs. The ANLG port provides two 5V channels on a 3.5 mm TRS connector; use a TRS-to-two-TS splitter when separate clock and run/reset connections are required, and configure An.1 and An.2 for the receiver. Check its required signal and voltage levels.

For DIN Sync / Sync24, set AnL to din and use the dedicated DIN Sync adapter. DIN Sync uses both ANLG channels and is not interchangeable with TRS-MIDI wiring. See Nome II Quick Start: all setup answers and Settings.

The DAW controls the tempo, but why do my drum machines not start?

Tempo synchronization and starting a sequencer are separate functions. Configure A.PL (Auto-Play) to start the desired MIDI output when external synchronization starts: bot for both outputs, Mi.1 for OUT 1, or Mi.2 for OUT 2. Also check that the receiving machine accepts MIDI Start/Stop. This applies when Nome II follows U-SYNC or the supported audio/analog pulse modes.

See Automatically start and stop sequencers. For a concrete DAW/hardware setup question, see the Ableton hardware discussion.

Can Nome II control my DAW’s tempo and transport while using U-SYNC?

U-SYNC synchronizes Nome II to the DAW. Bidirectional control is an additional integration that lets Nome II send tempo and transport commands back to supported DAWs; it is not the same as making the DAW follow incoming MIDI clock. Follow the U-SYNC manual’s installation and control-integration instructions for your exact DAW and plugin version. The setup reference lists the supported bidirectional DAWs for this documented release. Do not apply an older forum statement about missing DAW control to a newer release without checking its documentation.

See The DAW Control and Nome II Quick Start: all setup answers. This distinction occurs in Logic workflow questions and Logic transport questions.

Should I also enable the Nome II Clock USB-MIDI input when using U-SYNC?

No. The Nome II Clock USB-MIDI input is the separate route for software that follows MIDI clock. The manual explicitly says not to use it with U-SYNC. Choose one synchronization route and configure the U-SYNC DAW-control integration separately where supported. Ordinary MIDI note forwarding through Nome II is a different function.

See The Clock interface, The DAW Control and MIDI Forwarding interfaces Out 1&2.

Does U-SYNC also correct the timing of MIDI notes sent by my DAW?

For U-SYNC 1.4.1, do not assume that clock synchronization also schedules your DAW’s individual MIDI notes. Nome II can merge and forward MIDI data from its USB output interfaces to its physical MIDI outputs, but this is distinct from synchronizing a hardware sequencer’s clock. When diagnosing a late recording, identify whether notes come from a clocked hardware sequencer or from the DAW, then check the DAW’s routing and recording/monitoring latency settings for that path.

See MIDI Forwarding interfaces Out 1&2 and the DAW-sequenced notes discussion. Do not treat a planned feature mentioned in an old thread as a released capability.

Can I distribute Nome II’s clock through a USB-MIDI host or MIDI router?

For timing-sensitive hardware, use Nome II’s physical MIDI outputs where possible. A USB-MIDI host or router introduces another part of the timing path; its behavior must be assessed in the actual setup. Connecting Nome II by USB for U-SYNC does not require you to distribute clock to every instrument over USB. You can use U-SYNC between computer and Nome II, and physical MIDI or ANLG from Nome II to the instruments.

See Nome II Quick Start: all setup answers and the support response in the CME H12MIDI Pro discussion.

Why does Play wait for the next bar instead of starting immediately?

In standalone operation, the default behavior starts playback on the next bar of Nome II’s already-running internal clock. rES (Reset mode) changes the reset/start behavior; use the settings table to choose the immediate-start behavior. Cnt (count-off) and PL.1/PL.2 button functions are separate settings, so check those as well when a button behaves differently from expected.

See Settings and Nome II Quick Start: all setup answers. Start delay and count-in are recurring topics in the Nome questions forum.

Will a looper or a live drummer stay synchronized automatically?

A looper must support external clock, and its response to clock and transport is specific to that model. If it does not follow satisfactorily, the setup reference explains alternatives: send dedicated regular pulses from the looper to Nome II, or use count-off, Smart Tap Tempo and time nudging to keep time manually.

Nome II does not detect the beat in arbitrary live audio. For a drummer who does not follow a click, use count-off and Smart Tap Tempo; these require taps from a person or an appropriate control source. Firmware 5.5 includes Smart Tap Tempo, so older descriptions of the original tap-tempo behavior are not the current instructions.

See Count-off: count done by the musician, Catch up live timing with Smart Tap Tempo and Match external gear’s timing with Time Nudging. Related discussions include looper setup and tap tempo.

Can Nome II follow a DJ set, Ableton Link or Pro DJ Link directly?

This documented setup has no native direct DJ synchronization. Nome II can follow regular sharp pulses sent to INPUT when inP matches their rate. An ordinary song sent to INPUT is not a substitute for that pulse signal. The Quick Start mentions a planned expansion for Link integration; that announcement is not an instruction to use a built-in Link feature.

See Sync to an analog clock or an audio signal and Nome II Quick Start: all setup answers. DJ sync and Ableton Link are also raised in the Nome questions forum.

Can I use Nome II on Windows, and why are USB-MIDI ports missing after an update?

Nome II’s USB-MIDI functions and the availability of the U-SYNC plugin are separate. For the release covered here, U-SYNC is documented for Mac; Windows users can use the 24P audio-sync workflow instead. The USB-MIDI interfaces may have generic names on Windows. If interfaces are missing after a firmware update, follow the manual’s instructions to remove the previously registered device setup in Windows Device Manager or macOS Audio MIDI Setup, then disconnect and reconnect Nome II.

See USB communication & commands, Update the Nome Firmware and Syncing to your DAW using the 24P mode (Windows).