I've been using Bitwig since 2017 and to me its just on another level compared to some of the other DAWs around. I have Ableton 11 which is really good but Bitwigs is my go to for a Saturday night jamming with the clip launcher loaded with samples and midi. I like to record then as now and then you hit gold...Cheers mate
Trying so hard to like Bitwig and find it incredible you use it as your primary and only DAW. There are so many upsides. But there are things that don't make sense like the way the cursor operates in the timeline when editing windows is open and not being able to drop the cursor midway to start playback for instance. Being unable to apply FX directly to audio events. If it could blend the best of Ableton with the best of Studio One it would be the perfect DAW.
I was glad I got my new iMac just before they rolled out the new silicon. It seems things are falling into place now but for a few months so much didn't work with it. I have a pretty much zero tolerance policy for adopting first gen of any tech. I'll make the switch to it in a few years when I feel my iMac is slowing down (though I ran my Macbook for 8 years before finally replacing it so that might be a ways out). I'm sure in 3 years when I see how fast people are rendering 4k on the new silicon and everything is designed for it I'll be swayed to upgrade 🙃
I was pretty close to buying an iMac last year as well. I was limping along on my old MacBook Pro. Never thought I would buy a MacBook Air but the performance was undeniable. It took almost a week of work to get all my plugins working so you're not joking about the first gen tech issues! But I was pretty determined and got through the pain lol
@@GourlieRecords Oh yeah no issues with audio artifacting. Up until this latest release of Bitwig I was running it through Rosetta. It was faster than my previous computer but not by too much. Now it's way faster. Render time on videos is probably where I see the improved performance the most. It's pretty insane in final cut. Even opening Final cut is almost instantaneous. The only issues I have are the occasional freezing on final cut or when air dropping and I think it's probably just software issues.
@@SOLush Interesting... I definitely will never move off iMac cause I run through some chunky projects daily. But eventually will need to upgrade my 8 year old macbook for mobile working... good to know the Airs are an option now! Much friendlier price tag!
Do you use bitwig headless? Since bitwig's audio engine permits network connectivity can you create an audio render farm using bitwig? Note that all realtime AUDIO runs outside the main process. Even built in bitwig devices are all running in the realtime engine. Ie, not ONLY plugins, but all bitwig built in devices are in two parts, there's a UI rendering part of a bitwig synth, like their FM4 device, in Java, which runs in the main process, but the actual FM synthesizer is native code, not in Java, I believe. The main process only handles UI and all audio in, audio out and DSP is in a separate subprocess or multiple subprocesses.
I don't use Bitwig headless but would love to learn more about it. It's cool to hear your knowledge on this. Do you run a bunch of Mac minis or something to render your audio? Haha
I’ve never used Reason before. If you like tweaking things, the “Grid” and general modularity of Bitwig is a lot of fun to use once you get the hang of it
Bitwig is a huge upgrade from Reason or Ableton, but it's not ready to take on the big boys (Pro Tools, Cubase, Logic) for general purpose studio work. One of the big problems with Bitwig is it actually worse support for control surfaces than Ableton, and certainly it's far worse than Cubase or ProTools or Logic all of which support about 30 to 50 times more control surface makes and models than bitwig does. The good part of bitwig is you can probably script your own custom controller workflows, so if that's your cup of tea, bitwig rocks. Oh the other good part of bitwig is that it's engine is light years ahead of all the other single process engines out there.
I know this is true as its missing a lot of stuff I love from Cubase. What particularly are you finding is missing? To me it feels like someone who finds Ableton Live "fine" will find bitwig "pretty good", but someone coming from Cubase or Logic or ProTools will be pretty frustrated.
@@WarrenPostma whats missing from bitwig???? if so one huge thing is ARA MELODYNE i record alot of artist who wants to press record vocals into melodyne just to edit 40 tracks 🤣
@@soundsfromYYBY In cubase I don't have to buy Melodyne as the built in VariAudio does the same thing. A pro level Pitch correction solution like VariAudio or Melodyne really should be built into Bitwig.
I've been using Bitwig since 2017 and to me its just on another level compared to some of the other DAWs around. I have Ableton 11 which is really good but Bitwigs is my go to for a Saturday night jamming with the clip launcher loaded with samples and midi. I like to record then as now and then you hit gold...Cheers mate
Trying so hard to like Bitwig and find it incredible you use it as your primary and only DAW. There are so many upsides. But there are things that don't make sense like the way the cursor operates in the timeline when editing windows is open and not being able to drop the cursor midway to start playback for instance. Being unable to apply FX directly to audio events. If it could blend the best of Ableton with the best of Studio One it would be the perfect DAW.
I was glad I got my new iMac just before they rolled out the new silicon. It seems things are falling into place now but for a few months so much didn't work with it. I have a pretty much zero tolerance policy for adopting first gen of any tech. I'll make the switch to it in a few years when I feel my iMac is slowing down (though I ran my Macbook for 8 years before finally replacing it so that might be a ways out). I'm sure in 3 years when I see how fast people are rendering 4k on the new silicon and everything is designed for it I'll be swayed to upgrade 🙃
I was pretty close to buying an iMac last year as well. I was limping along on my old MacBook Pro. Never thought I would buy a MacBook Air but the performance was undeniable. It took almost a week of work to get all my plugins working so you're not joking about the first gen tech issues! But I was pretty determined and got through the pain lol
@@SOLush Wow you're running on an Air!? Is it actually holding up without any audio artifacting? How's your render time on videos?
@@GourlieRecords Oh yeah no issues with audio artifacting. Up until this latest release of Bitwig I was running it through Rosetta. It was faster than my previous computer but not by too much. Now it's way faster. Render time on videos is probably where I see the improved performance the most. It's pretty insane in final cut. Even opening Final cut is almost instantaneous. The only issues I have are the occasional freezing on final cut or when air dropping and I think it's probably just software issues.
@@SOLush Interesting... I definitely will never move off iMac cause I run through some chunky projects daily. But eventually will need to upgrade my 8 year old macbook for mobile working... good to know the Airs are an option now! Much friendlier price tag!
When you are dragging the compiled tracks is there a way to lock the onsets of each track?
Do you use bitwig headless? Since bitwig's audio engine permits network connectivity can you create an audio render farm using bitwig?
Note that all realtime AUDIO runs outside the main process. Even built in bitwig devices are all running in the realtime engine. Ie, not ONLY plugins, but all bitwig built in devices are in two parts, there's a UI rendering part of a bitwig synth, like their FM4 device, in Java, which runs in the main process, but the actual FM synthesizer is native code, not in Java, I believe.
The main process only handles UI and all audio in, audio out and DSP is in a separate subprocess or multiple subprocesses.
I don't use Bitwig headless but would love to learn more about it. It's cool to hear your knowledge on this. Do you run a bunch of Mac minis or something to render your audio? Haha
Thank You!
You’re welcome!
I'm honestly debating switching, I'm a lifelong reason user and this seems to work similar
I’ve never used Reason before. If you like tweaking things, the “Grid” and general modularity of Bitwig is a lot of fun to use once you get the hang of it
Try the demo!
Wait for Reason 12 before deciding
I'm a Reason user also. I'm thinking of adding Bitwig and using Reason as a VST within Bitwig.
Bitwig is a huge upgrade from Reason or Ableton, but it's not ready to take on the big boys (Pro Tools, Cubase, Logic) for general purpose studio work. One of the big problems with Bitwig is it actually worse support for control surfaces than Ableton, and certainly it's far worse than Cubase or ProTools or Logic all of which support about 30 to 50 times more control surface makes and models than bitwig does.
The good part of bitwig is you can probably script your own custom controller workflows, so if that's your cup of tea, bitwig rocks.
Oh the other good part of bitwig is that it's engine is light years ahead of all the other single process engines out there.
I like this DAW, iam noob...I have m2 MacBook pro 16 16GB I this enough? Wow nice
Operators work on audio tracks too
Hell yeah! Gonna dig into that once bitwig’s authentication servers go back online…
if you only a producer or sound designer bitwig great for you...but its a lot it's missing when it comes to a all around creator
I know this is true as its missing a lot of stuff I love from Cubase. What particularly are you finding is missing? To me it feels like someone who finds Ableton Live "fine" will find bitwig "pretty good", but someone coming from Cubase or Logic or ProTools will be pretty frustrated.
@@WarrenPostma whats missing from bitwig???? if so one huge thing is ARA MELODYNE i record alot of artist who wants to press record vocals into melodyne just to edit 40 tracks 🤣
@@soundsfromYYBY In cubase I don't have to buy Melodyne as the built in VariAudio does the same thing.
A pro level Pitch correction solution like VariAudio or Melodyne really should be built into Bitwig.
@@soundsfromYYBY Bitwig does have basic pitch curve editing, but it's nowhere good enough to complete with Melodyne or VariAudio.
@@WarrenPostma i know what cubase do first daw i used it was nuendo. melodyne is built in with studio one it comes with it also