FabFilter Pro Q 3 in Mixcraft 9
Can anyone confirm to me that FabFilter Q 3 will work in Mixcraft 9 Pro Studio before I spend €145 on it?
I love Micxraft, but I've had issues with a couple of plug ins recently which don't seem to be mixcraft compatable. Don't really want to invest in a new DAW which I'll struggle learning how to use 🤦🏼♂️
Thanks in advance.
submitted by rcorbett263
AKAI MPK mini mk2 MIDI keyboard suddenly stopped being recognized in Mixcraft. I'm getting desperate...
So, my AKAI MPK mini mk2 keyboard, which I've been using for two years with absolutely no issues, suddenly stopped working the other day. It doesn't seem to be correlated with anything else happening, it just stopped working.
I'm running Mixcraft 7 with the most recent build (316) and Windows 10 fully updated.
I've tried looking through all the settings and preferences and nothing seems to work. I went to AKAI's website, downloaded the most recent firmware for the keyboard and installed it. No difference. I downloaded MIDI-OX, which is a MIDI device testing software, and the keyboard is responding exactly as it should.
I can't for the life of me figure out WHY Mixcraft is suddenly not getting the signal from the keyboard. I've tried running Mixcraft with every other program closed. I'm running out of ideas.
EDIT: I BELIEVE I HAVE RESOLVED THE PROBLEM. I'LL DESCRIBE THE SOLUTION IN CASE SOMEONE HAS THE SAME ISSUE.
After posting this, I tried a series of different things... opening different Mixcraft projects (songs) and testing out the keyboard, restarting the computer and starting Mixcraft before opening anything else, etc. Eventually, after going through about six or seven different projects, I found one where the keyboard actually was responding. It was working but still kind of buggy. I could get it to work by arming and disarming a track a couple times. Then, with the track armed, it would work. The keyboard itself was also acting kind of weird... the light on the arpeggiator on/off button was randomly turning on and off, even though I wasn't pressing it, and the arpeggiator itself wasn't turning on and off, just the light going on and off.
But at least I had SOME response. I kept searching through different projects and finding that in some of them I could get at least some response from the keyboard. Eventually I opened a project and found one particular virtual instrument track where the "instrument" that was selected for that track was not a virtual instrument but the MIDI keyboard itself. I had never even noticed before that the MIDI keyboard shows up in the list of available virtual instruments. As soon as I switched the input for that track from the MIDI keyboard to an actual virtual instrument all the problems suddenly went away.
It seems crazy that having a MIDI keyboard selected as an instrument in ONE project would affect other projects ESPECIALLY if you've done a reset of the computer and opened an entirely separate project, without even having opened the affected project. I can't explain it, but I'm just glad that things seem back to normal!
submitted by lambcaseded