A live-coding lighting controller, building on the Open Lighting Architecture with Clojure and bits of Overtone.
(mk2/deactivate mk2-watcher)
CompilerException clojure.lang.ExceptionInfo: Invariant violation in `afterglow.controllers.launchpad-mk2:564` [pred-form, val]:
[(#{:launchpad-mk2 :launchpad-mk2-watcher} (type controller)), :launchpad-pro] {:*?data* nil, :elidable? true, :dt #inst "2016-02-12T02:08:55.758-00:00", :val :launchpad-pro, :ns-str "afterglow.controllers.launchpad-mk2", :val-type clojure.lang.Keyword, :?err nil, :*assert* true, :?data nil, :?line 564, :form-str "(#{:launchpad-mk2 :launchpad-mk2-watcher} (type controller))"}, compiling:(/home/benjamin/Sources/clojure/afterglow/test/afterglow/afterglow_sample.clj:16:1)
Don't know if this is caused by
(def mk2-controller @(:controller mk2-watcher)).
That is the command I wanted you to be able to use, but I will leave Cursive support to a Cursive user. I would suggest you explore Edit :arrow_forward: Structural Editing and Navigate :arrow_forward: Structural Movement when you have time.
What does
(type c) give you?
Oh, I see!
Yes, my mistake.
Line 686 needs to be
{:type :launchpad-mk2})]
So if you had put your cursor after the closing paren of set-pad-color and issued that command, it would have redefined just that function for us.
I’m afraid the easiest way to recover from the fact that I gave your controller the wrong type tag is to shut down and reload the REPL after that line is fixed.
I do not yet have contributor guidelines, but we both know what these are about. In the commit messages say something like “correct error in reference manual” for the first, and “correct copy paste error” for the second.
I have a house full of people practicing LED glove performances, and the pizza has just arrived. An interesting Thursday. :grinning:
I will look at photos of the Mk2 and think about where to move the non-arrow round buttons. If you have any thoughts, please let me know. The are the tap-tempo, shift, stop (starts and stops sending DMX for the show) and user-mode buttons (suspends the mapping to let you switch between it and Ableton Live).
Ok, having found a photo of the Mk2, I have moved some round buttons around. Other than the arrows, the only button active along the top is now the User 2 button, which suspends and reactivates the mapping. There was not a great place to put Click (Tap Tempo) or Shift, so I have made Volume be Tap Tempo, and Pan be Shift. Stop has moved to the button which is actually labeled Stop.
Since I can’t actually test these things, I am a bit nervous about having broken something. If you have a chance to pull the latest code and give it a try, I would appreciate it!
I have moved the buttons again slightly because after studying the Mini and S decals and photos, I can make the Mk2, Mini, and S all use the same round button mapping, and it makes slightly more sense than I described above. When you have time to test, it should be as documented here (follow the link to the photo of the Mini).
Actually, @hastebrot , I just greatly changed the way all controller bindings work, so that Afterglow figures out what code to call based on the device identification response it gets back from MIDI, and you no longer need to know which namespace to load. I have been able to test it with all the other controllers I support, but I still lack a Launchpad Mk2. If you could test that the new instructions work for you with the latest
0.2.1-SNAPSHOT code in the next few days I would greatly appreciate it.
Great, thanks. I have several days of documentation and screen shots and movies to capture, so there is time. I will be splitting the Launchpad (and Ableton Push and now Push 2) instructions into their own pages, so I will post an updated link here if the location changes before you get to it.
Here is an example of what the Afterglow interface on the new Push 2 controller’s color display looks like: https://raw.githubusercontent.com/brunchboy/wayang/master/assets/Example.gif
The updated Launchpad instructions are now on a separate page. You can find the current Mk2 instructions here.
@hastebrot , I’ve changed things around again, and made it even easier. Now once you use the sample show, your Mk2 should simply light up and start working on its own, as described here. I just have a few interface movies to capture, and I will be ready to cut this release.
Hello, @boriskalkex, without knowing more details about what you have in mind, I can’t really say if afterglow would be appropriate. It might be overkill, but of course, you don’t need to use all of afterglow. The answer depends both on the details of your goals, and the skills and preferences of your coder.
And what I should be doing.
Have you verified that your DMX interface is compatible with OLA, and confirmed end-to-end communication is working? I would say that is the first step. Then you will need to find or create fixture definitions for any of the lights you want to use, measure out where you are going to hang them, and create your show definition which patches the right fixtures at the right addresses and physical locations and orientations. Then you can start creating cues and assigning them to the grid. Are you using any physical grid controllers, or just the web interface? And are you trying to do any kind of synchronization with Pioneer Pro DJ Link, Ableton Link, or MIDI clock? Trying to do all this for the first time by Sunday may be a bit ambitious, but I will help as much as I can (I am busy at work this week though).
I currently only have LED Pixels connected to OLA, which I tested through the web interface. Since I do not have any Fixtures for testing I can only use my oscilloscope to verify that DMX is working but it seems fine. I am using a USB Serial and a MAX485.
Since we rent the Fixtures only for sunday I can't test anything but the LED Strips before that day, but it might be possible that I can get my hands on some PAR 64 cans for testing tommorrow.
We are using a Pioneer CDJ for DJ'ing and I would like to use an OSC Client for the Tablet that sits in my closet all year.
I am doing this show every year but we were using some proprietary old software before and I wanted to find something better. I can always use that as a fallback.
I am actually doing another event in July where I seriously wanted to use OLA and maybe afterglow to drive ~ 5000 Pixels and the event on Sunday is a bit of a test to experiment a bit, while I have the equipment.
I wanted to use the salary from that event to buy a small moving head that I can use for testing.
Since we rent the Fixtures only for sunday I can't test anything but the LED Strips before that day, but it might be possible that I can get my hands on some PAR 64 cans for testing tommorrow.
We are using a Pioneer CDJ for DJ'ing and I would like to use an OSC Client for the Tablet that sits in my closet all year.
I am doing this show every year but we were using some proprietary old software before and I wanted to find something better. I can always use that as a fallback.
I am actually doing another event in July where I seriously wanted to use OLA and maybe afterglow to drive ~ 5000 Pixels and the event on Sunday is a bit of a test to experiment a bit, while I have the equipment.
I wanted to use the salary from that event to buy a small moving head that I can use for testing.
I could not get afterglow to send data to ola yet, but thats mainly because I have no Idea what I am doing.
I also tried setting up a leiningen project in intelliJ using afterglow as a dependency, but there is something wrong with it.