Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m confused...

FL Studio.vsti Weird GUI Glitches in 2.4 & 2.5 in Mojave

Image-Line recently released a beta version of FL Studio 20 that can now operate as a VSTi and AU plugin for Mac.(FINALLY!!!
2 people have
this problem
+1
Reply
  • Hey BULLETHEAD BEATZ,

    Thanks for posting!

    That is exciting that FL is testing a new VSTi/AU plugin for incorporation with other DAWs! MPC compliance with third party plugins can vary depending on the compatibility. In addition, we all know software beta versions can be very temperamental.

    Hopefully we will see a sleek integration of the two in the future!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • This reply was removed on 2019-04-11.
    see the change log
  • This reply was removed on 2019-04-11.
    see the change log
  • This reply was removed on 2019-04-11.
    see the change log
  • This reply was removed on 2019-04-11.
    see the change log
  • 1
    Ok, this will be the 3rd time trying to post this, LOL...

    Once Image-Line released a Beta of FL Studio that now operates as a VSTi and au for Mac, (FINALLY!!!\U0001F601) lol.., I downloaded it and installed it onto my Mac. I'm running Mac OS X 10.14.4 Mojave and at the time of testing, I had just upgraded to MPC 2.5. Once installed, I scanned all of my "new plugins" in 2.5 and FL studio.vsti was found. So I next selected FL.Studio.vsti as a plugin and click the icon. At first, a hub type box with the outputs and latency adjuster on it appeared. So I clicked the Fruity icon and FL Studio 20 opened up. But as soon as I tried to touch any part of the GUI with the cursor, FL started glitching extremely bad. Rendering it unusable....I tried 2.4, same results. Also since 2.4, a lot of my Waves plugins open up with blank GUIs. You can select presets or and control them via the MPC X/Live screen and qlinks controls. Other plugins like Camel Crusher crashes the MPC software, (2.4 and 2.5) when using the vst version. The AU works but has a blank screen. I then decided to try 2.3 and to my surprise, everything worked, including FL Studio 20! No glitches whatsoever. It does crash 2.3 if you double press the stop button on the X, (weird). But I can now enjoy FL's dopeness inside the MPC software. I also decided to install MPC 2.5 and the FL Studio Beta on my Macbook Pro running OS X 10.13.6 High Sierrs and FL didn't glitch in 2.5 like it did in Mojave! Also my Waves plugins worked with 2.5 in High Sierra! So \ it's safe to assume that the problem lies within 2.4 & 2.5 running inside Mac OS X 10.14 Mojave. So if you're on Mojave and wann a try running FL Studio as a plugin, then stay on 2.3. If you're on High Sierra, you're good for take off! Hopefully we can get this resolved..
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Hey BULLETHEAD BEATZ,

    Thanks for posting!

    This is great information to know. I'll make sure to forward it to our development team! :)

    Thanks for your feedback!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • 1
    Akai is fully aware of GUI Glitches. I called to talk to a customer support agent and he claimed there was nothing in his data base to reference for troubleshooting. I called based off my third party waves plug ins not showing the GUI properly. There is an issue they know and it is not a priority at this time. I get the glitches with the Beta as well. But the third party plug in's aren't betas and they don't work .... yet they used to at one point.
    • The version of FL"IS" a beta, BUT....It works fine in MPC 2.3 in Mojave but it glitches in MPC 2.4 and 2.5 in Mojave, (OS X10.14.4) Like I stated previously, The "Beta" works fine in OS X 10.13.6 High Sierra in all 3 MPC versions< (2.3, 2.4, & 2.5). It also works fine in Studio One 4 Pro as well as Ableton Live 10. Along with Waves, Camel Crusher, and a few others experiencing issues in 2.4 & 2.5, it's pretty obvious the problem is more than likely with the Akai MPC 2.4 & 2.5.....imo
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Your absolutely right but Akai must make it a priority to look into and fix.... I think the push for the Splice feature plus Force and whatever else that we haven't heard about is more important right now..... I can get the Waves plug ins to load in the MPC if I load it as a VST in FL Studio but of course you can't record midi ...so really why is it even possible to load the MPC if it can't work as intended.... an instrument to create midi data.....
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited