Official feature request thread(?)

[Wuji]

Hello,

To save both the users and developers trawling through emails and posts on feature requests, is there yet a feature request/official feature request thread anywhere online?

Obviously, the benefits/rules would be to post feature requests, but to ensure you read through the thread as to save repeating a request (avoiding long threads).

Would it be possible to get someone here/a user/someone from the bitwig team to monitor the thread and get a poll where every feature mentioned is added, thus providing a means to see the populations desire for a certain feature, without an overly long thread with people agreeing: "+1 for blah blah blah feature" or "I agree with blah feature", enabling a thread that would just have feature requests, or, (for those who haven't done the research/or have missed a feature) if the feature already exists, someone highlighting/explaining that it already does exist?

I've got a few in mind, but will save them in case such a thread is already in place.

[machinesworking]

I think this is an "if they call, they will come" type of thing. There's no official thread, but if you make one, and update the original post to include all relevant requests, I'm sure the Bitwiggers would take notice. Do something like limit it to 5 features per user, that way the most relevant to all are represented.

With that in mind here's mine:

1. REX, .sd2, Ogg, .caf etc. support- Bitwig should be able to convert at least these files to WAV.

2. Mouse Wheel support - Digital Performer has this and it's really great for faders, I hardly use my Mackie Control at all when using DP.

3. Better CPU performance- Bitwig is a 25% step down in performance from Live, and even worse with DAWs like Logic, DP, Reaper etc. Too big of a cut, they need to improve that.

4. Launching clips should at the very least be able to be assigned to a specific MIDI port and key. I understand that controller integration is important etc. but I'm surprised by this Omission compared to Live?

5. ReWire support- Even better, design your own version. Bitwig is in development, it's not going to probably ever meet everyone's needs, so being able to lock transport with another DAW, and route audio etc. is essential to a lot of people. The main problem with ReWire as it stands is the losing of VSTs, your own version of ReWire without losing VSTs would convert me from Live yesterday!

[Echoes in the Attic]

There is the "things you would like to see in Bitwig" thread which has kind of been the default so far, but yeah nothing stickied which would be nice.

[Simulant]

I'd like to see an extensive list, some acknowledgement, and an official word as to whether they'll implement it and when.

[Ogopogo]

So you want a complete roadmap of everything they're going to do and when? Not gonna happen. It will tie their hands. They need to be able to reassess priorities, rework ideas if they aren't working out, and release stuff when it's good and ready rather than when they estimated it would be ready a year or more before. Trying to lay it all out for people is just asking to get screamed at when it inevitably doesn't go as planned. Just let them work, they don't need us backseat developing. They will probably inform us of the more important stuff, as they have done with groups and vst multi out.

Anyway here is the unofficial wishlist thread so far: http://www.kvraudio.com/forum/viewtopic ... 9&t=406975

Yeah, I might be nice if that were renamed Feature Request or something and stickied so that there aren't a bunch of fr threads that fall of and disappear.

[Wuji]

Yeah, I'm not looking for a when or even if they'll implement, just a concise, succinct feature request thread.

In short, is it possible to have a thread and add things to a poll as it goes on like I have said?

Respectfully, I think my proposal, if possible to execute, is preferable to either the 5 feature requests per user (which, still, again, leads to longer than necessary threads for both users and developers), or, what is so far the "what you would like to see in bitwig", as, this has turned into more of a discussion etc. The whole thing is to get feature requests to the developers as concisely as possible, and have the thread constructed as concisely as possible, for those who don't have time/the desire to read through 20 pages of the same stuff being asked in a different way; as well as providing a clear indication of interest behind features.

The whole thing would go/the sticky would be:

OFFICIAL BITWIG FEATURE REQUEST

TICK THE POLL FOR FEATURES YOU WANT TO SEE, OR ADD A REQUEST IF THE FEATURE HAS NOT YET BEEN REQUESTED

RULES/GUIDELINES:

1. ENSURE TO READ THE POLL AND THROUGH THE ENTIRE THREAD BEFORE POSTING A REQUEST (INCASE THE FEATURE HAS JUST RECENTLY BEEN REQUESTED, BUT NOT YET ADDED TO THE POLL, THIS SAVES EVERYONE TIME AND KEEPS THE THREAD CONCISE)

2. ONLY POST FEATURE REQUESTS OR EXPLAIN THAT A FEATURE ALREADY EXISTS IF IT HAS BEEN REQUESTED AND NOT YET EXPLAINED/POINTED OUT (PREFERABLY AS CONCISELY AS POSSIBLE, OR BY PROVIDING A LINK TO A THREAD/SITE/POST/SUGGEST MANUAL PAGE, ETC)

3. WHEN POSTING REQUESTS, BEGIN WITH CONCISE AND AS EXPLANATORY AS POSSIBLE TITLE (IN CAPITALS), SUCH AS: "SPECTRUM ANALYSER IN THE EQ", FOLLOWED BY FURTHER DETAILED EXPLANATION OF WHY IT'S IMPORTANT/USEFUL, HOW IT WOULD WORK, WHY IT SHOULD BE IMPLEMENTED/ALL THE OTHER DETAILS, SUCH AS: - A spectrum analyser included in the eq (as in logic and other eqs) allows for easier eq edits/crafting in general, but, in particular is useful for adjusting frequencies that may not be in the monitors frequency response/range.

[Wuji]

I'm just going to start it and see if it works.

[Ogopogo]

A poll in one thread would probably get unwieldy pretty quick. There are a million things and some stuff can be looked at different ways. You'll probably run out of places in the poll and polling forums members isn't exactly scientific either. Discussions are probably the best. And it's not really official if Bitwig doesn't set it up is it? I say just keep adding on to that main thread or start a thread for a specific feature if you really think it's important enough or requires its own discussion. Maybe bitwig will sticky it if they see fit. Starting an "official" poll thread will probably just add to the noise.

[Simulant]

So you want a complete roadmap of everything they're going to do and when? Not gonna happen. It will tie their hands. They need to be able to reassess priorities, rework ideas if they aren't working out, and release stuff when it's good and ready rather than when they estimated it would be ready a year or more before. Trying to lay it all out for people is just asking to get screamed at when it inevitably doesn't go as planned. Just let them work, they don't need us backseat developing. They will probably inform us of the more important stuff, as they have done with groups and vst multi out.

Anyway here is the unofficial wishlist thread so far: http://www.kvraudio.com/forum/viewtopic ... 9&t=406975

Yeah, I might be nice if that were renamed Feature Request or something and stickied so that there aren't a bunch of fr threads that fall of and disappear.

Do you work for Bitwig? If not, please don't interfere and tell me what I can and can't do! I don't need or want your advice.

[Simulant]

I'm just going to start it and see if it works.

A poll is a good idea, but only when we have an extensive list. Some things have been confirmed already, but what we need is a thread where the first post is updated as people add requests. Then maybe set up a poll with those features, see who wants what.

From what I've seen, the developers are listening and making changes that we'll be happy with, which is pretty awesome.

Once there's an official thread up, it might cut down on the feature request posts that are all over the forum. And hopefully someone from Bitwig could give us an indication as to what they might implement.

[Wuji]

but what we need is a thread where the first post is updated as people add requests.

If people followed the guidelines concisely as I have laid out, then there'd be no need for this. The result would be pretty much synonymous to "but what we need is a thread where the first post is updated as people add requests."

[Ogopogo]

Do you work for Bitwig? If not, please don't interfere and tell me what I can and can't do! I don't need or want your advice.

I didn't tell you what do to. I told you that it's not gonna happen and why. You are free to want what you want and post about it, sure. But anybody who is familiar with how daw companies usually work will probably agree with what I said. Please don't tell me that I can't say what I want about the issue.

Edit. Actually yes, there is a statement in there that is saying to do something. But I mean that as part of the main point, which is that they are not going to do this because it will create lots of problems for them, so it's best to get used to that idea.

[Wuji]

Simulant, I agree it would be nice to know these things, but, also, I agree that it's a big ask to have this level of feedback from any DAW team, especially one that's (relatively) new, and possibly (i'm assuming) smaller staff level wise?

To reiterate, I just think a concise list and voting system would make sense. Discussion is good, but, just good to have a quick concise thread. It saves everybody time.

I've emailed the bitwig team, maybe they can take over the thread, or something, or they'll give their thumbs up or down to the idea. I just think that rather than users trawling through pages of unnecessary repetition and/or the bitwig team trawling through email after email of feature request, it would make sense to have one concise point of contact/request for them/us.

[Simulant]

Do you work for Bitwig? If not, please don't interfere and tell me what I can and can't do! I don't need or want your advice.

I didn't tell you what do to. I told you that it's not gonna happen and why. You are free to want what you want and post about it, sure. But anybody who is familiar with how daw companies usually work will probably agree with what I said. Please don't tell me that I can't say what I want about the issue.

Edit. Actually yes, there is a statement in there that is saying to do something. But I mean that as part of the main point, which is that they are not going to do this because it will create lots of problems for them, so it's best to get used to that idea.

Indeed, you can say what you want. And I can block you so that I don't need to read it! If you don't work for the company, you should stop pretending that you do. As I said earlier, I don't want or need your advice, especially on matters that can only be answered by Bitwig.

Anyhow, if you wish to press the issue further, I shall simply block you and won't be able to see your replies. You overstep the mark by telling me their answers to my questions.

As for having an official feature request thread, that'd be a great idea. Having them reply and say which they can implement would be even better. And an estimated timeframe would be awesome. I have no idea as to why you'd try to go against this, but I don't really care. I'm requesting it for me, not you.

[Ogopogo]

Alright, if don't want some reasonable input that goes against your desires, go ahead and block me and live in your own little world. As I said, you don't need to work for the company to have an idea of how it goes. Devs NEVER lay out their whole plan on when each little thing is going to happen for the reasons I explained.