3.2 (Beta 1) is OUT!!!

[antic604]

zoom via bar on top of the screen,...

On laptop's touchpad:
- Ctrl + two-finger scroll up/down zooms track in/out
- Alt + two-finger scroll up/down zooms current (or all selected) track(s) vertically

This probably works with mouse too?

[ozinga]

Maybe bitwig did not have the focus and did not receive the key event?

It definately has the focus. If i hit the key, the gui open up every time, but simply doesn't close it, if I hit the key again. I need to close it on X every time. And when I close it on X, I hit the key again, the gui open. This is how it is working for me at least. Can you guys fix it?

Strange. It works here. I have assigned V to Primary and it toggles it on and off. I am on Mac.

[dreamstate42]

zoom via bar on top of the screen,...

On laptop's touchpad:
- Ctrl + two-finger scroll up/down zooms track in/out
- Alt + two-finger scroll up/down zooms current (or all selected) track(s) vertically

This probably works with mouse too?

I haven't found a way to zoom a track vertically (track height) with mousewheel yet, but maybe I'm too dumb (or it's different on macOS than on Windows).

Horizontal zoom does however work with Shift + Ctrl / Alt + Ctrl, scrolling horizontally works with Shift / Alt.

[xbitz]

Maybe bitwig did not have the focus and did not receive the key event?

It definately has the focus. If i hit the key, the gui open up every time, but simply doesn't close it, if I hit the key again. I need to close it on X every time. And when I close it on X, I hit the key again, the gui open. This is how it is working for me at least. Can you guys fix it?

Strange. It works here. I have assigned V to Primary and it toggles it on and off. I am on Mac.

yepp on mac it's seems ok

[anoise]

Maybe bitwig did not have the focus and did not receive the key event?

It definately has the focus. If i hit the key, the gui open up every time, but simply doesn't close it, if I hit the key again. I need to close it on X every time. And when I close it on X, I hit the key again, the gui open. This is how it is working for me at least. Can you guys fix it?

Strange. It works here. I have assigned V to Primary and it toggles it on and off. I am on Mac.

On windows 10 the VST window steals the focus from Bitwig, so you have to click on Bitwig again to get to focus back to Bitwig's window, then the shortcut works to close the VST. This is not ideal.

[gentleclockdivider]

Is the grid feedback still restricted to audio buffer size ?

[keel]

Maybe bitwig did not have the focus and did not receive the key event?

It definately has the focus. If i hit the key, the gui open up every time, but simply doesn't close it, if I hit the key again. I need to close it on X every time. And when I close it on X, I hit the key again, the gui open. This is how it is working for me at least. Can you guys fix it?

Strange. It works here. I have assigned V to Primary and it toggles it on and off. I am on Mac.

Yeah, found out the reason. My bad It is about this focus thing. I need to click the track itself to get the focus back, which doesn't make any sense. If I am on piano roll, hit they key, the gui pop up. Then I want to close the gui in same button, to do that, I need to first active the track, then I can click the shortcut key again to close the gui. And this doesn't make any sense. The focus should be there all the time, if you have the gui open. The whole idea of this shortcut is that you don't have to do extra clicks and spend time. I can get the gui closed faster by just close it on X. So, can you guys please fix this? Please?

[xbitz]

^^^ usually the keys like esc, space, tab etc. are passed back to the host from the plugins, have you tried to assign it to the 'esc' key ?

[Tj Shredder]

Is the grid feedback still restricted to audio buffer size ?

This is a physical, technical restriction no software can overcome. To get zero delay feedback you need to program and calculate (CPU expensive) an approximation without feedback. That is what ZD filters do...

[Hanz Meyzer]

Those new additions for sure are great and will improve work a bunch. Also having a proper built-in EQ is very nice, and surely took a lot of time to design it.

BUT! I hope tilt for analyzer will come to any view, including EQ5 etc. Also WHERE ARE THE WORKFLOW IMPROVEMENTS IN PIANOROLL, SHORTCUTS ETC ETC? PLEASE LEARN FROM RENOISE. Where is VST undo? Why is the midi delay limited to 10ms minimum? And where is the freedrawable LFO?

Here some ideas:
viewtopic.php?p=7710545#p7710545


This time I will wait and not upgrade, even if the EQ+ looks very nice. Since I am using a VST eq anyway (melda eq is very good). MWaveshaper is free, too

[stamp]

^^^ usually the keys like esc, space, tab etc. are passed back to the host from the plugins, have you tried to assign it to the 'esc' key ?

Yes. But they are allready in use for other stuff. I find the all the focus stuff pretty f**ked up. Since you can't assign a key more then once there shouldn't be all these focus nonsense...

[SmajjL]

One Tarzan-method is to up the scale/waste space on purpose and use the "collapsed" mini-height TCPs instead as Default.
So use the large first, because they can be ALT+drag'ed together, and >
So that means that all you have to do is toggle the Use Large Track Height icon (hey! i'm zooming, or, summit..) the toggle remembers how the big-state was is what i'm saying.
Ps, did not say it was a perfect solution and i did not say i use it myself, yet.

[carlca]

Check your account; we made a very quick beta 2 update to address the vst2 issue with serum and some other vsts. I hope that it helps you testing, and sorry for that critical issue.

To Alex, and all your other fine colleagues, thanks for sorting out the vst2 issue so quickly - I didn't expect to get a fix until next week sometime

[antic604]

...and upgrades are optional.

The puke-inducing colours are not, though.

And I really enjoy working in Live again! Just started a new project and it's a lot of fun, even though I do miss modulators, some basic splitter tools, easy bouncing... Gotta explore those M4L options, i.e. Modulat.

I'm a visually-oriented person and I appreciate that Live (or S1, too) only "allows" colour to the tracks & clips, while everything else is limited to those same 4-5 colours / shades. Bitwig already in 3.1 added some weird phosphorescent hues (outside of the regular palette) to some devices, nesting brackets and displays. Now with those rainbows it looks like clown in a circus I wonder if there was some change in dev team responsible for the design? Because it's been going downhill lately, with seemingly random changes to some devices, while others are completely forgotten - e.g. why Compressor and Peak Limiter, but not Dynamics? Why mid/side splitter, but not multiband-3? Why FM-4 but not Polysynth? Live also has this (especially the AAS devices stand out in bad way) but it's been on the market for 20 years, not 6! And they still try: Wavetable, The Echo, Drum Buss, LFO/Shaper/Env.Follower all look great and consistent. They recently combined Simple and Ping Pong Delays into just ...Delay, to reduce the clutter. Even f**king Utility looks great now, with some design flair and consistency. Bitwig? Just have a look at what they did to Tool in 3.2 beta. It's just lazy and uninspired...

I'm obviously staying since I was stupid enough to activate both upgrade plans I bought for cheap, but I don't think I'll renew it anymore unless there's some fundamental shift in their priorities and direction.

[Vladislav_Gronk]

This is very cool, but I wish they had focused a bit more on "boring" workflow improvements instead of new shiny devices.