Moog Music Forum

When I set a slow attack and play a note if I play in legato the next note I press as a fast attack
Is this normal? The envelope should reset and all the notes should have the same (slow) attack?!

barryfell wrote:

nofuturenocore wrote:Hello,

I notice than when I Draw automation in Ableton Live 9 with Mouse ( I prefer to do it like this, more precise for me ) this doesn't work correctly with Sub Phatty.
It only change value when it read a point but the curve between those points are ignored ? Is this something normal with Analog gear or a bug ?

Thanks.

I'm not experiencing this issue. (Live 9 x64, Win8 x64, Firmware 1.2.7)

Hello, I have Ableton Live 9 Suite x32, Win7 x64, Firmware 1.2.7. Still have this annoying problem... SubPhatty only detect the 2 "Point" , the Lines are ignored.



Anobody having the same problem ?

nofuturenocore wrote:

barryfell wrote:

nofuturenocore wrote:Hello,

I notice than when I Draw automation in Ableton Live 9 with Mouse ( I prefer to do it like this, more precise for me ) this doesn't work correctly with Sub Phatty.
It only change value when it read a point but the curve between those points are ignored ? Is this something normal with Analog gear or a bug ?

Thanks.

I'm not experiencing this issue. (Live 9 x64, Win8 x64, Firmware 1.2.7)

Hello, I have Ableton Live 9 Suite x32, Win7 x64, Firmware 1.2.7. Still have this annoying problem... SubPhatty only detect the 2 "Point" , the Lines are ignored.



Anobody having the same problem ?

So are you saying it's jumping from one value to the next rather than say, rising, as per your screenshot?

Yes exactly... I think I changed all the Shift option to try if it was a problem somewhere ( using different channel for send and receive midi, disabling midi merge etc etc...) But no way to make this work... But when I record the automation with the SubPhatty or when I make a "Draw Mode" Automation this work correctly ...

nofuturenocore wrote:Yes exactly... I think I changed all the Shift option to try if it was a problem somewhere ( using different channel for send and receive midi, disabling midi merge etc etc...) But no way to make this work... But when I record the automation with the SubPhatty or when I make a "Draw Mode" Automation this work correctly ...

Very strange. I'd be inclined to think that the recording of automation from the SubP or drawing it in is doing the same thing, i.e jumping between values, but doing it very quickly and gradually, so you don't notice the stepping.

Maybe try reflashing the firmware or waiting until the next firmware release which I believe isn't far off?

Yep I'm gonna do the flash again and let you know if this change anything but from what I remember this was already not working before I made the 1.2.7 Update. Thanks for the help, good to know that this problem seems only to happen with me.

No way to make it work... Draw Mode and Automation coming from the Moog are still working correctly but this way is not working, The Subphatty don't read anything in the automation or make weird changes on some "Point" I set ....

hey, here's some new firmware.

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

changes in v1.2.9:

- fixed EG Reset / Multi-Trigger modes (I think... listen carefully)
- improved LFO MIDI Sync
- Keyboard Octave buttons send MIDI again
- VCO 1 Octave no longer affects Filter KB Tracking
- Amp EG Attack knob always adjusts Delay parameter while in Shift mode

Let me know if you continue to experience any unhappy behaviors in this version.

nofuturenocore: this thing you're describing with the automation is almost certainly a problem with your Ableton Live setup. Look at the MIDI LED on the sub phatty while you are sending a "ramp" of automation... if the light is not on, the Sub Phatty is not receiving MIDI CC data. In that case the problem is with the sender (ableton) not with the Sub Phatty. I tried doing automation just like in your example and it worked perfectly for me. the MIDI LED lights up solid the whole time the ramp automation is happening. I notice you have "remote" selected in the Live MIDI preferences... try turning this off ("remote" isn't the word in your language; it's the right-most item of the three on/off MIDI preferences in Live MIDI setup)... I don't know if that will help... but having it enabled isn't necessary.

Amos wrote:
- fixed EG Reset / Multi-Trigger modes (I think... listen carefully)

Let me know if you continue to experience any unhappy behaviors in this version.

Works for me!
Thanks.

Ableton Live v8.4.1 x64
OSX 10.8.4
SubP Firmware 1.2.9
Editor version 0.9.4

Since updating to 1.2.9 midi connection has been lost twice both in Live/vst editor & the standalone editor. when this happens the editor preferences says the hardware isn't connected. When local control is set to on via the panel it can be played manually but all midi connection with the computer is lost until the SubP is restarted.

Ableton Live v8.4.1 x64
OSX 10.8.4
SubP Firmware 1.2.9
Editor version 0.9.4
Connected via USB

SubP is loosing midi connection consistently now, whether using the editor or not. Tweaking any knob can do it, its happened while tweaking the cutoff, envelopes, Mod wave AMT etc, When playing midi from Abe Live. It doesn't happen straight away but when it does there's a stuck note, hitting panic stops it but midi connection is lost. Midi connection sometimes lost while sitting idle too. This is happening with local set to on & off.

that doesn't make any sense; nothing related to MIDI is changed at all.
Not that I'm doubting you, mind you -- just, it makes no sense.

1) try re-loading the same firmware, something may have gone amiss
2) try reverting to older firmware, see if the problem goes away, then put the new firmware back and see if the same problem resumes.

My unit on which this code was written has been on all night and still has MIDI communication.. I'll keep an eye on this.
Anyone else having the same issue?

Amos wrote:that doesn't make any sense; nothing related to MIDI is changed at all.
Not that I'm doubting you, mind you -- just, it makes no sense.

1) try re-loading the same firmware, something may have gone amiss
2) try reverting to older firmware, see if the problem goes away, then put the new firmware back and see if the same problem resumes.

My unit on which this code was written has been on all night and still has MIDI communication.. I'll keep an eye on this.
Anyone else having the same issue?

Well it seems to be making a liar out of me now, I've had it running a few hours now without a hitch. Maybe something was running in the background causing problems, if it happens again I'll let you know.

Amos wrote:
nofuturenocore: this thing you're describing with the automation is almost certainly a problem with your Ableton Live setup. Look at the MIDI LED on the sub phatty while you are sending a "ramp" of automation... if the light is not on, the Sub Phatty is not receiving MIDI CC data. In that case the problem is with the sender (ableton) not with the Sub Phatty. I tried doing automation just like in your example and it worked perfectly for me. the MIDI LED lights up solid the whole time the ramp automation is happening. I notice you have "remote" selected in the Live MIDI preferences... try turning this off ("remote" isn't the word in your language; it's the right-most item of the three on/off MIDI preferences in Live MIDI setup)... I don't know if that will help... but having it enabled isn't necessary.

The Takeover mode doesn't change anything.

So this is ... weird... The problem is that in 48000 Bitrate the SubPhatty is not accepting the Midi Data from "ramp" ( The Light in Ableton is always active but never on the SubPhatty) when I changed to 96000 then it worked... I don't see any link between Midi Data and audio Bitrate ... If someone understand what happen I'm interest.

Thanks Amos.

Are you using standard DIN or USB? Maybe it's a problem with your audio interface?