Lighting and control
ACME Pixel Line IP
Match the mounting variant, firmware and console personality before tracing missing pixels, strobe behavior or network reception.
Ask GLMedia about renting ACME Pixel Line IP for your event. Availability and configuration are subject to confirmation.
Model and purpose
- Manufacturer
- ACME
- Model
- ACME Pixel Line IP
- Variant
- STROBE 3 IP: omega brackets; STROBE 3 IPS: sliding clamps
- Zones / optics
- 32 RGB zones, 16 cool white zones; Smart Glass frost
- Power
- 100–240 VAC, 50/60 Hz; maximum 420 W
- Environment
- IP66; ambient -10–40 °C; no immersion
A linear effects fixture for scenic lines, pixel patterns and white strobe accents. Choose the DMX mode around the required cell and effect controls, then check the console’s actual channel map. A matching product name alone does not establish a matching personality.
Prepare your rental inquiry
- Date, city, venue and setup, event and pickup schedule.
- Intended use, area dimensions and equipment already supplied by the venue or production.
- Wash, effect or accent use; location and target area.
- Required zone or pixel control, profile and cabling, subject to model functions.
Specify equipment only or whether setup, programming, operation and strike are also needed. Scope is confirmed in the proposal.
You do not need a final equipment list: tell us the result you want and the part you need help with. Availability and scope are confirmed in the proposal.
Features and connections
The documented data paths are DMX/RDM over XLR and Art-Net or sACN over Ethernet. The manual specifies 5-pin XLR with a 3-pin option; inspect the supplied hardware and use suitable weatherproof connections outdoors.
The mounting versions must not be joined to each other. Select supports for the actual version, secure the fixture and provide the documented secondary attachment for suspension; the alignment connector does not replace a rigging assessment.
Prepare the system
- Record hardware, firmware under Information, DMX Channel Mode and address. Save the show before repatching. Use the REV M manual and V2.4 chart only where they match the installed revision.
- Prepare protected, grounded mains, approved power/data cables and the appropriate supports. Have qualified personnel assess circuit loading and mounting; do not estimate a power-link count from wattage alone.
- Isolate a test fixture, limit intensity and keep the beam clear of people. Select the intended Connect Option, then compare received values with a simple console look.
Questions and troubleshooting
The profile patches successfully but pixels or effects are wrong: what should I compare?
The same footprint can have different functions. 70 and 70N require separate maps; 117, 119 and 125 also place controls differently.
- Compare the exact mode label on the fixture with the console library revision and official chart. Check common dimmer, fine, frost and effect channels before individual cells.
- Compare RGB and white sections separately at low output. Do not infer a hardware fault from a visualizer alone, and do not assume a profile for the shorter variant is equivalent.
- If the needed mode is absent, preserve the patch and identify firmware support before updating. Do not add an undocumented mode simply because it appears on a product summary.
Network is connected but the fixture does not follow the console: where do I trace it?
An Ethernet connection does not establish the intended protocol, universe or address.
- Choose Art-Net or sACN explicitly in Connect Option for the test. Compare fixture IP/subnet with the sender’s interface and verify the agreed universe mapping at both ends.
- For Art-Net compare Net, Sub-Net and Universe; for sACN compare universe and priority. Check whether another sender or merge is affecting the output before changing the whole network.
- Use View DMX Value to compare a known transmitted channel. If values arrive, trace mode and intensity; if they do not, isolate source, cable and network route. Choose No DMX Status deliberately and test loss/recovery with the rig clear.
A chase runs backward or RGB changes when white strobe is used: what is a useful check?
Separate cell orientation from shared effect controls. The result depends on the selected mode, profile and revision.
- Run a slow single-cell chase and compare physical direction with the patch. Read Invert Pixel Order; change only the agreed test unit and check again.
- For strobe behavior, compare the chart’s master and RGB/white controls with actual received values. An effect parameter labeled Null is not sufficient evidence that every other shutter/rate parameter is ready for steady light.
- Compare a known matching unit at the same settings. Record firmware and raw values before reset or update; user reports do not establish a universal defect or a proven firmware remedy.
Quick reference
| Mode / footprint | Last valid start | Check |
|---|---|---|
| 117 | 396 | Shared controls and cell map |
| 119 | 394 | Fine dimmer and control channel |
| 125 | 388 | Separate RGB/white effect controls |
| 70 / 70N | 443 | Same size, different map |
Precautions
- Use continuous mains, never a dimmer output. Inspect seals, caps and cables; IP66 does not permit immersion or damaged connectors.
- Maintain ventilation and the manual’s clearances; surfaces may reach 65 °C. Stop for damage or serious errors and use authorized service.
- Avoid direct eye exposure and plan strobe cues with the event team. Test camera response with the actual settings; no flicker-free result is guaranteed.
Terms on this page
- DMX
- A data protocol controlling lighting functions; each model defines what its channels mean.
- RDM
- Management communication for querying or configuring compatible equipment over a compatible path.
- Patch
- Assignment of fixture, profile, address and universe in the control system.
- Personality
- A control mode defining the channels and functions used by a fixture.
Documentation and sources
- ACME Pixel Line IP — product / variants
- User Manual REV M — 07/21/2026
- DMX chart — firmware V2.4
- ACME fixture library
Consulted 2026-10-22. Scope: manual REV M and chart valid from V2.4. The product page has conflicting mode counts and an additional 69 listing; confirm the installed firmware/menu before patching. These are proposed checks, not a physical GLMedia test.