Bitwig 3.1 Composer-Focused Update: Top-3 Wishes Poll

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

Post

polishbroadcast wrote: Fri Jun 14, 2019 7:33 pm 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:
Darn, you just reminded me how much I liked the first interface.

Post

pdxindy wrote: Thu May 16, 2019 10:46 pm

Tempo Mapping... allows one to play a without a metronome and then the DAW will create a tempo map that matches what one plays and then that can be used to conform other tracks to that tempo.
YES!!

+1

Does that feature exist somewhere?
I work gridless because of this.

Post

stufflin wrote: Wed Jun 19, 2019 6:07 pm
pdxindy wrote: Thu May 16, 2019 10:46 pm

Tempo Mapping... allows one to play a without a metronome and then the DAW will create a tempo map that matches what one plays and then that can be used to conform other tracks to that tempo.
YES!!

+1

Does that feature exist somewhere?
I work gridless because of this.
Logic does this...

Cubase does too I believe... but I don't have Cubase so am not sure

Post

I want a drum rack that can target all pads to a single instance of a single instrument, and allow you to change the note assignments which each pad sends to that instrument, and name the notes by renaming the pad itself. Currently, the "send" note cannot be changed, and each pad gets its own instrument.

Why allow this? Two reasons:

1) To create a "standard mapping" from my pad controller, saved as a Drum Machine preset for each of my drum instruments or drum sets. This is so that, say, the kick pad (lower left) is always the kick pad, regardless of instrument. The target instrument/VST could be anything, like a Kontakt drum set, or Battery, or Superior Drummer. Various VSTs arbitrarily assign specific notes to specific hits, and there is no consistency to it. This solves that.

2) So that each note can be named after the hit in a proper drum scale, and allow you to use the drum score on ALL instruments, rather than forcing a chromatic piano scale to work for percussion. I mean, Bitwig has a drum score, and it's great. And it's useless unless the only thing you are working with is per-pad instruments. It should be usable with an all-in-one drum VST, but it isn't.

What would this look like? Pretty simple, really.

Just like today, you could drag an instrument onto a pad, which creates a chain. So nothing would break in the current workflow. But, each pad would gain 4 settings: Pad Name, Trigger note, Send note, and Target chain. These would all default to the hard-coded values they have today. But you could change them. Pad 1 could fire when it receives a C1, and send an E2 to Instrument A. Pad 2 could fire on D1, and send C2 to instrument A. So Instrument A is only loaded once, and responds to both pads.

And since each pad is nameable, that pad's name (and NOT the instrument name) is used in the drum score. Today, the name in the drum score comes from the instrument name, which of course would not work if the same instrument is responding to two different notes.

Perhaps the trigger note would need to remain hard-coded, and some sort of MIDI map effect could be used to map a pad controller or digital drum kit to a specific Drum Machine pads. As long as there is a way.

Post

Better bounce.

It would be nice if the bounced track gets name and color from the original instrument track with a suffix in the name and volume at 0dB. And keep sends+sends automation.

Post

stamp wrote: Fri Jun 21, 2019 10:16 pm Better bounce.

It would be nice if the bounced track gets name and color from the original instrument track with a suffix in the name and volume at 0dB. And keep sends+sends automation.
I agree, I sent a request to the team about this a couple weeks ago.

Post

If they could improve the playback from selection option that would be huge, when I’m in the piano roll or audio editor it takes more effort than it should to playback from the selected note or selected area. Every other DAW will playback right from the selected midi note or highlighted area. It works well in the arrange page but not in the editors so much, you have to use the cursor up in the ruler area to play back from selection which isn’t as accurate.

Post

stamp wrote: Fri Jun 21, 2019 10:16 pm Better bounce.

It would be nice if the bounced track gets name and color from the original instrument track with a suffix in the name and volume at 0dB. And keep sends+sends automation.
+1

Post

1. Another vote for GUI overhaul and upgraded piano roll.
2. I'd really like Live's "Capture and Insert Scene" feature.
3. I'd really, really like an "explode notes to tracks" option for Drum Machine that would create separate MIDI tracks for each pad of a single instance of Drum Machine for discrete editing.
Last edited by Notecrusher on Sun Jun 23, 2019 4:48 am, edited 1 time in total.

Post

Notecrusher wrote: Sat Jun 22, 2019 7:27 am "Capture and Insert Scene"
Is that different from "Add scene from playing clips"?
.................................
"Hell is other People" J.P.Sartre
.................................

Post

stamp wrote: Fri Jun 21, 2019 10:16 pm Better bounce.

It would be nice if the bounced track gets name and color from the original instrument track with a suffix in the name and volume at 0dB. And keep sends+sends automation.
Also realtime bounce in place for hw synths.
And to make it even more complete, render tails when bouncing in place and crossfade audio with midi. Automagically, of course.

Post

Notecrusher wrote: Sat Jun 22, 2019 7:27 am 1. Another vote for GUI overhaul and upgraded piano roll.
2. I'd really like Live's "Capture and Insert Scene" feature.
3. I'd really, really like an "explode notes to tracks" option for Drum Machine that would create separate MIDI tracks for each pad of a single instance of Drum Machine for discrete editing.
2&3 for sure. I'd really like them to wait for a GUI overhaul, which I don't think it really needs, until they have the thing more feature complete. Part of that, however, comes from the fact that I don't like the 2.x/3.x GUI as much as I liked the 1.x GUI.

That said, it apparently supports templates, so opening that up to the user base would be very nice indeed. However, as with Live, I think they like their look (basically I do as well) and want it associated with the program. I've had people look at both Logic and Reaper skinned and ask me what DAW it was. Probably not a real concern.

Post

Karbon L. Forms wrote: Sat Jun 22, 2019 1:01 pm
Notecrusher wrote: Sat Jun 22, 2019 7:27 am "Capture and Insert Scene"
Is that different from "Add scene from playing clips"?
THANK YOU I never knew that existed! I see it now in the ADD menu, I was looking on context menus.

Post

1 Better Piano roll / Midi Editing (and please, please fix the fold/drum view bug)
2 Midi Note chasing
(don't see this requested that often, doesn't this drive you all mad ?)
3 Adjust parameter with arrow keys

And

3b Stretch audioclips in preview
3c Better bounce / Freeze tracks also with external instruments.
3d Auto naming save-as
3e Narrow track width. You can scale tracks up in Bitwig but not down..
3f Auto truncate clips
3g drag parts of clips drum machine and auto trim like live

Post

stamp wrote: Fri Jun 21, 2019 10:16 pm Better bounce.

It would be nice if the bounced track gets name and color from the original instrument track with a suffix in the name and volume at 0dB. And keep sends+sends automation.
+1
RME Babyface Pro / Bitwig / Adam A7X / Maschine+

Post Reply

Return to “Bitwig”