Titanic's End is a mutant vehicle that debuted at Burning Man 2022 and has since participated in EDC and Framework events.

We are the largest team developing on Chromatik in the open so other artists can benefit from our work (see the license). This repo contains the shader & pattern code for the 128,000 LEDS, sound reactivity, MIDI control, OSC middleware, and ArtNet bidirectional control.

We use Chromatik (formerly known as LX Studio) to control the show. Although not required, we also support Chromatik financially because it's excellent. This README will get you up and running with it so you, too, can create stunning LED art.

Our work is notable for:

• AutoVJ - an autopilot that uses Pioneer Rekordbox's phrase and beat analysis to change patterns when a human VJ would
• GLSL shader support
• Developed to team-friendly maintainability standards for long-term enjoyment of the codebase
• GigglePixel, Pixelblaze, and ArtNet integration

Want a personal intro to the project and codebase? Contact current team lead Andrew Look by messaging andrew-m-look (s/-/./g) electronically at the big Gm.com thing.

Either go to https://adoptium.net/installation/ or, on a Mac with Homebrew:

brew install --cask temurin@17

# verify your installation by running:
/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/java --version

These are geared toward running Chromatik on a Macbook with git already installed. If you need help with anything, ask in the Slack #lighting-software channel!

First, you'll need an IDE (editor). IntelliJ's Community Edition is the best free one available. You can download it here: https://www.jetbrains.com/idea/

Steps for setup:

1. Clone the git repo you're looking at:

   git clone https://github.com/titanicsend/LXStudio-TE.git
   

2. Open the project director you cloned to when you're presented with "New Project" and "Open" options. That's the initial screen.

3. File → Project Structure (or ⌘-;)

   1. Platform Settings → SDKs

      1. Either add the installed Temurin 17 JDK
      2. Or, if that JDK is not installed, you can click the '+' and then select "Add JDK..."
         1. Navigate to /Library/Java/JavaVirtualMachines/temurin-17.jdk
         2. Select temurin-17.jdk

   2. Project Settings → Project

      1. Select the Temurin 17 JDK

4. Select "Titanic's End" in the top bar (in the dropdown to the right of the hammer) if you want to use the vehicle model, or "Testahedron" if you want the testahedron model.

5. Hit the green arrow "play" button. (If you just want to build, you can hit the hammer.)

6. Assuming things work okay, a UI for Chromatik will pop up: Great! Now, you can play with the buttons.

These are the steps to use google-java-format automatically and ensure that each commit gets formatted before being submitted.

1. Setup git pre-commit hook to run the google-java-format CLI tool on changed files

cp pre-commit ./git/hooks/pre-commit

Now commits will fail if there's a style violation, since this runs mvn spotless:check.

YOu can manually apply formatting fixes using mvn spotless:apply.

2. (Optional) Install the IDE plugin for IntelliJ
   1. After plugin install, go to Settings > Tools > Actions on Save and enable Reformat Code and Optimize Imports.
3. (Optional) Or install the IDE plugin for Eclipse.

• Maven resources compiler: Failed to copy [...]/target/generated-test-sources/test-annotations/Icon ' to '[...]/target/test-classes/Icon
  • Go to the top of your TE repo and run find . -name Icon\? -delete

So you've got the app up and running. You see some patterns in the code. How do you make sense of them?

To understand the point, edge, and panel naming scheme, see the Visual Map tab of the Modules, Edges and Panels sheet.

TE is using the full IDE-ready distribution instead of the P4 Processing Applet version. Don't struggle - ask questions in #lighting-software on Slack.

The tutorials in the LX Studio Wiki are an effective introduction.

These have been compiled by our team:

• Operation Modes and Art Direction Standards
• Using Tempo and Sound
• The APC40 and LX Studio

As you really get rolling, you’ll appreciate the API docs and public portion of the source.

Once it's running, go tell Slack so we can celebrate with you and maybe give you a tour. Or, if you prefer self-guided tours:

• Read the LX Studio Wiki
• Play with the UI until you have a modulator controlling the parameter for a pattern, and an effect applied on top.
  • See this guide from another memorable Burning Man art piece
• Define a new fixture in the UI
• [Optional] Save your playground as a new project with your name: Playground <YourName>.lxp. You can mess this project up and experiment broadly.

Things that can help improve your experience with LX Studio.

It can be handy to edit Chromatik's JSON config files in the IDE. Add the .lxf and .lxp extensions to be recognized as JSON.

1. Open IntelliJ preferences (⌘-, on Mac) and go to Editor → File Types → JSON.
2. Next, add "*.lxp" to the list, and so on.

Jeff's enjoying the following (he comes from Sublime and vim):

• CodeGlance
• Rainbow Brackets
• IdeaVim
• CSV
• KeyPromoter X
• Python Community Edition

