KVR Audio

dermage · Post by **dermage** » Tue Mar 02, 2021 2:47 am

Why make the version with the arp not backward compatible? Now i can't upgrade because I have several open projects using it.

Thats what I always fear and where tal is not so professional IMO. a future version should never break older projects.
He just decided that after having it out since almost 3 months.

electro · Post by **electro** » Tue Mar 02, 2021 7:33 am

Because the old Arp behavior was a bug. J-8 is supposed to behave identical to the hardware Jupiter in all aspects.

dermage · Post by **dermage** » Tue Mar 02, 2021 8:16 am

electro wrote: Tue Mar 02, 2021 7:33 am Because the old Arp behavior was a bug. J-8 is supposed to behave identical to the hardware Jupiter in all aspects.

Yeah but this was only known to us in the last few days. Suddenly other things can be seen as a bug.
Actually the arp was working OK for me otherwise I couldn't have made several tracks with it yet.
Now probably all of these will sound different. He actually could just have implemented a legacy switch in the menu or at least load the old arp behavior until it is changed by the user. Totally possibly in the world of a vst.

electro · Post by **electro** » Tue Mar 02, 2021 8:47 am

IMO if its different than the Jupiter 8, at the same parameters its wrong. Adding features such as an extra oscillator shape is a different thing because it doesn't break the precision of the model.

BDeep · Post by **BDeep** » Tue Mar 02, 2021 9:02 am

dermage wrote: Tue Mar 02, 2021 8:16 am
electro wrote: Tue Mar 02, 2021 7:33 am Because the old Arp behavior was a bug. J-8 is supposed to behave identical to the hardware Jupiter in all aspects.
Yeah but this was only known to us in the last few days. Suddenly other things can be seen as a bug.
Actually the arp was working OK for me otherwise I couldn't have made several tracks with it yet.
Now probably all of these will sound different. He actually could just have implemented a legacy switch in the menu or at least load the old arp behavior until it is changed by the user. Totally possibly in the world of a vst.

Have you asked Patrick if it really breaks old projects? It might very well be that he thought of it.
The fact that it isn’t user selectable doesn’t mean it isn’t there in the background.

Anyway, I hope you get it sorted, but I would definitely be in touch with TAL if I were you.

dermage · Post by **dermage** » Tue Mar 02, 2021 9:09 am

BDeep wrote: Tue Mar 02, 2021 9:02 amHave you asked Patrick if it really breaks old projects? It might very well be that he thought of it.
The fact that it isn’t user selectable doesn’t mean it isn’t there in the background.

Anyway, I hope you get it sorted, but I would definitely be in touch with TAL if I were you.

Have not contacted him yet, but reading his statement it definitely sounds to me it will play differently.

It will sound different in most cases if you already used the arpeggiator in an existing track. We also decided to implement only the real behaviour without any switches

BDeep · Post by **BDeep** » Tue Mar 02, 2021 9:13 am

Aw damn, I skimmed over that part. Hmmm, bummer

dermage · Post by **dermage** » Tue Mar 02, 2021 9:22 am

BDeep wrote: Tue Mar 02, 2021 9:13 am Aw damn, I skimmed over that part. Hmmm, bummer

I've just sent him a lengthy email

Let's see what he says, the last time he did a similar thing with Tal-Mod (but not as deep as changing the whole arp behavior) he implemented a legacy switch in the menu.

ghostwhistler · Post by **ghostwhistler** » Tue Mar 02, 2021 10:19 am

I notice the Arturia Jup V doesn't allow the VCO and Envelop modulators (the pair right next to the LFO controls on the TAL vst) to modulate xmod, unlike the TAL. Did the hardware allow that, or did TAL add it?

dermage · Post by **dermage** » Tue Mar 02, 2021 11:13 am

Patrick just said he will implement a legacy loading for the old Arp use.

EnGee · Post by **EnGee** » Tue Mar 02, 2021 11:21 am

dermage wrote: Tue Mar 02, 2021 11:13 am Patrick just said he will implement a legacy loading for the old Arp use.

That's really very nice of him

It motivates me to buy his other synths as well

dermage · Post by **dermage** » Tue Mar 02, 2021 11:37 am

EnGee wrote: Tue Mar 02, 2021 11:21 am
dermage wrote: Tue Mar 02, 2021 11:13 am Patrick just said he will implement a legacy loading for the old Arp use.
That's really very nice of him

It motivates me to buy his other synths as well

So strange the decision was to completely change the behavior of the Arp, so nice he is on the other side when reacting to feedback and support. That's the reason I support him, he cares for his users.
I just think he could have expected that users wouldn't be OK with this change in a minor version which breaks older projects

BDeep · Post by **BDeep** » Tue Mar 02, 2021 11:48 am

ghostwhistler wrote: Tue Mar 02, 2021 10:19 am I notice the Arturia Jup V doesn't allow the VCO and Envelop modulators (the pair right next to the LFO controls on the TAL vst) to modulate xmod, unlike the TAL. Did the hardware allow that, or did TAL add it?

I’m not familiar with the Arturia version, but the original indeed had this functionality.

BDeep · Post by **BDeep** » Tue Mar 02, 2021 11:49 am

dermage wrote: Tue Mar 02, 2021 11:13 am Patrick just said he will implement a legacy loading for the old Arp use.

That’s great to hear! Glad he’s on it

EnGee · Post by **EnGee** » Tue Mar 02, 2021 11:52 am

dermage wrote: Tue Mar 02, 2021 11:37 am
So strange the decision was to completely change the behavior of the Arp, so nice he is on the other side when reacting to feedback and support. That's the reason I support him, he cares for his users.
I just think he could have expected that users wouldn't be OK with this change in a minor version which breaks older projects

I don't know really what he was thinking, but I like his flexibility in taking decisions

Tal J-8