Latest News: Bitwig updates Bitwig Studio to v5.1
Bitwig 3.1 Composer-Focused Update: Top-3 Wishes Poll
-
- KVRer
- 14 posts since 28 Feb, 2017
1) Normalize a track/clip/event, with the option to set a ceiling. And correct the DC offset while you're at it
2) Option to export a track as mono.
3) Time stretching options in the Sampler.
2) Option to export a track as mono.
3) Time stretching options in the Sampler.
-
- KVRist
- 85 posts since 20 Dec, 2018
So here's a GIF showing my problem:
As you can see there's no way to copy or duplicate just the envelopes. The Time tool duplicates both the envelopes and the audio.
All I see in the Automation Editor Panel is Volume/Pan/Mute/S1 Effect/Crossfade Mode and none of them corresponds to the functions in the Detail Editor Panel.
Could you show me how to edit the formant and pitch envelopes in the "Automation Editor Window..."?
As you can see there's no way to copy or duplicate just the envelopes. The Time tool duplicates both the envelopes and the audio.
Have I missed something or are your "existing features" still not even close to what I'm asking for?
All I see in the Automation Editor Panel is Volume/Pan/Mute/S1 Effect/Crossfade Mode and none of them corresponds to the functions in the Detail Editor Panel.
Could you show me how to edit the formant and pitch envelopes in the "Automation Editor Window..."?
-
- KVRist
- 401 posts since 27 Mar, 2019 from stuck in Russia
automating audio gain is not the same as doing so with clip automations (using mixer volume), as you see gain affecting waveform directly. also you can't automate audio event pitch/formant outside of the audio event.pdxindy wrote: ↑Wed Jun 05, 2019 6:29 amUp to you whether you want to use the existing features or not...
For feature requests you should email support so they know.
- KVRAF
- 25421 posts since 3 Feb, 2005 from in the wilds
You initially asked about gain and did not mention pitch or formant. I was responding to your specific request... no big deal. I'm all in favor of your feature request.
-
- KVRist
- 191 posts since 13 Mar, 2018
It's beyond me why we can't copy automation for gain/pitch etc but still we can copy automation dots elsewhere. I wouldn't even consider fixing this fault (along a with lots of other user interface inconsistencies) a feature request but a matter of maintaining the fundamentals of the program and keeping things in order. Hopefully they will overhaul the entire UI in 3.1. It's not particularly convenient to learn by trial and error where the user interface behaves like you expect it to and where it does not.
-
- KVRist
- 85 posts since 20 Dec, 2018
Gotcha.
Yeah, I agree that this is more of a bug than a missing feature. +1 on the UI overhaul.kpv wrote: ↑Wed Jun 05, 2019 2:35 pm It's beyond me why we can't copy automation for gain/pitch etc but still we can copy automation dots elsewhere. I wouldn't even consider fixing this fault (along a with lots of other user interface inconsistencies) a feature request but a matter of maintaining the fundamentals of the program and keeping things in order. Hopefully they will overhaul the entire UI in 3.1. It's not particularly convenient to learn by trial and error where the user interface behaves like you expect it to and where it does not.
-
- KVRer
- 14 posts since 30 Dec, 2018
Some more suggestions to improve the UX of core DAW features in Bitwig:
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.
-
- KVRist
- 99 posts since 30 Mar, 2005
A button for randomized search results or item listings in Bitwig's browser would be awesome. Something like the loopcloud one. Good way to find some "unused" samples or presets.
-
- KVRAF
- 1996 posts since 16 Jan, 2013 from USA
Exactly how are these composer-related?Amfi wrote: ↑Wed Jun 05, 2019 6:46 pm Some more suggestions to improve the UX of core DAW features in Bitwig:
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.
-
- KVRer
- 14 posts since 30 Dec, 2018
I guess you are referring to mixing vs. composing. But can you really make this distinction? And does it matter? I do all at the same time (record midi/audio and mix) - it's more of an iterative processjonljacobi wrote: ↑Wed Jun 05, 2019 11:17 pmExactly how are these composer-related?Amfi wrote: ↑Wed Jun 05, 2019 6:46 pm Some more suggestions to improve the UX of core DAW features in Bitwig:
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.
- KVRian
- 985 posts since 10 Sep, 2014
Do more with less clicks allows you to compose faster, doesn't it?jonljacobi wrote: ↑Wed Jun 05, 2019 11:17 pmExactly how are these composer-related?Amfi wrote: ↑Wed Jun 05, 2019 6:46 pm Some more suggestions to improve the UX of core DAW features in Bitwig:
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.
-
- KVRer
- 14 posts since 30 Dec, 2018
it does indeedstamp wrote: ↑Thu Jun 06, 2019 4:14 pmDo more with less clicks allows you to compose faster, doesn't it?jonljacobi wrote: ↑Wed Jun 05, 2019 11:17 pmExactly how are these composer-related?Amfi wrote: ↑Wed Jun 05, 2019 6:46 pm Some more suggestions to improve the UX of core DAW features in Bitwig:
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.
-
polishbroadcast polishbroadcast https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=144016
- KVRist
- 46 posts since 16 Mar, 2007
Multi-takes / Comping
Match Tempo to Region
(for when you want to match a project to a loop you recorded)
Posted about it 2+ years ago: viewtopic.php?t=478843
Also requested on the Bitwig site.
Fiddly workaround for now: https://www.youtube.com/watch?v=Qm6add_lx5E
Match Tempo to Region
(for when you want to match a project to a loop you recorded)
Posted about it 2+ years ago: viewtopic.php?t=478843
Also requested on the Bitwig site.
Fiddly workaround for now: https://www.youtube.com/watch?v=Qm6add_lx5E
-
- KVRAF
- 1996 posts since 16 Jan, 2013 from USA
With that as your criteria, you can suggest anything you want. Hijack away.Amfi wrote: ↑Thu Jun 06, 2019 4:26 pmit does indeedstamp wrote: ↑Thu Jun 06, 2019 4:14 pmDo more with less clicks allows you to compose faster, doesn't it?jonljacobi wrote: ↑Wed Jun 05, 2019 11:17 pmExactly how are these composer-related?Amfi wrote: ↑Wed Jun 05, 2019 6:46 pm Some more suggestions to improve the UX of core DAW features in Bitwig:
1) Arrange view: show current level setting of each track (display the numeric value). Today, the current level is only shown when touching and moving the fader.
2) Mixer view: Allow editing multiple channels at a time. Today's behavior: if you select (shift-click) multiple channels and e.g. click "mute" on one of the selected channels, only this one channel will be muted. Expected behavior: all selected channels will get muted. Same for solo, level, pan etc. That's how it works in all other major DAWs (Logic, Ableton etc.)
3) Mixer view: Allow resizing mixer channels to make them narrower (not wider!), so that more channels fit on one screen and less scrolling is needed.