MX Player No Sound On DTS Audio: Causes, Limitations, And Workarounds

If MX Player plays your video perfectly but goes silent the moment the soundtrack is labeled DTS, you are not alone. This problem usually is not a “bug” in the file. It is almost always a codec and licensing reality: many Android devices and many apps do not ship with DTS decoders, and MX Player may not be able (or allowed) to decode DTS in your specific setup. This guide breaks down what is happening, how to confirm it quickly, what is and is not possible, and the most reliable workarounds.

1. What “No Sound On DTS” Usually Means

DTS (Digital Theater Systems) is a family of audio codecs commonly found in Blu-ray rips, MKV files, and home-theater oriented releases (for example, “DTS”, “DTS-HD MA”, “DTS:X”). When MX Player shows no audio, the most common explanation is simple: MX Player cannot decode that DTS audio stream on your device using the decoders it has available.

To understand why, it helps to separate three different layers that all have to cooperate for audio to play:

• The media file (container like MKV, with one or more audio tracks inside).
• The player (MX Player) and which audio decoders it includes.
• The device/OS (Android audio framework and hardware decoders), which may or may not support DTS.

If the player cannot decode the audio in software, and the device does not provide a compatible decoder through the Android media stack, you can end up with video playback but no sound.

1.1 DTS vs. The MKV Container: Why The File “Looks Fine”

A frequent confusion is seeing “MKV” and assuming “MKV is the codec.” MKV is just a container. The actual audio codec may be DTS, AAC, AC-3, E-AC-3, FLAC, Opus, and more. MX Player can open the MKV container but still fail to decode the DTS track inside it.

Also, many files include multiple audio tracks (for example, DTS 5.1 in one language and AAC stereo in another). If MX Player defaults to a DTS track, you may think the entire file is broken when a playable track exists.

1.2 DTS Core vs. DTS-HD MA vs. DTS:X: Why Some DTS Fails More Often

DTS comes in variants. The “DTS Core” track (lossy) is the baseline stream and is more widely decodable than DTS-HD MA or DTS:X. However, even “Core” DTS decoding is not universally available on Android devices and is not guaranteed in every app.

• DTS (Core): baseline lossy stream; sometimes decodable, often not on stock Android.
• DTS-HD MA: lossless extension; commonly not supported in mobile decoders.
• DTS:X: object-based metadata; usually requires specific decoder support.

In practice, if your file is labeled DTS-HD MA or DTS:X, you should be prepared to convert the audio or use a player/device that explicitly supports passthrough or decoding.

2. The Real Causes: Licensing, OS Support, And Decoder Availability

“No sound on DTS” tends to happen for a few recurring reasons. Often, more than one applies at the same time.

2.1 DTS Is Not Guaranteed In Android’s Standard Media Stack

Android’s official media support focuses on common consumer formats such as AAC and (in many cases) AC-3/E-AC-3 depending on device and licensing. DTS decoding is not a universal, baseline feature across Android devices. Some manufacturers add it; many do not.

So if MX Player tries to use Android’s hardware decoding pipeline (or system codecs) and the device does not expose a DTS decoder, the result can be silence.

2.2 App-Level Licensing And Distribution Constraints

DTS is a proprietary codec family. Distributing DTS decoders in a consumer application can require licensing. Many media apps choose not to include certain proprietary decoders globally because licensing obligations can vary by region, store policies, and distribution channel.

This is why two different players on the same device can behave differently: one might include its own licensed decoder, another might rely on system decoders, and another might avoid DTS entirely.

2.3 MX Player Decoder Mode: HW, HW+, Or SW

MX Player commonly offers multiple decoding paths:

• HW: hardware decoding through the device codecs.
• HW+: a hardware-accelerated path with broader container handling in some scenarios.
• SW: software decoding (CPU-based), which depends on what MX Player includes or can load.

If DTS is not available in the selected path, you can get silent audio even while video plays. Switching between HW, HW+, and SW sometimes restores sound for certain audio formats, but it cannot create DTS support where none exists.

2.4 Passthrough Expectations: When You Need A Receiver

Some setups do not need the phone/tablet to decode DTS at all. Instead, the device can “pass through” the raw bitstream over HDMI to a receiver or soundbar that decodes DTS. If passthrough is not enabled, not supported by the connection (for example, many casting paths), or not supported by the endpoint device, you may get silence.

This is especially common when playing on a TV using cast or screen-mirroring methods that only support AAC stereo output.

