Importing Foreign IR Remotes in RemoteMaster - Revision history

The Robman at 00:06, 23 November 2025

2025-11-23T00:06:20Z

The Robman: 15 revisions imported

2025-11-02T18:52:45Z

15 revisions imported

← Older revision	Revision as of 18:52, 2 November 2025
(No difference)

Barf: /* Example */

2022-05-15T10:05:13Z

Example

← Older revision		Revision as of 10:05, 15 May 2022
Line 39:		Line 39:
	We consider the Oppo BDP 103 BluRay player, which has a [http://download.oppodigital.com/BDP103/BDP-103_BDP-105_Remote_Code_v1.1.xls published set of IR commands].		We consider the Oppo BDP 103 BluRay player, which has a [http://download.oppodigital.com/BDP103/BDP-103_BDP-105_Remote_Code_v1.1.xls published set of IR commands].
	(The [http://www.hifi-remote.com/wiki/index.php?title=IrScrutinizer_Guide#Importing_.22text.22_files IrScrutinizer Tutorial]		(The [http://www.hifi-remote.com/wiki/index.php?title=IrScrutinizer_Guide#Importing_.22text.22_files IrScrutinizer Tutorial]
	describes how such files can be imported into IrScrutinizer.) Here we show the import from a csv file:		describes how such files can be imported into IrScrutinizer.) We have downloaded the Excel file and saved it as a csv (comma separated values) file. Here we show the import from that csv file:

	[[Image:Screenshot%20from%202022-05-14%2022-16-25.png]]		[[Image:Screenshot%20from%202022-05-14%2022-16-25.png]]

	We now assume that this command set has been imported in IrScrutinizer, see the screenshot below.		We now assume that this command set has been imported as parametrized in IrScrutinizer, see the screenshot below.
	~~Note that every~~ row denotes a command, has a name, a protocol, and one or more parameters. A comment may describe the command further.		Every row of the table denotes a command, has a (unique) name, a protocol, and one or more parameters. A comment may describe the command further.


Line 53:		Line 53:
	Here, the protocol is "NEC1", D = 73, and S is "nonexistent".		Here, the protocol is "NEC1", D = 73, and S is "nonexistent".
	Having inspected this table, and made		Having inspected this table, and made
	any desirable changes, the table is exported,		any desirable changes, the table is exported, by selecting the "Export" pane, selecting "Girr" as the Export format, checking "Parameters" and pressing "Export param. remote".

	~~This is exported~~ by selecting the "Export" pane, selecting "Girr" as the Export format, checking "Parameters" and pressing "Export param. remote".
	This creates a girr file.		This creates a girr file.

Barf: /* Solution */

2022-05-15T10:00:36Z

Solution

← Older revision		Revision as of 10:00, 15 May 2022
Line 28:		Line 28:
	= Solution =		= Solution =

	The [http://www.harctoolbox.org/Girr.html Girr format for IR signals] is an open and very versatile format for collections of IR signals. These can be parametrized, or in raw format. It is an XML based format.		The [http://www.harctoolbox.org/Girr.html Girr format for IR signals] is an open and very versatile format for collections of IR signals. These can be parametrized, or in raw format. It is an XML based format. It is the native format of [http://www.hifi-remote.com/wiki/index.php/IrScrutinizer_Guide IrScrutinizer].

	First, acquire or generate a suitable Girr file. ~~[IrScrutinizer_Guide~~ IrScrutinizer] can generate such files, either by (using a suitable hardware receiver) "learning" an available physical remote, or by importing/converting from other format. (See the example below).		First, acquire or generate a suitable Girr file. IrScrutinizer can generate such files, either by (using a suitable hardware receiver) "learning" an available physical remote, or by importing/converting from other format. (See the example below).

	This file is then imported into RMDU, by "Open"-ing them. (See pictures in the next section). If the Girr file contains more than one remote, the ~~useer is required~~ to select one of them. In rare cases, the user is requested to select between several possible alternative executors. Although the import almost always succeeds, in rare cases it may fail~~. The~~ import should be checked for plausibility. Assign the keys to functions, and make other desired fixes. The thus created device update can now be used as any other update.		This file is then imported into RMDU, by "Open"-ing them. (See pictures in the next section). If the Girr file contains more than one remote, RM inquires the user to select one of them. In rare cases, the user is requested to select between several possible alternative executors. Although the import almost always succeeds, in rare cases it may fail, so the import should be checked for plausibility. Assign the keys to functions, and make other desired fixes. The thus created device update can now be used as any other update.

	Importing remotes is still a quite complicated process. Limitations (for example by "uncommon" protocols, or if signals from several substantially different protocols are present), and in rare cases even bugs, may show up. In this case, please report in the forum.		Importing remotes is still a quite complicated process. Limitations (for example by "uncommon" protocols, or if signals from several substantially different protocols are present), and in rare cases even bugs, may show up. In this case, please report in the forum.

Barf: /* Importing Foreign IR Remotes in RemoteMaster */

2022-05-15T09:47:42Z

Importing Foreign IR Remotes in RemoteMaster

← Older revision		Revision as of 09:47, 15 May 2022
Line 1:		Line 1:
	~~= Importing Foreign IR Remotes in RemoteMaster =~~

	~~''This guide will take the reader through a method for importing foreign (i.e. non-JP1) IR remotes into RemoteMaster.''~~
	''The procedure requires some knowledge by the user, who have to make some manual decisions. The guide is not aimed at beginning users. Some prior knowledge about RemoteMaster and IrScrutinizer is assumed. Also, importing raw or unknown codes are not covered.''

	= Ultra-short version =		= Ultra-short version =

Barf: /* Ultra-short version */

2022-05-14T20:43:32Z

Ultra-short version

← Older revision		Revision as of 20:43, 14 May 2022
Line 6:		Line 6:
	= Ultra-short version =		= Ultra-short version =

	* Perform an "~~RemoteMaster~~" export from IrScrutinizer ~~1.3 (or later)~~ to a ~~temporary~~ file,		* Perform an "Girr" export from IrScrutinizer to a file,
	* Open the above created file in RemoteMaster~~. Select a usable executor manually~~. Perform ~~other~~ desired fixes.		* Open the above created file in RemoteMaster. Perform desired fixes.

	= History =		= History =

Barf: /* Support and help */

2022-05-14T20:40:00Z

Support and help

← Older revision		Revision as of 20:40, 14 May 2022
Line 82:		Line 82:
	file to a suitable name, etc.		file to a suitable name, etc.
	This is outside of the scope of this article, and described in detail the RM documentation.		This is outside of the scope of this article, and described in detail the RM documentation.

			= Remarks =

			== Import ict files from IrScope ==

			RMDU can also import ("open") ict files from the program [http://www.hifi-remote.com/wiki/index.php/IR_Scope_and_IR_Widget_User%27s_Guide IrScope].

	= Support and help =		= Support and help =

Barf: /* Example */

2022-05-14T20:26:29Z

Example

← Older revision		Revision as of 20:26, 14 May 2022
Line 62:		Line 62:
	This is exported by selecting the "Export" pane, selecting "Girr" as the Export format, checking "Parameters" and pressing "Export param. remote".		This is exported by selecting the "Export" pane, selecting "Girr" as the Export format, checking "Parameters" and pressing "Export param. remote".
	This creates a girr file.		This creates a girr file.

			[[Image:Screenshot%20from%202022-05-14%2021-15-25.png]]

	After starting RMDU, the just-created simple girr file is imported through File -> Open.		After starting RMDU, the just-created simple girr file is imported through File -> Open.

Barf: /* Solution */

2022-05-14T20:22:19Z

Solution

← Older revision		Revision as of 20:22, 14 May 2022
Line 38:		Line 38:

	This file is then imported into RMDU, by "Open"-ing them. (See pictures in the next section). If the Girr file contains more than one remote, the useer is required to select one of them. In rare cases, the user is requested to select between several possible alternative executors. Although the import almost always succeeds, in rare cases it may fail. The import should be checked for plausibility. Assign the keys to functions, and make other desired fixes. The thus created device update can now be used as any other update.		This file is then imported into RMDU, by "Open"-ing them. (See pictures in the next section). If the Girr file contains more than one remote, the useer is required to select one of them. In rare cases, the user is requested to select between several possible alternative executors. Although the import almost always succeeds, in rare cases it may fail. The import should be checked for plausibility. Assign the keys to functions, and make other desired fixes. The thus created device update can now be used as any other update.

	~~== Remark ==~~

	Importing remotes is still a quite complicated process. Limitations (for example by "uncommon" protocols, or if signals from several substantially different protocols are present), and in rare cases even bugs, may show up. In this case, please report in the forum.		Importing remotes is still a quite complicated process. Limitations (for example by "uncommon" protocols, or if signals from several substantially different protocols are present), and in rare cases even bugs, may show up. In this case, please report in the forum.

Barf: /* Preparation */

2022-05-14T20:21:51Z

Preparation

@@ Line 30: / Line 30: @@
 This is a very tedious and error prone approach.
 Importing these in a systematic way, with minimal interaction, is the topic of the current article.
 = Solution =

← Older revision		Revision as of 00:06, 23 November 2025
Line 7:		Line 7:

	The previous version of this article described a faily "dumb" method of exporting a Girr file from IrScrutinizer to a stripped-down RemoteMaster rmdu file, using a effectively empty, dummy executor called "ImportOnly". This is imported in RemoteMaster, after which the user has to chose the executor manually.		The previous version of this article described a faily "dumb" method of exporting a Girr file from IrScrutinizer to a stripped-down RemoteMaster rmdu file, using a effectively empty, dummy executor called "ImportOnly". This is imported in RemoteMaster, after which the user has to chose the executor manually.
	The previous version can be access through the Wiki history function, or directly [~~http~~://www.hifi-remote.com/wiki/index.php?title=Importing_Foreign_IR_Remotes_in_RemoteMaster&oldid=880 here].		The previous version can be access through the Wiki history function, or directly [https://www.hifi-remote.com/wiki/index.php?title=Importing_Foreign_IR_Remotes_in_RemoteMaster&oldid=880 here].

	Since then, amazing work has been done in RemoteMaster on importing foreign IR signals, or more exactly, mapping the foreign protocols on the JP1's executors. Accordingly, Girr files can be imported directly, which makes the importing procedure almost automatic.		Since then, amazing work has been done in RemoteMaster on importing foreign IR signals, or more exactly, mapping the foreign protocols on the JP1's executors. Accordingly, Girr files can be imported directly, which makes the importing procedure almost automatic.
Line 16:		Line 16:
	For usage with RemoteMaster ("RM"), this information is in general not directly usable.		For usage with RemoteMaster ("RM"), this information is in general not directly usable.
	Often, usable RM device update files ("rmdu") can be found in the		Often, usable RM device update files ("rmdu") can be found in the
	[~~http~~://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 JP1 device update repository] (see also		[https://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 JP1 device update repository] (see also
	[~~http~~://www.hifi-remote.com/forums/dload.php?action=file&file_id=8487 the master list] and		[https://www.hifi-remote.com/forums/dload.php?action=file&file_id=8487 the master list] and
	[http://www.getzweb.net/jp1/ the lookup tool]).		[http://www.getzweb.net/jp1/ the lookup tool]).
	But still some cases remain; in particular self captured ("learned") remotes.		But still some cases remain; in particular self captured ("learned") remotes.
Line 28:		Line 28:
	= Solution =		= Solution =

	The [http://www.harctoolbox.org/Girr.html Girr format for IR signals] is an open and very versatile format for collections of IR signals. These can be parametrized, or in raw format. It is an XML based format. It is the native format of [~~http~~://www.hifi-remote.com/wiki/index.php/IrScrutinizer_Guide IrScrutinizer].		The [http://www.harctoolbox.org/Girr.html Girr format for IR signals] is an open and very versatile format for collections of IR signals. These can be parametrized, or in raw format. It is an XML based format. It is the native format of [https://www.hifi-remote.com/wiki/index.php/IrScrutinizer_Guide IrScrutinizer].

	First, acquire or generate a suitable Girr file. IrScrutinizer can generate such files, either by (using a suitable hardware receiver) "learning" an available physical remote, or by importing/converting from other format. (See the example below).		First, acquire or generate a suitable Girr file. IrScrutinizer can generate such files, either by (using a suitable hardware receiver) "learning" an available physical remote, or by importing/converting from other format. (See the example below).
Line 38:		Line 38:
	= Example =		= Example =
	We consider the Oppo BDP 103 BluRay player, which has a [http://download.oppodigital.com/BDP103/BDP-103_BDP-105_Remote_Code_v1.1.xls published set of IR commands].		We consider the Oppo BDP 103 BluRay player, which has a [http://download.oppodigital.com/BDP103/BDP-103_BDP-105_Remote_Code_v1.1.xls published set of IR commands].
	(The [~~http~~://www.hifi-remote.com/wiki/index.php?title=IrScrutinizer_Guide#Importing_.22text.22_files IrScrutinizer Tutorial]		(The [https://www.hifi-remote.com/wiki/index.php?title=IrScrutinizer_Guide#Importing_.22text.22_files IrScrutinizer Tutorial]
	describes how such files can be imported into IrScrutinizer.) We have downloaded the Excel file and saved it as a csv (comma separated values) file. Here we show the import from that csv file:		describes how such files can be imported into IrScrutinizer.) We have downloaded the Excel file and saved it as a csv (comma separated values) file. Here we show the import from that csv file:

Line 80:		Line 80:
	== Import ict files from IrScope ==		== Import ict files from IrScope ==

	RMDU can also import ("open") ict files from the program [~~http~~://www.hifi-remote.com/wiki/index.php/IR_Scope_and_IR_Widget_User%27s_Guide IrScope].		RMDU can also import ("open") ict files from the program [https://www.hifi-remote.com/wiki/index.php/IR_Scope_and_IR_Widget_User%27s_Guide IrScope].

	= Support and help =		= Support and help =