What drives you crazy in Bitwig?

[pdxindy]

Hmmm... just checked, I see no way to do so.

I have a few 3rd party chorus plugins and none of them have a reset on transport option either.

You could automate the mix parameter to start from 0 and fade in a bit to hide any initial difference?

Renoise can do that!

I've never happened upon a need for restarting the Chorus phase at the same value.

I like my oscillators without temp sync, so I have no need for tempo sync'd oscillators.

That was some poor logic there.

I communicated poorly... I was trying to say, does a Chorus make enough difference that an LFO reset on it matters?.. I can easily hear when an LFO modulating something starts at a different phase. It is an obvious difference. I don't hear much difference with a Chorus. So what use case for it matters?

[Hanz Meyzer]

I think it's dependent on the amount and feedback of that fx. For example, I was using some dubby modulation, which is very dependent on rhythm. So I would like to nail it to an exact sync to the rhythm. Same for instance, if I use a chorus on a synthbass, where I would like to have a rhythmical synced modulation. If you have multiple of free running and also not start-synced modulations it might turn into a random-mess.

But ok, if I use the LFO modulator, set it to sync and change the start phase, I somehow can setup the start position - as long as I do not move the arrangement.

[MegaPixel]

I think it's reasonable to assume that the majority of sales are made around the time of a major release, and expired licenses are refreshed around that time, too. I could be wrong, of course.

I like to wait 0.5 to 1.5 years till I renew with yearly subbed software. Especially with BitWig at the moment, there needs to be a lot of time spent on enhancing / cleaning up what they got and extending that user interface menu with a lot more options to allow people to use it in the way that makes them comfortable with it.

I also don't like buying software at major version release date, v9.0.0 is going to be full of bugs they will be testing on the public for example. I would easily wait till v9.2.x or v9.3.x for things to be cleaned up and stable.

At the moment what I can't do in BitWig I jump over to FLStudio, do it there and then jump back to BitWig with the sample or note sequence exported as midi. The piano roll on FL is vastly superior to BitWigs, but that's about it... Also you remote control FLStudio ish via the FLStudio VSTI in BitWig.

[pdxindy]

I think it's dependent on the amount and feedback of that fx. For example, I was using some dubby modulation, which is very dependent on rhythm. So I would like to nail it to an exact sync to the rhythm. Same for instance, if I use a chorus on a synthbass, where I would like to have a rhythmical synced modulation. If you have multiple of free running and also not start-synced modulations it might turn into a random-mess.

But ok, if I use the LFO modulator, set it to sync and change the start phase, I somehow can setup the start position - as long as I do not move the arrangement.

The Bitwig Chorus LFO doesn't sync to tempo.

You could create a Grid FX patch that works as a Chorus and has a tempo synced LFO which resets on transport start.

[machinesworking]

I communicated poorly... I was trying to say, does a Chorus make enough difference that an LFO reset on it matters?.. I can easily hear when an LFO modulating something starts at a different phase. It is an obvious difference. I don't hear much difference with a Chorus. So what use case for it matters?

I'm like you, not that picky about it, but chorus like phasers and flangers is a doubling or delay effect, causing high and low end phasing that gives a nice sound. Obviously this is going to change the mix, if you were some super anal retentive tight beat producer it could be useful to sync that phase to the beat so there are less clashing frequencies. Some people want the bass of a kick on the 1st beat to be as loud as possible, so getting a modulation type effect synced would be handy.

It's in the end pretty nitpicky, but Bitwig is mostly about synchronized electronic music of all types so I get the logic of it.

[codec17]

I wish when you got minimal track height, you see the waveform instead of clipname. Space is there because name and waveform are ALMOST 50/50 in height. Wich is ridiculous IMHO. I rather have 75% waveform and 25% clipname. And changing trackheight is so clunky. I hope they change it sometime with a ALT or CTRL + scrollwheel or something.

[antic604]

...I hope they change it sometime with a ALT or CTRL + scrollwheel or something. :pray

SHIFT, please.

ALT and CTRL are already taken for left/right scrolling and in/out horizontal zoom respectively

[codec17]

...I hope they change it sometime with a ALT or CTRL + scrollwheel or something. :pray

SHIFT, please.

ALT and CTRL are already taken for left/right scrolling and in/out horizontal zoom respectively

I dont care.. If i can scroll... im in!

[codec17]

...I hope they change it sometime with a ALT or CTRL + scrollwheel or something. :pray

