FL Studio 12 and Komplete Kontrol S61 MK2

Not sure this has anything to do with Image-Line, integration is in NI's court.

 

Fl Studio 20 is alreadt out as "Release Candidate" version.. and it doesnt works.. if NI doesnt add that MCU function we have NO HOPE

 

hmmm yeah I thought NI maybe wait the right moment to implement deep integration for the new, refactored FL Studio DAW.... but looks like this version will never happen...

 

the most frustrating thing is that i owned the mk1 and it worked like a charm, i've sold it to get the mk2 and i'm still waiting for this very basic function
i'm still supporting NI from the day one, i have Komplete 11 Ultimate, Maschine Mk2 and now Mk3 and i'm still eternally waiting...

i think it's not rocket science to add MCU support, i suppose is a marketing choice to not support other DAWS at this point

 

hard to say what are their intentions, on the other hand Maschine MK3 supports FL Studio as far as I know. Why would they do that then? Why Maschine supports FL-S and Kontrol doesn't?

 

yessir, that's THE QUESTION !

 

Is it not possible via generic User Configuration Script like in Ableton (There is a configurable Midi Controller Script, where you can manually add a CC Channel per Midi Function like Transport Controls Play, Stop and so on.) to set up FL 20 with the requested basic transport controls?

 

NOPE, there's NO WAY to get Kontrol's "Rec, Stop, Play..." buttons work with FL Studio at the moment.

 

I use the white buttons for transport control in my midi template for unsupported hosts, set them to trigger not toggle and change the button name so they are clear, with the dedicated transport controls not lighting up your eye is drawn to the middle area so it's not too bad and at least allows for less mouse usage. Yeah it's a workaround and like all workarounds it works but it's getting around the underlying issue - that needs addressing but right now isn't and the fix may take time, so in the meantime you do what you need to to get things done.

btw I don't think it is as technically simple as some people seem to think, the dedicated buttons are simply not using midi at all but a different protocol so any 'fix' means a radical change in how they work.

 

Fl Studio is as well now mac compatible, and I'm really thinking testing it...So this gives NI with one release possible new userbase if they would implement FL Stduio Deep Integration...So probably this gives a bit more pressure on the developers side to implement it...

As well in the best rated daw softwares, FL Studio usually takes a place on the podium...

https://www.musicradar.com/tuition/tech/the-20-best-daw-software-apps-in-the-world-today-238905
http://musiccritic.com/equipment/software/best-daw-recording-software/
https://ehomerecordingstudio.com/de/beste-daw-software/

 

Hope to get the full support in FL Studio 20 for the NI Keyboards too.
It is a pity that after more than 6 month is still no support for FL Studio

 

These things, they can take time.

 

Fully agree EvilDragon, but I guess that NI does not have only 3 Developers and the code behind is not brand to NI due to the fact that the older MK1 was working.
Do you have any clue how long it will roughly takes?

 

As long as NI deems it necessary. First things first: does FL Studio support OSC? I can't find any info on that, so it seems like it doesn't. Because that's what's necessary for deeper integration that mk2 can offer to a DAW.

 

Thats the wrong order of actions. A DAW Software vendor can not always adapt the Software to the Hardware vendor. The MK1 was working independently of OSC support or not.
However, you are not the person who did the decision. Lets wait for a wonder.

 

In the same boat with Studio One and the lack of MCU on KKMK2. Reaper supports OSC, but there's no integration with KKMK2 or Maschine; so just because a DAW has OSC does not mean NI is going to support it; thus applying pressure to DAW developers to support OSC probably won't get us far.

Seems ridiculous that MK2 is a significant upgrade in almost every aspect, but a complete regression on this front-- even more ridiculous that 8 months later we're still waiting on this being added back.

As a customer that is heavily invested in NI, it would be nice to be given a roadmap with an ETA for MCU support to return, otherwise we'll just keep wasting our time and that of other people on a forum reiterating the same points time and time again.

 

That's because mk1 used MCU protocol. mk2 doesn't use it, it uses OSC instead. Live supports it, Cubase/Nuendo support it, Logic supports it, so they got integrations first. Also Reaper supports it but we'll see if support for it happens - NI is aware of this possibility for supporting Reaper, but it's a matter of scheduling on their side.

Certainly if a DAW supports OSC in some way it is going to be more likely that mk2 will support that DAW sooner than others which don't support it. Unless NI backports MCU into mk2... which they don't seem to be keen on doing that, if we go by this post.


Also, don't expect any firm timeframes officially stated by NI on this forum.

 

That matchs the point. A lot of people in the Forum of NI, FL Studio, maybe other DAW´s as well and a couple of Facebook Groups are discussing that issue and NI is completely ignoring there paying customers.
It is so easy to say i.e.: Sorry customers, we do not have this feature so far, but we have it on our screen and we are working on it and hopefully we will get it this quarter or something like this.

 

Absolutely agreed with this.

Whilst the veil of secrecy may work for consumer-oriented companies like Apple, we're dealing with what's meant to be a professional set of tools with NI. A public roadmap would be a solid starting point for NI. We're not talking some groundbreaking new feature that the competition could beat NI to market over, we're talking MCU.

Losing MCU is like losing the couch off the moving truck on the way to your at new house; it might be better, but you're missing a big feature the old one had. Losing MCU support isn't something that is mentioned in any of the sales materials published on the NI website, or mentioned on the box.

I could invest in Nuendo today for several team members, but MCU may come tomorrow. I wouldn't be best pleased. If I was going back to Ableton Live, we would use the Push 2 and Akai Advance or similar instead of anything NI. Whilst open-sourcing the firmware is never going to happen, I think there's good call for creating an SDK or API for integration of KK and Maschine into whatever software users want to use it with. I could probably hack together an OSC to MCU conversion layer given a couple of hours if NI were to play ball. This isn't the big issue that it's made out to be. Maschine/KK is already using Bome for virtual MIDI, it really can't be that difficult to change what a button triggers as an output.

 

It‘s very simple. A lot of existing users are holding their hands off the mk2 as longs these basic things are not supported when you already have it in the older version...