I have had my subphatty for a few months now with no issue for the most part, but today I Bought ableton push and need to free up a USB port so I tried for the first time to hook the sub phatty up via midi and/or a USB HUB. After using some combination of these two… My vst and stand alone version of the editor now do not see the Sub Phatty at all…regardless of the wiring. I have restarted,tried new cables,midi ports, used the old setup directly into my macbook pro’s midi port, all to no avail. Please help! 
I am using ableton 9.1 2012 2.6 i7 mbp with mavericks 10.9.2
another odd thing is ableton recognizes the Sub Phatty and if I use an external instrument and send it to the sub phatty via usb… It can produce sound. Its just the VST editor that can’t see the SP
I have now deleted the vst and standalone and tried a clean install with no improvements. If I run the standalone, he will initially tell me that I don’t have the sub phatty plugged in, but then when I change midi in to sub phatty then he can see it and all is well but vst and au still no dice. I really would love some help with this especially due to the nature of how my studio runs I need the sub phatty to use midi out and also automation neither of which are possible currently. Also being that the vst editor is the only convenient way to reach many of the features and my workflow (ideally) doesnt include looking at a manual every few minutes for shift commands. Sub 37 where are you!!?
Are you still using a hub? Let me suggest you never do it.
Try using another USB cable too, there are cables with lots of different specs. Unfortunately I don’t know which one is the best suited for the Sub.
I use powered USB hubs for all my gear including the Sub and have not had any problems. But note that a powered hub does not guarantee success, it only increases the chances. The length of the cable could also be an issue. Even though the maximum is supposed to be about 15 feet I usually add and extender for anything over 10 feet to be safe.
For a test you should use a short cable and no hub to verify that everything else is working properly.
I was unable to post for a brief period…My problem here is not a usb hub or usb cable as I have not changed what cable I was using. The problem only began once I tried once to use midi din in conjunction with USB then this problem surfaced. Even after removing the midi cables it is still like this.
Have you tried deleting any Sub Phatty objects in Audio MIDI Setup utility? I would delete any I find and then plug the Sub Phatty back in via USB.
i haven’t tried this… I will first thing tomorrow and will also hook up a second mbp and see if that one is able to do the job… I am a little sad that moog hasn’t responded to my email other than one “expect reply soon” mail…but still love you guys. I know you are probably busy with the sub 37 <3. For future reference, in case I get this guy back working normal… Will hooking up the sp with midi din instead of usb or usb/din help with the problem I was having? (automated filter sweeps in my daw were less sweeps and more filter steps/sweeps)
No it won’t. This is because hardware synths still use the old MIDI protocol, so if your software sends CC#19 you will have only 128 steps. This can be partially solved by sending 14bit MIDI MSB/LSB (CC#19/51), which will have a range of 0-16383. However, I don’t think a software like Ableton Live can do it, maybe Cubase or Logic will.
The workaround is to change the envelope parameters instead, before each note. In that way you will get the smooth sweeps you are looking for.
i think you are confused as to the sound that I am actually getting when I say steps/sweeps /steps its not like a badly made va vst with obvious stepping that is constant the sweep will have somewhat glitchy element to it when I use a sweep via automating the editor. something like this:
/
__/ (at this point sweep continues as intended)
/ and then randomly
/
/
/
it could be due to the fact that I had enabled 14 bit cc and as u said possibly ableton doesn’t support this feature?
edit* when I typed this post the / were in a steady constant shape but when I submitted the post it didn’t come out that way anyway I think maybe you get what I mean?
I don’t know if I understood correctly.
My guess is that the Cutoff value jumps?
If that is the case, then the cause is that Ableton effectively, does not support 14-bit values correctly. You should use 7-bit values instead (only CC#19)
ya it “jumps” or u could even say pauses as it follows automation as it should for about 2 secs then freezes a split second then hops back on path (as to where it would be if it didn’t jump) anyway I can’t exactly test it with 7 bit cc as it just freaks out every time I use the editor after I tried using a midi cable(many parameters just wildly shooting all over the damn place like crazy) . or just flat out says hardware disconnected.
alright then this looks like the “hardware disconnected” issue everyone but me is having. And I think it is the inability of Ableton to send 14-bit messages, as well.
have you tried using only your computer and the Sub, without any other hardware?
I have a definitive solution for the “Hardware disconnected” message in the SP editor for Mac:
Macs always have a dominant USB port. In my MacBook (mid 2012) it’s the one closest to the screen.
I used to gett disconnected all the time (stand alone, Live 9.1, VST & AU, etc.). Since the move, I have had my SP steady as a rock on a USB hub
with 3 other devices.
Apple Logo > More Info > System Report > USB to figure out which of your USB ports is #1
Hope this helps