• SONAR
  • What's Your Favorite Underrated Sonar Feature or Technique? (p.6)
2014/05/30 22:24:56
b rock
Anderton
I also need to give a nod to the draw tool for generating waveforms for automation. It's not just that you can create waveforms (tremolo, anyone?) but that it's so easy to vary the height and phase. The random option does instant sample-and-hold effects, which is also cool. I hardly ever see anyone mention this feature.

 
Perfect fit for the theme of this thread.  Adding to the Draw Tool tips:
 
If you output the Draw Tool automation to another MIDI track (through a virtual MIDI cable), it will be converted to a MIDI CC message.  From there, it's a snap to create a library of modulation effects (virtual LFOs).  Extensible 'Groove Clips' of vibratos, tremolo, pans, sweeps, S&H ... varying rates, depths, fade-ins/outs, combinations of waveforms.  A drag 'n' drop collection of control clips that works across any synth, effect, or most track control.
2014/05/30 22:26:29
scook
this is the stuff
2014/05/30 22:49:41
Anderton
b rock
If you output the Draw Tool automation to another MIDI track (through a virtual MIDI cable), it will be converted to a MIDI CC message.  From there, it's a snap to create a library of modulation effects (virtual LFOs).  Extensible 'Groove Clips' of vibratos, tremolo, pans, sweeps, S&H ... varying rates, depths, fade-ins/outs, combinations of waveforms.  A drag 'n' drop collection of control clips that works across any synth, effect, or most track control.



Wow. Just...wow!
2014/05/30 22:56:19
b rock
dubdisciple
The ability to bounce arpreggiator to midi notes that can be edited. Arpreggiators are great but can be stiff and monotonous. Being able to instantly render out all that is heard from pressing one note or chord opens a lot of flexible ways to edit and add variety.


Automation on arp parameters can help (when they work).  But the 'hidden gem' feature here is the potential to customize your own arpeggiator sequences.  I'll shill my own freebies again here, but strictly as examples:
 
Alesion ARP Presets  Alesion Pattern Construction Kits
 
It should be easier in Sonar X to create your own / convert to .ptn files as the basis for arpeggiator customization (without having to resurrect Project5 as a translator).  Granted, there are a lot of shipping .ptn files in the Sonar package.  I just haven't found those to be the most useful for mining the deep potential.
2014/05/31 01:27:23
dubdisciple
B rock..I will try these later. Thanks!
2014/05/31 02:06:53
konradh
About the Sonitus multiband:  Using other tools, I have never been about to find the right frequency to cut pops or to reduce sibilance.  I know in theory, but can't ever seem to get good results.  Suggestions?
 
*I have sometimes eliminated pops with very tedious and careful wave trimming, but that is not ideal and it is hard to get just right.
2014/05/31 09:10:37
icontakt
I don't know if the Matrix view is underrated because I heard that it's actually not as flexible as Live's equivalent feature, and I still don't feel like using it for songwriting even after reading Craig's recent thread on it and doing some experiment.
 
However, I appreciate that Sonar has it. A singer I work with is lazy so he doesn't try to remember each melody in the harmony I create in the PRV in advance. On the other hand, I'm too busy to remember the melodies so I need to play the MIDI clips and let him hear the exact lines he needs to sing. To do that, you'd normally have to unmute or unarchive the MIDI track, navigate to the start of the clip, start playback, and then re-mute or re-archive the track before recording the vocal. But there's an easy way. What I do prior to the recording session is to convert the MIDI clips for all harmony parts into groove clips (no need to bounce them to audio clips) and then drag them into the Matrix view. When I need to tell the singer what melodies he needs to sing for the section, I just hit Alt+5 to open the Matrix view, tell the singer "Sing this melody," and click the cell in the Matrix view. There's no need to unmute or unarchive the MIDI tracks because even when they are archived you can still hear the sound the Matrix cells play (so you can even hide these MIDI tracks from the Track view).
 
Also, I import some background music files into the Matrix cells and play them when the singer needs to relax a bit (before starting recording, etc.).
 
 

(Larger image here)
2014/05/31 11:41:56
Beepster
Well probably not underrated and not really my "favorite" but the Multi-Dock is a freaking life saver for me considering I work on a single screen and honestly don't think I'd really want a second screen even I could afford it (I would just get a BIGGER screen). I would like to see some improvements on it (like being able to cycle through whatever is in the dock using the arrow keys, being able to drag the tabs around to where I want them, an option to fullscreen it with a simple keybinding, etc...) but damn is it a million times easier to manage a project instead of having a million Windows floating around and having to hunt through them to find what you want.
 
As far as techniques I was told this is a little weird but I like using the Comp mode for my MIDI drums. I treat it just like I do an audio track. I slam out sections one at a time doing multiple takes with different ideas then see what sounds right, flatten the stuff I choose (or make multiple full versions) and clone the track then archive the original and delete everything except the flattened take lanes.
 
Then I listen to those and practice along or just play to my scratch tracks basing my performance on what worked from the originals. At this point I try to perform the song in it's entirety multiple times trying out different fills, turnaraounds, etc, recording each one. I might end up with a dozen performances.
 
