NAMM is here, Bitwig announcement predictions were all wrong!

[takaii]

People at kvr bitwig forum...
-"bitwig stop making features and work on bugs, we want a stable software".
Bitwig listens and do that for us because we wanted.
Then when the namm show comes people be like.
-"no new features? We want basics features give us. No good hardware implementation etc. Such a shame no new features -.-"
What will bitwig do? We say one thing but want it stable and no new features yet we want new features. If we continou like this its just a matter of time until bitwig stops listening to ut
Never endimg happy bitwig forum (y)

[Andrei Marchenko]

When i talk about NAMM i want to see maybe some prototypes or whatever that brings me to the side when i can still believe in Bitwig. Personally i don't give a f*** about all this supa-drupa Surface or midi-keyboards. Ideas - that's what will be the main every time. So ideas about new in-build synths or devices and etc. Dev's thoughts about roadmap for BWS for example - would be nice to hear.

[svervs]

Maschine4Bitwig only to have it sit and rot because of some stupid reason that I have idea why. I'm a bit jaded only for the fact Maschine users could have the same integration that Push has right now expect without the 64 pads.

I doubt we will ever see serious help from NI for Maschine, there’s just too much business involved.
Or any official Bitwig support of Push, there maybe even contractual clauses from the Ableton times.

Not to mention the urban closeness of these 3 companies, they probably bump into each other every once in a while.
Most likely, we will never see Maschine being supported, because the Bitwig guys are banging all the hot Native Instruments girls …

[TeotiGraphix]

Maschine4Bitwig only to have it sit and rot because of some stupid reason that I have idea why. I'm a bit jaded only for the fact Maschine users could have the same integration that Push has right now expect without the 64 pads.

I doubt we will ever see serious help from NI for Maschine, there’s just too much business involved.
Or any official Bitwig support of Push, there maybe even contractual clauses from the Ableton times.

Not to mention the urban closeness of these 3 companies, they probably bump into each other every once in a while.
Most likely, we will never see Maschine being supported, because the Bitwig guys are banging all the hot Native Instruments girls …

Well... I was actually in email contact with NI Maschine devs and they checked out the code in my github account so that is not exactly the case.

The case is the ball must have been deflated mid stream, that is where most of my fickleness comes on this matter, things were happening and then I can't get any information, hot to cold type thing.

As far as official support, I don't quite understand what you mean. Bitwig has an API to program against, it does MIDI and OSC, we implemented MIDI per an Ableton Spec, their midi note and cc, pad colors etc. So other than BW being pals with the Push devs and getting support that way, the script other than it wasn't developed by an actual Bitwig employee is about as official as it gets.

Maschine, well, I had it doing pretty much insane things and bypasses the stupid controller pages and had things working like the Push.

Mike

[svervs]

So other than BW being pals with the Push devs and getting support that way, the script other than it wasn't developed by an actual Bitwig employee is about as official as it gets.

Was in no way meant to degrade the quality, because it's not "official".
By "official" I mean, Bitwig commissioning you/Moss, giving access to whatever be needed, and putting some deserved money in everyones bank account, and become "The DAW that supports Push™". Because Push is already a huge selling point of BWS.
It will always be a "community (of 1-2)" thing. What if you devs decide to "F++ck all that shit, I'm out, I'll grow sheeps to build my own drums!" ...?!

[TeotiGraphix]

So other than BW being pals with the Push devs and getting support that way, the script other than it wasn't developed by an actual Bitwig employee is about as official as it gets.

Was in no way meant to degrade the quality, because it's not "official".
By "official" I mean, Bitwig commissioning you/Moss, giving access to whatever be needed, and putting some deserved money in everyones bank account, and become "The DAW that supports Push™". Because Push is already a huge selling point of BWS.
It will always be a "community (of 1-2)" thing. What if you devs decide to "F++ck all that shit, I'm out, I'll grow sheeps to build my own drums!" ...?!

Yeah ok, I know the get the #$%^ out of town with software dev for sure, github might as well be a landfill.

But in reality, it's been almost two years since Moss and I started Push so really, if there was any interest in obtaining anything more than community effort, it seems it's obvious what the answer is.

I'm not complaining either because open source is one of those things you do not because you think you are going to get paid but maybe because it might lead to future opportunities. At least that is why i have done so much OS dev, not just with Bitwig but a lot of other projects Apache etc.

Mike

[svervs]

it seems it's obvious what the answer is.

Yep ...

So, please, forget about the sheeps ... and just use presets ...