No need to apologise. I don't have the skills right now to do it my self so will just have to wait for someone else to sort it.
Been keeping an eye out for it to happen and thought this might be it
Looking forward to getting the chance to try some of your stuff tho. Looks tasty
NEW MODULE.
High Quality pitchshifter, controls are the same as the former pitchshifter, except for the windowratio, which wasn't working great anyways (offsetting the other controls).
Module isn't totally finished yet, but good to go for some testing.
Probably this evening I'll add a pre-delay, so it can be used as a combined delay/pitchshifter.
YES!!!! will test it now!
I have a question regarding midi2LFO sync. It seems like i potentially can use your Clock2Timing module, and i can connect that to your LFO's. But i just cant get it to sync up to incoming midi clock. Do you have some project/picture of how to do that?
Thanks:)
the clock2timing module needs a pulse from the midi clock module (convert the int counter output to triggers with the integer-change module in the logics folder). Connect the hz output to the ratioVCA (maths folder) to set a division of this rate and connect it to one of the LFO modules.
For the delay, use the "basedelay" output, followed by the ratioVCA. Though the nominator and denominator will work in inverse operation in comparison to the LFO (eg. increasing the rate of an LFO will decrease the time between clock pulses. So while you should multiply a LFO to go faster, with a delay, you should divide it with the same amount.).
as my soundcloud is over-full (that's "dunglish", right?), I just uploaded a recording of the pitchshifter as a video on my facebook.. so, here we go: a HQ pitchshifter with delay which can be synced to midi clock (or any other trigger source) with my clock2timing module XD
https://www.facebook.com/SirSickSik/videos/10157012454175626/
oh my, this is getting more and more fun! Just figured out how to use to for-loop to create a spectral oscillator 
SO! New module!
Spectral oscillator with up to 32 harmonics.
-Range sets the maximum harmonic above rootnote in power of 2. Harmonics above max will be wrapped back to 1 and start counting up again.
-jump sets harmonic 'jumpsize' between previous and next harmonic. (eg 3 will go: 1->4->7->10... etc)
-offset sets the offset of the harmonics after a wrap has taken place.
-also features linear frequency dependent FM
This module can draw some serious CPU! Though, I was able to use 2 of it with envelope and sequencer and almost reach 2x 32 harmonics (without crashing, just weird glitching... also pretty weird..)
With this setup i get kind-of midi sync. Except it isnt in the right tempo. Not matter what division/multiply i set. If i change the daw tempo, the tempo of the LFO goes up, but its still not right..
Thanks:)
oh hmm, should be working..
just checked it and if I connect a LFO to the trigger input and my LFO to the hz input, it just follows the other LFO perfectly..
might it be that you hear a phase-offset, which causes the LFO-wobble to be too late/early?
Or maybe the clock of the daw is in a different setting causing the axoloti to respond differently? have you tried this out by multiplying or dividing by 3?
ps, the first two ticks, it will still look for a tempo. So until it found the tempo and updated the hz output, it sends out a random number (I think..) Next to this, you might want to check your midi tempo.. how fast/slow are you going?
Might be that the counter restarts after hitting the max-count because there is too much time between ticks in the low-rate case?
Working now! Not really sure why it wasnt before. But that leads to another question (sorry). What if i do 3/4 instead of a 4/4 beat? How should i set the division/multiply to get 3/4? I fiddled around, but dont really understand the whole multiply/division thing.
And what about locking the phase/reset?
Lets say have the LFO set up to produce a squarewave. I let it modulate the freq of a normal osc, to do arpeggio-style up/down octaves.
I want the up/down change to happen exactly when a bar is hitting. Not slightly before or after.
I can adjust the phase of the LFO so i locks perfectly, and all is great. I then stop the daw and press play on the daw again and play my patch. The phase then needs to be readjusted. This seems to happen pretty much all the time. Sorry for my constant ignorance/stupidity, but how can i make the phase lock? Sometimes, When i have release a the keyboard (with long release on the osc) and stop the daw i can hear the LFO going much faster all of the sudden. Sometimes not.
THANKS!!
the module gets it's tempo calculation from the amount of samples that are in between ticks, so if you reset it, this count is on zero, and thus, time converted to frequency... frequency is infinite. That's why it always needs at least 2 ticks before it can lock to the tempo.
This counting is done realtime, so if you press pause for a while and then press play again, it takes this last count as the next tempo setting.. if it takes long before you press start, the counter maybe repeated already because it passed it's upper limit (32bit) and the axoloti thinks it only took a couple of counts between ticks...
For phase-locking your LFO's, I'ld recommend to just connect a counter to the trigger source and use the "c" outlet to reset your LFO's after # triggers (or a button with a logic "and" module, so you can press it if you want to lock it to the input triggers)
New oscillator coming up!
Improved version of the saw/tri oscillator! Using floats instead of ints, the up/down ramp of the triangle now respond correctly (in the first module, there was a small offset when switching direction).
Still thinking about a nice function for morphing to smooth/hard saturated PWM pulses.. though, to tired right now haha
NEW MODULE!
OSC:
SiTrSaPu_Osc
cpu use 8 to 9% (loading 4 oscillators with different shapes already takes 7% and can take quite some cpu to combine them into a continous morph. So this might take off some cpu for some projects.)
Controls for continuous morph between saw->tri->ramp and normal->saturated (pulse) and a toggle button for selecting between tri/saw mode or sine/saw mode.
Sine/saw mode has a dampened character and the modulations do not cause the waveform to make sudden jumps.
Tri/saw mode creates lots of aggressive overtones, because, depending on the slope and shift parameters, the waveform gets inverted at certain phase-positions. Though a bit unexpected, this waveform comes out really nice when used as FM modulator for a second SiTrSaPu_Osc.
The FM is linear frequency modulation utilising the frequency-dependent index-width control.
The Slope parameter controls the slope of the saw<->tri<->ramp morpher, continously shifting the high position of the waveform from the beginning of the phase to the end of the phase.
Shift has two different effects, depending on whether triangle or sine shape is selected.
When sine-shape is selected it morphs between a sine to saw modulation (slope controls sine->saw) and a with pulse-width modulated sine (slope controls pulse width).
When the triangle-shape is selected, you can see what actually happened before it was converted to a saw: the phase gets shifted at certain positions, causing sudden, saw-like jumps. The nice thing about this shifting, is that it doesn't influence the power ratio between positive and negative values, making it perfect for use as a FM modulator of a second SiTrSaPu_osc.
Has an inbuild filter for DC-offset canceling and a high frequency filter to smooth it out a bit more.
LFO sync:
Something like this?:
I tried different values for the logic/counter, but still no luck. Still no phase lock.
I guess i'll leave the tempo sync project on the shelf and work on other parts of my patch, if i cant get this part of it working now. Dont want to pollute the thread constantly:)
MidiClock_01.axp (5.5 KB)
you have connected the count output instead of the trigger "c" output...
also, the counter is still set to 0... if you'ld put it on any other value, it would have counted as a gate as it's higher then 0..
About the waveform, there are only 5 posible waveforms. The one you selected is a square wave from -64 to +64, so it will be hard to see on the scope
several new modules!
EDRUM:
BD1: bassdrum module with seperate "hit" pitch and "bass" pitch. Play a bass, while keeping the kick tight!
CY1: cymbal module consisting of 6 sine oscillators with 3 parameters to control tonal character.
CR1 (FM variation on CY1, though still working on the different FM-modes (different routings between oscillators, you could add these yourself also!)-> only 1 available now! mode 0!! Just don't connect anything to mode..)
