Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback to turn on the lights in the buttons on the APC mini midi controller #115

Open
dejvidg opened this issue Jun 3, 2022 · 11 comments
Assignees
Labels

Comments

@dejvidg
Copy link

dejvidg commented Jun 3, 2022

Hello.
I use an APC mini midi controller and avoltes titanium ONE using MIDImonster.

Communication works fine for me, the only problem I have is that avolites doesn't send me feedback if the cue is active or not, so I can't turn on the lights on the buttons.

I've been trying to do feedback with the midimonster to turn on the lights in the APC mini midi controller for a while but I fail. I noticed on the internet that some did this using luas script. I don’t know exactly in which note I should write the commands and what the commands should look like. Could someone please help me and give me an example of the program?

Each key has a red, green and yellow light. I would like to know how to turn on each and how to make them flash if they are active. I am aware that Avolites titan one doesn't have feedback for cue whether it is active or not, so all this must be done manually in a script.

I am also interested in commands for the light to light only when the key is pressed. And commands for the light to light up when the key is pressed and turns off when the key is pressed again.

I want it to look something like this: https://www.youtube.com/watch?v=8uRpIvr2BQU&ab_channel=YLP
(read description point 5.).

I also found this if anything helps you: https://www.bome.com/wp-content/uploads/cma_attachments/1494878547803_APC-Mini.png

Im asking for help. Thanks in advance.

@Spacelord09 Spacelord09 self-assigned this Jun 15, 2022
@Spacelord09
Copy link
Collaborator

Hey @dejvidg,

a little click on his channel returned this: Youtube-Video

I hope this answers your question. If not, please reopen this issue again ;)

@dejvidg
Copy link
Author

dejvidg commented Jun 20, 2022

Hello @Spacelord09

Thanks for the video and reply!

I tried this method and I did the same as in the clip but it doesn't work for me. I use notepad on windows 10.

Midimonster works for me normal in I get signal in avolites titanium one. But the lights in the keys don't turn on.
Here in this link, I describe everything:
https://drive.google.com/drive/folders/1ZMAT4Ktqme07cZXKbkQit6JoEsB7Kpjm?usp=sharing

Maybe I made a mistake somewhere. Can you please help me?

Could I make my light in buttons light on when I press a button?

Could it be programmed so that the light in the button goes on when I press a key and goes out when I press a key again?

And so that the light only comes on when the button is pressed (flash button)?

@kimwida
Copy link

kimwida commented Aug 10, 2022

You missed step 1.
Add step 1 codes to your "monster.cfg".

@dejvidg
Copy link
Author

dejvidg commented Aug 10, 2022 via email

@kimwida
Copy link

kimwida commented Aug 10, 2022

Oh.
I made this clip for just buttons lighting.
I mean it is not for feedback. It's just something like skin. Fixed skin.
I've used feedback similar one. It is not feedback because Titan doesn't support it.
The way how to work is I programmed expected playbacks behaivor with lua.
It is very long, complicated and even unstabled. Sometimes it lost feedback signals.
So I am waiting Avolites midi feedback.

Your question 1) Yes, I am using it now. 2) Yes, I am using it now. 3) I think so. I don't use it.

First of all, make sure you install lua correctly and it works.

Ok. I added my feedback lua full code below link.

https://drive.google.com/file/d/15ULa-fjKIXJGF-hINHV30EtojhKYO56B/view?usp=sharing

@dejvidg
Copy link
Author

dejvidg commented Aug 11, 2022 via email

@dejvidg
Copy link
Author

dejvidg commented Aug 11, 2022 via email

@kimwida
Copy link

kimwida commented Aug 12, 2022

That's why I use lua backend.
There's a lot of ways to light and feedback apcmini.
midi-OX, grandma2 on PC, dot2, bome.
But all of them can't be run with midimonster, because windows midi library or something can be used only one program.
midikey2key is very good for setting apcmini but you can't use it with midimonster at this time.
If midikey2key is upgraded to send osc, I think it would work.
In midimonster, you delete winmidi and add osc backend and it's done!

@dejvidg
Copy link
Author

dejvidg commented Aug 15, 2022 via email

@kimwida
Copy link

kimwida commented Aug 16, 2022

I used MIDI-OX way years ago, I didn't use it for a long time and I don't have source.
But as I said before, it can't be used with midimonster at once either if midimonster use midi backend.
So I lunch MIDI-OX, light buttons, terminate MIDI-OX and run midimonster.
It needed a lot of steps, so I automated it using autohotkey.
Any it is similar way that you use MidiKey2Key and midimonster.
I know it is not best way, but at least it light buttons and you can use midi controller with Titan One for free.
If you want feedback similar one, study midimonster lua codes or wait some time until another solutions come.

@kimwida
Copy link

kimwida commented Aug 16, 2022

Today, I researched my lost feedback signal things in my lua code and midimonster.
I thought that there was some lag between lua and midimonster for lost signal. But it is not!!!
I found that lua and midimonster react at real time perfectly. It's so great!!!
The lost feedback signal is because Avolites Titan can't support feedbacks.
In detail, when I pushed multiple playbacks at once and I hit a fading playback gain, the problem occured.
It does not have something to do with midimonster and lua.
It's just because I couldn't implement the situation. That's all.
I wrote it for someone who could misunderstand lua and midimonster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants