DUPLICATE command for SONAR

Paste Special lets you specify any number of repetitions. For example if you have a four on the floor kick that lasts for one measure, copy it, place the Now time at the end of the meausure, and specify 100 repetitions or whatever when you paste special.

John
For audio if you wish to repeat an audio clip turn it into a loop. Once a loop you simply drag out the end to cover as many measures as you like.

Great point, especially because if you're turning audio into a loop and not changing the tempo, there won't be any change in sound quality. 

siordanescu
Groove clip looping is also a useful tool!
 

Right and I think I covered that.

miracledee
Duplicate tool is particularly useful when you arrange samples on the audio track itself (to form a 1 bar rythm) and then duplicate it , add some variation to some samples, then duplicate...add variation & so on. 

 
It sounds like you're describing successive duplications rather than duplicating a clip multiple times with a single command. If that's the case, I don't understand how what you describe is different from bouncing the samples to create a clip, then ctrl+drag to duplicate the clip for modifying, followed by successive ctrl+drag/modify operations. Ctrl+drag takes the same number of keystrokes as Ctrl+B.
 

We answered the way we did in response to a question. If we were really adverse to a feature request there wouldn't be an entire forum dedicated to it. When a question is posted here its handled as such. Unless there really isn't a possible answer. In that case we will move it to the feature requests forum.
 
 

The title is. Yes I did read the OP. I actually went to some trouble trying to help the OP out. When something is posted here and there is an answer the forum tries to provide it. 
 
As a user I knew that what the OP wanted to do was doable in Sonar. Perhaps not in the way the OP wanted but very doable. Therefor I answered as I believed the answer to be. 
 
Why people find fault when no fault is intended or done is beyond my understanding. Offering a way to do something is not cause for recriminations.    

John
The title is. Yes I did read the OP.

no, the title of the thread is a statement, and the op is a feature request, a la "i'd like to do this..." and not "how do i do something like this..." - it's about the workflow rather than the achieved effect

John
One can choose to see it in anyway they want. If a question mark had been on the title how would have viewed it? 

it wasn't a question - did you read the op?

miracledee
Based on the ctrl+drag suggestion, I did a little test.
I created a simple 1bar beat in Sonar. Kick, hats, snare on 3 different audio tracks.
Same arrangement done in FLStudio Playlist view.
 
Now I measured the time it took for me to make 7 more copies of the 1bar beat (for a total of an 8bar section).
First Sonar (ctrl+drag) - result : 15seconds
Next FL (ctrl+B) - result : 3seconds.
The difference is considerable.

Well of course, that's obvious. But I don't understand the point of a test that doesn't relate at all to what I said, which was "It sounds like you're describing successive duplications rather than duplicating a clip multiple times with a single command. If that's the case..." because you said "duplicate it, add some variation to some samples, then duplicate...add variation & so on."
 
In the context of what you seemed to be describing, with snap on it takes 1200 ms in SONAR to click a clip and drag it to the right so it snaps to the end of the existing clip. To click on the clip and type a keyboard command takes about 800 ms. I verified this by doing a screen movie grab and putting it on the Vegas timeline. So I think what I presented was a reasonable workaround. 400 ms is negligible compared to the time you'll spend creating the variations in between copies.
 
Now make 8 copies of a 1-bar loop by ctrl+B compared to dragging a loop out to 8 measures and let me know which is faster. Different techniques are faster for different contexts.
 
I never said it wouldn't be useful to have an additional keyboard shortcut to duplicate a clip. But at least for now, SONAR doesn't have one. However there are three ways to duplicate clips and they were mentioned in case you're not aware of them. None of us can know what you know or don't know about SONAR, all we can do is make suggestions for ways to accomplish what you want.
 

pwalpwal
 
it wasn't a question - did you read the op?

Then it was posted in the wrong forum. You can hardly blame John, Subtlearts, or me, for assuming the OP posted in the forum "focused on the use of SONAR software" because he wanted to know about the use of SONAR software.
 
I challenge anyone to show me anything said in any post in this thread that "demonized" the OP. I suspect this post will go unanswered.

pwalpwal

Anderton

pwalpwal
 
it wasn't a question - did you read the op?

Then it was posted in the wrong forum. You can hardly blame John, or me, for assuming the OP posted in the forum "focused on the use of SONAR software" because he wanted to know about the use of SONAR software.

