Compiled Standalone doesn't detect MIDI IN messages.
-
Hello fellas,
Need your advice again.
I compiled a standalone directly from HISE. However, it doesn't seem to detect any MIDI input from my keyboard. It plays fine when I trigger UI keyboard with the mouse, but completely ignores messages from my outboard keyboard.
I don't have a clue what could be going wrong and its absolutely killing my successful-build-vibes.
Anyone experience this before?
Any help is appreciated.
-
@RastaChess You need to add a MIDI sources floating tile so you can choose the MIDI input device for your app.
-
@d-healey I did that. But nothing shows up in the midi MIDI sources window. Even though I use the keyboard within HISE just fine. So I;m clearly receiving midi within HISE, but somehow blocking it from the interface script?
-
@RastaChess Post a snippet
-
@RastaChess The output plugin needs to have your midi-keyboard activated through the tile on your plugin settings page (which I assume you have) to receive midi, as David mentioned. Also you need to add a midi panel for the midi-channels too.
-
@andioak So, I do have a settings page. Just the HISE provided one. That part works fine. I have a midi resources floating tile along side it. However nothing shows up in it. Though I'm running multiple scripts, I narrowed the issue down to the user interface script. When I load the plugin in HISE with the interface script deactivated, the midi sources show up on their designated window. But as soon as I reactivate the interface screen, puff, it's gone.
I just can't think of what could be causing this.thanks for the help.
-
@RastaChess
When I load the plugin in HISE with the interface script deactivated, the midi sources show up on their designated window. But as soon as I reactivate the interface screen, puff, it's gone.
What do you mean by "deactivated"?
-
@d-healey I mean "disabled" (Orange square dimmed).
-
@RastaChess Make a minimal snippet that demonstrates the issue and post it.
-
@d-healey I wouldn't know which part to snip. I'll try to narrow it down some more.
-
@RastaChess So this took a while... I've finally tracked this issue down. It boils down to this:
In making a global look and feel toggle button, the midi sources window is impacted. It seems that the midi-sources window get's it's graphics logic from the general old button. So when I change the the look and feel of the global toggle button, I end up loosing the midi sources window, which is basically made out of buttons. I'm including a snippet below where you can see the look and feel script I'm using for the buttons, and a midi sources window below it. Or rather you won't see the midi sources window, if you have the same problem as me that is.I don't have a workaround for it yet. I tried to assign local look and feel to the buttons. But I couldn't get that to work.
Any suggestions? or maybe an example on how to implement look and feel to a particular button?
thanks.
HiseSnippet 1012.3ocuV8tahaDDeMfiposW6I0GfU2m3jHDfv0VoSokCBDgZBfN3hpTTzoE60lswdWj8ZRQUmTed5CQel5av0Y8ZiM83RSQ5Jefj4u+lc1Y9sLMTXSihDgHCq4aVQQFeg4rMb4x9KILNZz4HimXdEIRRCwZU81rhDEQcPFFkuPovvpBJ4ye8i8H9DtMMWEBcsfYSujEvj4Zm18mX99CINz4rfBd2o6HaAuuvWDC0SYylnUD66HdzwDkakLQFGMvgIEgyjDIMBYTomvYyrkh64Z+ulEwV3SUBsPyfDoUOYMMbMid+PguipxU5P8Wx7cllc9iPP1ll2MJq6Fei4ULG1V84ckuNw.NOhh8EiR6Vlk2oLa8wJy8TRFEJoJ5R5olyrCYqj4VT0ymaNhCWRtDn8WrTz9hJ4V1ru.7fKaDPtiNLDD1FQsSa1rNF954ur5ImXMexEWb4.bu2Le9jwUsf6jHI1m3hOCOf6w3zF1gT3jcguXAwWivkBwcuh6LjR8qAYwBbuQH0iolbFFyskLAu1ybBI2OW344S6EKkB9ypicyL5UGKV7KOu5uU0ZMIDS.z.4FD.pWhqZwbw0TxqI9wT7YmgcI9QzD28ZDQk5wlDWV3oET0gWCEluVDyga9WSskDNfdsaH2z91SZCmZxMml8Osu83D0sRUebhsVMusNtScbaU5vVV3ODPljFnEaowzElu+XXpwnSFxZP5TD+1Egu8sYPW8c6oKHCi+euI7PMf1exZ.uS0Af+p9JanAK3iER5Ddsjd.zgv+SStt60lZYHT36SC2qYEwT3CEXMdbvBZXcbxMwVGgszcW8O5ws5aq2MK3nfOhyjSVQSky4tZsGhBT5xshxHsBAWkIDFOIkvPuxgXPRrL0BsPIkeQBazaFcNQRxRDjS.mUzPIScbLNmtFHz0LQVlmSitSJVAby8EAqDbUEXT4Q.6utExe+5taxw+G5hJjopxTRXclF5KHRF2aNCZfp78UlEUULqnwEy57t2ybjKQFlF+IHtjx7VJUR+QdmSej9xDZ8YvfLzZQY6PPlNB778pbkOpmpEsq11EUi9P5a3gCgSrOQt6qIpmRSM.yY6Pgqno4QL4lhO09e3IllO3SLO1R7olSYR6k6uFKsmZDlf9TTikytnF35BLK4EXEyg+7g9J7+B7.SlZH6JhLjAyXliiCziH.5bN0ORMKURMKokapjUcfYTtShv6gOoFaojMRM1JyHJfXGJdqsd2U8z+mknApIdxu9wB9YXfLd6JqoYyFMQAv35assUG+iAhg8GS6CHlSOfX5b.w7hCHlu8.h46NfX99GLFESwqhkh.85.nX5fDpSCiAbBLYkLEh9azpKFwC -
This post is deleted! -
-
@d-healey this is great thank you. I'll try to implement it if all else fails. But, I guess I was hoping not to have to make changes to every laf button in every project I've built so far. After all, they are all going to need a Midi-Sources window and custom buttons.
Is there anything else I can try?
Have you reproduced this error in your system? or is it just happening to me?
Maybe it is possible to create a look and feel for the midi sources window?
-
@RastaChess
I guess I was hoping not to have to make changes to every laf button in every project I've built so far. After all, they are all going to need a Midi-Sources window and custom buttons.
Why not use a single global script that's applied to all your projects?
Maybe it is possible to create a look and feel for the midi sources window?
That's what local laf is.
