Home Cinema Control (HCC): Emby library UI with OPPO/Chinoppo local playback

[tousled 3]

Hi everyone,

I’m opening a new thread because I didn’t want to hijack older OPPO/Xnoppo-related discussions.

I’ve been working on a project called Home Cinema Control (HCC).

The idea is simple:

Use Emby as the library and browsing interface, but let an OPPO / Chinoppo player handle the actual playback locally through SMB/NFS path mapping.

So instead of trying to make Emby transcode or stream content to a device that may not handle certain formats properly through DLNA/client playback, HCC acts as a bridge:

Emby library → HCC → SMB/NFS path mapping → OPPO/Chinoppo local playback

The project is inspired by the same kind of workflow that Xnoppo made useful for OPPO/Chinoppo users, but the goal is to make it more modern, maintained, Docker-friendly and easier to configure through a web UI.

Current focus:

• Emby integration.

• OPPO / Chinoppo playback target.

• SMB/NFS path mapping.

• Docker deployment.

• Web configuration UI.

• Playback reporting back to Emby where possible.

• Clear logs and diagnostics.

• LG webOS TV control at the moment.

Also supported:

• Better configuration for libraries, path mappings and monitored devices.

Planned / under consideration:

• Sony / Philips / Android TV / Google TV support.

• Home Assistant integration.

• Philips Hue / Ambilight cinema scenes.

• Kodi / Zidoo / Dune playback targets if there is enough interest.

The main use case is not to replace Emby. Quite the opposite: HCC assumes Emby remains the main library UI. The goal is to keep the comfort of browsing in Emby while using dedicated local playback hardware for users who care about:

• UHD remuxes.

• ISO / BDMV / folder-based libraries.

• Dolby Vision / HDR.

• Atmos / DTS:X / HD audio.

• NAS-based storage.

• OPPO 203/205 clones such as M9702 / M9201 / M9203 / M9205.

• Avoiding unnecessary transcoding.

• Keeping a family-friendly library interface without giving up playback quality.

GitHub: https://github.com/tousled/home-cinema-control

Current release / setup instructions: https://github.com/tousled/home-cinema-control/releases/tag/1.1.2

I’d really appreciate feedback from Emby users, especially anyone who:

• Uses or used Xnoppo.

• Has an OPPO / Chinoppo player.

• Stores movies on a NAS/Remotely through SMB or NFS.

• Has trouble with ISO / BDMV / full-disc playback.

• Wants Emby as the browsing interface but prefers external/local playback.

• Runs Emby in Docker, Unraid, Synology, QNAP, ASUSTOR or similar.

Thanks in advance for any feedback, criticism, compatibility reports or suggestions.

[Luke 43375]

Thanks for sharing.

[tousled 3]

Thank you! I hope that anyone who’s had problems with Xnoppo will be able to enjoy their home cinema with this new app

[tousled 3]

 

Hi everyone

Home Cinema Control 1.2.1 is now available.

The main addition in this release is support for Sony Bravia TVs, expanding HCC’s existing TV and home cinema device integrations.

This version also includes several fixes and internal improvements to make configuration and general operation smoother.

The new version is available on GitHub and Docker Hub.

GitHub Release
Docker Hub

As always, any testing, feedback or bug reports would be greatly appreciated

[borry73 0]

Hi, thnx for this great program.

I`ve tested xnoppo in the past but it didn`t work flawless for me.

I`ve got emby runnning on a homebuild server with openmediavault, a LG OLED 65G6, marantz nr1711  and a chinoppo (sold my oppo 203  ) and sofar it works perfectly.

Only little thing i could find is that the chinoppo needs to be turned on before i use Emby, home cinema control doesn`t activate the player.

[tousled 3]

Hello! Thank you very much for using it, and I’m glad it’s working well for you! Yes, that’s something I tried to do at the time – to make the Chinoppo turn on by itself without you having to use the remote control – but it was something I didn’t manage to do, because it didn’t respond to any API commands. Or, at least, I couldn’t find one

[tousled 3]

Home Cinema Control 1.4.0 released — Home Assistant integration

HCC 1.4.0 is now available.

The main addition is a new Home Assistant integration. HCC can publish playback lifecycle events when an intercepted Emby playback starts, pauses, resumes or stops, allowing Home Assistant to react without coupling home automation directly to the Emby/OPPO playback implementation.

Typical uses would be cinema-room lighting, scene restoration or other local automations around a movie session.

Home Assistant delivery is asynchronous and isolated from the playback-critical path, so webhook failures or a temporarily unavailable HA instance cannot prevent the Emby → HCC → OPPO handoff from working.

1.4.0 also adds background update notifications through Home Assistant and supported TV integrations, plus optional anonymous startup timing telemetry to help measure playback-start performance on different installations.

There has also been a substantial internal cleanup around provider boundaries and playback lifecycle handling. Emby-specific payload interpretation now remains in the Emby adapter while the common playback layer deals with shared behaviour.

For anyone who missed the very recent 1.3.2/1.3.3 updates, 1.4.0 also includes the Windows path-mapping correction and the fix for direct playback of .strm-backed Emby items.

Release:
https://github.com/tousled/home-cinema-control/releases/tag/1.4.0

Project:
https://github.com/tousled/home-cinema-control

Feedback from different Emby installations is very welcome.

[Eigeplackter 116]

I just pulled the image and opened up webpage, but even though there‘s an english install guide, I can‘t cope with an only spanish Interface.

Will there be an option to change UI language any time soon ?

[tousled 3]

52 minutes ago, Eigeplackter said:

I just pulled the image and opened up webpage, but even though there‘s an english install guide, I can‘t cope with an only spanish Interface.

Will there be an option to change UI language any time soon ?

Hi! Thanks for contacting me. There's already a button. It's in the lower-left corner, as shown in the image below: