JClosed


Oh boy, oh boy, oh boy..... Automation modes. The overwrite mode seems to be just what I was missing in Sonar. Am I wrong when I think the "old" pre-X2 default mode was"touch"?

The old mode in SONAR was a mix of Touch and Overwrite. 


SP

Any chance of a (huge) overhaul of ACT within X2s life cycle?

TabSel


Any chance of a (huge) overhaul of ACT within X2s life cycle?

I don't know.


SP

Actually Touch mode is exactly what X1's mode was. 

Overwrite starts writing automation immediately when you roll the transport with an armed parameter (we prevent accidently adding all parameters via the write button)

Latch mode is similar to overwrite mode except its like a triggered overwrite mode - it only starts overwriting after you touch a parameter)

Both overwrite and latch are useful when you want to do roll the transport and erase prior automation as time advances. i.e. a what you hear is what you are recording mode.

That's exactly what I was hoping for. This will make Sonar far more usable if you have a control surface (I use a BCF2000) and want to correct (parts of) an already recorded parameter automation envelope (like volume). Great work!

Finally got a chance to watch the whole video:

It seems like the elegance and ease of use of the proi channel is moving into the track view which is going to be a time saver big time. Not having to ctrl+arrow to zoom is massive for me. Very Ableton! I really think Cakewalk is on the right track here- making things intuitive and easy without sacrificing power/adaptibility. And the old hotkeys will still be accessible for the grumpy old men. 

One thing that I wish sonar had to delete a track is just click and on it and press delete/backspace. Same for pro channel modules- to remove, click on and press delete/backspace. No "do you really wish to delete this?" or anything like that either. If a mistake is made the undo function can clean it up.

But excellent demo again Seth and Brandon- being able to put out LIVE an hour and a half of tightly bound information with no dead air, and humour and taking questions from the audience and leave us still wanting more.... great job!

(sorry, double post+ browser going crazy)

(edit: sorry for the wierd layout, I just can't get this to work!)

Tears of joy yes !!! 

See it's nice to be able to buss it.. that's good ... but here is one scenario I face often. 

Daily I record scores to picture, with tempo changes, meter changes and stuff... 

I do it on Sonar, because everyone knows X1 the second best DAW in the world ... (X2 being first)..lol

then I take my stem bounces to session musicans that are on Cubase or another DAW to record guitar/other stuff, or to a "pro" studio way too proud of running Protools HD..... 

Will I export my MIDI files, bring that into protools with all my 100 of MIDI tracks templates and useless MIDI data ? not really..

What if it does not work once in the session, and I have people waiting for this to happen? the meter is running ... !

I had problems importing stems and MIDI tempo maps into Digital performer for example... 

 Or what if there is an unknown offset in the way the MIDI data is inserted and once I have my overdub tracks back, it's out of sync?... it's too unreliable to do it this way, and it's time consuming.

I do a click track, everyone records to that click track, and I sync back the overdubs from the click track I receive.

but as you stated, it works by routing it to a VSTI ... but it's not so convenient ... it's extra steps for something that has the potential of being so simple and efficient..And I don't feel like patching this up as a loopback when it could be done internally.

I understand that not being able to EXPORT it is a limit that totally makes sense ( any Logic pro user probably have bounced mixes with un-intentional metronome over it too many times...I did, and still do!)

but by BOUNCING it to track, makes it a conscious decision to have it in your project. 

Another situation here. at some point, i did keyboard sequences for a big local cover band. 

They do medleys of 10 minutes, 10 songs, I was asked to send them stems (along with clicks), so that they can insert those into a "master" sonar project, where they don't have/need tempo sync, just bunches of files playing together.

I have 10 sonar projects, merging into 1, do I want to copy/paste MIDI tempo map 10X .. No !! it's way too much secretary work.. 

And what about count-ins ? they want 2 beats of count-in before each song (but the count in might occur in the end of last song, but in the new song tempo...) see how it gets somehow complex?

Or the band might also want to have time between songs to change instruments, load patches etc. So that means they will have to keep on counting clicks meanwhile they do their stuff if they want 20 secs? (remember, they just want 2 clicks before starting a song!) it's way too complicated, especially when all they need is to nudge audio data along with the audio click.  

So yes... having the option of bouncing to disk makes lots of sense to me ...;) 

I would dream of making a time selection-bounce to clip (select BUSSES-METRONOME) then OK ... the job is done ... !

Sorry for the long message! 

Excellent t-shirt Seth!

Which pack the the vocals come from?  I think you guys mentioned that they came from the Project 5 set of samples?