Yeah it would seem that instrument tracks have not been implemented properly and there are problems. It's a shame though, because I certainly can see the point of them. When they work properly, it just makes sense to have both the MIDI and the audio part represented by one track. And it's certainly a lot tidier to work with. 

jb101
I only tend to use S.I.T. when I am sketching an idea out, and replace them with synth and MIDI tracks when I get going. I guess that's why I've not noticed this.

Mostly I clone audio tracks, e.g. to process a bass part as separately as D.I. and through an amp sim.

Have you ever tried putting the amp sim on a bus and mixing it into the D.I. track via a send? It means one less track to worry about in your track pane...

Yes, it would be nice if they worked at well and the audio+MIDI solution but they don't. As to what makes sense, that is a judgement call. For myself, cosmetics don't matter nearly as much as project stability.

sharke
 
Have you ever tried putting the amp sim on a bus and mixing it into the D.I. track via a send? It means one less track to worry about in your track pane...

Yeah but that just adds another track to the bus pane instead. At least the track pane has folders which allow one to group the tracks into a folder and collapse it. I have used both clones and sends sometime both at the same time, it may depend on sunspot activity as much as anything else as to what method gets used.

scook

sharke Have you ever tried putting the amp sim on a bus and mixing it into the D.I. track via a send? It means one less track to worry about in your track pane...

Yeah but that just adds another track to the bus pane instead. At least the track pane has folders which allow one to group the tracks into a folder and collapse it. I have used both clones and sends sometime both at the same time, it may depend on sunspot activity as much as anything else as to what method gets used.

As Scook said, I prefer to have two bass tracks in a folder, which are then routed to a bass bus, where I often add the 4K bus compressor, and maybe EQ to help blend them together.

For me this ends up less cluttered and less confusing for simple brain.

Back in the day:

Simple instrument tracks were a feature added due to users requests about a simple way to add a ss, then route it to a midi track, then route it to an added audio track.

It was meant to be different.

It's not a bug.I don't believe it is anyway.

Grem
Back in the day:

Simple instrument tracks were a feature added due to users requests about a simple way to add a ss, then route it to a midi track, then route it to an added audio track.

It was meant to be different.

It's not a bug.

I understand that SIT's are "meant to be different" from audio tracks and MIDI tracks - they are different by definition. It's not clear why cloning should behave differently with them. An instrument track still represents the same thing as an audio track in the context of your mix, i.e. it's "another instrument part." Therefore I see no reason why anyone would have a different motive for cloning them. 

So have we figured out how to unlink the parameters though? I mean it doesn't really make any sense to have cloned SITs follow every change. All that would do is just make things louder and even if you did it just to have the same synth setup for a different performance within the project not being able to mix that new performance independently... well, that's just weird.
 
IDK... maybe I'm missing something. I usually am.

Beepster
So have we figured out how to unlink the parameters though? I mean it doesn't really make any sense to have cloned SITs follow every change. All that would do is just make things louder and even if you did it just to have the same synth setup for a different performance within the project not being able to mix that new performance independently... well, that's just weird.
 
IDK... maybe I'm missing something. I usually am.

As far as I was able to establish last night, there is no way of unlinking the controls once you've cloned an instrument track. You're right, it doesn't make any sense when you take the reasons for cloning a track into consideration. 
 
I guess I should have read the manual's entry on cloning instead of Cakewalk's online help document, which doesn't mention how instrument track cloning is different. 

Beepster - "So have we figured out how to unlink the parameters though? I mean it doesn't really make any sense to have cloned SITs follow every change. All that would do is just make things louder and even if you did it just to have the same synth setup for a different performance within the project not being able to mix that new performance independently... well, that's just weird.

IDK... maybe I'm missing something. I usually am."

If you clone a S.I.T. It only creates a new MIDI track linked to ONE soft synth. There are no linked controls, as there is only one soft synth, that both the original track and the cloned track use.

You cannot unlink the two "Audio tracks", as there is only one. Two MIDI tracks, if you will, both routed to ONE synth.