MyDMX

MyDMX is ADJ's proprietary DMX lighting control platform — a software-plus-hardware ecosystem that lets DJs, event pros, churches, and installation techs control DMX lighting rigs from a computer, tablet, or standalone hardware device. At its core, MyDMX converts the creative side of lighting control — building scenes, chases, color programs, and timed effects — into a visual, click-based interface rather than a traditional lighting console with physical faders. The MyDMX ecosystem spans multiple product tiers: tablet-based wireless control (MyDMX GO), compact USB dongles (MyDMX Buddy), full computer-based software with dedicated hardware interfaces (MyDMX 3.0, MyDMX 5, MyDMX 5 Express), and rack-mount standalone hardware for permanent installs (MyDMX RM). Every version connects to standard DMX fixtures — moving heads, LED washes, par cans, strobes, fog machines — via the 5-pin or 3-pin DMX standard. No proprietary fixture required. MyDMX's built-in fixture library contains 20,000+ profiles (in MyDMX 5), so most name-brand DMX fixtures are pre-mapped out of the box. You add your fixtures from the library, build your scenes visually, then trigger them live during a show — manually, on a timer, to music tempo, or via MIDI. For anyone who wants real DMX control without learning a full professional console platform, MyDMX is the most accessible on-ramp in the market.

The MyDMX lineup covers a wide range of use cases, and picking the wrong version is the most common mistake new buyers make. Here's where each one sits: **MyDMX GO** is the tablet-first option — an iOS/Android app paired with a small hardware interface. It's built for mobile DJs and small venue operators who want wireless control without a laptop. You run the show from a tablet, the hardware dongle connects to your DMX rig. Universe capacity is limited (~1 universe), and programming depth is shallower than the PC/Mac software, but for straightforward mobile rigs it's the most portable option. **MyDMX 3.0** is the workhorse mid-tier. It ships as a PC/Mac software bundle with a dedicated USB interface and has been the go-to platform for working DJs and club installers for years. The software is mature and stable. The hardware interface supports 1 universe natively; two interfaces give you 2 universes. The 3.0 hardware is fully compatible with MyDMX 5 software, so buying 3.0 hardware now doesn't lock you out of future upgrades. **MyDMX 5** is the current flagship. Completely rebuilt platform with an advanced FX engine, Super Scene timeline, 3D visualizer, MIDI/music sync, touchscreen layout support, and 20,000+ fixture profiles. Supports up to 2 universes per hardware interface (or additional universes via unlocks at DMXSoft.com). This is the version for serious semi-pro users. **MyDMX 5 Express** is the entry hardware tier for the MyDMX 5 software — lower price, but with a reduced fixture channel capacity compared to the full MyDMX 5 bundle. Right software, smaller hardware footprint. Good for smaller rigs that don't need the full channel headroom. **MyDMX Buddy** is the most compact option — a small USB dongle that runs the MyDMX software. It comes with an express license. Basic shows are covered, but to use the Easy Remote mobile app for wireless control, you'll need to purchase a full license upgrade. No standalone mode. **MyDMX RM (Rack Mount)** is not a software product — it's a self-contained rack-mount hardware controller for permanent installations. It stores your show internally and runs it without any computer or software. Built for venues where a dedicated laptop is impractical: houses of worship, clubs, themed environments, and permanent event spaces.

MyDMX 5 and MyDMX 5 Express run the same software — the difference is entirely in the hardware interface bundled with each, and the channel capacity that hardware supports. The full **MyDMX 5** bundle includes the larger hardware interface with higher channel headroom. It's built for rigs that use the full range of DMX control — complex moving heads with many channels, large fixture counts, or rigs where you're running close to the 512-channel-per-universe limit. The interface also supports more universes without additional unlocks. **MyDMX 5 Express** ships with a smaller, lower-cost hardware interface that limits the total fixture channel count you can use simultaneously. It's designed for smaller rigs — a club installer with a dozen LED pars and a few moving heads, a DJ running a moderate fixture package — where the reduced ceiling isn't a practical constraint. The software itself is identical. If you start with Express hardware and later outgrow it, you'll need to purchase the full MyDMX 5 hardware interface — the software license itself isn't the bottleneck. For users who are uncertain about which to buy: assess your fixture count and total channel usage. If you're running fewer than 200 channels across your rig, Express hardware will likely serve you fine. If you're running complex moving heads and large fixture counts, go full MyDMX 5 from the start.

