Moog Music Forum

jocks13 wrote:2. mod.wheel controls filter cutoff instead of filter mod.depth.

This is the same thing as:

MOD SOURCE = FILTER EG
FILTER SUSTAIN = 100%
FILTER AMT = 100%

Now your mod wheel controls filter cutoff.

T

S+H is basically a random LFO yeah? What I like to do to is: LFO SOURCE - S+H LFO RATE - 0% (with LFO-speed set to low or mid range) Under the hood set LFO to re-trigger every note Now with your mod-wheel up, you can choose where you want a bit of randomness by turning up your PITCH, FILTER or WAVE ...

try this: make as sure as you can that Reason is sending MIDI clock. Then do a simple test track where you are playing a single long MIDI note, and generating a slow ramp automation for CC3 (LFO Rate). Like, ramp up from 50% to 100% (er, MIDI value 64 to 127) over four bars, or eight bars. Set up a...

I don't get it. I swear I've at one point had midi-sync working, but now I'm doubting myself. Updated to 1.2.9, still can't get my midi to sync. Host is Reason 7. Midi-over-USB only. Sequencer is running. I've got Reason's midi-clock-sync setup to output to the Sub Phatty. I've turned on SubP midi-c...

Amos wrote: are you reporting no MIDI sync when using the latest v1.3.1?

No. I'm still way back on an older firmware.

I didn't want to start reporting issues that have probably already been fixed - just didn't know what the latest stable version was. Thanks for the heads up!!

T

I had LFO-midi-sync working before, now can't get my sub to midi-sync - haven't changed my setup at all. I figure my first step should be updating my firmware to see if it resolves the issue. I updated the firmware when I first received the unit to 1_1_8. What is the newest, most stable firmware I s...

marty wrote: Anybody else experienced this?

marty

Yes. I've found that the LFO at the tip-top of it's range (with LFO key-tracking at max) goes to zero.

T

You can't completely erase the market for the slim-phatty by making the sub-phatty do EVERYTHING that the more expensive synth does.

I'm afraid I wasn't clear. At a certain point the LFO's rate (via keyboard tracking) seems to max out and stop. This seems to be about middle-C (+1 octave) when keyboard-tracking is set to max (high-C). I don't think this is what people are looking for. I'm a little worried I'm still not being clear...

If you set LFO KB-tracking to the max, it appears to me like you indeed-CAN max out the LFO's rate.

But I'm no expert, so I'll let someone with more experience get the final word on this.

T

My Sub-Phatty just got here today. My first Moog! And my first piece of hardware.

I can honestly say that Marc's videos really sealed the deal for me.

I couldn't be more happy!

Thank you Marc Doty for your great series of videos.

T