Moog Music Forum

oh sry i didn't uderstand
So glide is ok!

question: now there is the 14bit midi also on little phatty....is better to set 14bit midi on when little phatty works with slim phatty via midi?

Thanks for all the hard work Amos.

Just updated to build 660. Working great.

Been playing with the MIDI Sync on the LFO and one thing I noticed is that every time I save a patch it resets the LFO Sync clock value to WH. Is this what it is supposed to do?

spin wrote:question: now there is the 14bit midi also on little phatty....is better to set 14bit midi on when little phatty works with slim phatty via midi?

Yes, it's definitely better! If you send 14-bit MIDI from Little Phatty to Slim, it should give very smooth results, almost as good as turning the knobs on the Slim directly.

Amos wrote:

spin wrote:question: now there is the 14bit midi also on little phatty....is better to set 14bit midi on when little phatty works with slim phatty via midi?

Yes, it's definitely better! If you send 14-bit MIDI from Little Phatty to Slim, it should give very smooth results, almost as good as turning the knobs on the Slim directly.

ok! sounds good!

Fuseball wrote:Been playing with the MIDI Sync on the LFO and one thing I noticed is that every time I save a patch it resets the LFO Sync clock value to WH. Is this what it is supposed to do?

I forgot about this! OK, here is what's going on:

When LFO Sync is set to MIDI CLOCK, the Clock divisions value is set according to the LFO RATE parameter.
When you load a new preset, the LFO Sync clock value changes according to the LFO Rate of the new preset.
When you save a preset, it actually saves and reloads the preset, so again it checks the LFO Rate and updates the Clock value.

So in the case of the preset you are saving, the LFO Rate corresponds to a MIDI Clock value of WHole note... if you want to save the preset such that it loads with a different LFO MIDI Clock value, select LFO RATE and use the Modulation knob to set the LFO Sync Clock value and then save the preset.

This is not a 100% perfect scheme but it seemed to make sense at the time.

I think the reason for confusion is this: If you are in LFO MIDI Sync mode and you change the LFO RATE, it changes the LFO Clock divisions parameter.
However, if you adjust the LFO CLOCK parameter (using cursor and Value knob), it does not change the LFO RATE.

I could make it so that the LFO Rate is updated when you change LFO Clock division (only when LFO Sync = MIDI)... but I'm not sure this would be really less confusing than the current scheme. Maybe it would only be differently confusing. What do you think?

but when LFO RATE = midi clock, the rate isn't set by incoming external midi clock? So, like arpeggiator, the rate knob should be disabled when lfo rate = midi clock?

Amos wrote:I could make it so that the LFO Rate is updated when you change LFO Clock division (only when LFO Sync = MIDI)... but I'm not sure this would be really less confusing than the current scheme. Maybe it would only be differently confusing. What do you think?

As you have LFO Clock division editable from the cursor and Value knob then I personally think it should be updating the LFO Rate as appropriate. At the moment it is two methods to achieve exactly the same thing but only one of them saves with the preset, which certainly caught me out!

The other way to make it less confusing might be to display the LFO Clock division but not make it editable from the Value knob - only from the LFO Rate via the Modulation knob.

spin wrote:but when LFO RATE = midi clock, the rate isn't set by incoming external midi clock? So, like arpeggiator, the rate knob should be disabled when lfo rate = midi clock?

That's a pretty valid argument too, although the LFO is more closely tied to the Modulation knob than the arpeggiator is in my mind.

Either way, I think if you change the LFO Clock Division value somewhere it should be saved with the preset. Making sounds on the LP is such a gloriously right-brained activity that you don't want to be worrying about whether you've adjusted that value from the correct place... just that it sounds right.

Really the most sensible thing, I think, would be to have the LFO clock divisions only editable via the cursor/value knob and NOT saved with the preset, since LFO clock source and clock divisions are technically global values.

However, LFO RATE is a per-preset parameter, and there is some logical connection between LFO Rate and LFO Clock divisions when the LFO is synced to MIDI (they both relate to how fast the LFO is going). Plus, I like the fact you can sweep through the LFO clock divisions using the LFO Rate knob; that seems a lot more fun to me than disabling the knob altogether...

So, I think I may do as you suggest, and have changes to LFO Clock divisions update the LFO Rate (only when LFO Clock source = MIDI). It's a little odd but should result in more intuitive behavior when you're in the midst of creative sound design...

(I hope!)

I really enjoyed the 'Checksum Error' Little Phatty performed an amazing light display lol

Altered the Phattyloader timing and LP running perfectly now

Hey guys, i've been following this topic closely since i'm pretty exited about all the great features of the new OS. I got one question tho: Is there gonna be an official realease of the new firmware? i don't wanna be a beta tester because i'm playing live regularly with the LP and don't wanna have any troubles with it.... thanks for any info, and Amos thanks for all the great work!!

Here's a simple solution to the global/preset LFO issue.

Advanced preset menu option: preset lfo or global lfo.

If preset lfo is selected, the global settings are ignored. The lfo would run on the internal clock and the rate knob value when saved would load with the preset.

For global lfo:
The lfo rate knob value is ignored when the preset is saved. If set to internal the lfo continues to free run at whatever it was at before the preset was selected. This would add some functionality as well.

I would just need midi sync as a global lfo since it is easy enough to change to a specific correct value. If other users need a preset saved midi sync lfo then more work/code space might be needed.

patobrujo wrote:Hey guys, i've been following this topic closely since i'm pretty exited about all the great features of the new OS. I got one question tho: Is there gonna be an official realease of the new firmware? i don't wanna be a beta tester because i'm playing live regularly with the LP and don't wanna have any troubles with it.... thanks for any info, and Amos thanks for all the great work!!

I think it's basically solid/stable at this point.. I will do one more update to tidy up a couple of things, then official release is next week.
Some of these last details we're discussing, with LFO rate behavior and so on... may not be perfectly to everyone's liking in the "official release." Also, there may be features we've discussed which won't get implemented until a future official update. But, for now... I think we're almost there.

Amos,

Any ideas on the accent thing Joe Moog and I were talking about in polyphonic mode? What are your thoughts on this?

-Geoscience

geoscience wrote:Amos,

Any ideas on the accent thing Joe Moog and I were talking about in polyphonic mode? What are your thoughts on this?

-Geoscience

I don't think it makes sense and it may not be possible to have "legato" envelopes across multiple voices of a poly synth.
What's to distinguish two notes that you want to be "legato" from two notes that you want to play in harmony? Presuming you have available notes I mean.
As for the voices not matching each other, you may have to re-voice the patch on one instrument to make it sound more like the other. The same numeric parameter values may not sound exactly the same on every analog board. This isn't an issue when you play each one in isolation but if you want them to sound like multiple voices of the same instrument you may have to tweak the settings on one and re-save the patch on that instrument.

Thanks for the reply Amos! I'll figure out the right tweak. Seems to be (in general) that it is the volume that needs the tweaking.