3. Quick Diagnosis: Confirm It Is DTS And Identify Your Options

Before trying fixes, confirm what you are dealing with. Most wasted time comes from assuming the issue is “MX Player audio is broken” when it is really “this particular track is DTS and is not decodable on this device/path.”

3.1 Check The Active Audio Track And Switch Tracks

If the file has multiple audio tracks, switching is the fastest win.

• Open the audio track selector in MX Player.
• Look for an alternate track labeled AAC, MP3, FLAC, or Opus.
• Select it and test audio immediately.

If another track works, you have confirmed the core issue is DTS decode support, not a global volume, mute, or speaker issue.

3.2 Inspect The File With MediaInfo (Best For Certainty)

If you want certainty, use a tool like MediaInfo to read the exact audio codec and profile (for example, DTS-HD MA, number of channels, sampling rate). This is helpful because the most reliable workaround depends on whether the file is DTS Core versus DTS-HD MA.

3.3 Test Another Player To Separate “Device” From “App” Limitations

Install a second reputable player (for example, VLC) and test the same file:

• If VLC plays the audio but MX Player does not, the limitation is likely in MX Player’s decode path or configuration.
• If no app plays DTS audio, the device may lack any usable DTS decoder, or the particular DTS profile is unsupported.

This comparison quickly tells you whether you should focus on MX Player settings versus converting audio.

4. Workarounds That Actually Work (From Easiest To Most Reliable)

There is no single magic toggle that makes DTS universally play everywhere. The most dependable fixes fall into a few categories: use a different playable track, switch playback/decoder mode, use another player, use passthrough to a capable receiver, or convert the audio.

4.1 Switch MX Player Decoder Mode (HW, HW+, SW)

This is the first thing to try inside MX Player because it is quick and does not alter your file.

Start playback and open MX Player settings for the currently playing video.

Change the decoder from HW to HW+ or SW.

Re-test audio.

Why it helps sometimes: certain devices expose partial support through one decoder path but not another, or MX Player’s handling of the container plus audio may differ by mode.

Why it often does not help: if the device and the app do not have any DTS decoding capability, switching modes will not create one.

4.2 Use A Different Player That Includes DTS Support

Some players ship with broad software decoding support, which can play formats that many device codecs do not. VLC is a commonly recommended baseline test player because it includes many decoders and aims for wide format coverage.

• Pros: no file conversion required; usually quick.
• Cons: higher CPU usage; can reduce battery life on long playback; results vary by DTS profile and device performance.

If your priority is simply “play it now,” using an alternate player is often the fastest solution.

4.3 Convert DTS Audio To AAC (Most Compatible Fix)

If you want the file to play with sound everywhere (phones, tablets, TVs, browsers), converting the DTS track to AAC is the most broadly compatible approach.

A practical and quality-preserving approach is to keep the video stream untouched and only convert audio, then remux back into MKV or MP4.

• Best for compatibility: AAC-LC stereo (2.0) or AAC 5.1 if you need multichannel and your targets support it.
• Best for keeping surround: convert to AC-3 or E-AC-3 if your playback ecosystem supports it, but AAC is generally safer across mobile devices.

If you use FFmpeg, you can typically copy the video stream and convert only the audio stream. The exact command varies depending on your input and whether you want to keep multiple audio tracks. Always verify lip-sync and channel mapping after conversion.

4.4 Add A Secondary Compatible Audio Track Instead Of Replacing DTS

If you care about home theater playback later, you do not necessarily need to throw DTS away. A strong compromise is:

• Keep the original DTS track for receivers and systems that support it.
• Add an AAC stereo track for universal playback on phones and basic TVs.

This way, MX Player can switch to the AAC track on devices that cannot decode DTS, while your main theater setup can still use the DTS track.

4.5 Use HDMI Passthrough To A DTS-Capable Receiver (When Available)

If your goal is DTS playback on a sound system, passthrough can be the ideal solution because it avoids decoding on the phone/tablet entirely. The receiver does the DTS decoding.

However, passthrough depends on:

• The connection type (HDMI is typical; many casting methods do not support DTS bitstream).
• Whether Android and the device allow bitstream output in your setup.
• Whether your receiver/soundbar explicitly supports the DTS variant in your file.

If passthrough is not supported end-to-end, you might get silence or forced downmixing.

4.6 Re-Download Or Re-Rip With A More Compatible Audio Track

