I bought a Hub to use with a number of buttons (18 to be precise) on a virtual organ midi controller. This controller console uses a Mac mini exclusively, along with Hauptwerk. I thought I could use the buttons as pistons as on a real organ, but the Mac app does not seem to support using a Hub. Should I return the Hub and buttons since I can't use them? Or will the app be updated to include using a Hub?
@anton Hello! I just wanted to update you and let you know that so far, everything you have helped me with on this project has worked quite well. I still don't have any clue how to autostart terminal, but so far it has not been hard to just restart it when I need. What I'm wondering about now is this - I've bought six more flic buttons to add (these will complete what I've planned on the virtual organ), and need to add them to the hub. I've got enough keystrokes left to assign to them, but am now wondering if I need to do anything to the python program to allow it to recognize them and send the internet request. Could you advise? I'm adding to this thread instead of starting a new one, in order for you to place it in context. Thanks! Diane
@anton Hi anton - the program is running well - thanks again for your help on that. I have googled how to get a python script in terminal to autostart, but I am overwhelmed by what looks like outdated information, and coding language I'm not super familiar with. Can you give me the step by step information to get that last piece set up? I did manage quite easily to set up a static IP address, so that's working as well. It's just the autostart part that I haven't got down yet. Thanks! Diane
@anton Thank you so much for all your help! The problem ended up being your first point - the app had not had me set up an internet connection. Nothing directed me to do that when I downloaded, so I thought it was using the connection my phone already had. Once I did that, then all worked according to your second set of instructions. As for setting up a static IP address, I've decided to take my chances and set everything up in the hope that the current IP address will last for a few weeks at least, and take that time to research the best way to set it up. I may have to go to my internet provider and get their help, and I didn't want to hang around on hold all day. But for now everything works, and I've been having a good time practicing on the organ as it should work, so thank you! The only thing left to do is to get the program to autostart each time I reboot the organ computer. Thanks! Diane
@ddcaruso7 Don't worry about flooding with questions.
First, start by verifying that the Flic Hub is connected to the same network. Go into the settings view of the Flic app while connected to a hub and see what IP you have. The first 3 numbers should match your Mac's IP. You can also try the "TEST INTERNET ACCESS" button. Also, try to execute the action manually from within the app (by pressing the three-dot-icon next to the action). This is to rule out if there are any troubles with the connection between the Flics and the Hub. After doing this, if still not working, check in the terminal window on the mac to see if the program has output any error messages.
Regarding the IP, you are correct that it can change, and it would be an issue in that case. I forgot to mention it, because usually the router will give the same address to the same computer, but it is possible that your router to re-use addresses for other devices.
Anyhow, to solve this, you can set a Static (permanent) IP in your mac settings. You can have a look at this guide: https://www.linksys.com/my/support-article?articleNum=142254 . Only change the IPv4 address field and the first 3 numbers must match the old address. So if you had 192.160.2.10, you can set it manually to, for example, 192.168.2.150. Use a last number in the range of 10-250.
The server program I created does not support https. It could be updated to support it, but that I can't help you with right now.
Hope it helps 
/A
@anton Sorry to flood you with questions and replies, but here goes: Because the IP address has changed, I went back to step 5 of your first set of instructions to see if that would work. It did, and the text edit program produced a number in response to searching on Safari from my phone. I then went back to step 5 of your second set of instructions, made sure that the request was correct, and pressed that flic button, but am getting no response from: 1. text edit, 2. terminal or 3. Hauptwerk (where I assigned the keystroke attached to that button). Am I missing a step or something? Not sure what is supposed to happen as a response from the Mac, but right now I'm not seeing anything, even though I verified the address through my phone. Help! Thanks, Diane
@anton I just had an odd thing happen: I double checked the IP address to begin setting up the http request (can I use https?) and I noticed that my IP address has changed from the last time. Only two numbers different, but still - will that present a problem each time this happens? I do know that IP addresses can shift around, but wasn't thinking about how this might affect the Flic button request? Thanks!
Diane
@anton Thanks! Working on it all now. Yes, I would like to add the program to Autostart, since I do restart this computer about once a week to clear things. Having that be automatic would be one less thing to start up. Diane
@ddcaruso7 Great! I was a little bit worried that it was too technical, but good to hear that you got it working
The next step (configuring the Hub and the Buttons) should be the easy part:
Delete the buttons from the Mac app (or any other application that you have paired them to) so that they are free to use with the Hub.
Login to the the Flic app for iOS (or Android). You will only need to use the app during configuration.
Make sure that you are within range, say 5-10 meters, of the hub and then press the “Add Hub” on the main screen.
Once you are inside the hub in the app, follow the instructions in the app to scan all your buttons. Make sure that you name them something so that you can remember which button is which. It is not guaranteed that they will be ordered in the correct way in the UI. Alternatively you can choose to start with only 2-3 buttons just to try it out and then add the rest later on.
On one of the buttons, add the “Internet Request” action to the “Click” trigger. Input the same URL that you verified earlier. Once you have saved the action you should be able to try it out by pressing the button and see if your Mac reacts with a keypress.
Once verified, use the “Clone Config” feature to copy this action config to all the other buttons (so that you don’t have to manually add them). This can be done via the settings menu (gear icon up to the right). Make sure you select all the other buttons as the target.
Once copied to all other buttons, you will now need to manually go into each of the buttons and update the last number in the URL /1 - /18.
That should be it!
Let me know how it goes! If you are happy with it then we can add the program to Autostart so that you don't have to start it from the terminal. Unless you are ok with doing it manually.
/A
@anton OK - I've gotten through your first set of instructions, and would appreciate help with the next steps to set up the hub. I did do the text edit to make sure that all the buttons were found through the IP address. At least, each input produced something on the text edit screen! I have also installed the Flic app on my phone. Thanks!
@anton Thank you! I will work on this part this morning and report back to you for part two if I have trouble setting up the hub. In either case, I'll let you know what happens. I appreciate the effort you have taken to set this up for me!
@ddcaruso7 Ok, I have written a really simple web server program in Python that translates web requests into local keyboard presses. However, I must mention that you need to keep in mind that this server will be accessible by any device on your same WiFi network. So anyone who knows the URL can also send the same requests to your computer. You need to decide if you trust your own network.
Instructions:
Save As...) If you want to you can also view the code if you are interested in how it works: https://misc-scl-cdn.s3.amazonaws.com/FlicServer.py~/Documents/Flic or similar.cd ~/Documents/Flic to move into the folder where you saved the program.python2.7 FlicServer.pyctrl+chttp://192.168.1.10:4343/api/v1/button/1 (remember to change the IP address correctly). The last number "1" in the URL can be changed between 1-18 for the buttons.Now, before we configure the Flics, we want to see if it actually works. So, open a text editor on your Mac and make sure that the window is selected. This way you will be able to see if the keyboard presses are working as they should. Using another computer/phone on your network, open a web browser and type the URL. If it works, then confirm the URL for all 18 buttons.
Let me know once you have gotten this far and I can help you with setting up the Flic Hub (if you don’t figure it out for yourself)
For reference, here is the code:
#!/usr/bin/python2.7
import sys
import time
import threading
from BaseHTTPServer import BaseHTTPRequestHandler, HTTPServer
from Quartz.CoreGraphics import CGEventPost
from Quartz.CoreGraphics import kCGHIDEventTap
from Quartz.CoreGraphics import CGEventCreateKeyboardEvent
# Button 1: '8' -> 28
# Button 2: '9' -> 25
# Button 3: 'b' -> 11
# Button 4: 'n' -> 45
# Button 5: 'm' -> 46
# Button 6: 'j' -> 38
# Button 7: 'k' -> 40
# Button 8: 'l' -> 37
# Button 9: 'z' -> 6
# Button 10: 'x' -> 7
# Button 11: 'c' -> 8
# Button 12: 'e' -> 14
# Button 13: 'r' -> 15
# Button 14: 'v' -> 9
# Button 15: 'q' -> 12
# Button 16: 'w' -> 13
# Button 17: '6' -> 22
# Button 18: '7' -> 26
PORT_NUMBER = 4343
def keyPress(keyCode):
print "Sending Keycode..."
eventDown = CGEventCreateKeyboardEvent(None, keyCode, True);
eventUp = CGEventCreateKeyboardEvent(None, keyCode, False);
CGEventPost(kCGHIDEventTap, eventDown);
CGEventPost(kCGHIDEventTap, eventUp);
class handleRoutes(BaseHTTPRequestHandler):
# GET request handler
def do_GET(self):
if (self.path.startswith('/api/v1/button/')):
keyCode = self.keyCodeForPath(self.path)
if (keyCode != None):
threading.Thread(target=keyPress, args=(keyCode,)).start()
return self.sendResponse('{"status": "success"}', 200, 'application/json')
else:
print "Could not find keycode for this button number."
return self.sendResponse('Not found.', 404, 'text/plain')
else:
return self.sendResponse('Not found.', 404, 'text/plain')
def sendResponse(self, res, status, type):
self.send_response(status)
self.send_header('Content-type', type)
self.end_headers()
self.wfile.write(res)
return
def keyCodeForPath(self, button):
if (button.endswith('/1')):
return 28
elif (button.endswith('/2')):
return 25
elif (button.endswith('/3')):
return 11
elif (button.endswith('/4')):
return 45
elif (button.endswith('/5')):
return 46
elif (button.endswith('/6')):
return 38
elif (button.endswith('/7')):
return 40
elif (button.endswith('/8')):
return 37
elif (button.endswith('/9')):
return 6
elif (button.endswith('/10')):
return 7
elif (button.endswith('/11')):
return 8
elif (button.endswith('/12')):
return 14
elif (button.endswith('/13')):
return 15
elif (button.endswith('/14')):
return 9
elif (button.endswith('/15')):
return 12
elif (button.endswith('/16')):
return 13
elif (button.endswith('/17')):
return 22
elif (button.endswith('/18')):
return 26
else:
return None
try:
server = HTTPServer(('', PORT_NUMBER), handleRoutes)
print 'Started Flic Button server on port ', PORT_NUMBER
server.serve_forever()
except KeyboardInterrupt:
print '\nClosing Flic Button server...'
server.socket.close()
@anton Thanks so much! Here are the keystrokes for buttons 1-18 (note: they won't make sense to you necessarily, because I have other keystrokes assigned to an x-keys stick, and I also ended up rearranging some after earlier assignments):
Button 1=8, 2=9, 3=b, =n, 5=m, 6=j, 7= k, 8=l, 9=z, 10=x, 11=c, 12=e, 13=r, 14=v, 15=q, 16=w, 17=6, 18=7.
The hub is currently wired via ethernet into the router, which is not in the same room as the organ - they are currently on opposite sides of the house, but use the same wifi. I can move the hub back to the organ computer though, if needed. And it's not a problem that I know of to assign an auto-start to a server program.
Does this mean that I won't use Keyboard Maestro for the integration? Just wondering.
Thanks!
Diane
@ddcaruso7 Ok, thank you, now I understand what you are trying to do! I'll try to figure out something that you can try, but I cant promise that it will be perfect.
Regarding "make the hub findable in the Mac app", this will not help you, since the Hub is stand-alone and the app is only used for setup of the hub. Once it is setup the events are not routed via the app.
So my idea is that I create a simple web server program that you can run on your mac. This program can emulate keyboard presses (just like Keyboard Maestro). Then you can setup the Hub via the iOS/Android app and configure it to send the press events to your computer via your local network. (Don't worry, I can make step-by-step instructions).
Can you give me a list of the keystrokes that you want to use? That way I can pre-configure the program for this.
Keep in mind, the requirements would be:
I can't say for sure if the click latency will be good enough for your use case, you will have to try that out for yourself.
/Anton
@anton Sorry, can't seem to upload the second screen shot of the Hauptwerk app and the detection screen.
@anton A couple of screen shots to help with understanding how everything integrates!
@anton Thanks so much! I'm an organist first, and a tech person last, but if you can give me the language and steps needed, I'll try.
Here is how the flic buttons look on the console, just so you see how I'd like to use them.
If I just use the Bluetooth that is on the computer (for only a few buttons), I use Keyboard Maestro to integrate Flic and Hauptwerk. I can assign a click action to the flic using KM and a keystroke, then use the device detection in Hauptwerk to find the keystroke that I want to assign to a process (ie, pistons) in Hauptwerk. Does that help? If I can integrate the flic app on my phone with Keyboard Maestro, then it might work. Alternatively, you could just make the hub findable in the Mac app with an update?
Anyway, thanks for the hope - I really want this to work, but it's too expensive to have and not use. My house is otherwise not smart, and I don't want to use the buttons for any other purpose except the organ. If I need to use your solution, I might just need step-by-step instructions. I am happy to send screen shots from Hauptwerk to answer any other questions about how it assigns functions.
Thanks!
Diane
@ddcaruso7 I need to understand better how you integrate the buttons. Im guessing that Hauptwerk is some sort of VST / Software Instrument that receives midi events from your connected midi controller, correct? Then, on the same machine, you run the Flic app and want to integrate that with the VST. How do you want to achieve this? Does Hauptwerk have some sort of API that you integrate with, or is it all through midi?
You are correct that the Mac app does not see the Hub, but you can still configure the Hub via an iOS device and have it send the click events to the Mac via HTTP requests. The iOS app would then only be needed during initial setup.
Like I said, I'll try to help you out, but I need to understand better.
/Anton
@Emil Thanks for this - the mac mini only allows up to eight connections. I thought the Hub would permit more to be used. But the Flic app for mac doesn't even see the Hub, so I can't use it in that way. So ten of my buttons are useless unless I can get the mini to see the hub. It would be easiest to just add the hub to the Mac app. Is there a tutorial I can watch to get my phone to perform your suggested Http request? I'm not that sophisticated technologically to figure it out on my own.
If you want to control the Mac mini, why don't you just connect the buttons directly to it?
Otherwise, you could use the iOS or Android app to set up the hub to perform a Http request to
some endpoint you set up on your Mac mini.
If you want to control the Mac mini, why don't you just connect the buttons directly to it?
Otherwise, you could use the iOS or Android app to set up the hub to perform a Http request to
some endpoint you set up on your Mac mini.