5 Reasons why i would love to switch to Bitwig 5, but CAN’T 

This is great!!!

Just to let you know I shared this with the CEO of Bitwig, good work on this video.

Really really well done! I've spent 5 years in Bitwig and this video covers pretty much all of my pain points at the moment. They truly need to consider working on the core features of their software... ESPECIALLY automation, piano roll, overall UI performance, and navigation.

One thing I love about Bitwig is the UI. As an older user (I'm 58) I think I would struggle with the tiny details of Ableton's interface. Bitwig has chunkier controls, and more primary colours to help with finding things. Accessibility is becoming increasingly important to me as I get older. I hope this is something they don't change - or at least, if they were to add interface customisation (which would be a great idea), then there should be an option to keep the original skin, for us oldies ;-)

Dude if @bitwig sees this and implements these changes. It will be the best daw. I 100% agree with this video. Also, you should have WAY more subscribers.. its criminal.

1: Waveform vertical zoom like in cubase...can't see my reverb tails to edit. 2: Import Grooves for quantize 3: A Mute icon for piano role

What a nice, caring, detailed, respectful, solution oriented way to criticize a piece of software! I hope someone over at Bitwig watches this video.. Really though, such a good video. Very well done. Subscribed (not only for the wizard hat! ;))

Thank you for being our voice!! If you work at bitwig and hope the best for the company please share this video with the people responsible for making bitwig the best DAW. I also gave up bitwig but always come back to see what changed, because I believe this DAW has potential. One more request, The primary mixer should show the input levels moving just like in the ableton, without the need to open the extended mixer, you could make the fader a bit more transparent and show the levels overlayed moving behind it, and also make the peak bar stays a bit longer in place, also just like in ableton cause it goes down so fast that makes it hard to see where it’s peaking Anyway, for me the main features that makes me stay in ableton is midi capture that was mentioned and simpler/sampler and the ability to slice samples and work with it easily, and also this mixer thing that makes me annoyed 😂😂

I fully agree with you!! I went back to Ableton.... Default settings for piano roll view, Piano Roll default zoom is a nightmare, Scale highlight and quatize (Cubase ist the best), Midi capture and comping, Gridlines, Automation are horrible, Sampler Warping and slicing, Chord track, Groove Pool AND the last feature is Undo support for third-party plug-ins!!! V5 was a not bad but is a 4 point version..... Thank you for this great video! I That's what i wanted always to say to the Bitwig team!!!

I love your style and the way you speak. Such a pleasure to listen to! Make more videos!

My main reasons for switching to Bitwig from Ableton were the mixer in arrangement view, audio editing in the clip launcher, bounce in place and plug-in sandboxing. I’d love them to add scales in the piano roll, a chord and arranger track and themes as the UI isn’t great to look at! What would be amazing is if they teamed up with Pure Data to give a Max for Live experience in Bitwig.

This is really good! Right on with all your points, the looping enhancements would be so nice and so easy for them to implement.

The looper is my biggest wish item. But the grid lines would be really appreciated as well. Great list!

Great video and pretty much sums up my experience. I love Bitwig and my first DAW was Ableton and I would love to fully make the switch and just go deep with Bitwig but too many basic things like you mention that frustrate me to no end.

Awesome list. So many basic features that are missing that I don’t use Bitwig as much as I use to. I know to most people it’s a small gripe, but I can’t stand the orange default system color of Bitwig. Customization like most other daws is greatly needed.

Great video Only one thing, I absolutely need the horizontal scenes :). It’s much more intuitive to work from top to bottom imo. The vertical view is good though when switching to an arrangement.

