How To Create a New Command in mpc-hc64.exe (Media Player Classic)

If you use Media Player Classic – Home Cinema (MPC‑HC) a lot, it’s natural to want your own shortcuts or custom actions. The 64‑bit version, mpc-hc64.exe, supports quite a bit of customization, but it’s not always obvious how to “create a new command.”

The trick is understanding the difference between:

• Built‑in commands you can remap
• Command line options you can call from outside
• Custom behavior you simulate using external tools or scripts

This FAQ walks through how MPC‑HC commands work, what “new command” really means, and the ways you can extend or trigger playback actions.

What Does “Creating a New Command” in MPC‑HC Actually Mean?

In MPC‑HC you can’t directly add brand‑new internal features from inside the app (like “Add a brand‑new menu item that MPC‑HC has never heard of”). What you can do is:

1. Remap existing internal commands

   • Change keyboard shortcuts
   • Change mouse bindings
   • Change remote control shortcuts (if supported)

2. Call MPC‑HC with different command line switches

   • For example, open a file, start fullscreen, jump to a time, etc.
   • These can be wrapped into a script or a desktop shortcut

3. Use external tools or scripts to extend behavior

   • Automation tools (AutoHotkey, PowerShell, batch files)
   • Media front‑ends or launcher apps that send commands to MPC‑HC
   • Custom remote‑control setups that map buttons to MPC‑HC actions

So “creating a new command” usually means creating a new way to trigger one or more existing MPC‑HC actions, often combined with external automation.

How Built‑In Commands and Shortcuts Work in mpc-hc64.exe

MPC‑HC has a long list of predefined actions, such as:

• Play/Pause
• Seek forward/backward
• Next/Previous file
• Volume up/down
• Toggle subtitles
• Toggle fullscreen
• Switch audio track
• Change subtitle delay, audio delay, and so on

Each of these is a command inside MPC‑HC. You can see and customize them in:

View → Options → Keys

There, you’ll find:

• A list of command names (e.g., “Play/Pause”, “Open File”, “Next Audio Track”)
• The current keyboard shortcut assigned
• The current mouse or remote assignment (if any)

You can’t add an entirely new internal command to this list, but you can:

• Assign a new key to an existing command
• Assign a mouse button or wheel combination
• Change or remove default bindings

This is the built‑in way to “create a command shortcut” inside MPC‑HC.

Step‑by‑Step: Creating a New Shortcut Command in MPC‑HC

If by “new command” you mean “a new key that does what I want,” here’s how to do it:

1. Open the Keys Settings

1. Launch mpc-hc64.exe.
2. Go to View → Options.
3. In the left sidebar, select Keys (sometimes labeled Player → Keys depending on build).

You’ll see a table of all available commands.

2. Choose the Command You Want to Trigger

Scroll through the commands and pick one that does what you need, for example:

• “Next Subtitle” to cycle through subtitles
• “Jump Forward (small)” to skip ahead
• “Increase Sub Delay” / “Decrease Sub Delay” for fine‑tuning subtitles

Click on that command’s row.

3. Add a New Keyboard Shortcut

1. In the right panel, there’s typically a section for “New Hotkey” or similar.
2. Click into the hotkey box.
3. Press your desired key combination, for example:
   • Ctrl + Alt + N
   • Shift + F12
4. Click Add (or the equivalent button).

The new shortcut will now appear attached to that command. You’ve effectively created a new command trigger inside MPC‑HC.

4. Optionally Add Mouse or Remote Control Actions

If you control MPC‑HC from a mouse or external device:

• Use the Mouse section in the same Keys options window.
• Choose which mouse gesture or button you want (e.g., Middle Click, XButton1).
• Assign it to the same or a different command.

Again, you’re not inventing new internal behavior, but you’re creating new ways to issue those commands.

Using Command Line Options: Creating External “Commands”

Another way to think about “new commands” with mpc-hc64.exe is via command line parameters.

You can run MPC‑HC with extra options, such as:

mpc-hc64.exe "C:Videosmovie.mkv" /fullscreen /play /close 

Common switches (names and exact availability may vary slightly by version) include:

• /play – start playing immediately
• /fullscreen – start in fullscreen
• /close – close after playback finishes
• /dub "audiofile" – specify external audio (depending on version)
• /sub "subtitles.srt" – load external subtitles

By combining these, you can create a custom desktop shortcut or script that acts like a new command, for example:

