There is a way to do this in Live, it's just really clunky. I set up my mapping for my EZD/Kontakt libraries, save the multi group in the User Library and then i'm set.EnGee wrote: Sun Aug 20, 2023 9:46 pm The only things that I don't like in Bitwig (and Live) are:
1. No mapping for 3rd part drums. So, if I want to use Addictive Drums and do my beats with it, I choose either S1 or Cubase.
If you had to stick to one DAW, which one would it be?
- KVRist
- 261 posts since 5 Jan, 2018 from Asheville, NC, USA
- KVRAF
- 4066 posts since 3 Jul, 2022
Common, you are "a bit" cool!sQeetz wrote: Sun Aug 20, 2023 4:37 pmI'm neither cool nor successful and still like Live best... It's the one DAW simple enough to not get in the way.soulata wrote: Sun Aug 20, 2023 2:01 pmI use Ableton Live as well but always get a feeling it"s only for the cool kids or cool, very successful people which I am not.
- KVRAF
- 4066 posts since 3 Jul, 2022
I regret I didn't click well with Live because their whole ecosystem is really interesting...dellboy wrote: Sun Aug 20, 2023 4:46 pmMaybe that's a good thing because it makes it easy and simple to use. In contrast I downloaded the Bitwig demo yesterday and spent a good half hour trying to figure out the browser and how to load stuff. Ableton's browser is simplicity itself.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7984 posts since 15 Aug, 2003 from seattle
Why Bitwig and Live don't become my 100% full time DAWs.EnGee wrote: Sun Aug 20, 2023 9:46 pm The only things that I don't like in Bitwig (and Live) are:
1. No mapping for 3rd part drums. So, if I want to use Addictive Drums and do my beats with it, I choose either S1 or Cubase.
2. Can't play midi patterns for drums. There are tons of midi patterns for advanced drumming and again only with S1 or Cubase I can play those midi and make Addictive Drums playing them, for example.
1. Super simplistic quantize settings.
2. No articulation maps for orchestral libraries.
3. no ARA or onboard solution for pitch correction at Melodyne level.
4. No groove pool in Bitwig, or video scoring, or SysEx support.
5. No count off click for just practicing in Live, you have to quickly turn off record while count off is happening. No click variations to speak of.
6. Simple MIDI editing in both.
7. Simple and basic arrangements that pale in comparison to DP, Logic or Cubase.
8. Limited selection of possible key shortcuts in Bitwig, hardwired super limited selection in Live.
9. "Always On" real time engines in both, so much much lower tracks counts in both. A quick Diva test had 16 tracks with 6 voices before overload in Bitwig and Live, VS 22 in Digital Performer and Reaper on the same machine with the same settings. that's 72% of Reaper and DP's capabilities, and with slight variations, that's been consistent for over a decade.
10. I find that I enjoy using both Bitwig and Live if I'm doing a song with 20 or so tracks at most, beyond that I end up feeling like I'm babysitting the UX of the DAW compared to the "dinosaurs", the older DAWs with "bloatware" have features for managing large projects, whereas I don't feel like Live or Bitwig were designed for that.
Of course use whatever you enjoy, and I own and use both, I'm just stating this because people constantly mention Bitwig and Live for their UX, but IMO it comes at a cost, you lose depth when you sacrifice functions for intuitiveness.
- KVRAF
- 4066 posts since 3 Jul, 2022
Interesting analysis.machinesworking wrote: Mon Aug 21, 2023 12:30 amWhy Bitwig and Live don't become my 100% full time DAWs.EnGee wrote: Sun Aug 20, 2023 9:46 pm The only things that I don't like in Bitwig (and Live) are:
1. No mapping for 3rd part drums. So, if I want to use Addictive Drums and do my beats with it, I choose either S1 or Cubase.
2. Can't play midi patterns for drums. There are tons of midi patterns for advanced drumming and again only with S1 or Cubase I can play those midi and make Addictive Drums playing them, for example.
1. Super simplistic quantize settings.
2. No articulation maps for orchestral libraries.
3. no ARA or onboard solution for pitch correction at Melodyne level.
4. No groove pool in Bitwig, or video scoring, or SysEx support.
5. No count off click for just practicing in Live, you have to quickly turn off record while count off is happening. No click variations to speak of.
6. Simple MIDI editing in both.
7. Simple and basic arrangements that pale in comparison to DP, Logic or Cubase.
8. Limited selection of possible key shortcuts in Bitwig, hardwired super limited selection in Live.
9. "Always On" real time engines in both, so much much lower tracks counts in both. A quick Diva test had 16 tracks with 6 voices before overload in Bitwig and Live, VS 22 in Digital Performer and Reaper on the same machine with the same settings. that's 72% of Reaper and DP's capabilities, and with slight variations, that's been consistent for over a decade.
10. I find that I enjoy using both Bitwig and Live if I'm doing a song with 20 or so tracks at most, beyond that I end up feeling like I'm babysitting the UX of the DAW compared to the "dinosaurs", the older DAWs with "bloatware" have features for managing large projects, whereas I don't feel like Live or Bitwig were designed for that.
Of course use whatever you enjoy, and I own and use both, I'm just stating this because people constantly mention Bitwig and Live for their UX, but IMO it comes at a cost, you lose depth when you sacrifice functions for intuitiveness.![]()
2 remarks though:
1 - There is a ton of configurable shortcuts in bitwig that you can map however you want. I don't get what you are missing.
2 - Both bitwig and live comme with a ton of features that don't exist elsewhere. Your point that each daw has specific features is certainly true but saying that cubase or Logic have a superset of features of live and bitwig is certainly not (you don't explicitly say that neither).
I agree that real time has its advantages and drawbacks. Like sandboximg, you get a rock solid stability while losing certainly marginally on resource consumption.
-
- KVRAF
- 9144 posts since 7 Oct, 2005
I understand your points and I agree with them. If I'm into film scoring or orchestral works (or any work that require large projects), mostly my choice would be between Cubase and Logic (I don't know or tried DP or Pro Tools). However, I'm into small projects with tracks number don't exceed 16 (including drums!), so Bitwig or Live is perfect for what I want. Of course I could also use Cubase or Logic and I will be also fine! But the 'depth' is what I don't need most of the times, as my editing is not that demanding and I don't use MPE or articulations, but I do use modulations and automations (not that complex). So, 'compact' DAW feels more comfortable to usemachinesworking wrote: Mon Aug 21, 2023 12:30 am
Why Bitwig and Live don't become my 100% full time DAWs.
1. Super simplistic quantize settings.
2. No articulation maps for orchestral libraries.
3. no ARA or onboard solution for pitch correction at Melodyne level.
4. No groove pool in Bitwig, or video scoring, or SysEx support.
5. No count off click for just practicing in Live, you have to quickly turn off record while count off is happening. No click variations to speak of.
6. Simple MIDI editing in both.
7. Simple and basic arrangements that pale in comparison to DP, Logic or Cubase.
8. Limited selection of possible key shortcuts in Bitwig, hardwired super limited selection in Live.
9. "Always On" real time engines in both, so much much lower tracks counts in both. A quick Diva test had 16 tracks with 6 voices before overload in Bitwig and Live, VS 22 in Digital Performer and Reaper on the same machine with the same settings. that's 72% of Reaper and DP's capabilities, and with slight variations, that's been consistent for over a decade.
10. I find that I enjoy using both Bitwig and Live if I'm doing a song with 20 or so tracks at most, beyond that I end up feeling like I'm babysitting the UX of the DAW compared to the "dinosaurs", the older DAWs with "bloatware" have features for managing large projects, whereas I don't feel like Live or Bitwig were designed for that.
Of course use whatever you enjoy, and I own and use both, I'm just stating this because people constantly mention Bitwig and Live for their UX, but IMO it comes at a cost, you lose depth when you sacrifice functions for intuitiveness.![]()
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
- KVRAF
- 2469 posts since 25 Sep, 2014 from Specific Northwest
Oh crap! Škoda has a haček on it? I've been pronouncing it wrong all these years!
This is becoming a pattern. I've been pronouncing 'güiro' wrong too, until I saw the word in a Spanish sentence. Typical Americans can't write foreign words correctly...
I'll never be one of the cool kids.
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
Unfortunately you don’t like the fact that Excel looks like AbletonJac459 wrote: Mon Aug 21, 2023 12:12 amI regret I didn't click well with Live because their whole ecosystem is really interesting...dellboy wrote: Sun Aug 20, 2023 4:46 pmMaybe that's a good thing because it makes it easy and simple to use. In contrast I downloaded the Bitwig demo yesterday and spent a good half hour trying to figure out the browser and how to load stuff. Ableton's browser is simplicity itself.
You should stop using Microsoft then
ABEFLGMOPPRRST 
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7984 posts since 15 Aug, 2003 from seattle
There are twice as many shortcuts in Logic and DP, three times as many likely in Reaper. This has to do with a much wider set of tools for linear arrangements than Bitwig has. This goes to the next point...Jac459 wrote: Mon Aug 21, 2023 1:32 am 2 remarks though:
1 - There is a ton of configurable shortcuts in bitwig that you can map however you want. I don't get what you are missing.
Well it would be a lie to say they don't really. Barring the Grid, Bitwig is very limited compared to Logic, Reaper, or DP (I've never been a Cubase user so I can't qualify there), just in terms of arrangement timelines, and all that entails. Where they both excel is with uninterrupted audio, time stretching, (not pitch really though), modern control surface support miles above the others, and in the case of Bitwig MPE and CLAP support, (although DP does MPE well and Reaper has CLAP).2 - Both bitwig and live comme with a ton of features that don't exist elsewhere. Your point that each daw has specific features is certainly true but saying that cubase or Logic have a superset of features of live and bitwig is certainly not (you don't explicitly say that neither).
You can't really compare the arrangement tools in them though, the Bitwig/Live method is about simplicity, not extensibility. Doesn't mean you can't get work done in them, just that Logic and DP have 30+ years of development
For sure, although these days I'm pretty good at managing plug ins and finding the sketchy ones. It's a feature all DAWs should have. It's the only DAW I will run Hybrid 3 in or any of the older Air plug ins that haven't been worked on in years. To be honest though, I haven't seen any significant increase in track count running all plug ins sanboxed or running them in Bitwig, they mention Memory in terms of system resources and there is zero change in track count or CPU use from running them all sandboxed. So IMO that part has little to do with Bitwigs CPU use, that's more about not having some sort of secondary buffer or rendering of audio not in real time, for tracks that are not record enabled. This is really super easy to prove if you own Logic, DP, Reaper etc. Bitwig and Live will show almost ZERO difference in CPU when a track is armed or not, but get 70% of what DP, Logic etc. can get CPU wise. Those DAWs on the other hand have significant hits on CPU from record arming tracks, since it gets rid of that buffer that gives them extra CPU.I agree that real time has its advantages and drawbacks. Like sandboximg, you get a rock solid stability while losing certainly marginally on resource consumption.
Digital Performer introduced a Live Performance Mode, that to a degree acts like what Live and Biwig do, it's a step towards a solution that doesn't ignore the benefits of either method.
Basically there are significant advantages to either approach, my biggest issue with Bitwig is it follows Lives approach too much, some parts are simple, then you can go into the weeds building an FM synth in the Grid, the same thing is true in Live with Max. Don't get me wrong though I love them both, it's just that I do end up missing the old school feature set when I work in them at times. My perfect DAW would be Bitwig mixed with DP, Max/MSP, and Metasynth!
- KVRAF
- 2469 posts since 25 Sep, 2014 from Specific Northwest
I always thought Live looked like Max. Very 1999.liquidsound wrote: Mon Aug 21, 2023 3:12 am Unfortunately you don’t like the fact that Excel looks like Ableton![]()
You should stop using Microsoft then![]()
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
A classic then!syntonica wrote: Mon Aug 21, 2023 4:47 amI always thought Live looked like Max. Very 1999.liquidsound wrote: Mon Aug 21, 2023 3:12 am Unfortunately you don’t like the fact that Excel looks like Ableton![]()
You should stop using Microsoft then![]()
ABEFLGMOPPRRST 
- KVRAF
- 2469 posts since 25 Sep, 2014 from Specific Northwest
Tragically ugly! So ugly, in fact, I could never get into Max as its ugliness was so distracting.liquidsound wrote: Mon Aug 21, 2023 5:10 amA classic then!syntonica wrote: Mon Aug 21, 2023 4:47 amI always thought Live looked like Max. Very 1999.liquidsound wrote: Mon Aug 21, 2023 3:12 am Unfortunately you don’t like the fact that Excel looks like Ableton![]()
You should stop using Microsoft then![]()
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7984 posts since 15 Aug, 2003 from seattle
- KVRAF
- 4066 posts since 3 Jul, 2022
Definitely agree. 100% with you on this one.liquidsound wrote: Mon Aug 21, 2023 3:12 am [Unfortunately you don’t like the fact that Excel looks like Ableton![]()
You should stop using Microsoft then![]()
Tbh, it is not that I dislike ableton, it is that I love bitwig too much.
- KVRAF
- 4066 posts since 3 Jul, 2022
Thank you for your detailed feedback.machinesworking wrote: Mon Aug 21, 2023 4:45 amThere are twice as many shortcuts in Logic and DP, three times as many likely in Reaper. This has to do with a much wider set of tools for linear arrangements than Bitwig has. This goes to the next point...Jac459 wrote: Mon Aug 21, 2023 1:32 am 2 remarks though:
1 - There is a ton of configurable shortcuts in bitwig that you can map however you want. I don't get what you are missing.Well it would be a lie to say they don't really. Barring the Grid, Bitwig is very limited compared to Logic, Reaper, or DP (I've never been a Cubase user so I can't qualify there), just in terms of arrangement timelines, and all that entails. Where they both excel is with uninterrupted audio, time stretching, (not pitch really though), modern control surface support miles above the others, and in the case of Bitwig MPE and CLAP support, (although DP does MPE well and Reaper has CLAP).2 - Both bitwig and live comme with a ton of features that don't exist elsewhere. Your point that each daw has specific features is certainly true but saying that cubase or Logic have a superset of features of live and bitwig is certainly not (you don't explicitly say that neither).
You can't really compare the arrangement tools in them though, the Bitwig/Live method is about simplicity, not extensibility. Doesn't mean you can't get work done in them, just that Logic and DP have 30+ years of development
For sure, although these days I'm pretty good at managing plug ins and finding the sketchy ones. It's a feature all DAWs should have. It's the only DAW I will run Hybrid 3 in or any of the older Air plug ins that haven't been worked on in years. To be honest though, I haven't seen any significant increase in track count running all plug ins sanboxed or running them in Bitwig, they mention Memory in terms of system resources and there is zero change in track count or CPU use from running them all sandboxed. So IMO that part has little to do with Bitwigs CPU use, that's more about not having some sort of secondary buffer or rendering of audio not in real time, for tracks that are not record enabled. This is really super easy to prove if you own Logic, DP, Reaper etc. Bitwig and Live will show almost ZERO difference in CPU when a track is armed or not, but get 70% of what DP, Logic etc. can get CPU wise. Those DAWs on the other hand have significant hits on CPU from record arming tracks, since it gets rid of that buffer that gives them extra CPU.I agree that real time has its advantages and drawbacks. Like sandboximg, you get a rock solid stability while losing certainly marginally on resource consumption.
Digital Performer introduced a Live Performance Mode, that to a degree acts like what Live and Biwig do, it's a step towards a solution that doesn't ignore the benefits of either method.
Basically there are significant advantages to either approach, my biggest issue with Bitwig is it follows Lives approach too much, some parts are simple, then you can go into the weeds building an FM synth in the Grid, the same thing is true in Live with Max. Don't get me wrong though I love them both, it's just that I do end up missing the old school feature set when I work in them at times. My perfect DAW would be Bitwig mixed with DP, Max/MSP, and Metasynth!
I am not as experienced as you on DAW as I used only reason, Live, bitwig and cubasis recently.
Decades ago, I used cubase and cakewalk, but it isn't relevant anymore.
That being said, if you are looking at the arrangement, surely you can find better feature coverage on the older DAWs, but talking about modulations, it seems to me that they are far behind. Bitwig on this very important aspect is king to me with audiorate modulations and so many different modulations proposed.
You were referring to do fm in the Grid but you actually don't even need the grid... you can do fm with just the modulations.
It is bloody powerful.
Now, are modulations more important than arrangement ? Or recoding ? It definitely depends. It is very much workflow dependant...