Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 11 03:19

    brunchboy on master

    Update to link to netlify hoste… (compare)

  • Jun 11 03:01

    brunchboy on master

    Update doc readme to reflect us… (compare)

  • Jun 10 21:40

    brunchboy on master

    Fix typo in function name. (compare)

  • Jun 10 21:18

    brunchboy on master

    Remove insecure HTTP link, than… Try simplifying API doc path, u… (compare)

  • Jun 10 20:48

    brunchboy on master

    Working on netlify doc build. (compare)

  • Jun 10 20:27

    brunchboy on master

    Update Clojure version. Update Codox version. Try setting up Netlify build fo… (compare)

  • May 27 18:14
    brunchboy edited #70
  • May 27 18:12
    brunchboy edited #70
  • May 27 18:12
    brunchboy labeled #70
  • May 27 18:12
    brunchboy opened #70
  • May 22 05:21
    brunchboy closed #69
  • May 22 05:21

    brunchboy on master

    Update jquery.mincolors color p… Start wedding reception show. (compare)

  • May 22 01:44
    brunchboy opened #69
  • May 22 01:42
    brunchboy closed #23
  • May 22 01:41
    brunchboy closed #65
  • Apr 29 21:08

    brunchboy on master

    Fix more broken images due to w… (compare)

  • Apr 29 21:03

    brunchboy on master

    Fix more broken images due to w… (compare)

  • Apr 29 20:56

    brunchboy on master

    Try without line break? (Older … (compare)

  • Apr 29 20:53

    brunchboy on master

    Fix image macro with comma in a… (compare)

  • Apr 29 07:07

    brunchboy on master

    Make guide base URL independent… (compare)

James Elliott
@brunchboy
Sorry! I am running between events and misinformed you. Call (make-cues) to create them. I almost always call use-push which does that for me.
Home soon with better connectivity.
James Elliott
@brunchboy
The function make-cues in the examples namespace creates a bunch of example cues in the sample show. They should show up on your Launchpad, and verify that the cue coloring and control features are working. You can see the corresponding cues in the web UI if you call (core/start-web-server 16000 true) and click on the Sample Show link, and you should be able to tie the web interface to your Launchpad so they scroll each other using the Linked controller menu which appears below the web cue grid when your Mk2 binding is active.
The cues and the sample show themselves won’t be much use to you beyond examples and early testing; when you want to start working with your actual lights, we’ll need to work on creating fixture definitions for them, put them into your own show that works with an OLA universe you set up, and create cues that work with those. At that point, you will probably want to create your own Leiningen project which uses Afterglow as a dependency, rather than working in the checkout of Afterglow itself. This is described in the Getting Started section of the online documentation. But for testing whether the Mk2 mapping works, the Afterglow checkout, sample show, and make-cues are great.
Benjamin Gudehus
@hastebrot
So there is a lot wrong with the led positions.
James Elliott
@brunchboy
That will be easy to fix, can you describe what is wrong?
(And you are up late again! :grin: )
Benjamin Gudehus
@hastebrot
Using 1:1 as top-left and 8:8 as bottom right. Row 3 is empty, but 3:8 is cyan.
James Elliott
@brunchboy
Hmm, none of the rows should be empty, unless it has scrolled. Do you have the web page up to compare? For reference, in Afterglow, [0,0] is at the bottom left, and cues go up and to the right.
Are there any errors in logs/afterglow.log?
(Not sure if you can also access it without Google account)
This is better (was missing the function buttons): https://drive.google.com/file/d/0B3BCleLtO5vHeVhlMDctb19iTDQ/view?usp=sharing
James Elliott
@brunchboy
I do have a Google account, but don’t know if that was necessary. Anyway, thanks, that is very helpful. And strange.
Those colors are definitely wrong. Let me take another look at the programmer reference.
Do the arrows work to scroll you around?
Benjamin Gudehus
@hastebrot
Yes, I can scroll one page up and right.
James Elliott
@brunchboy
And given that your function buttons actually have dedicated labels, I probably want to move some of my mappings to the right side.
Cool, so that is working at least.
None of the colors are right.
Benjamin Gudehus
@hastebrot
All buttons in row 8 flicker. Which is wrong. Rows 2 and 7 are right with flickering.
James Elliott
@brunchboy
All of them? Or just the first six? Those are supposed to strobe twice per beat, like the web UI does, to reflect the fact that they are strobes.
Oh!
Found one problem, the SysEx starts differently. Pushing a fix momentarily.
Benjamin Gudehus
@hastebrot

Are there any errors in logs/afterglow.log?

I'll delete all old logs and restart the show.

James Elliott
@brunchboy
No need to restart.
Deleting the log is enough, it will be recreated if something happens.
Oh, if you start the show (by pressing Start in the web UI or the Stop button on the controller) and don’t have a Universe 1 configured in OLA (and olad running), there will be a ton of errors about that.
Benjamin Gudehus
@hastebrot
The first six in row 2 flickr (similar to the webpage).
James Elliott
@brunchboy
Rats, I was wrong about what I thought was an error, I was just looking at the wrong line in the manual. The SysEx seems to be what the manual says it should be.
(This is line 88 in launchpad_mk2.clj and the middle of Page 12 in the Programmer Reference.)
Benjamin Gudehus
@hastebrot

Pressing "Start" in the web UI results in showing this error:

Unable to write UpdateDmxData message to OLA: Cannot connect, is it running?

I've installed OLA, but I think it doesn't run.
James Elliott
@brunchboy
You may be right. We can troubleshoot that another time.
I am mystified about what is going on here, I may need to take Novation up on their offer of loaning me an Mk2, but that would take a long time to arrive.
Benjamin Gudehus
@hastebrot
James Elliott
@brunchboy
You could try sending various colors: I realized that what I said earlier about the pads being updated 15 times per second won’t cause us problems if we use a pad that has a static color, because Afterglow only sends changed colors on each grid update.
Benjamin Gudehus
@hastebrot
set-pad-color throws a NPE.
James Elliott
@brunchboy
I’m working on the exact syntax for you to try.
(mk2/set-pad-color @( :controller mk2-watcher) 0 0 (create-color "white"))
The :controller key holds an atom, so you need to dereference it using @ or (deref ...).
Benjamin Gudehus
@hastebrot
Ahh, thanks. So, origin [0,0] is at the bottom-left.
James Elliott
@brunchboy
Correct. What did that color end up looking like?
Benjamin Gudehus
@hastebrot
And maroon is cyan.
is defined maroon as [128, 0, 0] in RGB
And red is green.
James Elliott
@brunchboy

If you have a MIDI monitoring tool, it might be nice to call

(def c @(:controller mk2-watcher))
(mk2/deactivate mk2-watcher)

That will stop afterglow sending stuff, then you can call (mk2/set-pad-color c 0 0 (create-color "white")) and see exactly what bytes are being sent to the controller, and if they match what the reference manual says they should.

Benjamin Gudehus
@hastebrot
KMidimon can monitor a MIDI data stream, in order to diagnose a malfunctioning piece of equipment or to examine the contents of a MIDI sequence during playback.
James Elliott
@brunchboy
Excellent.
Deactivating the binding will stop the tempo flashes, rainbow cues, and other such messages that would drown out what we are looking for.