Now, I need your help. If you have experienced any bugs or odd behaviour when using the Sub Phatty, please test for the same odd behaviour in v1.2.2 and let me know if your problems are fixed, or if they persist.
The surest way to make sure your problem gets fixed is to post it in this thread.
Thanks very much for your help! My hope is to have a release version ready next week.
The more feedback I can get here, the better that process will go.
Setting knob mode to Snap in firmware 1.2.1 seems to prevent the panel lockup for me. I’ll get 1.2.2 installed tonight and try the different knob modes in Ableton to see if it’s still happening.
The bug I had with Initialize Globals appears to be fixed! It used to hose the WAVE buttons and the filter EG, but no longer It’s easy to get to an initialized state now, yay!
I am experiencing some issues when upgrading my SUB PHATTY. I had to power off the synth because it took a long time to upgrade but now, I have ONLY the LFO rate led blinking and nothing else work.
What i s the procedure to restart completely the upgrade process ? I have tried PITCH AMT - HARD SYNC - ACTIVATE PANEL without any success…
I just updated to 1.2.2 via USB seemed fine.I then started editing my Bank 1 Patch 1 sound. Took me 20 minutes to create a new sound which also had LFO midi sync from Logic. Patch sounded great and I set up a blank audio track in Logic and hit record. I hit playback to hear the newly recorded Sub Phatty audio track which sounded good so I started playing along on the Sub Phatty still in the same un saved patch I had just made then something strange I noticed. All by itself the patch I just spent 20 minutes making sounded somewhat different somehow and I did not touch any SP dials. THe LFO mod wheel was NO LONGER controlling the filter so I started testing parameters, still remaining in this messed up patch and found another BIG PROBLEM the filter knob was having no effect on the sound at all. I tried to rescue the patch by checking hidden parameters that set the filter to it’s 4 pole settings. That did not fix the filter control. The patch was literally crashed. Something killed the Modulation wheel to the LFO Controlling the Filter CF, and the Filter CF knob stopped working leaving the frequency fixed and it sounded wide open. I decided to scrap the patch and check others in the same bank. THEY were all messed up, in fact something was weird with ALL my presets.I decided to reboot the SP. Well that fixed the patch memory my patches were safe and intact, I only lost my great unsaved patch that was an off spring of Bank1-1. I then had the bright idea of looking at the audio track in Logic but viewing the Event editor of the audio region and event editor showed there was some sys ex that was recorded with the audio. So I did an experiment and made a quick edit of a SP patch and hit play on logic WALLA, the playback of the audio track sent a sys ex bullet to the Sub Phatty and killed the current patch in the edit buffer in the same way AND my preset memory seemed messed up again !!! I re boot the SP patches in memory were normal again. I took a screen shot of the Logic session for Amos so he can see the sys ex data that is in the Audio track which by the way I had no idea Logic could even record midi data to track that’s recording audio.
As an idea I reloaded v1.2.2 with turbo set to none. From this point on I was unable to recreate the problem, I am attributing the problem to a bad load of the OS and problem SOLVED.
Other bug to report: Is anybody else having a problem with note calibration hidden parameter command. WHen my Sub Phatty gets to the low octave in the routine, it hangs on the low octave note that’s being tuned automatically forcing me to reboot the Sub Phatty.
Here’s a bug I think: the Initialize Preset command by definition is to reset all shift mode parameters of a patch to default settings. That should mean the Hidden parameters and the front panel shift parameters. I think it is also effecting non shift mode parameters, I found that this command reset all the envelope parameters to where ever they were set on the front panel kinda like an activate panel command would. In this case I had all the envelope parameter knobs set to fully counter clockwise which did not reflect how they are stored in the patch as I earlier while in shift mode zeroed out all the shift parameters that are assigned to the envelope knobs. Hope this isn’t too confusing to reproduce or understand
Hi AMOS ~ Firmware loaded fine and seems to be behaving well - so far so good…
I think part of my confusion perhaps is the i/o Icons for global parameters are not entirely clear to me in the software GUI. Editor is still not right under 10.6.8, in any case ~ same issues as last week~ Have yet to hook SubPhatty up to Mountain Lion laptop again since updating FW though- will get to it soon - hopefully later today - best, Pete
Thanks for all your hard work Amos. Cannot wait for the editor.
If you change the oscillator 2 beat frequency to something not center on the active panel, then switch to a preset, then switch back to active panel, the oscillator 2 frequency is where the oscillator 2 beat frequency knob was positioned.
This probably isn’t a bug, because the active panel is working as it should. But it might be nice if I don’t have to remember to reset the oscillator frequency after changing the oscillator 2 beat frequency.
Hmm. You’re right, it’s not a bug, it’s a logical consequence of the way things work; you’ve moved a knob and then you’ve requested “the real panel settings,” including the knob in question. The confusion is because you moved the knob while it was controlling a different parameter (beat freq, in shift mode), so it doesn’t seem exactly right…
Is there a way around it? The easiest I can think of is just to re-center the freq knob after you’ve dialed in a beat frequency and exited shift mode. I’m open to clever suggestions, as usual
I totally understand – I wasn’t being flippant, either – if anyone can suggest a change which would help this particular use case, I’ll be glad to implement it.
Meanwhile, I’ve posted a new firmware version… there are two changes of note in v1.2.3:
Octave up/down works (via MIDI) when Local Control is turned off
There is a change in the way Relative knob mode works, which needs testing please.
See repost from other thread below:
OK! Here’s a new version. I made some changes to Relative mode, it seems to avoid this problem for me now.
remember that (for now) Local Control is ON every time you power on the Sub Phatty, and must be turned off each time, if your setup loops MIDI through a DAW like Ableton Live (or any other DAW).
I thought this was a good idea at the time… since if you don’t know about Local Control and it’s off, it can seem like your synth is broken… but now, I’m thinking it’s better for Local Control to be persistent. I’ll change this soon.
Anyway, be sure Local Control is off and Knob Mode is Relative, and tell me if this problem is fixed or if it persists.
I just want to emphasize also, if you’re sending MIDI out from a synth to a DAW, and sending that same MIDI back from the DAW to the synth in real time (like in this example with Live, above) you really must work with Local Control turned off; otherwise the synth gets two copies of every MIDI message (one local, one echoed from the DAW) and invalid things happen, especially in Relative mode.
V 1.2.3 seems to solve the issue with local off engaged.
I have the Sub Phatty connected via usb midi and a fatar keyboard connected to the midi in of my audio card interface.
Just one question: When I play from the fatar keyboard with midi in set to the “fatar midi in” only turning any knob on the Sub Pahtty has no impact on the sound. Is it normal? Is local off affecting knobs too?
With local on engaged + Knob in relative mode
I have the problem when I play from the sub phatty keyboard with midi in of the ableton track set either to “sub phatty” or “all ins”
I works only when i set the midi in of the ableton track to “fatar in” only.
=> this option is not ideal because I can not record the automation of the Sub Phatty!
With local on engaged + Knob in snap mode
everything works
I understand your point about local on not being ideal but in a ideal world I would prefer to be able to play from the Sub Phatty keyboard when I am not connected to a my DAW. But I noticed sometimes like “midi glitches” that may be due to being in local on mode (Sub Phatty receiving information twice).
However as it works fine in Snap mode I think there is still a bug as it should work in Relative mode too.