If you control the source (for example, your own disc backup), selecting a more compatible audio option during ripping can save time later. Many tools let you pick an AAC or AC-3 track, or transcode to AAC during the process.

If you do not control the source and the file has only DTS audio, conversion or a different player becomes the realistic path.

5. Limitations You Cannot “Fix” With Settings

It is useful to be clear about what is truly a limitation, not a configuration mistake. This helps you avoid endlessly toggling settings that cannot change the outcome.

5.1 If Your Device Has No DTS Decoder, The App Cannot Use Hardware DTS

Hardware decoding depends on what the device exposes. If the device does not include a DTS decoder (or does not expose it through Android’s codec APIs), MX Player cannot magically access it.

5.2 If The File Is DTS-HD MA Or DTS:X, Many Mobile Pipelines Will Not Decode It

Even when a device can handle certain DTS streams, advanced variants are more likely to fail. Some files include both a DTS Core and an HD extension; support varies by player and device. If you encounter DTS-HD MA silence, converting to AAC or using a player that can decode that variant in software is usually the practical answer.

5.3 Casting And Mirroring Often Break Surround Formats

Many casting pipelines prioritize compatibility and bandwidth. They may transcode audio, output only stereo, or reject unsupported bitstreams. So you might see this pattern:

• Local playback on the phone: silence (cannot decode DTS).
• Cast to TV: also silence (cast path does not accept DTS).
• Converted AAC version: works everywhere.

This is not MX Player being inconsistent; it is the end-to-end capabilities of the playback route.

6. A Practical Decision Tree (Pick The Best Fix Fast)

If you want a simple plan, use this decision tree to avoid trial-and-error.

6.1 If You Need A 30-Second Fix

• Switch to another audio track (AAC/MP3) if available.
• Switch decoder mode (HW to HW+ or SW).
• Try VLC for the same file.

6.2 If You Want It To Work On Every Device

• Convert DTS to AAC and remux while copying the video stream.
• Or add an AAC track while keeping DTS for home theater use.

6.3 If You Want True DTS On A Sound System

• Use HDMI passthrough to a DTS-capable receiver where supported.
• Use a playback device known for DTS support (some TVs, set-top boxes, or media players), rather than relying on a phone.

7. Common Questions About MX Player And DTS Audio

7.1 Why Does MX Player Play AC-3 But Not DTS?

Codec support differs by device, OS build, and player. Some environments have better support for Dolby-family formats than DTS, and some apps include decoders for one set of formats but not the other. Also, AC-3/E-AC-3 content is more common in streaming ecosystems, which can influence device support priorities.

7.2 Is My DTS File Corrupted If There Is No Sound?

Not necessarily. If another player on another platform (for example, a PC media player) plays the audio, the file is likely fine. Silence in MX Player typically indicates unsupported decoding in that playback context.

7.3 Does Renaming The File Or Changing The Container Fix DTS?

Changing MKV to MP4 (or renaming extensions) does not change the underlying audio codec. If the audio is DTS, it remains DTS. Container changes can help with compatibility in some cases, but they do not convert DTS into a playable codec.

7.4 Will “SW Decode” Always Fix It?

No. Software decoding only works if the player includes (or can load) a compatible decoder for that codec variant. If the app does not have DTS decoding capability, switching to SW will not help. Additionally, heavy DTS variants can be CPU-intensive on low-end devices.

7.5 What Audio Codec Should I Use For Maximum Compatibility?

For broad playback across phones, tablets, TVs, and browsers, AAC is usually the safest choice. If you need surround sound and your target devices support it, consider E-AC-3 or AC-3, but test in your real environment.

8. Summary: The Reliable Path Forward

MX Player “no sound on DTS” is usually a codec availability issue, not a mystery volume setting. DTS decoding is not guaranteed on Android, DTS variants differ in support, and casting routes frequently restrict audio formats. The most reliable workarounds are to switch to a non-DTS audio track, use a player with broader software decoding support, or convert (or add) an AAC track for universal compatibility. If your goal is full home-theater DTS, passthrough to a DTS-capable receiver can work when your device and connection support it.

Citations

• DTS Digital Surround and DTS audio technology overview. (DTS)
• Android media framework and codec architecture documentation (MediaCodec). (Android Developers)
• VLC features and format support (cross-platform decoder approach). (VideoLAN)
• MediaInfo tool for inspecting container tracks and codecs. (MediaArea)
• FFmpeg documentation (audio transcoding and remuxing concepts). (FFmpeg)