The MyDMX Buddy is ADJ's most compact entry point into the PC/Mac MyDMX software — a small USB dongle-style interface that runs the MyDMX software under an express license. It's designed for users who want basic lighting control without the cost or size of the full MyDMX hardware interface, and for minimalists who only need to drive a single, modest DMX rig. The Buddy ships with an express license, which covers standard scene-building and playback functionality. The primary limitation is the Easy Remote mobile app: to use Easy Remote for wireless control from a phone or tablet (triggering scenes remotely), you'll need to upgrade to a full MyDMX license. The upgrade is available through ADJ's software purchase channels. The Buddy itself has no standalone mode — it must be tethered to a running computer to function. The Buddy is best suited for: permanent small-venue installations where a dedicated computer runs MyDMX, DJs or techs who just need a backup DMX interface, or users who want to experiment with the MyDMX software before committing to a larger hardware purchase. If you need wireless remote control from the floor or wireless app triggering, plan your license upgrade budget before buying the Buddy — without the full license, Easy Remote access is unavailable.

The MyDMX RM is ADJ's rack-mount standalone DMX controller — a 1U hardware unit that stores your lighting show internally and runs it without requiring any computer, software, or operator once it's programmed. It's designed for permanent installation environments where a dedicated laptop running MyDMX software would be impractical, unreliable, or unnecessary. Typical applications include houses of worship with a fixed architectural lighting rig, nightclubs or event venues with a permanent fixture installation, themed entertainment environments, and corporate AV installations. The RM handles the show autonomously: power it on, select a show, and it runs. No software to crash, no computer to maintain, no USB dongle to forget. Programming is done externally using the MyDMX software on a computer, then transferred to the RM unit for standalone playback. This gives you the full MyDMX programming interface during the design phase while delivering the reliability of dedicated hardware during operation. Show files are stored on the unit, and multiple shows can be stored for different events or configurations — you select which to run from the front panel. For touring or mobile applications, the RM is not the right tool — its strengths are permanence and reliability in fixed installations. For those use cases, the MyDMX 5 or 3.0 laptop-based setups offer more flexibility.

Yes — the MyDMX 3.0 and MyDMX 5 PC/Mac software runs on both Windows and macOS. ADJ maintains builds for both platforms, and most users across DJ, mobile entertainment, and install markets run on Windows given its prevalence in that market, but Mac is fully supported and commonly used by sound/lighting techs in church and theater environments. For current compatibility specifics, check the system requirements on the MyDMX product page at adj.com before installing — ADJ updates these as new OS versions are released, and older macOS or Windows versions may fall out of support over time. As of 2026, MyDMX 5 supports current versions of Windows 10/11 and macOS (Intel and Apple Silicon with Rosetta or native support depending on the version). MyDMX GO (the tablet version) runs on iOS and Android, and also works on Amazon Fire tablets — useful for DJs who want an inexpensive dedicated tablet for lighting control without tying up an iPhone or iPad. The GO app connects to ADJ's cloud-based fixture library and stores shows locally on the device.