You are the legend!!! Everything you said is absolutely needed! I have some more things you have not mentioned, but I believe they’re REALLY important for composers like me who do film scoring. 1. Ability to resize tracks like in Logic, Cubase or Studio One. When I’m working on large electro- orchestral production I need to have an ability to resize tracks just by using mouse wheel like in many other DAWs. Bitwig has a button which makes tracks tiny but this is not a solution at all. We, film composers, need to freely resize tracks in large projects with 100+ track string templates. 2. When I want to record a midi note in the current region, Bitwig just splits the region. That behaviour looks like a bug and make Bitwig totally unusable when I want to just add a midi note by playing it on my keyboard. Every time I want to edit midi I need to hit cmd +j to join midi region which is absolutely crazy to me. I wondering why nobody talks about it, but it’s absolutely true. 3. Unable to “play from playhead” in the piano roll like in Studio One. It’s really inconvenient to hit this upper panel on the piano roll to move playhead starting position. I want to just hit anywhere and then hit spacebar for playback( like in Studio One) 4. Unable to organise deactivated tracks. If there are many tracks being deactivated there are no way to organise it. You need to create a folder with audio bounce and deactivated tracks which is absolute workflow killer for all of us. 5. Unable to draw smooth automation in track view by mouse. I can do it in clip view but it getting buggy as I adding many points. 6. Video support is absolutely needed. All these things are not just small inconvenience. It’s absolute dealbreaker for me, unfortunately. I love Bitwig soo much and I hope developers will see this video and WILL FOCUS ON BASIC STUFF IN THE FUTURE DEVELOPMENT. Bitwig is already innovative product. Just give people DAW functions, please, guys! In general, if Studio One and Bitwig could be one program it seems like it would be ideal daw for 95 % on this planet So much respect to @Sternenhertz for this video!

I did ask them about stickiness of automation nodes and acceleration of moving nodes. Their reply was that actually users like this and I can use fine adjustment through shift… well, I guess I’m not one of their favourite users who like it. Also about polarity. He was a fanboy and now he works for them so I wouldn’t listen to his talks. He will always find workarounds and will always and sometimes in a rude manner defend bitwig. For example he was openly talking for years that bitwig don’t need mseg. Now when they are out he says it’s is the best thing ever happened. ARA support, no thank you. It may and will make engine unstable. Grid lines. I couldn’t understand why I liked interface of Ableton so much. I didn’t even notice bars but yea, this is number one!

Good song at the end - and enjoyed watching it all.

29:19 - "the most obvious thing missing" for bounce in place is hubrd comping, because bounce in place removes the MIDI notes completely; instead, it could put them in a separate comp lane, so you could mix & match bounced audio with source MIDI as you wish :)

Nice comments on Bitwig 5. I dedicated numerous years (and financial resources) to Bitwig, holding onto my affection for its concept. Nevertheless, my dissatisfaction grew due to the excessive emphasis on introducing new features, often at the expense of addressing and enhancing the fundamental functions of the DAW. Despite submitting more than 50 feature requests, I witnessed none of them being put into action. Particularly disappointing was the lack of progress in enhancing the piano roll. As a result, I made the decision to part ways with Bitwig and invest my resources in a DAW that offers superior support for piano roll functionality. While Bitwig excels in sound design, it falls short in the realms of composition, mixing, and mastering, leading to a challenging experience in those aspects.

erm.... after using BITWIG for a long time... I have to say that BITWIG is more of a platform for sound fricklers. It´s a "random DAW" of sound and clip patterns... This is a strength - but also an absolute weakness. BITWIG lags in so many ways... I'm using BITWIG less and less and I'm back on Cubase and Ableton plus modlation plugins like Kiloheats. Best compromise.

I am only a few days into Bitwig (after using Reaper and Ableton Live and many others in my life) and found your overview of good and 'bad' very interesting and entertaining. You got yourself a new subscriber.

Great well structured take on what is missing! I do think DAWs like Ableton are basically in maintenance mode (Cubase is another). While Bitwig isn't transparent hopefully they get to fixing some of the basic however the folks over at Ableton have clearly shown they will ignore the community and just keep up with basic patching of the product. Let's hope Bitwig learn from that and don't make the same mistake.

Very nice song at the end!

thank you! i'm just searching about bitwig, hoping to get out of PT hell...and your video helped me realize i can't switch yet either. i'm a drummer and no grid lines are an immediate deal breaker. as well, the lack of overdub/loop recording. (pro tools calls it playlists, which are critical) i also learned that searching about someone's disappointments is a great way to learn about a DAW haha

