I find the S1 4 implementation very helpful for trying out different chords to create different harmonies in the early stages of fleshing out a song once I have the melody roughly in place.  I used to do that sort of thing in BiaBox, but much prefer the flexibility and speed of S1 4 for this.  Frankly I find it pretty amazing, though I will almost certainly re-record the final guitar (audio) tracks - if for no other reason that I'm going to have to learn them to play live anyway.

I think the most misunderstood thing about chord tracks is that they are only useful for writing your chord progression (a crutch for music theory challenged users), rather than the more powerful way they can be used to alter the chord progression for all of your tracks in the arrangement that are following the feature.
 
It is not simply a tool for writing your song's first track, while giving you suggestions for a pleasing chord progression in your song.  I'm sure it could be helpful in that way if you need the music theory assist, but it can be much more than that.
 
For example, say you wrote your song manually, such as a melody track using your own chord progression.  Then you got inspired and put down a dozen more tracks in your song that harmonize with that initial progression.
 
But wait, what if you then decided to alter one chord in the melody that didn't work harmonically with your other 12 tracks?
 
You could edit all the other tracks manually.  Or, if all of those tracks were following a chord track, then you could simply make the chord change to the chord track and the change would instantly ripple through all of your tracks!
 
Which workflow would you prefer???

I just sprung the upgrade fee to Studio One v.4 for this feature, only to discover there's no 32-bit version anymore, meaning I cannot use my 32-bit plugs in S1 anymore. Yes, I know, JBridge. More money.
 
I'd rather have paid Cake for an equivalent feature.

jpetersen
I just sprung the upgrade fee to Studio One v.4 for this feature, only to discover there's no 32-bit version anymore, meaning I cannot use my 32-bit plugs in S1 anymore. Yes, I know, JBridge. More money.
 
I'd rather have paid Cake for an equivalent feature.

It would be cool if Cake would add this, but I suspect it will be a long time before any new major features are added to Cake, just when they are trying to finish ironing out the bugs they already have. It's a free DAW now, so no money to be made adding core features.
 
It is convenient that Cake already has built-in bit bridging for plugins, but it seems to be common advice around here to migrate to 64-bit plugins wherever possible anyway to minimize incompatibilities.
 
I think 64-bit only is the trend we are beginning to see all over, as developers choose to spend their resources on the mainstream.  Maybe instead of JBridge, a good plan would be to finish existing projects in your current DAW with your 32-bit plugs, and then find 64-bit replacements for them when starting new projects in S1 v4.

abacab
 
 
But wait, what if you then decided to alter one chord in the melody that didn't work harmonically with your other 12 tracks?
 
You could edit all the other tracks manually.  Or, if all of those tracks were following a chord track, then you could simply make the chord change to the chord track and the change would instantly ripple through all of your tracks!
 
Which workflow would you prefer???

 
It depends. Small steps will work, greater steps (i.e. greater than a third) are a bit difficult. You've to adjust manually. That means: new recording or melodyne or prv. 
 
cheers :) 

I think complaining about not being Ableton to use your 32 bit plugins in a modern DAW is like complainging you can’t redeem all the green stamps you collected decades ago are useless. At some point legacy technology becomes more trouble than it is worth. If that 32 bit plug means that much, just keep an old install around of a DAW that utilizes it.

mkerl
 
That means: new recording or melodyne or prv.

 
Or chord track.  Then you could make BIG changes in one step too.  

dubdisciple
I think complaining about not being Ableton to use your 32 bit plugins in a modern DAW is like complainging you can’t redeem all the green stamps you collected decades ago are useless.

It's like buying a modern amp and discovering they're saving money by nixing the passive channel.
 
From now on new amps are only going to support active guitars.
 
I can't use my guitars collected decades ago and are useless unless I buy a preamp (in this case: JBridge)

abacab

mkerl
 
That means: new recording or melodyne or prv.

 
Or chord track.  Then you could make BIG changes in one step too.  

Chord track has limits when it comes to BIG changes. It's in the nature of things. You can experiment with different modes, but more often than not you have to adjust the result to make it sound good. Manually.
 
cheers :) 

jpetersen

dubdisciple
I think complaining about not being Ableton to use your 32 bit plugins in a modern DAW is like complainging you can’t redeem all the green stamps you collected decades ago are useless.

It's like buying a modern amp and discovering they're saving money by nixing the passive channel.
 
From now on new amps are only going to support active guitars.
 
I can't use my guitars collected decades ago and are useless unless I buy a preamp (in this case: JBridge)

Apples and oranges. You are comparing core functionality to simply outdated technology. The choice to use integrated amp vs preamp and amp has been around for decades because one does not make the other obsolete. Jbridge is a converter. A preamp is part of the process whether integrated or not