Getting MyDMX up and running correctly the first time requires a specific sequence — skipping steps or rushing through it is the cause of most first-run failures. First, install the MyDMX software on your computer before connecting the hardware. Download the software from the product page at adj.com (not from a third-party site). Run the installer completely and let it finish, including any driver installation prompts. The installer includes the USB drivers that the interface needs — if you skip the software install and just plug in the hardware, Windows or macOS may not recognize it correctly. After the software is installed, reboot your computer. This is not optional — it ensures driver installation completes cleanly. After the reboot, wait for the OS to fully load. Then plug in the MyDMX interface via USB, wait about 10 seconds for it to be recognized (you'll hear the USB connection sound), and only then launch MyDMX. The correct order — boot, then plug in, then launch software — is critical. Reversing these steps causes a majority of first-run recognition failures. Once MyDMX launches, the interface should appear in the software's device panel. If it does, you're ready to patch fixtures and build your first scene. Connect your first DMX fixture to the interface's DMX output using a 3-pin or 5-pin DMX cable (the interface typically has both). Set the fixture's DMX start address to 1, patch it in the MyDMX Setup tab, and test control. Your first light should respond.

Non-recognition of the MyDMX interface is the most common setup issue, and it almost always comes down to one of four things: boot sequence, USB cable quality, driver installation, or firmware corruption. **Boot sequence first:** This fixes the majority of cases. Completely shut down your computer. Unplug the MyDMX interface. Power the computer on and let it fully boot — all startup processes complete, desktop loaded, OS settled. Then plug in the MyDMX interface and wait for the USB recognition sound. Only then open MyDMX. Do not plug the interface in before or during boot. Do not launch MyDMX before the interface shows as recognized. **USB cable:** The cable bundled with some MyDMX interfaces is low quality and causes intermittent or total recognition failures. Swap it out for a known-good, shielded USB cable. Also try a different USB port directly on the computer — avoid USB hubs, which add latency and connection instability. **Driver/software reinstall:** If sequence and cable are fine, uninstall MyDMX completely, reboot, then reinstall from the latest version downloaded from adj.com. Old or partial driver installations can prevent recognition. **CRP DISABLED / firmware corruption:** If you see the message 'CRP DISABLED' appear in Windows as a drive label when you plug the interface in, the interface firmware is corrupted and needs recovery. See the CRP DISABLED FAQ for the recovery process. This is a separate issue from a normal recognition failure.

CRP DISABLED is a firmware corruption state — not a software problem, and not a computer problem. It means the firmware on the MyDMX USB interface itself has become corrupted and the device is no longer operational as a DMX interface. When you plug the interface into a Windows computer, instead of appearing as a recognized MyDMX device, it shows up as a drive labeled 'CRP DISABLED.' On macOS, it may appear as an unrecognized USB device. The most common causes are: unplugging the interface while MyDMX software was actively running (which interrupts a data transfer mid-write), power surges through the USB port, or a system crash while the software had the interface open. The corruption affects only the interface's onboard firmware — your show files stored on the computer are unaffected. Recovery procedure: Download the Hardware Manager utility from adj.com (find the MyDMX product page and look under Downloads). Install Hardware Manager on your computer, connect the interface, and run Hardware Manager — it contains firmware recovery files for MyDMX interfaces and can push a fresh firmware to the corrupted device. Follow the on-screen prompts. Most CRP DISABLED interfaces recover successfully via Hardware Manager. If Hardware Manager cannot recover the interface, WTOOLS is the deeper recovery utility. Download it from adj.com. If WTOOLS also fails, the interface hardware has sustained physical damage and needs to be sent to ADJ service. To prevent recurrence: always close MyDMX software before unplugging the interface, and use a quality USB cable with stable power delivery.

It depends on which version of MyDMX you're running. For MyDMX 3.0, MyDMX 5, and the Buddy — yes, the USB hardware interface must be connected to run the software. The hardware interface serves dual duty: it's both the DMX output device and the license enforcement mechanism. Without it plugged in, the software will not run in full operational mode. For the dongle-licensed versions, the correct procedure is: boot your computer fully, then plug in the interface, then launch MyDMX. The timing matters — plugging the interface in too early (during boot) or launching the software before the interface is recognized are common causes of 'interface not found' errors on startup. The forum-confirmed best practice is to plug the dongle in after boot but before launching the software. MyDMX GO on a tablet works differently — the hardware interface connects via a dedicated port on the tablet or via a compatible adapter, but the GO app's licensing is tied to the ADJ account/device registration rather than a tethered dongle in the traditional sense. If you're building a permanent installation with MyDMX RM, the hardware is self-contained — no separate computer dongle is in play. The RM unit is the controller and runs autonomously once programmed.

MyDMX includes a built-in fixture library with 20,000+ profiles (MyDMX 5) covering the vast majority of current DMX fixtures from major manufacturers. In most cases, your fixture is already in there — you just need to find and add it. In MyDMX 5, go to the Setup tab. Click 'Add Fixture' or use the fixture browser panel. You can search by manufacturer and model name. When you find your fixture, select the correct DMX mode (check your fixture's manual for the mode and channel count, then match it here). Assign it a universe and starting DMX address. Click Add. Your fixture now appears in the patch list with all its channels pre-mapped — pan, tilt, color, gobo, dimmer, strobe, etc. — ready to control from the scene-building interface. If your fixture isn't in the library: first update the library (MyDMX 5 can pull the latest profile updates from ADJ's server — check the update option in the software). If it's still not listed after updating, you can create a custom profile using MyDMX's built-in profile editor. Open the editor, input your fixture's channel map from its DMX chart (found in the manual or product page downloads), and save it as a custom profile. The custom profile then appears in your library like any built-in profile. For generic fixtures without official profiles — cheap LED pars, no-name controllers — use the generic fixture type and manually assign channels. It's less elegant but works for simple RGB or RGBW fixtures.

Hardware Manager is a free standalone utility from ADJ that handles firmware and settings management for MyDMX interfaces and select ADJ fixtures. It's a separate program from the MyDMX software itself — you download it from adj.com (look under the Downloads section of your specific MyDMX product page) and run it independently. The main uses for Hardware Manager are: firmware updates for MyDMX interfaces (new firmware versions fix bugs, add features, and improve USB stability); firmware recovery for interfaces in the CRP DISABLED state (corrupted firmware); settings adjustments for devices where navigating the onboard menu is cumbersome; and factory reset operations for MyDMX hardware via computer rather than front-panel menus. In practice, most users need Hardware Manager in two situations: when ADJ releases a MyDMX software update that also requires an interface firmware update (the release notes will tell you), or when troubleshooting an interface that's showing CRP DISABLED or failing to be recognized. In the latter case, Hardware Manager is your first recovery tool before considering a depot repair. Hardware Manager is also used for some ADJ fixtures outside the MyDMX ecosystem — certain fixture lines receive firmware updates via USB and Hardware Manager rather than OTA (Aria X2 handles OTA on newer fixture lines). If your fixture's product page lists a 'Hardware Manager' download, that's your signal it uses this tool for updates.

Scenes are the fundamental programming unit in MyDMX — a scene is a saved lighting state (or sequence of states) that you can trigger with a single button press during a show. Building scenes well is what separates a polished lighting show from a chaotic one. To create a scene in MyDMX 5: after your fixtures are patched in the Setup tab, switch to the Live tab (or the Scenes tab, depending on your layout). Select the fixtures you want to control, then use the control panel — color pickers, position sliders, gobo selectors, intensity faders — to set each fixture to the look you want. This is your first 'step' of the scene. Click 'Record' or the scene slot you want to save it to. Name the scene. It's now stored and playable. For simple static scenes (a single frozen look), one step is all you need. For dynamic scenes — a color chase, a pan sweep, an alternating pattern — you add multiple steps. Each step defines a different fixture state, and MyDMX plays through the steps in sequence at the speed you set. The time between steps is adjustable from milliseconds to several seconds. More steps, faster timing = a chase effect. Fewer steps, slower timing = a slow sweep or transition. Scene organization: MyDMX uses pages and banks to organize scenes. Group scenes logically — opener looks on page 1, color chases on page 2, drum solos on page 3. This keeps live triggering fast and intuitive. Once you're in a show with 40+ scenes, clean organization is the difference between hitting the right look and hunting for it in front of an audience.

MIDI triggering in MyDMX lets you fire lighting scenes from a pad controller, keyboard, DAW, or any MIDI-capable device. This is popular with DJs who want to trigger lighting changes from a launch pad alongside music cues, and with AV techs who want to automate lighting from a show control system. The setup process is straightforward: in MyDMX, navigate to the user tab that contains the scenes you want to trigger. Right-click a scene button. Select 'Waiting for MIDI command' from the context menu — the button will show it's in learn mode. Then press the pad, key, or button on your MIDI controller that you want to assign to that scene. MyDMX captures the MIDI note or CC message and binds it to the scene. Repeat for each scene you want to assign. Note-On messages (the kind sent when you press a pad or key) are the standard trigger type. For **DAW automation**: MyDMX can receive CC (Continuous Controller) messages to control DMX channel values directly, allowing you to write lighting automation into a DAW timeline. This lets you build a timed lighting show that fires from your DAW alongside music tracks or video. Map the DMX channel you want to automate to a CC number in MyDMX's MIDI config, then draw automation for that CC in your DAW. Setup requirements: your MIDI controller or DAW output must be visible to the computer running MyDMX. Hardware MIDI controllers connect via USB or a MIDI interface. For DAW-to-MyDMX on the same machine, use a virtual MIDI port — loopMIDI on Windows, IAC Bus on macOS. Both are free and straightforward to configure.

Getting two moving heads to mirror each other symmetrically — both sweeping outward from center rather than both moving in the same direction — requires inverting the pan and/or tilt channels for one of the fixtures at the patch level. MyDMX handles this in the Setup tab, but the control is in a view mode that most users don't find by default. Here's the procedure: open the Setup tab in MyDMX. In the top-right corner of the Setup panel, look for the view mode buttons and switch from the default grid/icon view to **list view**. In list view, all your patched fixtures are shown as rows with their individual attributes listed. Find the fixture you want to mirror. Click to select it. In the attribute column, locate the Pan and Tilt channels. Each channel has an 'Invert' toggle — click it for Pan, Tilt, or both depending on how you want the fixture mirrored. With Pan inverted, the fixture will sweep in the opposite horizontal direction from your other fixtures when you send the same pan command — sweep right in MyDMX, and the mirrored fixture sweeps left. Invert Tilt to reverse the vertical axis. Invert both for a full mirror. This inversion applies globally to the fixture patch, meaning every scene that uses that fixture will automatically use the inverted values. You don't need to offset values manually scene by scene. The result is a symmetrical rig that responds to single pan/tilt commands as a properly mirrored pair.

For permanent installations — a church sanctuary, a nightclub, a themed environment — you want the lighting system to run without operator interaction, without a computer left on-site, and ideally without anything that can crash or require maintenance. MyDMX offers two paths for this: MyDMX RM (dedicated standalone hardware) and standalone show playback via the software. The **MyDMX RM** is the cleanest solution. Program your show on a laptop using the MyDMX software, transfer the completed show to the RM via USB, and the RM runs it indefinitely without any computer. Power it on, select your show from the front panel, and it runs. No dongle to lose, no software to crash, no laptop to leave on-site. For **laptop-based permanent installs** using MyDMX 5 or 3.0: configure Windows or macOS to auto-boot to the desktop, set MyDMX to launch on startup (add it to startup items), and configure a startup script or USB sequencing delay to ensure the interface is recognized before MyDMX launches. Use a quality powered USB hub to ensure consistent power to the interface. Set MyDMX to auto-resume the last active show on launch. Lock down the computer to prevent accidental changes — a simple kiosk-mode setup or restricted user account works for this. For any permanent install, also configure your DMX fixtures for their own startup behavior: set them to their default look (color, position) on power-up so the rig looks intentional even before MyDMX sends its first command.

MyDMX GO is designed to be the most accessible MyDMX experience — install the app, connect the hardware, and you're controlling lights in minutes without a full computer setup. Here's how to get started. First, download the MyDMX GO app from the App Store (iOS) or Google Play (Android). Amazon Fire tablets are also supported, useful as dedicated inexpensive control panels. Connect the MyDMX GO hardware interface to your tablet using the appropriate cable or adapter — iOS devices typically need a Lightning or USB-C adapter, Android via USB-C or micro-USB depending on your tablet model. The interface provides the actual DMX signal output to your fixtures; the tablet is the control brain. Once connected, launch the GO app. It will recognize the interface. Add your fixtures from the GO library — search by manufacturer and model, select your DMX mode, assign a start address, and patch them. Set your fixtures' physical DMX addresses to match what you patched in the app. Connect your fixtures to the interface's DMX output. Test control by selecting a fixture and moving sliders. MyDMX GO's workflow is simplified compared to the full PC/Mac software: you build scenes using a visual interface, assign them to the on-screen buttons, and trigger them live. The GO library is updated from ADJ's servers and includes 15,000+ fixture profiles. The GO platform is intended for simpler rigs — mobile DJs, small venues, events with fewer than ~100 fixtures. If your rig grows more complex, the step up to MyDMX 5 PC/Mac software gives you significantly more programming depth.

Yes — MyDMX controls any standard DMX512-compliant fixture, regardless of manufacturer. DMX is an industry-wide open standard, and MyDMX's hardware outputs standard DMX512 data that any compliant fixture can receive. There's no ADJ lock-in at the protocol level. MyDMX's built-in fixture library includes profiles from hundreds of manufacturers beyond ADJ: Chauvet, Martin, Robe, Elation, GLP, ETC, and many others are in the library. In MyDMX 5's 20,000+ profile library, most current-production fixtures from major brands are already profiled. Search by manufacturer in the Setup tab's fixture browser. If a specific fixture isn't in the library, you can create a custom profile: open the profile editor, enter your fixture's channel assignments from its DMX chart (found in the manufacturer's user manual or product page), and save the custom profile to your library. Custom profiles behave identically to built-in profiles once saved. For generic no-name fixtures without published profiles, use a generic RGB, RGBW, or dimmer profile and manually assign channels. This works reliably for simple fixtures like basic LED pars. For complex fixtures without a published DMX chart, you may need to map channels by trial and error — a process that works but takes time. One practical note: profile accuracy matters. A profile that incorrectly maps a fixture's channel order will produce unexpected behavior (intensity controlling color, gobos not responding, etc.). When in doubt, verify channel assignments against the fixture's manual.

The software is talking to the interface, but the fixtures aren't listening — this is almost always a wiring, addressing, or patch mismatch issue. Work through this checklist in order. **DMX address mismatch:** This is the #1 cause. Verify the physical DMX start address set on each fixture matches the address you patched in MyDMX's Setup tab. If MyDMX is sending channel 1 data but your fixture is set to start at address 100, it receives nothing relevant. Check the fixture's onboard display to confirm its current address, and confirm it matches the patch. **Cable connectivity and DMX signal:** Confirm your DMX cable runs from the MyDMX interface's DMX output directly to the first fixture's DMX input. Check that the cable is a proper DMX cable (not a generic XLR audio cable — though generic XLR often works, a bad cable is always suspect). Try a different cable. Verify the connector is fully seated. If you have multiple fixtures daisy-chained, isolate just the first fixture on the chain to confirm signal is reaching it. **DMX mode / channel count:** The fixture must be set to the same DMX mode you selected in the patch. If MyDMX thinks the fixture is in 7-channel mode but the fixture is physically set to 14-channel mode, channel assignments won't align. Check the fixture's menu for its current operational mode and match it to your MyDMX patch. **Termination:** If you have multiple fixtures chained, ensure you have a 120-ohm terminator on the last fixture's DMX output. Missing termination can cause intermittent or total loss of signal for some or all fixtures, especially in longer chains.

Mid-show crashes are a MyDMX user's worst nightmare. The good news: the vast majority of them are preventable with the right setup habits. **Boot sequence — the most impactful fix:** Fully reboot your computer before every show. Do not plug in the MyDMX interface until the OS has completely loaded. After the OS settles, plug in the interface, wait for recognition, then launch MyDMX. Skipping this sequence is the single biggest predictor of mid-show freezes. This applies regardless of whether you 'just used it yesterday' — start fresh every show. **USB cable and port:** Replace the included cable with a quality shielded USB cable and plug it directly into the computer's USB port — not a hub. USB hubs introduce connection instability that manifests as random crashes, especially during sustained shows. **Close competing applications:** DJ software, audio interfaces, streaming tools, web browsers, and video applications all consume CPU and RAM that MyDMX needs. On show nights, close everything that isn't MyDMX before launch. Check Task Manager (Windows) or Activity Monitor (Mac) to confirm low background resource usage. **Known MyDMX 5 bugs (as of 2026):** ADJ has confirmed open crash bugs in MyDMX 5 related to: deleting fixtures mid-session, using undo/redo on scene steps, triggering next/previous scene rapidly, trigger-on functions, and beam mapping operations. Avoid these actions during live shows and save your show file frequently during programming. ADJ has confirmed fixes are in development — stay on the latest release and watch adj.com for update announcements. **Backup plan:** For critical shows, have a second laptop with MyDMX loaded and your show file ready to take over. A 60-second recovery on a backup system is far better than a 10-minute scramble.

Show file compatibility between MyDMX versions is not always guaranteed, and an upgrade from one major version to another can leave show files that won't open, open with errors, or open with missing/altered content. The most common scenario: upgrading from MyDMX 3.0 to MyDMX 5. MyDMX 5 can import 3.0 show files, but it's a migration process rather than a perfect load. The import typically handles scenes, fixture patches, and basic programming well, but may drop or misinterpret features that changed between versions — certain effects parameters, advanced trigger settings, or features that were deprecated or redesigned. After importing, go through your scenes systematically to verify they behave as expected before using the file live. If the file won't open at all (error on launch, immediate crash, corrupted file warning): first verify you're using the correct software version for the file type. Opening a MyDMX 5 file in MyDMX 3.0 software won't work — newer file formats don't backport. If you have a corrupted file, check for a backup: MyDMX typically creates auto-save or backup copies during active sessions. Look for files with .bak extensions or timestamp variants in the show file directory. Best practice: before any software upgrade, back up all your show files to a separate location. After upgrading, test your most critical shows immediately in a non-show environment. Keep a clean install of the previous version on a separate drive or partition until you've confirmed all your shows migrate correctly.

MyDMX interface firmware updates are handled through the Hardware Manager utility — not through the MyDMX software itself. Here's the process: First, download Hardware Manager from adj.com — navigate to your MyDMX product page (e.g., the MyDMX 5 or MyDMX 3.0 page) and look in the Downloads section. Install Hardware Manager on your PC or Mac. Check the ADJ website or Hardware Manager's release notes to verify whether a firmware update is actually available for your interface model — don't update if your firmware is already current, as unnecessary updates carry a small risk of issues. To update: launch Hardware Manager first. Then connect the MyDMX interface via USB (follow the same boot-then-connect sequence: computer fully booted, then plug in interface). Hardware Manager should detect the connected interface and display its current firmware version. If an update is available, you'll see the option to update. Follow the on-screen prompts — the update takes a minute or two. Do not disconnect the interface or close Hardware Manager during the update. An interrupted firmware update is the most common cause of CRP DISABLED corruption. After the update completes, disconnect and reconnect the interface, launch MyDMX normally, and verify it operates correctly. Some firmware updates improve USB stability significantly, so if you've been experiencing interface recognition issues, checking for a firmware update via Hardware Manager is a worthwhile troubleshooting step even before the other fixes.

It depends on which version of MyDMX you're running and how old the machine is. MyDMX 3.0 has relatively modest system requirements and runs acceptably on older hardware — a dual-core processor from the mid-2010s with 4GB RAM and a clean Windows 7/8/10 install can handle it. The software is not computationally intensive for a normal show. MyDMX 5 has higher requirements. The rebuilt platform, 3D visualizer, FX engine, and expanded fixture library all add up to heavier resource usage. ADJ recommends checking the official system requirements on the MyDMX 5 product page before installing. As a practical guide: 4GB RAM is a minimum, 8GB is comfortable; an Intel Core i5 (4th gen or newer) or AMD equivalent handles it; a dedicated graphics card helps with the 3D visualizer but isn't strictly required. Running MyDMX 5 on a low-spec machine — especially with the 3D visualizer enabled — may result in the performance issues and crashes that users often attribute to software bugs but are actually hardware bottlenecks. Regardless of machine age, a few habits matter more than raw specs for show reliability: keep the laptop's OS clean (minimal background processes, no antivirus scans running mid-show), disable automatic Windows updates during show days, disable sleep/hibernate, set the power plan to High Performance, and ensure the USB controller chipset is not a budget integrated hub. A clean mid-tier laptop from 2018-2020 running Windows 10 with nothing extra installed will outperform a newer but bloated machine for MyDMX purposes.