Tal J-8

[zvenx]

"I will fix that and the problem and the factory presets should load correct after that. The problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz."

From Patrick.
rsp

[PatchAdamz]

"I will fix that and the problem and the factory presets should load correct after that. The problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz."

From Patrick.
rsp

Excellent support, as always.

[planetearth]

"I will fix that and the problem and the factory presets should load correct after that. The problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz."

From Patrick.
rsp

If "the problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz," then why did I find the problem on my new install of the v1.2.0RC demo (with the presents that came with it) in a new session? Unless the presets that came with it were saved with the 20 Hz version of the synth (which Patrick says isn't the case), how were they screwed up on mine?

Either way, I'm glad he's addressing it so quickly. I'm just curious as to how it actually happened.

Steve

[Echoes in the Attic]

"I will fix that and the problem and the factory presets should load correct after that. The problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz."

From Patrick.
rsp

If "the problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz," then why did I find the problem on my new install of the v1.2.0RC demo (with the presents that came with it) in a new session? Unless the presets that came with it were saved with the 20 Hz version of the synth (which Patrick says isn't the case), how were they screwed up on mine?

Either way, I'm glad he's addressing it so quickly. I'm just curious as to how it actually happened.

Steve

I think what you said is right. The presets affected were saved before the change was made and so they stayed at the relative same place on the slider, which became a higher rate after the scale adjustment.

[planetearth]

"I will fix that and the problem and the factory presets should load correct after that. The problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz."

From Patrick.
rsp

If "the problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz," then why did I find the problem on my new install of the v1.2.0RC demo (with the presents that came with it) in a new session? Unless the presets that came with it were saved with the 20 Hz version of the synth (which Patrick says isn't the case), how were they screwed up on mine?

Either way, I'm glad he's addressing it so quickly. I'm just curious as to how it actually happened.

Steve

I think what you said is right. The presets affected were saved before the change was made and so they stayed at the relative same place on the slider, which became a higher rate after the scale adjustment.

But I got the presets when I got the v1.2.0RC synth. I had no previous version of this on my system. So the presets I downloaded were "bad" -- though only from the LFO rate perspective; I'm not implying they were "corrupt" or a danger to my system or anything. And it's fine if the presets I downloaded had the wrong LFO ranges stored within them, but that's not quite what Patrick said, as I understand it. He said "the first public release already supported 40 Hz".

Either way, I'm glad he's resolving it. There's nothing on his site about it yet, but that's fine -- I'm in no rush.

I appreciate everyone's help in figuring out what was going on here!

Steve

[Echoes in the Attic]

It wouldn’t matter what version you got the presets with. The point is that they were made with an earlier version when that position of the slider corresponded to a different rate. The range of the control changed after the preset was saved. So it seems like presets store the position of a knob or slider (like a percentage) as opposed to the unit value of that control, like hz.

[planetearth]

It wouldn’t matter what version you got the presets with. The point is that they were made with an earlier version when that position of the slider corresponded to a different rate. The range of the control changed after the preset was saved. So it seems like presets store the position of a knob or slider (like a percentage) as opposed to the unit value of that control, like hz.

Right, but isn't Patrick saying that was all fixed before the first public version was released? He said, "The first public release already supported 40 Hz." I got the presets with the latest public version of both. I just don't see how the presets still had the old settings in them. That's all I'm asking. I'm not suggesting anything about Patrick or what he said either, I'm simply trying to understand what he said versus what we're seeing.

Steve

[zvenx]

"I will fix that and the problem and the factory presets should load correct after that. The problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz."

From Patrick.
rsp

If "the problem affects only presets and sessions saved with the 20 Hz version of the synth. The first public release already supported 40 Hz," then why did I find the problem on my new install of the v1.2.0RC demo (with the presents that came with it) in a new session? Unless the presets that came with it were saved with the 20 Hz version of the synth (which Patrick says isn't the case), how were they screwed up on mine?

Either way, I'm glad he's addressing it so quickly. I'm just curious as to how it actually happened.

Steve

I think what you said is right. The presets affected were saved before the change was made and so they stayed at the relative same place on the slider, which became a higher rate after the scale adjustment.

This, sort of..
They were created and saved before the LFO rate was increased from 20 to 40 HZ.
rsp

[zvenx]

It wouldn’t matter what version you got the presets with. The point is that they were made with an earlier version when that position of the slider corresponded to a different rate. The range of the control changed after the preset was saved. So it seems like presets store the position of a knob or slider (like a percentage) as opposed to the unit value of that control, like hz.

Right, but isn't Patrick saying that was all fixed before the first public version was released? He said, "The first public release already supported 40 Hz." I got the presets with the latest public version of both. I just don't see how the presets still had the old settings in them. That's all I'm asking. I'm not suggesting anything about Patrick or what he said either, I'm simply trying to understand what he said versus what we're seeing.

Steve

Patrick didn't say anything about stuff has already been fixed, he said he will fix it.
The released presets were done before the LFO was increased to 40 Hz. The full picture concurs exactly with Captain's observations, and also explains why some of us (based on your DAW among other things) have different values.

Either way he knows why and will now fix it.
rsp

[Realistortion]

Been working with this synth for a few days now, absolutely loving it, as I have loved pretty much everything TAL has put out so far. This has been everything that I expected Arturia's new Jup-8 to be. It was a major let down to see that they did away with the split/dual mode which is a major selling point for the Jupiter, to me. Not only that, but they allowed for separate upper and lower outputs, stereo panning amongst a few things aswell.

Testing the oscillators, unison mode and other patches side by side, I hear no major differences in the oscillators or "fatness". However, TAL's can be pushed further, has better sounding filters, and it's far more flexible in polyphony and unison modes.

I'm glad that this came out when it did, I was going to be really sad having to keep using the Jup V3, V4 has a great sound engine and some other cool functions, but the omission and outright removal (hell, even refusal to expand on what was already there in V3) of functions which make the Jupiter such a unique instrument was a big dissapointment.

[zvenx]

Patrick's initial release date was a week before it was actually released which would have been before Arturia announced and released theirs (with v8). In things we will never know, it would have been interesting to see if that would have changed anything.
rsp

[barroco87]

Works cool on win 10, fl studio 20.1 Good price for this VST

[Echoes in the Attic]

It wouldn’t matter what version you got the presets with. The point is that they were made with an earlier version when that position of the slider corresponded to a different rate. The range of the control changed after the preset was saved. So it seems like presets store the position of a knob or slider (like a percentage) as opposed to the unit value of that control, like hz.

Right, but isn't Patrick saying that was all fixed before the first public version was released? He said, "The first public release already supported 40 Hz." I got the presets with the latest public version of both. I just don't see how the presets still had the old settings in them. That's all I'm asking. I'm not suggesting anything about Patrick or what he said either, I'm simply trying to understand what he said versus what we're seeing.

Steve

The first public release changed ("not really a "fix", just change) the scale of the lfo rate from 20 to 40hz yes, but presets made with previous versions had that slider set at a given position which then became twice the hz value after that change. This is the thing that has not been fixed yet.

[zvenx]

And just like that:

Version 1.2.1

Noise oscillator in unisono mode fixed.
Factory presets load with doubled LFO rate fixed.
SC dialog can also be closed when clickin at the SC button.
FX lock not working fixed.
MIDI lock not working fixed.

rsp

[Sound Author]

So has anyone figured out how to ping the filter?