SHIFT, please.

ALT and CTRL are already taken for left/right scrolling and in/out horizontal zoom respectively

I dont care.. If i can scroll... im in! They really know how too make use of the pixels as much as they can.

[MegaPixel]

Here's some ideas for them.... If only...

Main Window - Concept

To view full size image: https://aftc.io/share/WigBit/MainWindow.jpg

Change 1:
Handles on main timeline blocks for resize and repeat (top right and btm right) for resize & Nicer cursors

Change 2:
Main timeline now has the horizontal & vertical scroll bars from FLStudio but slightly enhanced to fit with WigBit & a new cursor)

Change 3:
Main window right browser window, removed devices (recursive capabilities in concept settings screen)

Change 4:
Piano roll mouse location cursor now has horizontal & vertical lines coming off it so you know where you are when zoomed out and dragging stuff etc. Also highlights background grid row and the key your on, on the virtual keyboard to the left.

Change 5:
Piano roll, selection area now boxes only selected notes and you can stretch them by grabbing the left and right sides (cursor indications). Drag by grabbing any notes and mouse move as usual.

Change 6:
Piano roll, notes now have resize handles on right.

Change 7:
Piano roll, FLStudio scroll bars, slightly adjusted for WigBit, for horizontal and vertical scroll.


Settings Window - Concept

Extra options, just some added of I would like to see wigbit add. Eg. Disable recursive browser folder reading on either popup instrument browser or the right main window browser.



Instrument Popup Selection - Devices


Changes
1. Removed music tab
2. Cleaned it up by moving any device types to left frame
3. Removed counters (also now becomes an option in settings if you want it back on)

Similar changes for the other sections:

Instrument Popup Selection - Presets


Instrument Popup Selection - MultiSamples


Instrument Popup Selection - Samples

[Echoes in the Attic]

The single thing that drives me the most crazy in Bitwig is that when I'm using a pen on my surface tablet (which is a one-handed workflow), you can't use the touch dial or other functions properly one-handed with just the pen because they force two handed gestures. I've suggested a simple setting that lets the dial stay open when you tap, but they didn't listen. It would be so easy and mean that a pen would be usable (Can't use it with touch setting turned off for pen because there is a delay that offset the input).

[MegaPixel]

Bit better / more interactive than the screen shots, who knows maybe the wigbit guys might find it interesting.

https://aftc.io/share/WigBitDemo/

[antic604]

Bit better / more interactive than the screen shots, who knows maybe the wigbit guys might find it interesting.

https://aftc.io/share/WigBitDemo/

To be perfectly honest I appreciate the amount of work you've put into it, but I disagree with most of the requests (e.g. we need less scroll bars, not more / more visible) or at least they point towards you simply not being familiar with Bitwig yet and trying to impose other DAWs' looks & workflow onto it. Like the coursors, "lighter" icons or browser organisation, for example. It takes half a day to learn what does what for observant and patient user. It is Bitwig's strength that the options and settings are so few & far between. I get a headache when I think of FL, Cubase or Reaper with endless, multi-level menus wherever you click or pages & pages of Settings.

But, obviously, all the above is IMO and you're fully entitled to share the ideas with users & devs for their consideration

[lokanchung]

Bit better / more interactive than the screen shots, who knows maybe the wigbit guys might find it interesting.


https://aftc.io/share/WigBitDemo/

Nice job. But here's some points I don't like.
- We need neater cursor. Yes but your design needs some rework to fit in.
- I don't care about scroll bars.But I never used it to zoom in/out in my 15 yrs of FL Studio experience.
- No need for extra scroll bar at the bottom of arranger.
- I use music tab in the browser when I'm searching for reference while mixing.
- Two lines you can from box selection don't represent selectied area but time range. It's meaningful when duplicating or stretching notes.
- Pitches are pretty clear without horizontal cursor because of piano-like highlights. I'd rather have thicker octave lines and bar lines.
- Why prevent resizing from left?

I guess you took many things from FL Studio. My top 5 features to steal would be
- Knife tool
- Piano roll extras (strum tool, note glue, note wrap)
- Automation Curves
- Set note length (stock note length)
- Linked Clips

[Whywhy]

What drives me crazy about bitwig is their massive amount of smoothing cc data for vst instruments.
Please, let the final users decide if they need it or not. Bitwig could be my only daw but this little thing push me far away from it.