I agree with you on a lot of these things. I'm not using Bitwig as a tool for live performances though so to me a great chunk of your feature requests are moot. Still very valid suggestions! I fell in love with Bitwig two years ago and sold my Ableton license a year after. Never ever looking back. Ableton feels absolutely ancient in comparison and the reason I actually switched to Bitwig was Abletons stubbornness and terrible support while having HUGE issues under the hood. Abletons has big problems with delay compensation and timing which made it completely unusable for me and to this day I am astonished that so little people talk about this. Everything with internal LFOs\sequencers that need to be synchronized to the host on playback are out of sync as soon as you introduce plugins with latency in front of them (AutoPan, Cableguys Shaperbox, Kickstart, Dmitry Sches Tanra, Devious Machines Infiltrator......). This has insane consequences and I was just so sick of finding workarounds instead of actually being creative. My most beloved feature is definitely the whole audio rate modulator stuff in Bitwig and how great it is integrated. It blew my mind and I couldn't live without it. Max For Live feels like a Frankenstein patchwork in comparison. And YES... PLEASE give us a Sampler+ with transient detection and sensitivity. I dearly miss Logics Quick Sampler or Ableton Simpler in my workflow.

wow what a video! well done.

99 of 100 people will complain about anything... length, message, etc. but the 100th person is the one who really appreciate what you´re doing! for those people these kind of videos are made for! it´s a great video with lots and lots of information and btw a great combination of facts and fun - the lenghts only shows your passion for this specific DAW and its potencial! thx for this video!

Thanks so much. This video just saved me money. I was considering the switch but some of these missing features are too glaring to overlook.

Very insightful video. About Touch Control however, can't you get a Stylus pen for your Touchscreen Monitor, or if it's not supported, get a Touchscreen Monitor that features Stylus input?

I agree. I stopped upgrading, but it is my favorite DAW.

I want midi comping

if they get the scale lock mode like Ableton I'll switch

Having different GUI colours would be great. It’s been the same colour for years. It’s beautiful but it’d be nice to have a change.

As per lore, Ableton implements one user suggested feature every 10 years.

I've never used Bitwig but have been eyeing it for a while. Yea, the gridlines are a dealbreaker for me. Thanks for the video

Video support, Automation lane QOL would be nice like not having percentages but actually having the number from inside the plugin for the thing you're trying to automate.

Sternahertz…Bitwig should employ you mate. How I’ve missed your Bitwig channel is astonishing. Pity it’s too late for me. I’m too ill to use Bitwig much now. Even though I have Omnisphere, Soundtoys 5 and some other top plug ins. But I’m. Rey impressed with your video. Brilliant work man.

Reaper, Cubase, Ableton . Bitwig 5 and no scale highlight in pianoroll in 2023????????

Great video , I dream of a functional implementation of the touch screen.

I love the outtro track.

Thank you so much for this video! I agree with all your complaints, and have been very frustrated with their lack of attention to basic features, and popular demand...

yes, yes yes - especially loop station like features + chord track features. And please bitwig stop developing features I can get using modular synth plugins. Yea the grid "was" nice with lot potential but I really do not want to build features in the grid that could be much more easy done with dedicated DAW feature. THX for this great Video .

Agreed, they do need to stop focusing on new features and spend a year or 3 working on the core. I would love to get rid of that double select range thing and have all that functionality wrapped up into 1 area selection with edge grab, the white and black selection areas, the white for me stops me dead in my tracks so many times because it's not what I wanted or just need to get it out of the way. Grid line colour changes would be great to make them more defined, piano roll needs a huge amount of work, 1 that annoys the hell out of me is that the auto zoom when you click on a midi clip often has all the notes off the screen then, you double click the clip again and it may or may not bring them into view. I also hate having note selection play a preview so I always have that turned off, but when I click on the piano keys to the left they are turned off also... Come on... lol. The little things matter, they matter a lot. I do love the MSEG stuff though, when I made a feature request to them I designed UI/UX interfaces in bitwig for using them, what they did took it a step further and I do love them.

Yo Bitwig hire this guy as UI/UX intern

G for me. Sampler time stretch much much needed.

