CONCISE BITWIG FEATURE REQUEST

[Ogopogo]

When it comes to the ab sliders maybe there is a more basic way to work them in than just plopping them on the gui. I mean they are just two busses with crossfading right? Maybe there is or will be another way to set that up, or maybe you could do it with as many of your own busses as you want. For example you could have something like the x/y instrument layer only it could fade between four busses instead of chains. Then you could also set up your own effects on each of the busses.

[grymmjack]

A: agreed, I'd like to see Bitwig setup something similar. But seeming as there isn't yet something, I thought it might catch on/would make sense to put this together, as, there are threads and threads of people all saying the same thing, and posts and posts of people repeating the same features with different words, and, it just makes sense to put it together in this way, for everyone.

B: it would arguably be the most efficient format for everyone involved if the guidelines were adhered to (the opposite of poor); this way all feature requests would be/are noted, though none are repeated whilst at the same time preference/support for the requests is rated. I'm willing to hear other suggestions if you have any for a more efficient, succinct yet thorough approach?

I was just going to send a load of feature requests to bitwig, or just add them to the list on here, either starting a new thread or to one of the existing ones, but thought of attempting to put something more concise together, as, reading through pages of posts repeating themselves, or in the case of any developers, emails/messages, just seems painfully inefficient, and I would assume that everyone would think similarly.

I opened the question here: http://www.kvraudio.com/forum/viewtopic ... 3#p5704843

Though, it seems it hasn't taken off, it hasn't been turned into a sticky and the guys at bitwig haven't replied, so, fair enough, I'm sure they're busy, I was just trying to save everyone some time.

You have good intentions. You remind me of days of old KVR when people like yourself took up such causes personally to help mechanize this kind of thing, and I don't want to discourage you. You aren't hurting anyone, I think I was projecting a little because we've not seen an official way for Bitwig to handle this kind of stuff and I am now emotionally tied to BWS because I like it very much and hope that it becomes a huge success and somehow think that the support (which on a personal level and note Dom has been great) and the ad-hoc nature of how it's delivered might not cover all the bases. I have no proof of this, it's just a hunch.

Keep doing your thing, Jono.

It just seemed like there were more than 10 FR's in all of KVR (:)) and your list was pretty short, also my reaction stemmed from the way the poll was setup: You can choose up to 10, and there are only 10 possibilities All of those FR's sound pretty good, so I'd have voted for all 10. What concerns me is that this was the first real attempt from a user who promoted themselves to some higher purpose with good intentions but that poll was way too closed off and rigid to allow the capture to happen with say 80% or more coverage. I think if you want to serve like this, you're on the right track in life in general, but please be more thorough. I have to believe there were more than 10 FR's for BWS in all of KVR and these 10 are personal favorites of yours and hence I'm cynical of the outcome making much of a difference.

As I stated and you agreed, Bitwig needs to step up to the plate to do this, and judging by the frequency and the BWS communication here, they are doing a good job it's just that I'm paranoid for small time developers and am really getting on good with their software so want them to succeed.

Have a good day,

[gjvti]

I checked global macro, but in fact I would expect Kapture like global parameter snapshoots save/recall (perhaps within scenes) - to streamline save/recall process users should be able to define which parameters globally they would like to save/recall with scenes.

[ansolas]

This should be the default behavior of any modern DAW:
https://forum.ableton.com/viewtopic.php?f=35&t=207928

[Bako]

what BTW could do as alternative to copy , paste time to hugely increase WORKFLOW is to be able to select section of the song with time selection tool and SIMPLY grab that selection and move or pase it in different section of the song without (currently ) 1. selecting a song section 2. cutting withing selection ctrl + e . 3 copy that selection . 4 paste the selection . little too long , time consuming workflow reducer. it would be huge WORKFLOW improvement

demonstration here in this video from 13.48
couldn't find EN demo video . there he names different loop selection takes . but you don't have to name selection to make it faster.
it really is a huge creative tool -WORKFLOW is a key WORD here !!! i tried it and i really wish BTW could have something similar. it makes you think differently cos' it enables you to think very fast and creative !!!

THX FOR MAKING BTW !

[Coockie1176ln]

Crossfading for djs is called a and b and excist in bitwig

[yoshi303]

i like polls (voted), just miss :

+ right mouse click to select time tool, cut tool, arrow tool...

+ track delay +/-

.

[audientronic]

I guess video is the fish.

[xbitz]

a major a piano roll overhaul with audition tool, scale snapping, a tool which can draw, delete, modify notes using only mouse buttons, a note brush, multi-note operations etc. quite easy just have to copy the one in Sonar

so a piano roll workflow somehow should work like this >


and clip linking, that's all

[Regnas]

All I need is on my signature....

[xbitz]

All I need is on my signature....

"Be able to change devices etc (by drag and drop) in layered editing mode."
device bar is changing accordingly to the selected track (not in clip mode) in 1.2 , a small step for bitwig, but ...

"Floating windows... (anyone?)"

I would add x-ray feature for laptop users, just is in Sonar (yepp I really like Sonar btw as u can see, but BWS too)



otherwise it's useless

[SB-SIX]

RECORD QUANTIZE - I'd like to be able to switch on record quantization, so when live playing/drumming on a midi device records notes quantized to the grid

EASILY ADJUST LOOP MARKERS OUTSIDE SCREEN BOUNDS - When a loop is bigger than the visible area, loop markers cannot be shortened without zooming out. They solved this in ableton: The loops can always be adjusted on the edges of the view.

VISIBLE PLAY MARKER IN SAMPLER - I'd like to see what portion of the sample is played

[Eta Carinae]

I would like VST multi outs to act like normal audio tracks, so that I can route them anywhere. And I also want VST 3 support. Can you add these to the poll?

[xbitz]

RECORD QUANTIZE - I'd like to be able to switch on record quantization, so when live playing/drumming on a midi device records notes quantized to the grid

EASILY ADJUST LOOP MARKERS OUTSIDE SCREEN BOUNDS - When a loop is bigger than the visible area, loop markers cannot be shortened without zooming out. They solved this in ableton: The loops can always be adjusted on the edges of the view.

VISIBLE PLAY MARKER IN SAMPLER - I'd like to see what portion of the sample is played

RECORD QUANTIZE


EASILY ADJUST LOOP MARKERS OUTSIDE SCREEN BOUNDS
just should use the time selection(2) tool then the Loop Selected Region tool (default is Ctrl+L)

[panox80]

at the moment i'd like to have a spectrum in eq and a spectrum in the box...i think this is essential at this point of the daw