Once I've got a bunch of decent performances or mostly decent performances I start using the Fast Comping approach (slice the song up into relevant sections, go into Fast Comp mode, use the arrow keys to audition and choose the best for that section, etc... just like you'd do with a vocal track or something).
 
I'll listen back to the whole thing to make sure everything flows properly and my splits are in the optimal spots (like if there is a fill that steps over the measure line or something but I want to use it I'll make sure I get the whole fill and then correct it later). Once it's good I flatten it down, clone/archive/delete unneeded lanes so I am working with ONE lane again (BTW I hide those original tracks too so I'm always looking at the right tracks/clips).
 
After all THAT I pop open the clip in the PRV and comb through the whole thing moving notes, adjusting velocities, getting rid of double/bad notes, inputting missed notes, etc. (this takes can take a loooong time but is worth it because Quantize doesn't work on my chaotic stuff).
 
Now I've got a good, solid drum track to write/record my bass part over top of.
 
That's about as far as I've gotten so far with my current project (first one in X3) but my next plan is going to be either go back and redo the drums live from the controller again so they compliment the newly written bass parts even more or I might just use the same take and just do my revised drum track in the PRV (to save time but I probably will do it live stating the whole process over again).
 
I can't do double kick with the pK (it only allows for one "expression" pedal which I have but it's awkward to play) and I can only play it so fast before it starts dropping notes (as well as how weird it is playing "drums" on the thing and that I'm an "okay" drummer but not as good as the material requires) so there will be parts where I'll probably wipe out the double kick notes in the PRV and then do some finger double kick in Sound On Sound mode then bounce it into the original clip or simply input that stuff directly into the PRV (but that's not nearly as fun... lol).
 
It is definitely a LOT of work but when I consider how much time I used to spend in band practices 2-3 times a week, every week, to obtain middling results on my drum parts and NEVER being able to capture a decent recording even with hours of setting up mics, mixers, moving my DAW into the band room, etc then this way is actually WAY quicker and sounds a million times better.
 
The only problem is apparently when you use Comping to work on MIDI clips like this it REALLY strains computer resources because instead of like audio clips which all use the same file from the pool every time you split a MIDI clip it creates two copies of the original because it wants to treat them as a whole new clip for separate PRV editing. This can be avoided by switching off Non-Destructive editing but that doesn't work for me. So what started happening was because I'd be working with a dozen take lanes all chopped up into a dozen or so sections I ended up with... well... a LOT of MIDI clips all being read at the same time even if only one was audible (thank you scook for teaching me about that). This gave me frequent dropouts. The solution was to CRANK my hard disk buffers and to make sure to delete or archive any unneeded MIDI clips (thus the constant flattening/bouncing/archiving).
 
So yeah... convoluted? Weird? Crazy? Perhaps but this is REALLY working out better for my drum parts than I ever could have hoped and I'm just OCD enough to actually enjoy doing it.
 
Oh and another feature that rules is the "Archive" function. If that wasn't there even my ultra high powered PC would be brought to it's knees very early on in my writing process OR I'd have to constantly be ditching material that I may or may not want to use. I prefer to just go nuts on stuff until the part is written THEN go back and delete the crap. That way my creative flow isn't constantly being interrupted... at least not by that type of thing. Plenty of other interruptions in my life as it is.
 
And if you read all that... well... perhaps you are just as crazy as I am. lol
2014/05/31 11:53:42
Glyn Barnes
Groove Quantize. A MIDI quantize function that can add rather then remove "feel"
2014/05/31 12:18:26
rbowser
Beepster...the Multi-Dock is a freaking life saver for me considering I work on a single screen and honestly don't think I'd really want a second screen even I could afford it (I would just get a BIGGER screen)  I would like to see some improvements on it (like being able to cycle through whatever is in the dock...
...a million times easier to manage a project instead of having a million Windows floating around and having to hunt through them to find what you want...


Hey, Beepster - Reading your post sent me out on a hunt, but I didn't bag the answer.  There Is a keybinding to step through the open tabs without using the mouse - But I couldn't find the info anywhere.  I just remember it was mentioned on a recent thread that you could step through the open tabs like that.  Hmm. - I primarily work in the PRV and keep it open, so am not concerned about the rare occurrence of needing to open another open tab.

But the multi-dock has been around for a very long time, it's not new with the X series. It just looked less clunky in 8.5 than it does now, but worked the same - Absolutely The Main Ingredient to developing a good work flow.

I can't imagine the scenario of having all those views floating around!--especially on one screen.  Crazy.

Having two screens is extremely cool, however.  Before I had a second screen, I thought it sounded like a rather over-the-top luxury that wouldn't make much difference.  It just took having the actual experience of using two screens to grasp why it's so helpful.  Now I would totally freak out if I had to go back to one screen.  Having major work spaces open at the same time, taking up the whole screen, nice and big - that's not luxury, it is a Major work flow enhancer.

ANyway - Basically wanted to give a +1 for the good ol' multi-dock, and maybe attract the attention of someone who can jog my memory about what shortcut there is for stepping through the tabs.

Randy
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account