ok. thanks
That explains it.
I must say I am not all satified with that, even if you can do an override solution by turning up the volume release. It work as long as the arp is running, but when you want to stop it messes things up a bit.
Also, it retriggers the filter envelope, even if gate legato is on (especially sad to not be able to use that in latch=A mode, with a long filter sweep and running notes, without the last note is sustained…)
Yeah,
I think there definately need an arp gate amount parameter. Even if, the only choices are 50% and 100%. I have been using the arp a lot lately with filter keytrack all the up to produce complex waveform sweeps to process external audio. 50% gate will mess things up, especially for people who have already written music to a sequencer.
OK maybe I can add an arp “gate length” parameter to allow you to adjust this. Even if it only had two settings (50% and 100%) then you could still choose between the old way (arp notes at 100% of step duration) or the new way.
Seems like there was some other feature I wanted to squeeze into the last remaining space but I can’t remember what it is right now…
Edit: I think I was typing at the same time as Sir Nose… 
Also, sounds like maybe we need three settings minimum: 50%, 100% and “>100%” meaning truly overlapping (legato) notes. This last option might be difficult as it’s never been the case… from the beginning, each arpeggiator note has re-triggered the envelopes. (Unless my memory is going faulty…) In any case, I can see the utility of “legato” arpeggiations, although in Latch mode it could cause some difficulty as the envelopes would never re-trigger… hmm.
Yes, yes Yes YEs YES! 
I’ve got an issue i just noticed after i upgraded, but am unsure if it existed before the upgrade and am unsure if it an issue with my unit.
anyways, when adjusting the volume knob while playing a note, it goes louder momentarily before setting the new volume level. I noticed it with the BouncySeq preset with the filter wide open when adjusting the volume. it’s there on other presets, but it is hardly noticable to the ear.
can anyone else see this problem?
edit:
i should have said “can anyone else hear this problem”
check that preset, Advanced Preset menu, and see if the “Vol Sens:” parameter is nonzero.
application note: Because the Little Phatty did not originally support volume velocity sensitivity, I had to add this feature by “mapping” note velocity to the Master Volume parameter. This means that if you play a soft note (with Vol Sens: >0) and you adjust the Master Volume while the note is held, the volume will jump to maximum as the volume knob movement overrides the volume as set by Velocity. It’s the same as if you sent a MIDI CC to set filter cutoff to 50% and then you move the Filter knob; the knob overrides the MIDI control. So, it’s best to move the volume knob “between” notes in a performance, rather than during a note. When the “Vol Sens” parameter = 0, this should not be an issue… in that case, note volume is always the maximum as set by the volume knob, so there should be no jump in volume as you move the knob.
ADVANCED PRESET
VOL SENSE: 4
ok, so not a bug per-se, but a byproduct of a new feature. agreed, it shouldn’t be an issue in most cases. i noticed it with the headphones on when adjusting the volume to the filter so I didn’t blow my head off.
good to know that at least my LPII isn’t faulty.
OK which would you rather use: global arp gate length, or per-preset arp gate length?
and ANOTHER question… while I am making last minute changes…
Some folks have requested Triplet values for LFO (and maybe Arp) MIDI sync. I guess this is crucial for dubstep now
Other folks have said that it is hard to change LFO sync values in real time performance if there are triplets in the list, as this throws off the rhythm (if you land on a triplet and then switch back to a non-triplet sync division). So… what shall I do? Add triplets or no?
Please note also that if I change the number of sync options, it can mess up preset compatibility. You’d need to re-program a lot of your clock division settings, most likely, as the parameter value that corresponds to a particular clock division would change. I hope this question makes sense… I’d really like some feedback. Thanks!
Both?
No … just kidding …
If I have the opportunity to choose, I prefer per preset.
Can you see anything that speaks against that?
I think triplets would be a very elegant (yes!) and useful possibility. Dubstep or not.
If that means I have to reprogram some patches, it’s pretty easy done.
Just for the LFO or for the arp as well?
EDIT: Misleading wording …
How about initiating LFO sync values by pressing the Enter button? The active preset would be indicated by an asterisk or something. This would avoid those unwanted LFO rates. In my opinion, this would also be nice with Arpp as well.
edit. I forgot to mention that I think triplets are a good idea.
Does the Arp Gate have to be tied to a note division, or could it be any fraction? That is, if you’re arp-ing 1/4 notes, would the gate division have to be a choice of 1/4, 1/8, 1/16 (say) or could you dial in something like 99% to keep the length but lose the always-on problem?
Personally I think even a limited choice of two settings would be great, but even better would be the option to assign gate length to mod wheel or something… I doubt there’s room for that though.
oh geez… yes gate length to mod wheel would be awesome. No I don’t think I can pull that off easily enough.
In any case gate length is currently a percentage of whatever the current step length (tempo * clock division), that’s how I intend to keep it, for simplicity. It used to be 100% and is now 50%, the 50% scales automatically as you adjust tempo or clock divisions. Right now I’m seeing about adding a choice of 50% or 100%… after that, 25% or 75% is fairly easy… “actually overlapping” or >100% gate length might be more difficult. Or, maybe I’m just having a slow brain day (after expending mega brain power all last week!)
OS3.01T
I just played around with the alternative tunings, to see what happens when you use it per patch vs global.
I can’t seem to get it work with different tunings per patch. They get the global tuning however I do.
If I choose tuning #11 (any but #0) and save the patch, then I change patch and go back again, the patch tuning is #0.
Yes, this is a bug I fixed yesterday. I’ll post an update later today with a fix. 
Cool - thanks, Amos. BTW, I also noticed that sometimes when you switch to a preset, the Filter pot is indeed affecting a parameter, but which parameter it’s controlling is not lit on the SP.
Does the “new” Poly behavior require something other then the “POLY: x of y” setup? I got my third Phatty yesterday and went poly after updating them all to 3.1, so the subtleties may be lost on me, I’m afraid. I DO love the poly, though. Thank you, thank you, thank you for all the effort you’ve put into this, Amos!
Side Rant:
I got into Moog equipment when I picked up a Moogerfooger. I remember going into my local music shop and telling the guy that I was looking for an off-the-wall, but useful effect. He brought in the Phaser, to which I said, “Nah - I’ve already got a phaser.” He laughed and basically forced me to try out the Moog unit. I was floored, and I walked out with it in hand. Less than 5 months later, I have three Moogerfoogers (one is the delay, which I sent back for the factory mod), a CP-251, an LP, and two SPs. I can’t get enough of this stuff!!! The fact that Bob’s vision is carried on by the current guard and that people like Amos are so enthusiastic about what they do is the icing on the cake!
Would there be any way to adjust gate length smoothly in real time? For example, Value knob, one of the pots - I mean I have no idea how these things are implemented in the code, never mind the hardware, so I might be pipedreaming. But some kind of realtime gate length mod would be the canine’s cojones if it’s at all possible.
Aside from that, you must be busting a gut for us all here. Buy yourself a drink and pretend it’s from me.
[quote=“Amos”]
New MIDI features:
Can now choose to filter MIDI output as follows:
- Transmit All MIDI CCs from the LP (default behavior)
- send All CCs minus Volume (CC7)
- no CCs from the knobs, only MIDI notes and pitch/mod wheel messages
- no CCs, no wheels, only MIDI notes
(All controls continue to affect the sound of the Phatty as before, only MIDI output is filtered)
Thanks again for adding my request (and all the other features of this release), Amos. You’re the best!
The smallest/smoothest granular increment I could use would be MIDI clock ticks… since the arp has to be compatible with MIDI Sync and it basically only checks to see if it’s time to do something, 24 times per quarter note. If your arp is already running at 32nd notes, that’s only three clock ticks per 100% note duration… your only options then would be “note is never on” (0 ticks), 33%, 66%, or 100% duration. The longer your clock division, the smoother/more options you might have… but it does get complicated. Then how do you map this to something smooth like a knob (all of which are kind of allocated already) without causing more confusion? I don’t have a ready answer.
Ha, thank you. I will! And I may settle for a simple menu choice of 50%/100% duration… or possibly a couple more increments… on the principle that “some choice is better than none.”
edit: last note for today – sorry Assar, no update with Alt Tuning bugfix yet today… too much new stuff (per previous messages) and current version is not stable for release today. Probably tomorrow.
Now, if you need me… I’ll be at the pub.
No hurry, it’s not a show stopper …
+1