Grid lines and piano roll improvement for sure, but for me the #1 reason not to switch is : VERTICAL ZOOM ...Click and drag up/down in the tracks section is painfull and slow, and even worse if you're on a laptop with trackpad only ... the one in Ableton is good, but the one in Logic is perfect : Zoom in all direction with 2 fingers by just pressing Alt ... so fast !!!

the thing that bugged me with bitwig is the color thing for some reason, because like let's say you add an audio/instrument track the color would be always different and i would always have to click to that color unlike in ableton but bitwig's performance tho, it's really good, you can run plugins 2x than that of ableton (resorting to either freeze of flatten tracks)

I started with FL Studio in 2004 but switched to Ableton after one year. I used it for nearly 17 years before I switched to Bitwig. Thanks to that, I got used to switching between the vertical and horizontal layout of Ableton's different views right in the beginning. And I think a vertical layout for the session view/launcher really makes sense. A mixer has a vertical layout, most MIDI controllers have a vertical layout, so having a vertical layout for the session view/launcher makes absolute sense. Also, when we arrange different things in front of us that are equally important, we want to use, and want to have a good access to all of them, then we arrange then side by side in a row. Those things could be tools or channels. Arranging equally important things next to each other in a row just feels natural and practical because they're all in good reach. Because of that, I barely use the launcher in Bitwig's mix view and nearly exclusively the dedicated launcher. The only purpose I use the one in the mix view is for is moving clips between the launcher and arrangement. And I think making the layout of the arrangement vertical to have a consistency, also wouldn't be very helpful. We primarily read from left to right and only move vertically at the end of the line. When we draw a time line, let's say to show the history of life on Earth, we draw it from left to right. Also, when we have an automation curve where a certain parameter is automated upwards, the curve would go to the right with a vertical arrangement. That's not very intuitive. It's "pump up the volume" and not "pump right the volume". So I think that in the long run, it's best to just get used to switch between a vertical launcher and a horizontal arrangement because in itself, it's most logical and intuitive to be vertical or horizontal respectively.

