Bitwig 2.0 - Functionality Discussion!
-
- KVRist
- 84 posts since 3 Jan, 2016
Yes, that's what I heard too. No one can confirm it but fingers crossed! And yes they can talk about it, Alpha testers already have the beta version and some said that they can post vids too if they like.
Polarity had a live stream a day ago playing around with the beta version but don't take my word for it, if you ever receive an invite for the beta, I am sure they will fill you in with any necessary instruction regarding discretion, if any needed.
Peace
Polarity had a live stream a day ago playing around with the beta version but don't take my word for it, if you ever receive an invite for the beta, I am sure they will fill you in with any necessary instruction regarding discretion, if any needed.
Peace
-
- KVRist
- 90 posts since 1 Aug, 2008
Is it possible to hide graphics of devices to save some cpu?
Does deactivate device also unload ram?
Can you select more devices from different tracks and turn them off to hear affect of plugins in whole mix?
Does the project remembers folded device state (small collumn without paramaetr readout)?
Could it be setted up to be folded like default state?
This will saves me tousands of clicks.

Does deactivate device also unload ram?
Can you select more devices from different tracks and turn them off to hear affect of plugins in whole mix?
Does the project remembers folded device state (small collumn without paramaetr readout)?
Could it be setted up to be folded like default state?
This will saves me tousands of clicks.
-
- KVRist
- 90 posts since 1 Aug, 2008
Thanks for that comparisin. Now lets discuss it. These are good news because it is possible to have it smaller with the new layout. Because I see some wasted space. It doesnt matter how they present project tab. How many times do you click it?TeotiGraphix wrote:Do the math, it's like +/- 5 px we are talking about here.
As far as the actual impl of the title and tool bar that is still being discussed in beta.
But before you start talking, measure stuff first, it is an optical illusion, you are loosing NO space. It's the new design you don't like.
For me bigger floating after click (touch for touch compatibility) transport bar will be more than enough otherwise I need room for music making and thats the space bellow. I think we computer users are now hostages of touch devices that have only one input device
- KVRian
- 1372 posts since 28 Dec, 2012 from Meredith NH
Realistically, the display profiles should adapt to this (touch/mouse) since the whole UI is a flow layout. It's just if Bitwig has plans to do this right now or if ever.linkstate wrote: I think we computer users are now hostages of touch devices that have only one input device
Michael Schmalle
http://www.teotigraphix.com
Surfing on sine waves
Maschine4Bitwig - Studio, MK2, MikroMK2, MK1
http://www.teotigraphix.com/bitwig/maschine
http://www.teotigraphix.com
Surfing on sine waves
Maschine4Bitwig - Studio, MK2, MikroMK2, MK1
http://www.teotigraphix.com/bitwig/maschine
-
- KVRian
- 798 posts since 17 Nov, 2015 from Yuma
i like the new design a lot more. but my question is, is it still that nervewrecking fiddlily thing to get the cursor changes in the transportbar? like its a matter of ONE pixel up or down to get the cursor icon you wanted, e.g. to set the loop region. this was and is one one the single most annoying things to do in bitwig 1.3.15,linkstate wrote:Thanks for that comparisin. Now lets discuss it. These are good news because it is possible to have it smaller with the new layout. Because I see some wasted space. It doesnt matter how they present project tab. How many times do you click it?TeotiGraphix wrote:Do the math, it's like +/- 5 px we are talking about here.
As far as the actual impl of the title and tool bar that is still being discussed in beta.
But before you start talking, measure stuff first, it is an optical illusion, you are loosing NO space. It's the new design you don't like.
For me bigger floating after click (touch for touch compatibility) transport bar will be more than enough otherwise I need room for music making and thats the space bellow. I think we computer users are now hostages of touch devices that have only one input device
like worst case: u defined a large loop area upfront, then while checking the track later, u want to get a new shorter loop region but instead of setting the loop region u missed the loop cursor and instead moved the whole loop region from before.
the whole transportbar was a nerve wrecking ball tbh^^. i really hope this is better now^^. PLZ! ;D
[aˈtoːm] [aːl] [ˈa(ː)tonaːl] IV
https://soundcloud.com/atomaalatonal4
https://soundcloud.com/atomaalatonal4
- KVRAF
- 4804 posts since 21 Jan, 2008 from oO
Maybe set up a shortcut for "Loop selected region". That way you can quickly define a loop area, no need to use the mouse here imo.
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRian
- 844 posts since 6 Nov, 2004 from UK
This was one of my biggest issues in v1 as well, and it's a turn off for anyone coming from other daws such as logic where 'swiping the region' is fast & natural. There's plenty to grab hold off.i like the new design a lot more. but my question is, is it still that nervewrecking fiddlily thing to get the cursor changes in the transportbar? like its a matter of ONE pixel up or down to get the cursor icon you wanted, e.g. to set the loop region. this was and is one one the single most annoying things to do in bitwig 1.3.15,
Whilst still not perfect, v2 works better because you can now easily swipe time regions anywhere on the arranger area, without selecting any extra tools. This mean that a quick swipe followed by pressing your "loop selected region" shortcut key (mines set to "L") will do the job nicely.
-
- KVRAF
- 2140 posts since 16 Jan, 2013 from USA
As I've said, I like the whole deal. Everyone is going to have a different take on what is the correct size, and eyesight varies quite a bit.Andrey Marchenko wrote:For sure. I don't like design solution for transport bar since day one. It's too huge.TeotiGraphix wrote:It's the new design you don't like.
-
- KVRAF
- 5144 posts since 3 Oct, 2013
no it was upscaled to 125%, right is the 100%Andrey Marchenko wrote: xbitz, you think that UI became bigger?

pheeew
"Where we're workarounding, we don't NEED features." - powermat
-
- KVRist
- 90 posts since 1 Aug, 2008
I would like to see more divergence between fat bars and buttons for touch and computer (90% usage) with keyboard and mouse with maximum working area. Maybe GUI downscale would do it. 
-
- KVRian
- 1224 posts since 2 Dec, 2008 from Finland
Looking at screenshots people are posting... what happened to the snap settings (lower right corner in arranger and edit view), looks like they're gone?
And someone mentioned Python support, what's that about?
And someone mentioned Python support, what's that about?
- KVRer
- 17 posts since 5 Apr, 2014
Don't worry, it's still there.ras.s wrote:Looking at screenshots people are posting... what happened to the snap settings (lower right corner in arranger and edit view), looks like they're gone?

Specs.: MacMini" (2018) OS X 10.14.3, i7 3,2 GHz, 64GB Ram, 1TB + ext. 2x1 TB SSD Samsung EVO 840 in Akitio Neutrino Thunder Duo, UAD Apollo Twin mk2 Quad, Roland A-49 and many many VST(i)'s.
-
Andrei Marchenko Andrei Marchenko https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=312360
- KVRian
- 866 posts since 12 Sep, 2013
xbitz, thanks!
- KVRist
- 459 posts since 28 Mar, 2014 from Los Angeles, CA
This is hilarious (and totally not useful), but goes to show how ingrained the new modular system is. You can modulate the spectrum analyzer fall rate. 



