Moog Music Forum

Hi Tobias, Sub 37 should not make Cubase stumble at all... especially if Cubase is the master clock and Sub 37 isn't sending any clock back to Cubase... make sure ECHO DIN / ECHO USB settings are both OFF on the Sub 37 MIDI settings... although it sounds like you did this already. Does it make any d...

jigdagod wrote:I was able to see the beta forum, but no longer have access to it. Any reason why that would happen?

it was accidentally made public for a few hours, but it isn't supposed to be. email gil and ask to be added to the beta forum if you haven't; he'll need your forum user name.

Far from abandoned! In fact there's already firmware with poly chain enabled; we're only waiting to begin beta-testing it until Sub 37 Editor is released... which is behind schedule, we anticipated it would be out by now. This has a knock-on effect of delaying action on the Sub Phatty, because the s...

contact [email protected] for all your beta-requesting needs. I have been trying to keep up but it's difficult... at least six people have emailed me just today and I haven't replied yet because I'm waiting for a new beta build (which should be ready later today).

Cheers,

Amos

Just tried to install the 3.3 Midi driver in Windows 10 x64. But Windows always prefers the standart microsoft driver. When I try to select it manually it don´t work (marked with a yellow sign n the device manager). HI moonbooter, if you double-click the driver in device manager, is there any error...

you could try bunging some audio into the gate input. The external audio input isn't digitally scanned so it can't trigger anything.

Please post this sort of thing in the Beta Tester forum; otherwise you'll just confuse and frighten people.

The numbers/symbols for preset names thing should be fixed in Editor beta 0.9.30; I think there's some small holdup in releasing it, but it or 0.9.31 will be along soon.

If I'm tweaking via the software editor, then ableton records those changes as being from the editor with all the nice parameter names, and on playback it gets sent to the editor and shows knob movements. The editor sends the changes to the synth, not ableton. If I'm recording changes from the hard...

that's normal if it's in MIDI learn mode - press all four buttons to put it in this mode; send any MIDI message to learn the channel of that MIDI message (sets Minitaur MIDI channel to whatever channel the MIDI message was sent on) and take it out of this mode. Or cycle power and it should reboot in...

hold down the KNOB SHIFT button, and while holding it press the Output MUTE button. This should create a random preset, if you're using recent Sub 37 firmware.

I don't always check this forum or my PMs here, so your best bet is to email me directly.

Cheers,

Amos

CC 64 Sustain response is fixed in the newest beta firmware (which Paul is using) but has a bug in the current production firmware (1.1.0 I think). This explains the different results. Sorry for the bug! I'll send you a link to new firmware.

So for now, when in step edit mode the bright LED that indicates the currently-playing step is always a fixed brightness even when you turn down the overall panel LED brightness. I tried it the other way first and it didn't work well The blinking arp/seq rate led remains bright regardless of the se...

The arpegiator led doesn't dim. Is this normal? Yep, same on mine This is indeed normal, at least for now. The deal is, the sequencer in step-edit mode needs at least two LED brightness levels, maybe three. There's "step is active but not playing" (dim) and "step is playing" (br...

1) sounds like a MIDI loop - if you are sending MIDI out from the synth and that same MIDI is being sent back to your synth from a DAW, it might be causing this. You can turn off Local Control on the synth or turn off the monitoring in your DAW that is sending the synth's own MIDI output back to its...