It's funny what you're saying about the touch going horribly wrong.. I also had that same experience, like I wanted to use touch screen to just simply record loops as I would with Push 2, and the fact that I MUST have the clip launcher in view in order to record a clip and there's no 'session record' button (also does not exist with the Push 2 support from DivenByMoss) and this drives me absolutely mad to the point where I'm actually considering starting songs in Ableton and importing them to Bitwig using the Ableton import features (which work surprisingly well if you're only using VST). And if I record a bunch of midi and then want to select a section of that to loop after the fact, its nearly impossible to do on a touch screen... I suppose I am very used to the Push 2 workflow in Ableton but I wish every other DAw would just copy that workflow as much as possible.

Bitwig user since v1 here and also Cubase user since 1995... Bitwig for Ideas and fun, Cubase for serious productions... With all your Ideas, maybe switching 100% to Bitwig. Awesome Video and nice track at the end.

I just purchased BitWig on their 10th birthday celebration sale. And when I was looking around and trying out a few things out. I started creating a few melodies and working with the midi notes. And for almost 2 hours I was searching for gridlines, only to find out 2 days later that it doesn't exist. I wanted to change from 32 to 16 and could not find it. I got frustrated and closed the DAW.

Great video, Thanks 🙏

and we need scale highlighting

All that shiny stuff doesnt matter when Bitwig doesnt show gridlines. A DAW without visible gridlines is 100% unusable to me.. Absolutely insane that someone thought this would be a good idea and even more insane that people accept it. True Reality-Check-Truman-Show-Moment..

I was considering trying Bitwig after 15 years with Ableton (+occasionally Reaper) but this video was exactly what I needed to understand that basically all the things Ableton version 8/9+''s updates have left me disappointed with... are nearly all the same degree of neglected or even *worse* in Bitwig. I appreciate some generative music toys but deeply do not care about them if i don't have good tools for writing music WITH INTENTION first. it's making me wish these DAWs were more modular in design so I could just have FL Studio's piano roll without committing to how to handles channels/groups/etc. as it is, with all DAWs trying to both do "EVERYTHING" (in theory) AND be distinctive, it seems like *every* developer will get at least one aspect dead-wrong, and our choice of DAW comes down to deciding which thing we can accept being dead-wrong. Yeah, sodium has accumulated.

I left Cubase for Bitwig years ago and never looked back.

Great video. Re: automation, I feel like that with Reason4, I haven’t used it in.. 13 years? But I remember the way it put automation into its own clips, independent of notes, was amazing. You’d set a default value, for when the play head isn’t over a relevant automation clip, it didn’t read the situation like a continuous graph that could break as you cut and paste sections in your track. The “automation simplify” tools. Were super useful. Compared to that, ableton ^and^ bitwig, feel like swimming through glue 🤣 Plenty of other reason features came far too late for me to stick with the platform. But I’d love if bitwig could implement some of these features that made this part of its sequencer so great.

Im working only a few days w Bitwig. Great Daw. But only some day of playing around and I find many of your issues too. Especially the music theory functions like Chord Track. Assign a key to song and show pressed chords in piano roll .... the modular concept is awesome... i have no live intensions so I stay at my current daw and don't switch :-)

That outro beat is too fire!

I think your point about "developing niche functions vs. targeting core features" is actually a tough dilemma. I feel like Ableton is an example of the opposite. I think Live is a victim of its success; used by all kinds of different music makers, who all seek different workflows and features. Including "never using it live", or never using the Session View. I feel like Ableton may be too small to cover all this ground, and may have trouble keeping a sense of focus for their feature development. Because of that, I'm not sure how mad I can be at Bitwig for prioritizing its uniqueness. At any rate, coming from the hardware world, I think there is always a feeling that we have as musicians that "the perfect tool never exists, unless you are willing to build it". I would still love to see your suggestions implemented though! I never used Bitwig (yet) but these sound like very useful changes. ps: I have to admit, like some have pointed out, I prefer Live's horizontal scenes, precisely because I don't want them to feel like a linear arrangement. It helps me visualize them as easily movable bricks that I don't commit to yet. Still, I would prefer vertical scenes to be an option for people who want them :D

im going to implement a chord generator in Bitwig

Hope bitwig watches this

I want to be able to quantize wave onsets in one click in the clip view.

Great list! Also, expanding your request about UI tweakability, this maybe very subjective, but I find Bitwig's very high contract colour scheme nice but quite hard to look at for long periods of time; I think it should be tweakable and themeable like in Ableton where it's very simple but efficient. Bitwig should be at least able to switch between light and dark colour themes which almost every app already does in 2023! And yes, I second the chord tracks request! Or at least display which chord the selected MIDI notes form. Continuing with the topic of UI / UX, I would also like to have a lane for articulations. That is done very well in Cubase as far as I remember, basically you have another lane in the bottom of the piano roll which displays current articulation. You select a portion of the timeline (or some MIDI notes) and change the articulation, and that is reflected in the lane. The thing with these UI / UX fixes, Bitwig don't even have to invent anything, it is already implemented (mostly) in different DAWs and tested by time :) As for the looping fix, I don't think the fix you mentioned is very easy to implement: it requires tracks below the current to have exactly the same settings as the current track; imagine the user has something completely different on those tracks. What should Bitwig do then? I'm not saying it's impossible but I just don't think it's an easy fix. Maybe it can be implemented as 'clip folders', similarly to comping in Ableton, but instead of playing only selected clip, play all of them at once; then, after the jam, the user could 'explode' the folder into many identical tracks and work with those.

God tier video!

The radial menu on the touch is really bad. Amazing that it opens UNDER your finger. How are we supposed to use the menu we can't see? The menu should expand to the sides of the finger and above the finger, leaving underneath clear.

It’s very disappointing that they haven’t worked on touch functionality since v2. What are good touch screens to use with Ableton live/bigwig (especially for Mac)?

I come from ableton too, but man, using bitwig recently, I am sooooo gonna move, there are a few other things that bother me in bitwig as well but the positives are just overwhelming (no no file normalization on bouncing is literally a sin, there is a workaround but its long).. I mean i am in fulll support, i can only imagine what bitwig 7 or 8 would look like.

23:04 and speaking of handles.... in Live's MIDI editor, when a loop bracket extends beyond the visible screen, hovering over the end of the visible portion causes a small handle to appear on the loop indicator. This handle allows you to drag the end of the loop to adjust its length. The is extremly handy for large loops or if you are zoomed in. However, in Bitwig, how often did I have to zoom out of the current MIDI view just to see the end of the loop selection, before I could grab the end of the loop indicator. super annoying.

i want bitwigs devices, abletons automation and browser. If they could just fuse both of them itd would be my favorite daw

Very interesting to see other people's perspectives on the shortcomings of a DAW. For example, the touch screen issues are completely irrelevant to me but I can understand why they are important to you. I agree with a lot of the points you covered. Some of the flaws were things I' hadn't realised were broken because I haven't been using Bitwig very long. Others were things I'd already found myself (lack of transparent clips to show bar lines, lack of MIDI comping). There's one thing that bothers me a LOT, because I'm a pianist: Bitwig treats piano pedal CCs (64 and a couple of others) as controller information, which means it doesn't stay with the notes when you move a clip around. This is INSANE. Piano pedals are part of the note information, and should be stored and moved around with the notes. End of story. This is simply wrong and broken. I did email them about this and was told that it's "on the roadmap" to be changed, but I'm not sure the fix is in BW5 as I haven't tried that yet. Probably it isn't. Another thing: you can't export individual tracks or clips as MIDI. You can ONLY export the entire project. This is also a bit weird. Perhaps the reasons relate to the Bitwig policy of discarding MIDI internally and using proprietary formats... but it's still a massive pain if you're collaborating with other producers/composers. I recently tried to record a piano part for a friend, and both this and the way CC64 sustain is handled caused me so much trouble that in the end I couldn't do it and had to give up (Cubase would have let me do this in no time). Like you, I love Bitwig and would like to stay with it. But they need to communicate better with customers and listen to what we are saying.

Absolutly agree!

From the first frames it became clear that this master of magic with a tiger jacket knows his business!

SuperCollider integration would be nice. I'd love to write my own SynthDefs than can be played like any other plugin. Or write patterns that control other plugins. I know it will never, _ever_ happen, but I can dream, dammit!

If they do a function where i could render as loop like in Live and FL Studio, i would not think two times before buying a license.

Auto fades on start and end for recorded audio on clip grid is a must. Can't use it as a looper for live synths otherwise - recorded clip is clicking on loop! Ableton do it easily...

as a software developer, this is very much in the same vein as video game players when it comes to delusional feature requests. The reality is that it is incredibly easy to dream up features but each of these features could take weeks of man hours and thousands of real dollars, and prioritizing development is a really hard challenge. Things like touch control are incredibly hard to justify when it’s used by such a small part of the user base. Some of these are rightfully frustrating to not see after many requests, but these things take time and I’m sure if requests keep coming in it’s planned for development and only a matter of time

28:39 It's the "Toggle Active" keybind that you're looking for, it also works on entire tracks and individual Grid modules. P.S. Linked clips is my top request switching from FL, it makes iterative composition so much easier.

midi comping is my #1

Thanks. I'm moving out of FL Studio - was going to get Ableton, but took a pause to consider Bitwig. Those lack of grid lines alone is enough to walk away. There are other things I don't like either, but that is a no no.

Great video, even though a bit too long ;) Bitwig has't, well... touched the touch features since they were released in v1.3 :( However, 80% of your FRs are related to live performance, which is a very small portion of user base, so I'm hoping they'll not throw ALL dev efforts towards it :) Personally, I want midi and hybrid comping, midi capture, alias/linked clips, note step input, scene follow actions, an action called "play the same clip/scene from start" (I often loop clips of weird length in a regular 4/4 music), new synths based on additive, granular and physical modelling synthesis, pattern tracks, sidechain inputs for all midi & audio triggered modulators. Basic stuff, really ;)

