IR Remote not operating as it should on new App

[pgriffith 88]

Hi Softworkz

I have several original MS Media Center remotes and several clones of them (all RC6 standard) and they all perform as below.

The issue I have is the skip FWD 30 secs/ skip BACK 10 secs buttons work only ONCE per video. So if I skip FWD 30 secs, it will do that once, it won't do it again, and skip BACK will not work after skipping FWD once. If I stop that video and then play it again, I can choose to use either FWD or BACK again, but only once.

They are recognised consistently in the Remote Control section of the app as the correct FWD/BACK buttons.

The FWD and BACK functions seem have moved the to the left/right buttons on the 4 way pad (illustration in link below). These buttons are still recognised in the Emby Remote Control section as Directional Navigation buttons.

I reported this back in July to Luke on Emby Theater as one day it just stopped functioning like it used to.

See this post 

 

The mapping of all the buttons on all my PC's using IR remotes are all standard, I have only changed the mapping for one button on each machine to open the Windows Start Menu. This allows me to Start Emby and stop/start Chrome running Youtube in its old Leanback/TV mode from the Start Menu without ever needing a mouse or keyboard. So for example, on my main lounge PC, I have remapped the DVD Menu button on the remote to CTRL ESC which of course is the keyboard shortcut for the Start Menu, ALL other buttons have their mappings unchanged and are as Microsoft designed them to be.

[softworkz 5066]

As a matter of fact, proper remote control button interaction can only be found in the WMC UI apps (at the time of writing).

The Windows app itself is only in charge of detecting button presses via OS API and the test UI under settings. Then it forwards those events to the inner application, which hits the same implementation like before.

Hence I can only defer this to @Luketo comment on.

[frankmb 41]

Is there any update on remote control support for Windows Emby app? The announcement for the new app outlines "Enhanced Support for Remote Control and Gamepad Input (Windows & Xbox)". I thought it meant I would be able to buy a new remote control for Windows supported by Emby. Are there new Windows Media Centre remotes being sold? Windows Media Centre itself was discontinued a decade ago now I think.

[pgriffith 88]

You can still find them on Ebay

For example, here's 2 I found in 30 seconds on Ebay, both with receivers.

https://www.ebay.com.au/itm/305507424793?mkcid=16&mkevt=1&mkrid=705-154756-20017-0&ssspo=KnoC8s00SHG&sssrc=2047675&ssuid=uXOEsjaYTXa&widget_ver=artemis&media=COPY

https://www.ebay.com.au/itm/261913475420?mkcid=16&mkevt=1&mkrid=705-154756-20017-0&ssspo=OgLHCfPCRYK&sssrc=2047675&ssuid=uXOEsjaYTXa&widget_ver=artemis&media=COPY

RC6 is the IR protocol that's used.

The IR receivers seem to be harder to get, but once you have one you can pretty much use any RC6 remote with it.

[softworkz 5066]

Essentially (almost) ALL IR remotes which are indicating support for Windows are working.