as hosts, you both should be able to spot the difference, and should also have moved it to the correct forum

 
No. I feel hosts should not arbitrarily second-guess an OP's intentions. I think it's condescending to say "we know better" and act in a way that may negate the OP's intention, given where the thread was posted.
 
Also, this is a FORUM whose premise is discussion. Helping in a polite, constructive, fact-based way will benefit others who want to know how to get the most out of SONAR. It is those making totally unfounded comments about "demonization," not the OP or those suggesting other methods of duplication, who have put a negative spin on an otherwise helpful discussion. 
 
Based on your premise that this was just a feature request and that a discussion is inappropriate, then you're probably equally upset I did not delete the post from Wicked giving specific examples that went beyond what the OP posted. But I think Wicked contributed something of value to the discussion as well. 
 
There is also nothing preventing the OP, or you, or me from posting a feature request for a duplicate command and thus leaving this thread, which contains useful and constructive information, intact.
 
Miracledee clearly understood we were trying to help, as he was polite enough to thank us for our replies and provide additional information that furthered the discussion. I doubt he felt "demonized," and I continue to challenge anyone to show anything that would indicate any disrespect or demonization of the OP. 

bronsoncoxWhether or not it was a formal feature request in the correct forum, you can very clearly interpret it as such.

 
Yes, you can. But I didn't, because people usually post in the SONAR forum looking for how to accomplish something. People often ask for a feature that already exists, or for which there's a reasonable facsimile. It's not always a good idea to assume that someone posting, as well as those following the thread, have an extensive knowledge of SONAR.
 
The thread title is: "Duplicate Command for SONAR." There are several ways to interpret that, and people who want to know about duplicate commands in SONAR, or want to discuss the topic, will likely click on that thinking it relates to something they might want to know. I try to write responses that are useful to anyone who might check a thread, for whatever reason they click on it, because a forum is about discussion. 
 

Once again, a simple "you should submit an FR" would have sufficed.

 
Similarly, a simple "I assume he just posted in the wrong forum and needs to know he can submit a feature request because I think he wants a very specific duplication command, not just info on 'Duplication Command for SONAR' as the thread title suggests" would have sufficed rather than choosing to go down the "demonization" path.
 

Instead, Post #10 is what we get. Read it as "well, my workaround is just as good as your idea if not better".

 
I prefer you read it as what I said. The OP presented new information in Post #7 about doing successive copies and making variations. That seemed different from what he said originally, which is why I specifically stated "It sounds like... and "if that's the case." If I'm not sure I understand something, I ask a question and seek clarification. 
 

"Well of course, that's obvious. But I don't understand the point of a test that doesn't relate at all to what I said..."
Post #20 is where it stopped being about the OP and started being about the Anderton.

 
No, it became about a test that was not what the OP described wanting to do in post #7, so I said I didn't understand how that related to successive duplications. Maybe it does, but if so, then I still don't get it.
 

RE: my passive-aggressive statement, please go back and really re-read posts #20-22.

 
I did. The only people who had posted prior to your throwing the accusation of "demonization" into the mix was me, subtlearts, siordanescu and John. You referred to "demonization" as the "standard operating procedure," yet none of us demonized anyone. You made that tie-in more specific by bringing up "workarounds," which is what the four of us presented. You say it wasn't directed at any of us. If that's true, it seems extremely odd to introduce demonization in the context of a thread where up until your post, there was a polite, civil discussion intended to help the OP and those reading the thread to understand duplication commands for SONAR. 
 

Also, 1200ms vs 800ms. #science
 
I would recommend going back and duplicating each of those video clips a few more times to see how significant a 3 to 2 ratio might be. It adds up after awhile.

 
I wrote: "400 ms is negligible compared to the time you'll spend creating the variations in between copies." In fact I confirmed it's faster to use Ctrl+D. However, in the spirit of full disclosure, I've had second thoughts and I may be wrong about that depending on the particular task at hand, the number of clips that need to be duplicated, the extent of the variations, and whether the person is a touch-typist or not. I can explain further if you'd like. I spend a lot of time studying clickstreams in product development situations and when writing documentation.
 
The bottom line is if you know ALL the tools available to perform a function, you can choose the right tool for the right job.