the simple ability to use a daw as a looper and hang onto all the layers as audio tracks would be an instant buy for me.

One thing that baffled me about Bitwig was that group and my pre-master channel's faders get ignored when exporting individual tracks via post-fader. This is really annoying when you want your bounced pre-master volume to be equal to the exported individual tracks. Unless there is something obvious i am missing, this makes group processing of any kind difficult to handle as well. It's not a problem as long as you don't have that requirement but some beat selling sites demand this. Otherwise I absolutely LOVE Bitwig. I haven't been this creative in years since I started using it. Oh and best feature might be multiple sessions and the ease of copying things over.

Everyone asks for improvements in the software, but very few people know the hard work behind programming, sometimes functions are not implemented simply because of the initial design of the software, it is possible that to implement a single function they have to modify other things that are already well established and functional and not introduce too many bugs, it wouldn't hurt Ableton, for example, floating windows, but they would probably have to change the core of the program, and only they know the lines of code that would have to be modified.

gawd absolutely. for me it's the looping. LET US CHOOSE OUR OWN LOOP LENGTHS DO NOT MAKE ME SLAVE TO THE PROJECT TEMPO

Bitwig Released on 25.03.2014 & Abelton 1998 / Cubase 1993 ... give them some time to make it right and try to find a way around.. no big deals for anyone... i understand your points, but i am shure they will implement any requests or the communit will... love! :*

