I am simply trying to emulate Ableton's legato mode. 1/8 note launch quantize.
I cannot get Bitwig to record what i am hearing when launching midi clips, nor even play precisely what i am hitting on the controller pads.
Bitwig cuts out a lot of hits when simply playing back. The recorded aftermath is even worse.
What is recorded is a mess of seemingly random (quantized?) start points or clip positions.
When carrying out the same thing in Ableton, what i hear is what i get. Also, it appears to just be a lot better at launching clips. I am rapid firing at 174 bpm (improvising dnb drums). Ableton handles it. Smoothly transitions between any clip at any rate of playing/pad hitting. What is recorded is exactly what was played.
I have the project launch quantize set exactly how i would in ableton. Tried all the legato modes.
Any other tips or settings to try?
problems recording midi clips to arrangement
- KVRian
- 533 posts since 11 Apr, 2019 from UK
No idea how to help you sorry. Turn quantization off completely? A complete guess... Check DSP level, CPU load, if it's in middle or above then bounce all other tracks down and turn the vst tracks off, then try and do your drum thing again...
I'm on 5.3.13 and I've noticed it do some mad things with large sound samples, lagging out, playing at wrong time or position inside the edited clip, or even not playing clips at all sometimes, and that's on the main timeline. But these are in projects where I have a 1 hour + sample that I am chopping up, re-ordering and adjusting gain etc etc. Next to no CPU/GPU usage and loading of SSD/NVME, but it's not something I can replicate often, so I don't waste my time contacting support with a youtube video of it going batshit crazy. But when bitwig goes mental it really goes mental...
Email support and let the fates decide...
Maybe go back to BW5.x.x if your on 6.
I'm on 5.3.13 and I've noticed it do some mad things with large sound samples, lagging out, playing at wrong time or position inside the edited clip, or even not playing clips at all sometimes, and that's on the main timeline. But these are in projects where I have a 1 hour + sample that I am chopping up, re-ordering and adjusting gain etc etc. Next to no CPU/GPU usage and loading of SSD/NVME, but it's not something I can replicate often, so I don't waste my time contacting support with a youtube video of it going batshit crazy. But when bitwig goes mental it really goes mental...
Email support and let the fates decide...
Maybe go back to BW5.x.x if your on 6.
Web Developer by day, DAW tinkerer by night...
