TAL-Pha Released! Alpha Juno II Emulation from TAL-Software

[Vortifex]

Also note that on talalpha there is different behavior when RR is set on or off.

With RR off (default) the initial phasing goes away after some playing while with RR on the phasing is constant.

I find the opposite. If I have two saws slightly detuned, with 0 release, and play staccato notes, it makes no difference to the attack characteristic if RR is on or off. But if I add some release, say 4 seconds, and then play staccato notes so the note begins while the release from the previous note is still decaying, the attack characteristic will cycle with RR off.

But with RR on, the attack characteristic will remain static for the first few notes, but then begin to cycle. If there is a pause allowing the release to fully decay, and you start playing again, it 'resets' and you get the static attack characteristic again until you've played more notes.

Edit: I tested this with polyphony at 6 voices. It seems the cycling with RR on is just a consequence of the voices maxing out, effectively making each new note legato. Setting polyphony to 12 with RR on makes it take much longer for the cycling to begin due it taking longer for the voices to max out.

[chk071]

Hmm... I guess that works if the oscillators don't have the same waveform, but, if they do, you get phasing.

When DCO2 is slightly detuned, the phasing occurs no matter what is the waveshape is.
FWIW, in my sketch above, both DCO's are set to sawtooth.

Alright.

Could this be solved by "spreading" the phase values of osc 1 and 2 a bit further? And, more importantly, is THIS how the original works as well?

[phreaque]

Alright.

Could this be solved by "spreading" the phase values of osc 1 and 2 a bit further? And, more importantly, is THIS how the original works as well?

The original hardware synthesizer does that yes, because DCO1, 2 & sub oscillator components are all following the one main digital clock to adjust their phases.

For the plugin now, if there's a phase knob for one of the DCO's, it will make the difference for sure.

[Chris-S]

On the hardware the 3 components (saw, pulse, sub) are always in sync.

[Chris-S]

Which poly mode was the hardware using, round robin (new voice for each note) or re-use (new voice only when playing chords)?

[phreaque]

Which poly mode was the hardware using, round robin (new voice for each note) or re-use (new voice only when playing chords)?

Re-use with kill oldest voice.

[gentleclockdivider]

Just a little heads up for those who talso own Talmod
One of the characteristics of the alphas' filter ( besides non self oscillation ) is that the resonance peaks are summed
You can get a verry simmilar effect on talmod by the use of 2 pole filters in serial , and assigning one of the available macros to both resonance controls of the filter
Ofcourse set both osc's to trig for phase allignement

[seafire]

On the hardware the 3 components (saw, pulse, sub) are always in sync.

That's because they all come from the same Osc.

[Chris-S]

With RR off (default) the initial phasing goes away after some playing while with RR on the phasing is constant.

I find the opposite.

So this seems to be patch dependant. I was using a Saw with some release.

Possible solution: Add a button "random phase" in DCO section which leads to a random phase offset when initializing a voice.

[hurricaneaudiolab]

Yes, allow the oscillators to run free I say, like on....Albino 3:

Screenshot 2024-02-25 at 1.49.49 PM.png

[mjudge55]

This is a long shot question but since this is the thread about TAL-Pha getting the most attention I'll ask here. I'm trying to create a Reason remote map for TAL-Pha and it's going fine except the HPF Cutoff control doesn't seem to want to map. "HPF Cutoff" does appear to be the proper parameter name but it doesn't work when I map it to a knob, although all other parameters seem to work so far. Any clues?

To be clear, I'm not talking about a project remote mapping, I'm talking about a custom map I've created for my controller so that every instance of TAL-Pha has the same mapping automatically.

One other tiny thing, while I'm on tiny things - I notice the Portamento time control doesn't do anything to control my hardware aJuno's corresponding parameter. Is this a parameter that can't be controlled by TAL-Pha? I seem to recall with other aJuno editor VSTs a couple of aJuno's parameters still can't be mapped, maybe it's the sysex implementation...

[Chris-S]

except the HPF Cutoff control doesn't seem to want to map. "HPF Cutoff" does appear to be the proper parameter name but it doesn't work when I map it to a knob, although all other parameters seem to work so far. Any clues?

Works here with SaviHost and "MIDI to Parameter". Note that the HPF is "stepped", so the plugin slider is moving only when the controller is going from value eg. 63 to 64.

[mjudge55]

except the HPF Cutoff control doesn't seem to want to map. "HPF Cutoff" does appear to be the proper parameter name but it doesn't work when I map it to a knob, although all other parameters seem to work so far. Any clues?

Works here with SaviHost and "MIDI to Parameter". Note that the HPF is "stepped", so the plugin slider is moving only when the controller is going from value eg. 63 to 64.

Yeah so in Reason (and Live) I can definitely map my controller to HPF Cutoff and it works and I understand the stepped nature, and when I record automation the automation lane is called "HPF Cutoff". What I'm trying to do though is add TAL-Pha to my controller's Reason .remotemap file so that every time I load up this VST in any project my controller maps automatically the way I've arranged it to in the .remotemap file. I've done this successfully with several VSTs so it's a thing. Occasionally you'll get a situation like this where the apparent name isn't the one the .remotemap file wants to see and it's a game of guesswork to figure out what it's supposed to be called there.

[Chris-S]

Yes, it's parameter 10, "HPF Cutoff".

[mjudge55]

Yes, it's parameter 10, "HPF Cutoff".

Yeah I know, but it doesn't work in the .remotemap file. All the others parameters do.