Razorwit
Hi folks,
I don't think it's working as the manual states (cloning only the MIDI track to the same synth)...at least not on my system. Here's what happens when I try it:
 
1. I create a project and create one S.I.T. That is the only track in the project. The synth that is associated with it shows up on both the track and the synth rack.

2. I clone the track

3. I end up with two new tracks, one MIDI and one synth output track. There is, as expected, no corresponding additional synth. So far this is mostly as the manual seems to state with the exception of the additional synth output that is created.

4. Here's the strange part. Now I have two synth output tracks (these are just audio tracks with their inputs set to the same output of the synth), and both of them are linked. Move the fader on one, and both move. Adjust the pan on one and the other one gets adjusted.
 
This is not the way things normally behave. If I insert a synth into the rack and create two tracks and assign the inputs to both of them to the same synth output they certainly aren't linked.
I understand that jb101 has been saying that cloning a S.I.T. only clones the MIDI track which is then routed to the same synth, but that's not how it working when I try it...
 
Dean

This is the behavior I see when I start a new project and clone a S.I.T. The funny thing is that when I clone a S.I.T. in a large project that I'm currently working on, I don't get this extra MIDI track at all. I just get one extra instrument track (that's linked in every way to the first). This is what I mean:
 

 

So the only thing being cloned is the input data to the soft synth. Even though track 27 and track 28 look separate tracks, they're really the same on the left of the pane. The data on the right of the pane can be adjusted for both tracks, while the controls on the left of the pane are linked. Might be useful if you wanted to split midi drums over multiple tracks while feeding a common drum synth.

ampfixer
So the only thing being cloned is the input data to the soft synth. Even though track 27 and track 28 look separate tracks, they're really the same on the left of the pane. The data on the right of the pane can be adjusted for both tracks, while the controls on the left of the pane are linked. Might be useful if you wanted to split midi drums over multiple tracks while feeding a common drum synth.

But surely if you wanted to have multiple MIDI tracks feeding the same drum synth, you'd just insert extra MIDI tracks and output them to that synth. There's no need to clone anything at all. 

Hey, I'm not trying to defend anything. I just wanted to know if I truly understood the problem.

The way I look at it is I think you are asking too much from simple instruments tracks. They were meant for quick and very easy usage. I have noticed lots of posts complaining about them because people want them to act as if they were regular MIDI and audio tracks. Clearly they are not. If one needs to do editing or any extra things using them it would be far better to use MIDI and separate audio tracks that have all the power people are looking for.   
 
The key word is simple.  When something is simplified it often means you lose power.   

John
The way I look at it is I think you are asking too much from simple instruments tracks. They were meant for quick and very easy usage. I have noticed lots of posts complaining about them because people want them to act as if they were regular MIDI and audio tracks. Clearly they are not. If one needs to do editing or any extra things using them it would be far better to use MIDI and separate audio tracks that have all the power people are looking for.    The key word is simple.  When something is simplified it often means you lose power.   

I think I agree with your sentiments, John.

The only thing that seems to confuse the issue is that the cloned track looks like a S.I.T., when, in fact, it is more like a MIDI track. I can see why people would want it to work differently, but it is what it is.

As I stated before, I use S.I.T. when I am initially sketching out an idea, but split them into Audio and MIDI tracks when I want to work on them. They are handy, but, as you say, they are simple. A little like me..

JB you are anything but simple. You and I agree most of the time if not all of the time. I knew you would see that post as I meant it to be. I thank you for that. Your method is the right method when using SITs One big reason CW allowed us to split them was just in case we needed to do further work on them.    
 
 

Sharke, did you say the options you have are for Clone and Copy?


If this is so, then wouldn't it be a copy of the track you would want, rather than a clone?
I, without reading the manual, would assume that a 'clone' would be a copy but with linked parametres, where as a 'copy' would be a copy of the track and everything associated, but without linking.
Clone = Linked
Copy = Unlinked (independant)

sharke
 
 
But surely if you wanted to have multiple MIDI tracks feeding the same drum synth, you'd just insert extra MIDI tracks and output them to that synth. There's no need to clone anything at all. 

This is true, it would be easier to create another midi track, but then you would also have to add in the midi/audio fx you used on the other track which would lead to more cpu usage.

John
The way I look at it is I think you are asking too much from simple instruments tracks. They were meant for quick and very easy usage. I have noticed lots of posts complaining about them because people want them to act as if they were regular MIDI and audio tracks. Clearly they are not. If one needs to do editing or any extra things using them it would be far better to use MIDI and separate audio tracks that have all the power people are looking for.    The key word is simple.  When something is simplified it often means you lose power.   

I guess if they really were "simple" then they would work as expected, and cloning them would result in nothing more than a clone of the track i.e. another instrument track with the same settings.