Sub Phatty beta firmware - final bug roundup

[Amos]

Ah, OK... probably we'll need some changes to the editor also, to get everything working together nicely.

I may need to adjust the way I am converting presets from the old format to the new one, if they are sounding louder... I did not do a lot of testing yet, probably was premature to put this online but I was looking for feedback.

I have invalidated the download link for v1.3.0; sounds like it needs more work. Thanks!

[nofuturenocore]

Hello Amos,

I have received my midi interface today and I can't stop playing with Max For Live and the Sub Phatty just amazing to have a pure Analog Synth with all the possibilities of Digital Gear.

I just have questions concerning the damages that could be make to the Sub Phatty during this kind of experimentation.
Does each Parameters of the SubP can accept 40 Hz LFO during 3-4 hours of use ? Or it could be dangerous for the Hardware to Map every parameters a this rate using Max For Live's "LFO" + "Multimaps" and "Envelope Follower" ?

[Amos]

Hello Amos,

I have received my midi interface today and I can't stop playing with Max For Live and the Sub Phatty just amazing to have a pure Analog Synth with all the possibilities of Digital Gear.

I just have questions concerning the damages that could be make to the Sub Phatty during this kind of experimentation.
Does each Parameters of the SubP can accept 40 Hz LFO during 3-4 hours of use ? Or it could be dangerous for the Hardware to Map every parameters a this rate using Max For Live's "LFO" + "Multimaps" and "Envelope Follower" ?

there is literally no danger at all. None. Modulate all the things!!

[nofuturenocore]

Hello Amos,

I have received my midi interface today and I can't stop playing with Max For Live and the Sub Phatty just amazing to have a pure Analog Synth with all the possibilities of Digital Gear.

I just have questions concerning the damages that could be make to the Sub Phatty during this kind of experimentation.
Does each Parameters of the SubP can accept 40 Hz LFO during 3-4 hours of use ? Or it could be dangerous for the Hardware to Map every parameters a this rate using Max For Live's "LFO" + "Multimaps" and "Envelope Follower" ?

there is literally no danger at all. None. Modulate all the things!!

<3 Moog

[Amos]

firmware update -- here is v1.3.1. This fixes a small math error in the preset-conversion routine, so the saved oscillator levels in your preset should be the same actual level in this new firmware, even though the level control pots have been re-scaled.

Please check and see if (1) presets still sound correct, and (2) mixer section knobs "feel better" (in terms of getting clean sound below 12:00 or so, and distortion above, and just generally seeming like a useful change or not)

thanks!

http://www.moogconnect.net/downloads/su ... _1_3_1.syx

[twelsch42]

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 should install? I haven't really been experiencing other issues with any sort of regularity.

thanks

[Amos]

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 should install? I haven't really been experiencing other issues with any sort of regularity.

thanks

v1.2.9 is the most recent stable version...
http://forum.moogmusic.com/viewtopic.ph ... 90#p119636

are you reporting no MIDI sync when using the latest v1.3.1?
before changing versions... try doing a "reset global settings" operation and then try MIDI sync again.
Let me know the result, thanks!

(Initialize Globals can be found at the bottom of this hardy chart thing:
http://www.moogconnect.net/downloads/su ... v1_1_4.pdf)

[twelsch42]

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

[twelsch42]

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-clock-sync (tried via under-the-hood and via CC from Reason.)

Reason has no trouble controlling any other features.
CC03 from Reason affects my LFO-rate, it's just never in sync with my sequencer.

Am I being obtuse and missing a step?

Thanks
T

[Amos]

Reason has no trouble controlling any other features.
CC03 from Reason affects my LFO-rate, it's just never in sync with my sequencer.

this is a little tricky to diagnose with Reason 7, do you have anything else that can send MIDI clock?

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 preset where there's some audible LFO action, and hit play.

one of two things will happen... either the LFO rate will increase smoothly and continuously, with no audible steps... or the LFO rate will step from one rate to another to another rate. The second case means there's some LFO clock sync happening. The first case means there's not.

Now, it's possible that in BOTH cases, the LFO might not actually line up with the downbeat of your sequencer. If the LFO rate is stepping between distinct different LFO speeds when you automate, then Reason is sending MIDI clock.. but when I was beta-testing Reason 7 I found a serious bug that relates to clock sync... basically, Reason sends out MIDI clock all the time, but when you hit Play in the sequencer it doesn't "re-sync" the clock messages to the downbeat... so the MIDI clock is running at the same rate as Reason's sequencer, but the phase relationship between the MIDI clocks and the downbeat is totally random, it's different every time you hit play. Made it totally impossible for me to sync up my hardware drum machine with Reason as the master clock, because the beats never lined up tightly except by a random miracle of hitting Play at exactly the perfect moment. Kind of killed the vibe for me, I hope they fix this soon.

[Paranoiak]

Just a simple question, is there a way to know the current firmware of the synth ?

[nofuturenocore]

Just a simple question, is there a way to know the current firmware of the synth ?

Hello,

You just have to open the Editor Preference and it will show the current firmware version of the SubP

[twelsch42]

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 preset where there's some audible LFO action, and hit play.

one of two things will happen... either the LFO rate will increase smoothly and continuously, with no audible steps... or the LFO rate will step from one rate to another to another rate. The second case means there's some LFO clock sync happening. The first case means there's not.

No audible steps. The waveform in the sequencer shows a smooth increase and never lines up with the sequencer-grid.

EDIT: I was being obtuse. I forgot a step in Reason where not only do you have to specify midi-clock-sync output in the Advanced pane of the preferences window. But you ALSO have to go to Options->Sync and select 'Send Midi Clock'

Thanks for your help - everything seems to be working fine.

T

[Amos]

I forgot a step in Reason where not only do you have to specify midi-clock-sync output in the Advanced pane of the preferences window. But you ALSO have to go to Options->Sync and select 'Send Midi Clock'

Thanks for your help - everything seems to be working fine.

Result! Hey that's great that it's working now... maybe the record of your troubles in this thread will help some other wayward Reason users in the future. Cheers!

[ul303]

firmware update -- here is v1.3.1. This fixes a small math error in the preset-conversion routine, so the saved oscillator levels in your preset should be the same actual level in this new firmware, even though the level control pots have been re-scaled.

Please check and see if (1) presets still sound correct, and (2) mixer section knobs "feel better" (in terms of getting clean sound below 12:00 or so, and distortion above, and just generally seeming like a useful change or not)

thanks!

http://www.moogconnect.net/downloads/su ... _1_3_1.syx

It is working with this version (conversion + editor in standalone mode).
IMO it is a better behavior...well it should be this way, right?
Surely this "bug" contributed to the reputation of the Sub Phatty and its gritty sound as reported in the reviews, people asking for softer side of the Sub Phatty, etc.

Amos: What about the sound over 12:00, can you ensure we can still achieve the same sound now between 12:00 to max than before? WOuld be a shame to loose this aspect of the sound of the Sub Phatty that contributes a lot to its character...