1 year after switching from Cubase to Bitwig and my productivity and creativity has increased 10 fold. The one thing a lot of people don't talk about is how much Cubase crashes, and how much work you lose in the process. There are workarounds but working with it every day, means several hours of work a week down the drain. BW has not crashed on me without a perfect crash resolution yet.

I get the gridlines problem in arranger view but its not as big of a problem people think. In the detail editor BOOM transparent lines over the waveform. Keep the arranger for arranging sections of your song instead of waveform chopping ;^)

Midi control and cc automation capture is like the only thing that keeps not just me but many people from using bitwig. In many ways it is way better than any other daw. But these few basic features keep it from being truly amazing.

To all arguing on the complexity of implementing core features requests, that's true. But the reality, is that we see a lot of niche sound design features at the expense of DAW ones and more important, live creative friendly features. This is so obvious, that I have seen synths threads where users where comparing Polymer to Serum and hopping for a VST version. Is this what we expect from a tool that was sold as a live oriented DAW? Users are stuck with it, not knowing where they go with their time and money investment? Maybe it's more simple for devs to outsource some independent Grid modules dev than working on the core of the DAW. Basic examples, there is no way to modulate the reset of the note counter or the release of latch. Of course it could be looked as side features. But it's not. Counting notes and releasing them is a core feature of any sequencer. What we are missing is an alternative to Live, not to the whole bunch of already exiting modular synths. Ok, they do what they want but, don't pack it in a live DAW looking alternative. And note, that I was not one of these crying people about the Spectral Suite paid feature. I'm ok to pay for what I really use if it can improve dev resources.

At 11:40…the intuitive dragging does says Bitwig’s menu that it’s for a Tablet computer.

Seriously, Bitwig should hire you as a consultant.

You should be hired as Bitwig's product manager. Your video was an extremely timely and extremely welcome review for me, as you have saved me for the time being from purchasing a license to Bitwig to serve primarily as a viable alternative to a hardware-based looper. Though I have been playing piano and keyboards for quite awhile, I have not used a DAW before and would be doing so primarily to enable loop-based live performance (strictly for at-home enjoyment). My question: in your experience is there ANY viable DAW-based looping solution OTHER THAN using Ableton and a M4L plug-in? For a variety of reasons probably very comparable to yours, I really don't want to invest in Ableton if I can avoid it. But is it possible to overcome the looping deficiencies in Bitwig through an available plug-in for that DAW? Any advice would be greatly appreciated!

No scrubbing is a pain in the ass. By the way this is day ONE for me, switching from Ableton after 13 years.

there's a reason why you produced 'Wellentanz' in Cubase

YesYesYes!!! I thought I was the only ony hating the time range selection always getting in the way, it's highely frustrating !!!!! Please Bitwig make the time range optional or come up with a better approach but this SUCKS!!

Precise editing is impossible with touch controls because your finger gets in the way. I prefer a Wacom tablet with a stylo.

I came from logic to Bitwig. Automation editing was one part of my workflow. In bitwig, the UI UX zoom is not good enough and integrated well with apple trackpad so i rather put lfo devices to set up the automation I want. And I like it more now. I’m lazier now and can’t go back to manually writing automation lanes and edit the hell out of everything like a control freak. This might solve your automation problem?