What drives you crazy in Bitwig?

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

lokanchung wrote: Sun Jul 18, 2021 3:39 am They broke shift to disable snap with automation handles.... I wrote them about this along with a suggestion about using ctrl to lock axis. Seems like every major update they break a few things. I wonder how this thing happens....
That's Bugwig for ya. I use Bitwig since 2015, and got used to the regressions, they will probably fix it in time, but will take ~1 year. At this point, if it's not a major bug that hinders my workflow, I don't care anymore... you have to live with the bugs or use another DAW.

Post

anoise wrote: Sun Jul 18, 2021 7:54 am That's Bugwig for ya. I use Bitwig since 2015, and got used to the regressions, they will probably fix it in time, but will take ~1 year. At this point, if it's not a major bug that hinders my workflow, I don't care anymore... you have to live with the bugs or use another DAW.
This kind of things can be fixed like in 4.0.2. Once they notice the problem... This particular bug impacts my workflow, especially editing pitch bends. Good thing is that I can simply choose not to renew my plan until things gets fixed and improved

Post

antic604 wrote: Sun Jul 18, 2021 7:39 am
MegaPixel wrote: Sat Jul 17, 2021 4:17 pm
pdxindy wrote: Sat Jul 17, 2021 3:39 pm
excuse me please wrote: Sat Jul 17, 2021 2:31 pm No vertical zoom in the midi editor?
There is vertical zoom in the midi editor
You got the crazy inverted zoom and scroll feature with middle mouse down and drag feature.... And the invisible drag area to the left of the virtual keyboard which up and down goes up and down and left and right scales.
Or use Ctrl+Alt+MW like a normal person :P
Holy crap I never knew that existed, thanks!

Post

PhilipVasta wrote: Sun Jul 18, 2021 6:09 pm
antic604 wrote: Sun Jul 18, 2021 7:39 am Or use Ctrl+Alt+MW like a normal person :P
Holy crap I never knew that existed, thanks!
I'm eagerly waiting when they're gonna add the same for resizing tracks vetically. Keyboard shortcuts they've added in one of v4 beta are great, but mouse action is better (IMO, obviously).
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

Comping window : not being able to prelisten lanes, and no horziontal dragging of clips.
Yes there are workarounds but these two things should be so logical.

Post

I just got into trying out Bitwig after having been an Ableton Live user for years, and while there's a lot of good stuff about Bitwig, man, I can't stand the thin-a$$ grid lines…why can't you make it thicker?
I've tried adjusting the two settings in prefs, but no luck.

Post

No tuner. When adding samples they double the tempo. That drives me up the wall.

Post

Pitch-Bend automation - If i doubleclick the value-field (= default it) of a point, it jumps to 0% instead 50%. For most values there are near-by values preicise enough, but especially pitch-bend needs a correct value!

Post

Lack of vst's undo and that tiny imprecise mixer faders grrrr :x :x :x

Post

What drives me really Crazy is that for slicing you Need to drag a file to the arranger richt click on the file and choose how you want to slice it to a drumrack or multisample next choose how to slice it on onsets beats or whatever. Next you need to delete the audio track since you dont need it anymore.

What a complete utterly non intuitive way of working compard to Abletons simpler.

Please Bitwig add a slicer mode to the sampler and from There put an option to slice it. Like in simpler from ableton. And put a sensitive slider/knob to choose the amount of slices/onsets.

Slicing in bitwig is done against the Bitwig User experience approach.

I really hope Bitwig Will read my post.

Post

questionaire wrote: Mon Aug 23, 2021 7:18 amPlease Bitwig add a slicer mode to the sampler and from There put an option to slice it. Like in simpler from ableton. And put a sensitive slider/knob to choose the amount of slices/onsets.

Slicing in bitwig is done against the Bitwig User experience approach.

I really hope Bitwig Will read my post.
They've seen - and probably also received by mail - this type of request hundreds of times. You're not the first person to want slicing and timestretching of audio in Sampler :)
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

antic604 wrote: Mon Aug 23, 2021 7:29 am
questionaire wrote: Mon Aug 23, 2021 7:18 amPlease Bitwig add a slicer mode to the sampler and from There put an option to slice it. Like in simpler from ableton. And put a sensitive slider/knob to choose the amount of slices/onsets.

Slicing in bitwig is done against the Bitwig User experience approach.

I really hope Bitwig Will read my post.
They've seen - and probably also received by mail - this type of request hundreds of times. You're not the first person to want slicing and timestretching of audio in Sampler :)
Thats good to hear, that there are more people complaining about this kind of workflow! Now then Bitwig action on this :-) !!!!

Slicing is more important then comping for me! Altough comping feature you are welcome aswell.

It should not be that hard to implement slicing into the sampler slicing functionality is already existing in Bitwig.

Post

questionaire wrote: Mon Aug 23, 2021 7:37 amSlicing is more important then comping for me!
Comping is more important than slicing for me.

Live is significantly better than Bitwig for slicing. I don't do much slicing so no biggie here.

Post

The DAW got Timestretch and was a big deal for me, and the Sampler got nice upgrades that is Nicerella, but does that hint that adding Timestretch for Sampler-playback is maby a Tad complicated or something, and all this is a hint? because they have been around it, hmm :)

Post

SmajjL wrote: Wed Aug 25, 2021 2:20 am The DAW got Timestretch and was a big deal for me, and the Sampler got nice upgrades that is Nicerella, but does that hint that adding Timestretch for Sampler-playback is maby a Tad complicated or something, and all this is a hint? because they have been around it, hmm :)
My guess is it would mainly be a big CPU hit... realtime timestretch of an audio clip while also running it with textures or cycles mode and modulating the speed and so on. But that is just a guess.

Post Reply

Return to “Bitwig”