Faster workflow with these 10 tips & tricks 💪 // Bitwig tutorial

[@CyanideLovesong]

Migrating over from Reaper (nothing against Reaper, it's great -- I just love the powerful 'toylike' fun of working in Bitwig) and this was super helpful. Several things in here I hadn't yet figured out! You can tell Bitwig cares a lot about user experience.

[@WilliamFord-vq1tk]

So much better than FL Studio. Like a breathe of fresh air.

[@dogclown33]

for someone who has recently switched to bitwig, this was super helpful..

[@ChrisMills-AmbientSpace]

This is excellent. Thank you. I love that I can slip/slide MIDI and audio. Cheers!

[@robingomez9319]

Ctrl E is a feature in other DAWs as well. What you can do in Bitwig instead is use the slice tool (I think default keybind is 4). You can click where you want to slice clips, or you can use modifier keys (can't recall if it's alt or shift or both) to slice in increments of your choice. It's much better Also the trick of bouncing a whole section can be done with a few less steps. Just highlight the section and hit ctrl b to instantly bounce in place into a new clip

[@mugatu8732]

the point of pressing "ctrl+e" a selection is that you cut 2 times instead of 1 time. it safes time. holding "5" is good for a single cut.

[@Rustyboyyy1]

Hey Ollie, I've watched your videos for ages and thought I had better listen to your music. Wow, it blew me away! I remember when Eat Static came out and you have taken that sound to a whole other level. So complex but smooth and the flow is incredible. Nice one.🤙🙂🏴󠁧󠁢󠁳󠁣󠁴󠁿

[@Complexautist]

Awesome, notes taken. Thanks for the tips

[@IamDiamondEyes]

Dude, you are awesome thank you for so much great insight!

[@bastianbrand904]

some very cool tricks! Thank you. The multitake/comping tool is another very quick instrument for call&response arrangement. It does mute the quiet track entirely, depends if you want that.

[@cezarcimpeanu6439]

Really useful tips. Didn`t really use most of these features. That CPU saver trick, really saved my project. Would love to see more of your tips from time to time! Thanks! ♥

[@jandr01d]

Brilliant, thanks!

[@riotcast2752]

The eq+ reference input trick is neat. Didn't think of it before!

[@rd-cv4vm]

even better add an modulator, "audio sidechain", on the frequency of your choice, instead of putting compressor, just affect the frequency that clashes. with this technic i have full kick and full bass never clashing as they replace eachother in time.

[@sternenherz]

@@rd-cv4vm Hello could you please explain this for beginners? :D or is there a tutorial on how to do that precisely? I want to make a liveset template where the kick-track automatically is the source for sidechain of the Bass-track (and also -partially- the Lead/Pad-Track)

[@Rustyboyyy1]

Great video ollie, thank you. Please do more🤙🏴󠁧󠁢󠁳󠁣󠁴󠁿

[@bomiller7908]

Coming from a hardcore reason background, the track vs clip thing sold me. I also own ableton and fl studio. They both have amazing festures and some things i hate. I have yet to find anything i dont like about bitwig (besides still getting used to the new browser) but i can see how its more efficient in the long run. One thing i love about reason is when you click inside a midi clip you can see the rest of the oncoming midi and the previous midi. Just for me helps write parts in context. Which is the main thing i didnt like about midi editing in ableton. I can see some benefits of viewing clip only and so glad that bitwig gives you both options. So far bitwig seems like its throwing in everything i like about reason, ableton and fl with the least amount of sacrifices for using it.

[@sternenherz]

Precision of Tip 3: Alt+Shift+Mousedrag moves the clip content based on the bar-grid-lines. Alt+Mousedrag moves the clip content freely. I really wish Bitwig would have a Glue-Tool. To glue together Slices (in the detail-edit-view! Ctrl+J doesnt work there).

[@frequency_sequencer]

Absolute Gold... Thanks Brother

[@ibsenproducer]

Great Tips and Tricks Ollie!

[@ze2like]

Thank you! 😊

[@danemiller4852]

Broooooooo. I've been thinking some of these were just not possible in bitwig... and yet color me surprised it's been an option the whole time! Thanks for pointing that out! Lol

[@Sjammienators]

Thanks mate, a few of the tricks are very useful 🙏

[@BursaProduction]

Pure Awesomeness

[@Pilzhirn]

Great, thanks 👍

[@CollectiveIntelligenceMusic]

Great video Ollie!

[@olliepsy]

Thanks Andrew, next step, you join the Bitwig clan 😎

[@joepeezly]

Nice!! Very helpful, thanks!

[@aevin_io]

Very cool tips! Specially the last one. Bitwig is amazing really. Quick question - i noticed how well organised you got your instruments in groups … are you using a template for that, or do the grouping as you go? Thanks again for the knowledge 🎉

[@iamerhach]

Thank you man.

[@jshstuff]

Awesome tips!

[@hleet]

super les tips & tricks

[@lxndrbe]

Awesome

[@eyefisher]

What is the name of the command that you set to Ctrl+I? In tip 6

[@eyefisher]

Never mind. I think I heard you say Insert Silence.

[@RainKerosene]

Real time examples, like you playing the midi clip and showing us the difference in speed and sound etc would be nice. If not necessary, just being constructive

[@florianarndt]

If only eq+ wasnt fucked up with its latency issue…

[@sternenherz]

Hello, i have no knowledge on this point, but i found this answer on reddit, about the EQ+ latency, maybe it helps: "I think you're mixing something up. - Linear Phase EQ: No Change in Phase but considerable Latency (Too much for any Monitoring stuff) - Normal EQ: Zero Latency possible at the cost of changes in Phase. - EQ+: Normal EQ with minimal Latency added for Click compensation If I understand you correctly you want an EQ without changes in phase with no Latency. This is not possible, there is no such thing (for math reasons)."

[@florianarndt]

@@sternenherz No this reddit post has nothing to do with EQ+‘s flaw. EQ+ introduces latency that does not get compensated by Bitwig and therefor messes certain things up. It‘s very unfortunate as it seems the developer have no intention of fixing it.

[@sternenherz]

@@florianarndt Latency which affects the whole project? Or only within the affected audio-material?

[@HelicopterRidesForCommunists]

Ableton desperately needs a bounce in place. Some of the things it lacks just baffle me. I dont get why they dont have them.

[@АлександрБелый-ц4ъ]

🔥🔥🔥🔥🔥🔥🔥🔥

[@gasparpini]

Tip 08 its nice, but when you do what you say, you will lost all individual sends of the desactivats tracks. The freeze function of bitwig is so bad. Im sorry

[@Lumaa_Lex]

Instead bounce in place - you can use Bounce, and it will bounce with all effects on. And easier to select whole subtrack and bounce to new track.

[@HelicopterRidesForCommunists]

I have always hated Ableton UI/Workflow. From day 1 the first time I ever used it. Its never intuitive for me. Thats its weakest aspect in a sea of wonderful qualities. Bitwig however takes a lot of what I loved about Reason's workflow/UI and it marries it with Ableton Live - and I am a convert now. I still use Live but when it comes to writing a complete song its Bitwig. Live I use live.

[@SketchUPDCFurniture]

tips & tricks ? да ты просто показал функции программы.

[@manitsony6703]

Get vid

[@vroteg]

Regarding tip 8. I never use bounce or bounce in place in bitwig because those functions are broken. Yes you heard me right and bitwig being bitwig just ignore people telling them there is an issue. Do simple experiment, bounce something in place and do the null test. You will be surprised. Also i would not use eq+ as it’s broken too. It works as a good phaser. Not so good eq…

[@synclavier5405]

Thank you for sharing this. Bitwig youtubers don't seem to be mentioning these fundamental issues

[@tharken1269]

Hey, what is the "null test" ? :D

[@samdietriich]

How is the shortcut called that u use for crtl+i ? Also thank u so much for these tips ollie 🙏🫶

[@olliepsy]

The shortcut is : insert silence, in Bitwig you can just type in the search filed ctrl+i and it'll give you the name ;)