Many of you may use VS Code in your day-to-day life. If you do, and you'd like IntelliJ to behave more like VS Code, I'd recommend:

1. In IntelliJ, open the "IntelliJ IDEA" menu and select "Preferences"
2. Click "Plugins"
3. Search for "VSCode Keymap"; install
4. Go back to "Preferences"
5. Go to "Keymap", select one of the VS Code keymap options, (either macOS or not) hit apply, and enjoy increased happiness in your IDE

If you just need to execute Chromatik to run a show without editing anything, you can do that:

0. Install Temurin JDK (see JDK installation above).

1. Build into a runnable JAR:

   mvn clean package  # Packaging creates the JAR and cleaning is optional

2. Execute the JAR (Note that the version number may be different — The version as of this document revision is 0.2.1-SNAPSHOT — substitute the correct version as necessary):

   java -jar target/LXStudio-TE-0.2.1-SNAPSHOT-jar-with-dependencies.jar vehicle Vehicle.lxp

3. If the Temurin JDK isn't your default Java, then you can use the full path, for example:

   /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin/java -jar target/LXStudio-TE-0.2.1-SNAPSHOT-jar-with-dependencies.jar vehicle Vehicle.lxp

4. Use Maven to execute the program instead of the java command:

   mvn clean compile  # Cleaning and compiling is optional, depending on your needs
   mvn exec:exec@Main -Dexec.args="vehicle Vehicle.lxp"

   Fun fact: The "Main" target isn't defined in the POM to have arguments, but it could, in which case you wouldn't need the vehicle Vehicle.lxp args.

If your ~/.m2 Maven cache has any conflicting things, you may need to delete the conflicts, otherwise the execution may complain about things like missing libraries or invalid versions, and the like. Finding the conflicts is a more advanced approach. A simple one is to just delete that whole directory:

rm -r ~/.m2

To run on machine startup (ie: press power button and Chromatik just starts up), you'll need to do three things:

1. Add TE.app to your startup items
   1. System Preferences > Users & Groups
   2. Click the user to run Chromatik with
   3. Login Items > "+" button > add TE.app
2. Change to automatic login
   1. System Preferences > Users & Groups
   2. Click "Login Options" underneath list of accounts (may need to enter password)
   3. Using the combo box, select desired user, ie "te" or whatever
   4. Uncheck all the boxes underneath
3. Remove the password from your user account
   1. System Preferences > Users & Groups
   2. Click the user > "Change Password"
   3. Leave new password blank
4. Keep in Dock
   1. When TE.app is running, right click on it, and say "Keep in Dock"
   2. This way, during a show, it's very easy for anyone non-technical to simply quit the program and re-run it if there is an issue

Restart your machine and you should see Chromatik open automatically on startup.

If Eclipse is like a warm snuggie to you, we'd appreciate you adding any SDK and environment configuration tips here.

The car's main Chromatik instance runs on a Mac Studio that lives on the car, connected to the car's LAN. The UI is controlled via a remote desktop (VNC) connection over a high-speed PTP wireless bridge. Since the VJ at this remote Front-of-House desk will want to use MIDI surfaces and controllers to perform, we needed to come up with a MIDI-over-WiFi solution to connect the USB MIDI devices to the box running Chromatik on the car.

In 2022, we utilized OSX's arcane built-in support for RTP-MIDI. This was brittle and fickle to maintain.

In 2023 we've changed to using a device called a BomeBox that uses a proprietary encapsulation protocol. To make this work:

1. The Bome Network tool should be installed on the computer that runs Chromatik. The "Multiple Named Virtual interfaces" upgrade is required.
2. The remote BomeBox should be on the same subnet, with updated firmware
3. Optionally, renamed the BomeBox. We changed "BomeBox" to "FoH" for "Front of House"
4. Connect the MIDI controllers to the BomeBox USB port via a USB Hub. In the Bome Network tool, enable Remote Direct Midi for those devices.
5. You can disable MIDI routes that aren't used, such as the DIN ports or MIDI messaging between the USB devices. This likely helps performance. Leave 2 routes per device: The bidirection pair Chromatik->Device, and Device->Chromatik.
6. Register the correct new names in Chromatik. The Bome Remote Direct Midi device names follow a pattern of "{BomeBoxName}: {DeviceName}", like "FoH: APC40 mkII". For example, in your main app you may need to lx.engine.midi.registerSurface(name, class) or match the name with an entry in lx.engine.midi.inputs[].getName(). If using more than one midi device of the same type BoxBox will present each device with a unique name by appending a number such as "FoH: Midi Fighter Twister (2)". registerSurface(name, class) needs to be called for each of these unique names.

Here's a video illustrating our configuration.

Please see LICENSE.md - significant parts of this repository are not open source and we support those authors' wishes.