-
Notifications
You must be signed in to change notification settings - Fork 50
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
Comments
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 ;) |
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. 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)? |
You missed step 1. |
Hello thanks for reply. I tried this too but it doesn't work. Without this
code at least the commands work for me, but with this code, even that
doesn't work. You can see the picture in the word document. So obviously I
am missing something. I also send you the zip of my midimonster so please
check if there is something wrong.
You can find pictures in the drive:
https://drive.google.com/drive/folders/1icDy2t-pBER3NSgPBT86VpyeQRA62J2D?usp=sharing
V V sre., 10. avg. 2022 ob 02:29 je oseba kimwida ***@***.***>
napisala:
… You missed step 1.
Add step 1 codes to your "monster.cfg".
—
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZPDNJ4BCLEQG4JVENPJO6DVYLZXXANCNFSM5Y4BQM4Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Oh. 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 |
Ok thanks for the reply.
Yes, I know that the lights do not come on because of the avolites titan
program, because the program does not give feedback, so it is necessary to
program it separately, as shown in the second video you sent.
So if I understand you correctly this method is not reliable? It is better
if you get feedback and then turn on the light in buttons but here
you can't get the feedback from program.
So right now I'm using midimonster in combination with titian one and akai
apc mini which works fine for me. But I have a problem when I have already
used a lot of keys, and when I have to press something quickly, I don't
know exactly which key is active. Therefore, it would be easier for me if
this button were lit, because then I can see exactly what is active and
what is not.
Maybe you know a solution? I see you also sent me some code, where can I
use it?
V V čet., 11. avg. 2022 ob 02:27 je oseba kimwida ***@***.***>
napisala:
… --Top 2nd line --output("put_apc_color48",apc_b)
--output("put_apc_color49",apc_b) --output("put_apc_color50",apc_b)
output("put_apc_color51",apc_y) --output("put_apc_color52",apc_r)
--output("put_apc_color53",apc_r) --output("put_apc_color54",apc_r)
--output("put_apc_color55",apc_r) --output("put_apc_color83",apc_g_b) --Top
3rd line output("put_apc_color40",apc_g) output("put_apc_color41",apc_g)
output("put_apc_color42",apc_g) output("put_apc_color43",apc_g)
output("put_apc_color44",apc_y) output("put_apc_color45",apc_y)
output("put_apc_color46",apc_y) output("put_apc_color47",apc_y)
output("put_apc_color84",apc_g) --Top 4th line
output("put_apc_color32",apc_y) output("put_apc_color33",apc_y)
output("put_apc_color34",apc_y) output("put_apc_color35",apc_y)
output("put_apc_color36",apc_r) output("put_apc_color37",apc_r)
output("put_apc_color38",apc_r) output("put_apc_color39",apc_g)
--output("put_apc_color85",apc_g) --Top 5th line
output("put_apc_color24",apc_g) output("put_apc_color25",apc_g)
output("put_apc_color26",apc_g) output("put_apc_color27",apc_g)
output("put_apc_color28",apc_g) output("put_apc_color29",apc_y)
output("put_apc_color30",apc_y) output("put_apc_color31",apc_r)
--output("put_apc_color86",apc_g) --Top 6th line
output("put_apc_color16",apc_r) output("put_apc_color17",apc_y)
output("put_apc_color18",apc_y) output("put_apc_color19",apc_y)
output("put_apc_color20",apc_g) output("put_apc_color21",apc_g)
output("put_apc_color22",apc_g) output("put_apc_color23",apc_r)
output("put_apc_color87",apc_b) --Top 7th line
output("put_apc_color8",apc_r) output("put_apc_color9",apc_g)
output("put_apc_color10",apc_g) output("put_apc_color11",apc_g)
output("put_apc_color12",apc_y) output("put_apc_color13",apc_y)
output("put_apc_color14",apc_y) output("put_apc_color15",apc_g)
output("put_apc_color88",apc_b) --Top 8th line
output("put_apc_color0",apc_r) output("put_apc_color1",apc_r)
output("put_apc_color2",apc_r) output("put_apc_color3",apc_r)
output("put_apc_color4",apc_r) output("put_apc_color5",apc_r)
output("put_apc_color6",apc_b) output("put_apc_color7",apc_g)
output("put_apc_color89",apc_g) --Bottom 9th line
output("put_apc_color64",apc_b) output("put_apc_color65",apc_r)
output("put_apc_color66",apc_r) output("put_apc_color67",apc_r)
output("put_apc_color68",apc_r) output("put_apc_color69",apc_r)
output("put_apc_color70",apc_b) --output("put_apc_color71",apc_r)
--output("put_apc_color98",apc_r) variable_set()
—
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZPDNJ7AFLYT6X3H4YWQEQLVYRCHPANCNFSM5Y4BQM4Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I also try this and the light are working fine but the problem is that I
can't run this program and the midimonster at the same time so first I have
to light up the buttons and then close midikey2key and then open the
midimonster and then it is working ok but then the light is on until I
plugged off the apc mini and the light in the button is always on because
there is no more feedback for lights in buttons and they stayed od from the
midi2key program so this is not the best solution.
https://www.youtube.com/watch?v=Urg7TQwxBS8&ab_channel=DerAbt
V V čet., 11. avg. 2022 ob 23:44 je oseba Dejvid Gal ***@***.***>
napisala:
… Ok thanks for the reply.
Yes, I know that the lights do not come on because of the avolites titan
program, because the program does not give feedback, so it is necessary to
program it separately, as shown in the second video you sent.
So if I understand you correctly this method is not reliable? It is better
if you get feedback and then turn on the light in buttons but here
you can't get the feedback from program.
So right now I'm using midimonster in combination with titian one and akai
apc mini which works fine for me. But I have a problem when I have already
used a lot of keys, and when I have to press something quickly, I don't
know exactly which key is active. Therefore, it would be easier for me if
this button were lit, because then I can see exactly what is active and
what is not.
Maybe you know a solution? I see you also sent me some code, where can I
use it?
V V čet., 11. avg. 2022 ob 02:27 je oseba kimwida <
***@***.***> napisala:
> --Top 2nd line --output("put_apc_color48",apc_b)
> --output("put_apc_color49",apc_b) --output("put_apc_color50",apc_b)
> output("put_apc_color51",apc_y) --output("put_apc_color52",apc_r)
> --output("put_apc_color53",apc_r) --output("put_apc_color54",apc_r)
> --output("put_apc_color55",apc_r) --output("put_apc_color83",apc_g_b) --Top
> 3rd line output("put_apc_color40",apc_g) output("put_apc_color41",apc_g)
> output("put_apc_color42",apc_g) output("put_apc_color43",apc_g)
> output("put_apc_color44",apc_y) output("put_apc_color45",apc_y)
> output("put_apc_color46",apc_y) output("put_apc_color47",apc_y)
> output("put_apc_color84",apc_g) --Top 4th line
> output("put_apc_color32",apc_y) output("put_apc_color33",apc_y)
> output("put_apc_color34",apc_y) output("put_apc_color35",apc_y)
> output("put_apc_color36",apc_r) output("put_apc_color37",apc_r)
> output("put_apc_color38",apc_r) output("put_apc_color39",apc_g)
> --output("put_apc_color85",apc_g) --Top 5th line
> output("put_apc_color24",apc_g) output("put_apc_color25",apc_g)
> output("put_apc_color26",apc_g) output("put_apc_color27",apc_g)
> output("put_apc_color28",apc_g) output("put_apc_color29",apc_y)
> output("put_apc_color30",apc_y) output("put_apc_color31",apc_r)
> --output("put_apc_color86",apc_g) --Top 6th line
> output("put_apc_color16",apc_r) output("put_apc_color17",apc_y)
> output("put_apc_color18",apc_y) output("put_apc_color19",apc_y)
> output("put_apc_color20",apc_g) output("put_apc_color21",apc_g)
> output("put_apc_color22",apc_g) output("put_apc_color23",apc_r)
> output("put_apc_color87",apc_b) --Top 7th line
> output("put_apc_color8",apc_r) output("put_apc_color9",apc_g)
> output("put_apc_color10",apc_g) output("put_apc_color11",apc_g)
> output("put_apc_color12",apc_y) output("put_apc_color13",apc_y)
> output("put_apc_color14",apc_y) output("put_apc_color15",apc_g)
> output("put_apc_color88",apc_b) --Top 8th line
> output("put_apc_color0",apc_r) output("put_apc_color1",apc_r)
> output("put_apc_color2",apc_r) output("put_apc_color3",apc_r)
> output("put_apc_color4",apc_r) output("put_apc_color5",apc_r)
> output("put_apc_color6",apc_b) output("put_apc_color7",apc_g)
> output("put_apc_color89",apc_g) --Bottom 9th line
> output("put_apc_color64",apc_b) output("put_apc_color65",apc_r)
> output("put_apc_color66",apc_r) output("put_apc_color67",apc_r)
> output("put_apc_color68",apc_r) output("put_apc_color69",apc_r)
> output("put_apc_color70",apc_b) --output("put_apc_color71",apc_r)
> --output("put_apc_color98",apc_r) variable_set()
>
> —
> Reply to this email directly, view it on GitHub
> <#115 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AZPDNJ7AFLYT6X3H4YWQEQLVYRCHPANCNFSM5Y4BQM4Q>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
That's why I use lua backend. |
Could you please explain one solution from start to finish because I don't
know exactly what I need to change to make it work. I also found this on yt:
https://www.youtube.com/watch?v=josb529YlVU&ab_channel=YLP
It says in the coment:
Josue David Lopez Camargo
Hello, your video is very interesting and I managed to compile in
midimosnter, but I still do not understand how the midiox converts the
signal into sACN, I am very interested to know more about the subject
YLP
You can make your midi controller's buttons light with using sysEX of
MIDI-OX. It doesn't mean feedback but just static color. It's better than
nothing.
And the converting is done by midiMonster. You have to edit monster.cfg.
Which of these solutions do you think is the simplest? Please, if you
present one solution to me from start to finish, I will do exactly the same
as you, so that everything will work in the end.
You can also send me the code. Thank you.
V V pet., 12. avg. 2022 ob 03:31 je oseba kimwida ***@***.***>
napisala:
… 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!
—
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZPDNJZKB2TVP7C3EI7EXMTVYWSQ5ANCNFSM5Y4BQM4Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I used MIDI-OX way years ago, I didn't use it for a long time and I don't have source. |
Today, I researched my lost feedback signal things in my lua code and midimonster. |
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.
The text was updated successfully, but these errors were encountered: