Acoustica - Software should be easy to use

support for bluetooth midi keyboard?

Support and feedback for Acoustica's Mixcraft audio mixing software.

Moderators: Acoustica Dan, Acoustica Greg, Acoustica Chris, Acoustica Eric

User avatar
jlouvar
Posts: 762
Joined: Wed Jul 24, 2013 4:56 pm
Location: California - USA

Re: support for bluetooth midi keyboard?

Postby jlouvar » Mon Apr 15, 2019 11:14 am

LeesKeys wrote:I have the same Korg Microkey midi controller which is USB rather than bluetooth connected. Mixcraft immediately recognizes this one.


Maybe MX8 doesn’t recognize both controllers simultaneously... What happeneds if you unplug the USB one and only use the bluetooth one?
Last edited by jlouvar on Mon Apr 15, 2019 11:17 am, edited 1 time in total.
- Joe -
MX 8.1 Pro, Build 418, 64-bit. i5, 1.80GHz, 8GB, Windows 10. Focusrite Scarlett 2i4, Event and PreSonus monitors, Sony MDR-7506, Korg TR61, Akai MPK249, Fender P & J basses, Ric, Strat, D35, stomp boxes and a lot of microphones, etc.

LeesKeys
Posts: 41
Joined: Wed Nov 08, 2017 7:29 am

Re: support for bluetooth midi keyboard?

Postby LeesKeys » Mon Apr 15, 2019 11:16 am

still doesn't recognize it

User avatar
Acoustica Greg
Posts: 19136
Joined: Wed Mar 01, 2006 5:30 pm
Location: California
Contact:

Re: support for bluetooth midi keyboard?

Postby Acoustica Greg » Mon Apr 15, 2019 12:17 pm

Hi,

If it's not working with other programs on your PC, it's probably not going to work with Mixcraft. Have you contacted Korg about this issue?

Greg
Mixcraft 8 - The Musician's DAW
Give it a try here: http://acoustica.com/mixcraft/
Check out our Mixcraft University video tutorials.

LeesKeys
Posts: 41
Joined: Wed Nov 08, 2017 7:29 am

Re: support for bluetooth midi keyboard?

Postby LeesKeys » Tue Apr 16, 2019 5:54 am

I’ve posted on the korg users forum. Maybe something will turn up

User avatar
Acoustica Greg
Posts: 19136
Joined: Wed Mar 01, 2006 5:30 pm
Location: California
Contact:

Re: support for bluetooth midi keyboard?

Postby Acoustica Greg » Wed Apr 17, 2019 10:31 am

Hi,

You could install MIDI Ox to see if your computer is detecting any MIDI from your bluetooth device:

https://www.sweetwater.com/sweetcare/articles/how-do-i-install-and-use-midi-ox-for-windows/

Keep in mind that other programs can intercept MIDI data, so when you're testing this stuff, make sure nothing else is running.

Greg
Mixcraft 8 - The Musician's DAW
Give it a try here: http://acoustica.com/mixcraft/
Check out our Mixcraft University video tutorials.

jwmix
Posts: 15
Joined: Mon Apr 30, 2018 12:06 pm

Re: support for bluetooth midi keyboard?

Postby jwmix » Sat May 11, 2019 12:39 pm

An old man simple explanation

MIDI Enhancements in Windows 10
https://www.midi.org/articles-old/midi- ... windows-10

API is App Programming Interface

A quick history list of APIs:

DOS API => Win32 API => WinRT API => UWP API

Many libraries => .Net Frameworks => .Net Core

DOS => WindowsXP => Windows 8 => Windows 10

By the way .NET Core is a run on any OS ( phone, computer or at least most).

Mixcraft is a Windows Win32 API program,
not talking about 32-bit or 64-bit, just
Win32 API type (think WindowsXP based).

Windows Midi Bluetooth is a Universal Windows Platform (UWP) API,
think Windows 10 WinRT/UWP based. WinRT "updates" Win32 and UWP is
the write once, run on any Windows device, phone to XBox to computer
to whatever is the next device.

Win32 based apps can access some WinRT/UWP APIs
(for usage until they become WinRT/UWP apps),
just like Win32 could "access" some DOS APIs.

WinRT/UWP apps can access some Win32 APIs (but why, depends on the actions).

Win32 API apps use various Windows "music" APIs,
(but do not generally use Windows WinRT/UWP "music" APIs).

WinRT/UWP API apps can use various Windows "music" APIs,
but for many reasons, most use the newer WinRT/UWP objects,
like AudioGraph, and the AudioGraph APIs.

AudioGraph (Windows 10) is a new Windows "music" API.

Mixcraft needs to access UWP, to be able to run, UWP Bluetooth actions.

So the question is, does Mixcraft, a Win32 WindowsXP based program,
access UWP (and/or AudioGraph)? I don't (yet) think so.

It's said that companies (with products out or in development)
that are now using UWP objects, will have the most say with Microsoft,
as to how these new objects work, (from update to update).

Nothing to do with this bluetooth device question,
but concerning music, one company wanted changes,
that got a lot of developers upset,
when the updated WinRT/UWP object(s),
did not work, like they did, before the change(s).

But if no one is talking, well MS had to go with the one, who is talking.

Are you (the DAW/music program users) talking to others/vendors about WinRT/UWP usage?

Windows 10 is the future of music now!

Notice that PowerShell was mentioned in the above link(s). You all already have
PowerShell installed, ready to use (with any DAW).

Music people make okay scripters/programmers, and PowerShell is really a good
first easy step, think simple scripting actions.

