900 pages 
itās the War and Peace of manuals.
2 Likes
iāve been doing this for agesā¦ jam (or record hardware into) in liveā¦ make arrangementā¦ finalize 90% of edits etcā¦ then export to Logic for mixing and that last 10%.
used to do the same thing w/audiomulch as well. export the stems to Logic for mixingā¦ final editsā¦
iāve used Logic since 2.4 or something so itās pretty cozy and i like it for mixing. though itās not perfectā¦ itās just what i know and am comfortable with. every now and then i make a whole track in logic thoughā¦ and once in a while do the same in Live including mixingā¦
protools, logic, cubase, DP all have some deep tools for certain things and a different paradigm for mixing. theyāre more classic console + tape machine type scenarios. though in recent years theyāre throwing everything + the kitchen sink into them to make them more Ableton-like w/clips etc.
1 Like
For me the appeal of Cubase is how good it is for mixing, due to the mixer and Control Room, also the piano roll and MIDI editing is very good, the Project Logical Editor, and the chord track. Cubase really excels at being a comprehensive ābread and butterā DAW, mainly for composition using a more linear workflow. There is the arranger track which you can use to create sections that you launch like clips, but itās not the same thing at all like session view in Live.
All this talk about DAWs and their different strengths really highlights why I think itās so important that the DAWproject file format becomes widely supported, as I also use multiple DAWs and would love to have a more convenient way to transfer my work back and forth between them.
5 Likes
Most of that are devices manuals. Some of them are pretty complex.
1 Like
Reasonās is ~1.6k pages, and itās very good too!
Introduction | Reason Studios
1 Like
Funny. I use live to do the final touches the same way some of you use Cubase or Logic. Write in reason/hardware finish in Live.
Thatās why you like session view so much! You use live as just a sketch pad. Insert the Gus Fring āweāre not the sameā meme hereā¦
2 Likes
I think for most people this kind of workflow - write in one DAW, mix/master in another - is mostly about changing the āsceneryā and environment, with enforces one to commit and also to see & think the track in a different light.
So frankly, no wonder any combination works 
2 Likes
Nobody?
Or any other suggestions on how to easily record automation of external hardware knob tweaks into the arrangement?
I sure canāt be the only one struggling with this, right?
1 Like
I donāt use external MIDI gear so canāt help, but Iām curious why do you care that the CCs are captured in track automation and NOT inside of the clip?
MIDI CC messages are part of the āMIDI specā so their natural place is to be inside of the clip that contains the MIDI.
Sorry if itās a silly question
1 Like
How Ableton 12 perform on Macs with M1?
Using Bitwig for almost 10 years but would really like to get Ableton too because of M4L.
Iām using it on both an M1 Air 8GB and M1 Mini 16GB and havenāt noticed any performance issues.
1 Like
Well, if you automate a parameter of a software synth or fx, you do it in the automation lanes. It makes sense to me to be able to use hardware gear the same way.
It also gives a much better overview than hidden inside a clip.
It is also easier to see where in the global timeline youāre editing the automation.
However, I just found a max4live device ControlChange8.5 which might do the trick. Will try later.
2 Likes
Thank you for info. Might wait for black friday or xmas sale, hope it will be on discount.
If I bought one of the upcoming Mac minis with the m4 chip, is Ableton likely to run well on it straight off, or is there a wait while Ableton figure out compatibility? Iām unfamiliar with Apple.
itāll run fine. software for apple silicon machines is the same regardless if itās M1/2/3/4 etcā¦ ableton has been compatible with apple silicon for a while now. the MacOS may be another issue though i think itās fine based on everything iāve read. itās a new OS so all the software devs havenāt caught up w/it but most are fine even if their site says ādonāt update to sequoia yetā. so, donāt worry.
2 Likes
Live 12.1 does not work on my M2 Mac Mini.
ControlChange8.5 doesnāt work bidirectional either.
So far, CC Map8 works pretty much exactly how Iād like, but it doesnāt show its parameters to Push 
even though the developer said it should (but its years ago, so that functionality might have been broken with updatesā¦)
Yeah, for anyone new to Mac, the CPU is never a compatibility issue (with the exception of once-every-15-years transitions like what just happened with Intel to Apple Siliconā¦ but thatās done now, so donāt worry) but the OS upgrades can be tricky with audio software.
Some years, the changes break things, and if youāre buying a new Mac right after the new OS came out, it might have some issues with your existing software out of the box. This yearās update, Sequoia, has been a pretty smooth transition, though, so as @ignatius says, donāt worry if vendors havenāt officially updated their compatibility statements.
Thatās odd re: the Mac Mini M2. Live 12.1 works fine on the M2, and M3 macbooks in my household.
Could it be a storage or RAM issue?
1 Like