HOW TO MAKE Easy Powerful Snappy Snares in Ableton and Bitwig
Вставка
- Опубліковано 15 лип 2024
- Hi Friends.
It's ya boi. Chat with me in the comments and leave a suggestion for what you'd like to see me cover next. Linked, below are some free snare generators for Bitwig and Ableton. See you next week :^D
drive.google.com/file/d/1Df1i...
0:00 - Intro and Thanks
0:42 - Corrections, Comments, and Feedback
4:32 - Making a custom snare in Ableton
6:48 - Making a custom snare in Bitwig
11:40 - Final Product
11:46 - Outro
Sick. Have seen some of your other videos in the past. Didn't realize you did bitwig stuff. Subscribed. Good stuff
No pedantic commentary this time! Glad to see you back buddy, I need to dig into the DS percussion in Ableton and mess around with making my own percussion more.
Love your teaching style, appreciate the videos.
My pleasure!
thank you!
as someone who's working professionally as a freelance producer, i'm really unhappy with ableton 11. i've tried the bitwig demo, really like it, but would be interested in your advice on the major pillars to learn before making the swap.
Same here! I like Ableton, but it's becoming more and more unstable. Have a few friends who have made the switch and am curious how it works for all types of producers
Hooray for the second one. Long may it continue.
at some point someone probably gonna boo on EQ+ in the comments, because it introduces a tiny bit of non-compensated latency, even with no active nodes. what I hear from Bitwig devs about it is apparently with PDC it may result in a click sound when adding EQ+ in active chain for some reason, so it would make it problematic in live situations, which is more important to them.
so the main reason people like to hate on EQ+ for this latency is that it makes parallel EQing a problem, but arguably any parallel EQing without using linear-phase EQ (which Bitwig doesn't have) will result in phase rotations and inevitably some phase cancellation effect.
the other reason is that this slight delay can mess up some sidechain setup, although you can just compensate it with timeshift close enough.
so personally I don't care and just use EQ+ by default. but knowing this quirk would help troubleshooting if anything is a bit off about phases where it matters and stuff.
Interesting. So this is only with playback where this problem occurs? Does it factor into a rendered file?
Yep, just set the timeshift device to 4 samples ahead and it is in sync again
@@CJnull the main problem is that latency isn't even divisible by samples 😅 it's almost 4 samples, and I think it may vary depending on samplerate of the audio engine. but apart from parallel processing this will get things in sync close enough
@@x-iso hm, I've set up a really simple test one day. Same audio on two tracks. One with timeshift on 4 samples, EQ+, and phase inverted. It became absolutely quiet. Maybe the test was not sofisticated enough?
@@CJnullidk, just tested in case something changed in v5, but it's audible even. you should see that signal is still passing through on spectrum analyzer, it goes on a ramp to higher frequencies. also for better test probably should pass white noise through it, but generally anything above 1khz should be pretty audible already.
Maybe I'm showing my lack of understanding here but I think the Bitwig Saturation device can be set up as a hard clipper
Same. I'll look into it and include this in the clipping review.
it can, but it has oversampling, which often results in peaks passing the clipping point, so something to take into account.
Hello, you have been permanently banned from r/Bitwig for mentioning LMMS. And you've been banned from r/MarioPaint for not using a Nintendo-licensed mouse.