You really need to learn PS (and it's easy ISE), use PS and share PS. If one
can follow "music" rules ( C major scale is A minor scale and modes ) then one
can follow simple PowerShell rules. Then after simple, like in music, move on
to "higher" actions.

PowerShell in Windows 10, can create Windows 10 type (WinRT/UWP) App(s) too or just
gives you back the data you need, when you really need it (think a few lines to
get a ton of data).

PowerShell can create "music" (motives, progressions, rhythms - planned or random),
control controllers, check dlls (vst or not, 32 or 64 bit, effect or instrument),
change/replace/add midi notes, cc options, and read/write music files, add effects
and track projects, move/share projects (computer to computer, near you or around
the world with others), and so much more, via loading music libraries, running other
exes, or just with PowerShell.

PowerShell is in the .Net Frameworks (and the newer .NET Core), so music
programs can embed PowerShell into their programs, like all the other .Net
Fameworks (or .Net Core) calls that they add to their music programs. Giving
their users track, vst, wav/midi, effect type lists info, etc. scripting in
real time.

But until they do, users can use PowerShell for/with Mixcraft info/actions
(perhaps work with / share with other DAW users, to develop all's music needs),
plus one can use PS for anything one uses a computer for (not just music). The saying
is, if you do anything more than once, then automate it via PowerShell (5.1).

By the way, the word is, PowerShell 7.0 (for Windows, Mac and Linux) is due out
soon (give or take a month, with the .Net Core 3) within perhaps another major
Windows update. What will be new (in music/video/PowerShell) this time?.

Read PowerShell blogs, and/or watch PowerShell ISE videos.

Adjust their PS business ways, to your PS Mixcraft music needs.

Have fun, find a PowerShell youngster (for help) and share!

User avatar
Acoustica Greg
Posts: 19136
Joined: Wed Mar 01, 2006 5:30 pm
Location: California
Contact:

Re: support for bluetooth midi keyboard?

Postby Acoustica Greg » Mon May 13, 2019 4:57 pm

Hi,

A bluetooth MIDI keyboard should just show up as another Windows MIDI device on the computer, if it's not doing that, then Mixcraft or any other program without special support for that device won't pick up the MIDI.

We do not have any special support for bluetooth, we're just going to pick up MIDI from valid Windows MIDI devices (hardware or software). I would hope the hardware manufacturer would be aiming to do this, or the hardware won't be very compatible with many programs.

The person who made this post stated it wasn't working in other programs, so there's probably something else going on in this case, like a driver issue or something. The first thing to do is to go to the hardware manufacturer's web page to download and install the latest drivers.

Greg
Mixcraft 8 - The Musician's DAW
Give it a try here: http://acoustica.com/mixcraft/
Check out our Mixcraft University video tutorials.

jwmix
Posts: 15
Joined: Mon Apr 30, 2018 12:06 pm

Re: support for bluetooth midi keyboard?

Postby jwmix » Mon May 20, 2019 1:50 pm

Old man speaking, (seems the world always repeats history).

Windows app developers (and hopefully their staff) have known
about Windows 10 for over 8 to 10 years (during Windows
10 development). Windows 10 was released as a free
update (why?) years ago (say over three years) and still
one hears old world (Win32) software say:

"we're just going to pick up MIDI from valid
Windows MIDI devices (hardware or software)."

Windows Bluetooth Midi is Windows 10 "valid" and works, but
how does old world software "pick up" new world "valid" actions?

"The first thing to do is to go to the hardware manufacturer's
web page to download and install the latest drivers."

No, that's old world ways, in the new world, the first thing to do,
is to use processes that access Windows.Devices (WinRT/UWP) APIs,
(hopefully, here, the DAW itself will access WinRT, or at the very
least, ride on the backs of other WinRT/UWP processes).

So again, old world (WIN32) programs must use new world (WinRT/UWP)
calls, if the old world software "cares" to use some of the modern,
new world actions, (like using the newer, modern ways of accessing
files/devices/watchers/video/audio/etc.).

The world went through all this before - "I want to keep my DOS, who
will ever use Win32".

Anyway, perhaps, search for Windows Bluetooth Midi processes, that do,
access the Windows.Devices API WinRT/UWP (they are out there).

Oh and of course, PowerShell can use WinRT/UWP. Users need to know their data.
Take control of their data. Share their data usage ways (with other DAW users).

Read PowerShell blogs, watch PowerShell ISE videos.

Adjust their PS business ways, to your PS Mixcraft music needs.

Have fun, find a PowerShell youngster (for help) and share!

LeesKeys
Posts: 41
Joined: Wed Nov 08, 2017 7:29 am

Re: support for bluetooth midi keyboard?

Postby LeesKeys » Wed May 22, 2019 4:38 am

Solution was simple enough once I engaged my brain! There is a specific driver (Korg Ble-Midi) which is needed for Mixcraft or any other Windows app to see the keyboard. Once that's installed microKey Air is recognized.

User avatar
jlouvar
Posts: 762
Joined: Wed Jul 24, 2013 4:56 pm
Location: California - USA

Re: support for bluetooth midi keyboard?

Postby jlouvar » Wed May 22, 2019 5:25 am

LeesKeys wrote:Solution was simple enough once I engaged my brain! There is a specific driver (Korg Ble-Midi) which is needed for Mixcraft or any other Windows app to see the keyboard. Once that's installed microKey Air is recognized.


It’s good to read that you got it working and thank you for posting the solution for others who may also run into the same problem.
- Joe -
MX 8.1 Pro, Build 418, 64-bit. i5, 1.80GHz, 8GB, Windows 10. Focusrite Scarlett 2i4, Event and PreSonus monitors, Sony MDR-7506, Korg TR61, Akai MPK249, Fender P & J basses, Ric, Strat, D35, stomp boxes and a lot of microphones, etc.


Return to “Mixcraft”

Who is online

Users browsing this forum: No registered users and 18 guests