Here's a list of supported receivers:

    { vendorId: 0x045E, productId: 0x006D }, // Microsoft SB
    { vendorId: 0x045E, productId: 0x00A0 }, //Microsoft BB
    { vendorId: 0x045E, productId: 0x00DA }, //Microsoft SF
    { vendorId: 0x107B, productId: 0x3009 }, //Gateway BB
    { vendorId: 0x1509, productId: 0x9242 }, //FIC BB
    { vendorId: 0x03EE, productId: 0x2501 }, //Mitsumi BB
    { vendorId: 0x0471, productId: 0x0815 }, //Philips BB
    { vendorId: 0x0609, productId: 0x031D }, //SMK BB
    { vendorId: 0x2040, productId: 0x6310 }, //Hauppauge BB
    { vendorId: 0x1009, productId: 0x000E }, //eMuzed BB
    { vendorId: 0x1019, productId: 0x0F38 }, //ECS BB
    { vendorId: 0x03F3, productId: 0x0094 }, //Adaptec BB
    { vendorId: 0x0FB8, productId: 0x0002 }, //Wistron BB
    { vendorId: 0x04E8, productId: 0x7061 }, //Samsung BB
    { vendorId: 0x1460, productId: 0x9150 }, //Tatung BB
    { vendorId: 0x03EE, productId: 0x2502 }, //Mitsumi SF
    { vendorId: 0x0609, productId: 0x0322 }, //SMK SF
    { vendorId: 0x1308, productId: 0xC001 }, //Shuttle BB
    { vendorId: 0x0768, productId: 0x0023 }, //Ricavision BB
    { vendorId: 0x0471, productId: 0x0608 }, //Philips SF
    { vendorId: 0x043E, productId: 0x9803 }, //LG BB
    { vendorId: 0x179D, productId: 0x0010 }, //Ricavision BB
    { vendorId: 0x179D, productId: 0x0020 }, //Ricavision SF
    { vendorId: 0x1784, productId: 0x0001 }, //Topseed BB
    { vendorId: 0x1784, productId: 0x0002 }, //Topseed SF
    { vendorId: 0x17B8, productId: 0x1100 }, //Trojan SF
    { vendorId: 0x17B8, productId: 0x044C }, //Trojan SF
    { vendorId: 0x17B8, productId: 0x04B0 }, //Trojan BB
    { vendorId: 0x15B1, productId: 0x8090 }, //Mitac SF
    { vendorId: 0x147A, productId: 0xE015 }, //Formosa21 BB
    { vendorId: 0x147A, productId: 0xE016 }, //Formosa21 SF
    { vendorId: 0x051C, productId: 0xC001 }, //Shuttle BB
    { vendorId: 0x051C, productId: 0xC002 }, //Shuttle SF
    { vendorId: 0x0C16, productId: 0x0081 }, //Gyration BB
    { vendorId: 0x0C16, productId: 0x0080 }, //Gyration SF
    { vendorId: 0x413C, productId: 0x8123 }, //Dell BB
    { vendorId: 0x413C, productId: 0x8124 }, //Dell SF
    { vendorId: 0x0409, productId: 0x0066 }, //V1 Emulator
    { vendorId: 0x0471, productId: 0x060C }, //V1 Emulator
    { vendorId: 0x0471, productId: 0x060D }, //V1 Emulator
    { vendorId: 0x0471, productId: 0x060F }, //V1 Emulator
    { vendorId: 0x04B4, productId: 0x4C67 }, //V1 Emulator
    { vendorId: 0x04EB, productId: 0xE002 }, //NorthStar Systems Corp. Emulator
    { vendorId: 0x04EB, productId: 0xE004 }, //Northstar Systems Corp. Emulator
    { vendorId: 0x0609, productId: 0x0334 }, //SMK RXX6000-0101F
    { vendorId: 0x0609, productId: 0x0338 }, //SMK RXX6000-0201F
    { vendorId: 0x0A48, productId: 0x3282 }, //V1 Emulator
    { vendorId: 0x0BDA, productId: 0x0161 }, //V1 Emulator
    { vendorId: 0x0BDA, productId: 0x0168 }, //V1 Emulator
    { vendorId: 0x147A, productId: 0xE017 }, //F21 snowflake emulator
    { vendorId: 0x147A, productId: 0xE018 }, //V1 Emulator
    { vendorId: 0x147A, productId: 0xE034 }, //V1 Emulator
    { vendorId: 0x147A, productId: 0xE037 }, //V1 Emulator
    { vendorId: 0x147A, productId: 0xE03A }, //V1 Emulator
    { vendorId: 0x147A, productId: 0xE03C }, //V1 Emulator
    { vendorId: 0x1784, productId: 0x0008 }, //V1 Emulator
    { vendorId: 0x1784, productId: 0x0006 }, //V1 Emulator
    { vendorId: 0x1934, productId: 0x0602 }, //V1 Emulator
    { vendorId: 0x1934, productId: 0x0702 }, //V1 Emulator
    { vendorId: 0x1B64, productId: 0x0138 }  //V1 Emulator

 

And those are just the OEMs which are producing the bare hardware - so when you don't see a manufacturer in this list it means nothing.
For example, Philips has never sold any IR remote, they are just manufacturing the received chipset and but many remotes (receivers) are using it.

You can hardly make a wrong choice.

[frankmb 41]

Thanks but this list does not help me much....

What remotes are compatible with Emby on Windows?

Is it only remotes made for Windows Media Center that I would need to buy used?

Are there other remotes than the ones that were made for Windows Media Center?

Are there any brand new remotes that will work?

 

I did see that there are new remotes for the XBOX Series X that look similar to the old Windows Media Center remotes but I assume those would not work for Emby on Windows. 

Edited January 10, 2025 by frankmb

[softworkz 5066]

11 hours ago, softworkz said:

Essentially (almost) ALL IR remotes which are indicating support for Windows are working.

11 hours ago, softworkz said:

You can hardly make a wrong choice.

I've written "almost" because I have a USB TV receiver which comes with a remote, but it interfaces with the USB receiver rather than Windows.

Opposed to Linux (where this is a mess) - the functionality that you can control is pretty clearly defined. There's no point for any manufacturer in producing a remote which cannot interact with Windows as it is required - unless it's a special case in combination with other hardware were the remote controls that hardware instead of interfacing with Windows.

[frankmb 41]

I am trying to finding a new infrared remote that would work but I'm having a lot of difficulty.

All I am finding for Windows is 2.4g remotes like this 

WeChip W1 Remote 2.4G Wireless Keyboard Multifunctional Remote Control for Nvidia Shield/Android TV Box/PC/Projector/HTPC/All-in-one PC https://a.co/d/1B1YexT

 

Would it work? 

 

Can you point me to one or two new options available to buy that include the remote and USB receiver?

[pgriffith 88]

I already sent you a link for 2 units that are brand new, here's another.

https://www.ebay.com.au/itm/375456567089?mkcid=16&mkevt=1&mkrid=705-154756-20017-0&ssspo=vwrrgf4ytlu&sssrc=2047675&ssuid=uXOEsjaYTXa&widget_ver=artemis&media=COPY

 

[frankmb 41]

Thanks. I didn't realize they were new old stock.

Anyways from what I can tell all these media centre IR remotes have been out of production for a long time.

I just dug out of storage the FLIRC I bought in 2015. I'm going to try to get something working with that.