• “Play this playlist fullscreen and close when done”
• “Launch MPC‑HC with a certain subtitle file pre‑loaded”
• “Start playback at a certain file path”

Example: Create a Desktop Shortcut as a “New Command”

1. Right‑click on your Desktop → New → Shortcut.

2. In the location box, enter something like:

   "C:Program FilesMPC-HCmpc-hc64.exe" "D:MediaPlaylist.m3u" /fullscreen /play 

3. Name the shortcut “Play My Playlist Fullscreen”.

4. Double‑clicking that shortcut is effectively a custom command you created.

You can make several such shortcuts, each with different command line options.

Extending MPC‑HC with External Tools and Scripts

To truly simulate a brand‑new command that does multiple things, you often need an external helper. Common approaches:

1. AutoHotkey or Similar Automation Tools

With tools like AutoHotkey on Windows, you can:

• Launch MPC‑HC with specific command line switches
• Send keystrokes to MPC‑HC after it opens
• Chain multiple actions (e.g., open a file, wait, change audio track, jump to timestamp)

A simple script might:

1. Start mpc-hc64.exe with a given file.
2. Wait a few seconds.
3. Send keystrokes to trigger subtitle or audio commands.
4. Optionally move/resize the window.

You then assign that script to its own hotkey. That script becomes your new composite command.

2. Batch Files or PowerShell Scripts

If you prefer not to install extra tools, you can:

• Create a .bat or .ps1 file that calls MPC‑HC with various arguments.
• Add any extra pre‑ or post‑processing you want (copying files, logging, etc.).

Example batch file:

@echo off "C:Program FilesMPC-HCmpc-hc64.exe" "D:Videoslesson.mp4" /fullscreen /play 

Running this is basically the same as a click‑to‑run command tailored to a specific task.

3. Media Front‑Ends or Launchers

Some users use front‑ends (like a media catalog or HTPC launcher) that:

• Organize their library
• Launch MPC‑HC via command line
• Pass arguments like file path, audio/subtitle preferences

In that setup, the “new command” is a combination of:

• A button or menu item in the front‑end
• The arguments it sends to mpc-hc64.exe

What Affects How Well Custom Commands Work?

How smoothly these “new commands” behave depends on several variables in your setup.

1. Operating System and Permissions

• Windows version (e.g., Windows 10 vs 11) can change:
  • Where MPC‑HC is installed
  • How shortcuts and scripts run
• User permissions:
  • If scripts require admin rights, they may prompt for confirmation
  • Folder permissions can affect which media files open without error

2. MPC‑HC Version and Build

Different MPC‑HC versions may:

• Support slightly different command line switches
• Have different default hotkeys
• Show options in slightly changed menus

Using old builds might limit what you can do with shortcuts or arguments.

3. Input Devices and Remote Controls

Your hardware affects how you “issue” commands:

• Standard keyboard and mouse:

  • Simple to configure key bindings
  • Mouse bindings depend on available buttons and scroll wheel actions

• Multimedia keyboards / IR remotes / game controllers:

  • May need driver software to convert button presses to keystrokes
  • Some remote software can send direct commands or simulated shortcuts

Not all devices map cleanly, and some may require extra configuration or third‑party tools.

4. Technical Comfort Level

Your own comfort with scripting or configuration decides how far you can go:

• If you’re comfortable editing config files or using scripts:

  • Complex, multi‑step “commands” are achievable
  • You can customize timing, window behavior, and more

• If you prefer to stay in the GUI:

  • You’ll likely focus on Options → Keys and desktop shortcuts
  • Less risk of breaking anything, but more limited automation

How Different Types of Users Approach “New Commands”

Because of those variables, there’s a wide spectrum of setups and approaches.

All of these are valid ways to “create new commands,” but they rely on quite different levels of effort and tools.

Where Your Own Setup Becomes the Missing Piece

The exact way you should “create a new command in mpc-hc64.exe” depends heavily on:

• Which version of Windows you’re using
• Which build of MPC‑HC you have installed
• Whether you rely on keyboard, mouse, remote, or some combination
• How comfortable you are with scripts, batch files, or tools like AutoHotkey
• Whether you’re trying to control a single PC, a dedicated HTPC, or a multi‑screen setup

Once you’re clear on those details, it becomes much easier to decide whether you just need a new in‑app shortcut, a custom desktop launcher, or a more advanced scripted command wrapped around mpc-hc64.exe.