Video - Revision history

Acald: Update video link to point to youtube instance of video instead of the defunct video.google.com

2013-05-12T03:27:28Z

Update video link to point to youtube instance of video instead of the defunct video.google.com

←Older revision		Revision as of 03:27, 12 May 2013
Line 5:		Line 5:
	\|}		\|}

	Watch ~~one of the two~~ demo ~~videos~~ instantly on ~~Google video~~:		Watch a demo video instantly on YouTube:

	:*[http://~~video~~.~~google~~.com/~~videoplay~~?~~docid=2176025602905109829&hl~~=en LinuxMCE 7.04 video]		:*[http://www.youtube.com/watch?v=G7JDX2R_uDc LinuxMCE 7.04 video]
	~~:*[http://video.google.com/videoplay?docid=-4422887272477313460&q=linuxmce&ei=iQUrSPfRKaTeqwP4k7SgCQ&hl=en An older LinuxMCE demo and comparison to Windows MCE~~]

	You can also download the video from the [[Mirrors]].		You can also download the video from the [[Mirrors]].

Mcefan at 04:28, 9 October 2012

2012-10-09T04:28:52Z

←Older revision		Revision as of 04:28, 9 October 2012
Line 1:		Line 1:
	[[Category: Documentation]]		[[Category:Documentation]]
	[[Category: ~~Installation_Tutorials~~]]		[[Category:Tutorials]]
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__

Twodogs at 14:17, 15 November 2011

2011-11-15T14:17:34Z

←Older revision		Revision as of 14:17, 15 November 2011
Line 1:		Line 1:
	[[Category: Documentation]]		[[Category: Documentation]]
			[[Category: Installation_Tutorials]]
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__

Coley: Undo revision 25015 by Jlhoyd05 (Talk)

2010-09-13T13:04:49Z

Undo revision 25015 by Jlhoyd05 (Talk)

←Older revision		Revision as of 13:04, 13 September 2010
Line 155:		Line 155:
	I used the same USB UIRT to control the TV in the bedroom. Note that because my TV does not support discrete codes, it is a nightmare to use with any universal remote control or any type of smarthome system. The better TV's, like Sony's, recognize discrete codes. This means that although the original remote control may only have 1 button to toggle the power on and off, the TV actually does recognize 3 separate i/r codes: The toggle power that's on the remote, as well as an explicit/discrete 'turn power on' and a discrete 'turn power off'. They just don't put all 3 buttons on the original remote to save space, but the TV does recognize them. Sites like remotecentral.com let you find discrete codes. Then LinuxMCE can control your TV reliably. When it's time to turn it on, the i/r transmitter sends the 'power on' button, and even if the TV is already on, it still stays on. The TV I used doesn't have discrete codes. It only recognizes the 1 button 'toggle power'. So LinuxMCE may think the TV is off, and send the 'toggle power' command to turn it on, when in fact the TV was already on and LinuxMCE inadvertently turned it off. Toggle codes are a nightmare for anybody that has ever tried to use any sort of universal remote, like a Logitech/Harmony because the remote never really knows what state the TV is in. Also, since infrared codes are inherently unreliable and don't always get through, if your TV supports discrete codes, like the Sony's do, LinuxMCE can just send the 'ON' 3 times to be 100% sure the TV got the command and goes on. But with toggle devices like the one I have it can't do that since sending the command 3 times would just turn it on, then off, then back on again. My TV has the same problem with inputs. It only recognizes a single 'toggle input' which just cycles through inputs. LinuxMCE remember what was the last input the TV was on, and how many times it needs to toggle to get to the next input. But this is very unreliable. Sometimes when the TV doesn't get a signal while hitting input select it 'freezes' for a couple seconds, and then LinuxMCE will get out of step, thinking it's on, say input 5, when it's really only on input 4. Again the better TV's, like Sony's, have discrete codes or buttons for each input. So LinuxMCE can just send the button 'input 4' and can re-transmit it 3 times to be sure it gets through, and not worry about trying to toggle. If you do have a toggle device like mine, and LinuxMCE ever gets out of sync, you can press and hold the red, green, yellow and blue buttons to get it back in sync. Holding the red button causes LinuxMCE to retransmit the 'power' command so if the TV went off instead of ON, it goes back ON. The green button retransmits the 'input select' button. The yellow retransmits the 'power on' to the receiver, and the blue retransmits the 'input select' to the receiver. Bottom line: if possible get TV's and Receivers with discrete codes and avoid TOAD's (toggle only analog devices). Nearly all the decent receivers actually do have discrete codes, so one possible solution at least to the input select problem with toggle-only TV's is to hook all the video sources to the receiver and let it do the switching, and leave the TV on 1 input. LinuxMCE automatically will setup your A/V gear like this. In the setup wizard it asks if you're using a receiver, and if you connected the video cable to it, and makes all the correct settings. You can view a graphical diagram of your a/v gear's connections in the admin site under Wizard, Devices, A/V Equipment, and click on the Connection Wizard.		I used the same USB UIRT to control the TV in the bedroom. Note that because my TV does not support discrete codes, it is a nightmare to use with any universal remote control or any type of smarthome system. The better TV's, like Sony's, recognize discrete codes. This means that although the original remote control may only have 1 button to toggle the power on and off, the TV actually does recognize 3 separate i/r codes: The toggle power that's on the remote, as well as an explicit/discrete 'turn power on' and a discrete 'turn power off'. They just don't put all 3 buttons on the original remote to save space, but the TV does recognize them. Sites like remotecentral.com let you find discrete codes. Then LinuxMCE can control your TV reliably. When it's time to turn it on, the i/r transmitter sends the 'power on' button, and even if the TV is already on, it still stays on. The TV I used doesn't have discrete codes. It only recognizes the 1 button 'toggle power'. So LinuxMCE may think the TV is off, and send the 'toggle power' command to turn it on, when in fact the TV was already on and LinuxMCE inadvertently turned it off. Toggle codes are a nightmare for anybody that has ever tried to use any sort of universal remote, like a Logitech/Harmony because the remote never really knows what state the TV is in. Also, since infrared codes are inherently unreliable and don't always get through, if your TV supports discrete codes, like the Sony's do, LinuxMCE can just send the 'ON' 3 times to be 100% sure the TV got the command and goes on. But with toggle devices like the one I have it can't do that since sending the command 3 times would just turn it on, then off, then back on again. My TV has the same problem with inputs. It only recognizes a single 'toggle input' which just cycles through inputs. LinuxMCE remember what was the last input the TV was on, and how many times it needs to toggle to get to the next input. But this is very unreliable. Sometimes when the TV doesn't get a signal while hitting input select it 'freezes' for a couple seconds, and then LinuxMCE will get out of step, thinking it's on, say input 5, when it's really only on input 4. Again the better TV's, like Sony's, have discrete codes or buttons for each input. So LinuxMCE can just send the button 'input 4' and can re-transmit it 3 times to be sure it gets through, and not worry about trying to toggle. If you do have a toggle device like mine, and LinuxMCE ever gets out of sync, you can press and hold the red, green, yellow and blue buttons to get it back in sync. Holding the red button causes LinuxMCE to retransmit the 'power' command so if the TV went off instead of ON, it goes back ON. The green button retransmits the 'input select' button. The yellow retransmits the 'power on' to the receiver, and the blue retransmits the 'input select' to the receiver. Bottom line: if possible get TV's and Receivers with discrete codes and avoid TOAD's (toggle only analog devices). Nearly all the decent receivers actually do have discrete codes, so one possible solution at least to the input select problem with toggle-only TV's is to hook all the video sources to the receiver and let it do the switching, and leave the TV on 1 input. LinuxMCE automatically will setup your A/V gear like this. In the setup wizard it asks if you're using a receiver, and if you connected the video cable to it, and makes all the correct settings. You can view a graphical diagram of your a/v gear's connections in the admin site under Wizard, Devices, A/V Equipment, and click on the Connection Wizard.
	==still typing the rest==		==still typing the rest==

	~~==Related Links==~~

	~~[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']~~

Coley: Undo revision 25016 by Mogul23 (Talk)

2010-09-13T13:03:37Z

Undo revision 25016 by Mogul23 (Talk)

←Older revision		Revision as of 13:03, 13 September 2010
Line 159:		Line 159:

	[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']		[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']

	~~[http://cargames.com.au/ '''car games''']~~

Mogul23: /* Related Links */

2010-09-11T20:00:28Z

Jlhoyd05: /* still typing the rest */

2010-09-11T16:50:51Z

still typing the rest

←Older revision		Revision as of 16:50, 11 September 2010
Line 155:		Line 155:
	I used the same USB UIRT to control the TV in the bedroom. Note that because my TV does not support discrete codes, it is a nightmare to use with any universal remote control or any type of smarthome system. The better TV's, like Sony's, recognize discrete codes. This means that although the original remote control may only have 1 button to toggle the power on and off, the TV actually does recognize 3 separate i/r codes: The toggle power that's on the remote, as well as an explicit/discrete 'turn power on' and a discrete 'turn power off'. They just don't put all 3 buttons on the original remote to save space, but the TV does recognize them. Sites like remotecentral.com let you find discrete codes. Then LinuxMCE can control your TV reliably. When it's time to turn it on, the i/r transmitter sends the 'power on' button, and even if the TV is already on, it still stays on. The TV I used doesn't have discrete codes. It only recognizes the 1 button 'toggle power'. So LinuxMCE may think the TV is off, and send the 'toggle power' command to turn it on, when in fact the TV was already on and LinuxMCE inadvertently turned it off. Toggle codes are a nightmare for anybody that has ever tried to use any sort of universal remote, like a Logitech/Harmony because the remote never really knows what state the TV is in. Also, since infrared codes are inherently unreliable and don't always get through, if your TV supports discrete codes, like the Sony's do, LinuxMCE can just send the 'ON' 3 times to be 100% sure the TV got the command and goes on. But with toggle devices like the one I have it can't do that since sending the command 3 times would just turn it on, then off, then back on again. My TV has the same problem with inputs. It only recognizes a single 'toggle input' which just cycles through inputs. LinuxMCE remember what was the last input the TV was on, and how many times it needs to toggle to get to the next input. But this is very unreliable. Sometimes when the TV doesn't get a signal while hitting input select it 'freezes' for a couple seconds, and then LinuxMCE will get out of step, thinking it's on, say input 5, when it's really only on input 4. Again the better TV's, like Sony's, have discrete codes or buttons for each input. So LinuxMCE can just send the button 'input 4' and can re-transmit it 3 times to be sure it gets through, and not worry about trying to toggle. If you do have a toggle device like mine, and LinuxMCE ever gets out of sync, you can press and hold the red, green, yellow and blue buttons to get it back in sync. Holding the red button causes LinuxMCE to retransmit the 'power' command so if the TV went off instead of ON, it goes back ON. The green button retransmits the 'input select' button. The yellow retransmits the 'power on' to the receiver, and the blue retransmits the 'input select' to the receiver. Bottom line: if possible get TV's and Receivers with discrete codes and avoid TOAD's (toggle only analog devices). Nearly all the decent receivers actually do have discrete codes, so one possible solution at least to the input select problem with toggle-only TV's is to hook all the video sources to the receiver and let it do the switching, and leave the TV on 1 input. LinuxMCE automatically will setup your A/V gear like this. In the setup wizard it asks if you're using a receiver, and if you connected the video cable to it, and makes all the correct settings. You can view a graphical diagram of your a/v gear's connections in the admin site under Wizard, Devices, A/V Equipment, and click on the Connection Wizard.		I used the same USB UIRT to control the TV in the bedroom. Note that because my TV does not support discrete codes, it is a nightmare to use with any universal remote control or any type of smarthome system. The better TV's, like Sony's, recognize discrete codes. This means that although the original remote control may only have 1 button to toggle the power on and off, the TV actually does recognize 3 separate i/r codes: The toggle power that's on the remote, as well as an explicit/discrete 'turn power on' and a discrete 'turn power off'. They just don't put all 3 buttons on the original remote to save space, but the TV does recognize them. Sites like remotecentral.com let you find discrete codes. Then LinuxMCE can control your TV reliably. When it's time to turn it on, the i/r transmitter sends the 'power on' button, and even if the TV is already on, it still stays on. The TV I used doesn't have discrete codes. It only recognizes the 1 button 'toggle power'. So LinuxMCE may think the TV is off, and send the 'toggle power' command to turn it on, when in fact the TV was already on and LinuxMCE inadvertently turned it off. Toggle codes are a nightmare for anybody that has ever tried to use any sort of universal remote, like a Logitech/Harmony because the remote never really knows what state the TV is in. Also, since infrared codes are inherently unreliable and don't always get through, if your TV supports discrete codes, like the Sony's do, LinuxMCE can just send the 'ON' 3 times to be 100% sure the TV got the command and goes on. But with toggle devices like the one I have it can't do that since sending the command 3 times would just turn it on, then off, then back on again. My TV has the same problem with inputs. It only recognizes a single 'toggle input' which just cycles through inputs. LinuxMCE remember what was the last input the TV was on, and how many times it needs to toggle to get to the next input. But this is very unreliable. Sometimes when the TV doesn't get a signal while hitting input select it 'freezes' for a couple seconds, and then LinuxMCE will get out of step, thinking it's on, say input 5, when it's really only on input 4. Again the better TV's, like Sony's, have discrete codes or buttons for each input. So LinuxMCE can just send the button 'input 4' and can re-transmit it 3 times to be sure it gets through, and not worry about trying to toggle. If you do have a toggle device like mine, and LinuxMCE ever gets out of sync, you can press and hold the red, green, yellow and blue buttons to get it back in sync. Holding the red button causes LinuxMCE to retransmit the 'power' command so if the TV went off instead of ON, it goes back ON. The green button retransmits the 'input select' button. The yellow retransmits the 'power on' to the receiver, and the blue retransmits the 'input select' to the receiver. Bottom line: if possible get TV's and Receivers with discrete codes and avoid TOAD's (toggle only analog devices). Nearly all the decent receivers actually do have discrete codes, so one possible solution at least to the input select problem with toggle-only TV's is to hook all the video sources to the receiver and let it do the switching, and leave the TV on 1 input. LinuxMCE automatically will setup your A/V gear like this. In the setup wizard it asks if you're using a receiver, and if you connected the video cable to it, and makes all the correct settings. You can view a graphical diagram of your a/v gear's connections in the admin site under Wizard, Devices, A/V Equipment, and click on the Connection Wizard.
	==still typing the rest==		==still typing the rest==

			==Related Links==

			[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']

Ray N at 20:59, 20 August 2009

2009-08-20T20:59:34Z

←Older revision		Revision as of 20:59, 20 August 2009
Line 1:		Line 1:
			[[Category: Documentation]]
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__

Ray N at 06:54, 9 August 2009

2009-08-09T06:54:55Z

←Older revision		Revision as of 06:54, 9 August 2009
Line 2:		Line 2:
	\| __TOC__		\| __TOC__
	\|}		\|}
	~~[[Category:User Setups]]~~

	Watch one of the two demo videos instantly on Google video:		Watch one of the two demo videos instantly on Google video:

Ray N: /* Equipment used in the demo */

2009-04-07T02:50:59Z

Equipment used in the demo

←Older revision		Revision as of 02:50, 7 April 2009
Line 33:		Line 33:
	#[http://www.usbuirt.com/ USB UIRT IR Receiver Transmitter] IRTrans and Tira supposedly are also fully supported, and some of the Windows ones work, but for receiving [[IR]] only, not for transmitting [[IR]] codes to other devices.		#[http://www.usbuirt.com/ USB UIRT IR Receiver Transmitter] IRTrans and Tira supposedly are also fully supported, and some of the Windows ones work, but for receiving [[IR]] only, not for transmitting [[IR]] codes to other devices.
	#[http://www.newegg.com/Product/Product.aspx?Item=N82E16880100851 Standard Windows MCE remote] Found some on Ebay for $7 without the receiver.		#[http://www.newegg.com/Product/Product.aspx?Item=N82E16880100851 Standard Windows MCE remote] Found some on Ebay for $7 without the receiver.
	#[[Fiire_Chief\|Fiire Chief Gyro Remote]] This is a possible exception to the rule that I use only "widely available" components, as there is only one source for this remote to my knowledge. The one used in the video was donated to me by [[Fiire]], who provided the code that was added into LinuxMCE 0704 to make it work. They also donated the thin clients and their LinuxMCE PC (called the Fiire Engine) and the HD camcorder for the new demo video. I didn't show the Fiire Engine in the video because you can do the same thing with a generic PC. I have no ownership or financial ties to Fiire, and encourage alternative solutions be added to this wiki. Fiire's remote itself is a custom OEM development, based off of the [[~~Using_the_Gyration_Remote_GYR3101US_Non~~-Fiire_Chief\|Gyration GYR3101US]]. Most features are available on both remotes with a proper event map, with exception of the "Follow Me" feature. A regular Windows MCE infrared remote is a less expensive solution. '''Please read about the long list of [[Fiire#Issues\|issues]] with Fiire hardware before purchasing.'''		#[[Fiire_Chief\|Fiire Chief Gyro Remote]] This is a possible exception to the rule that I use only "widely available" components, as there is only one source for this remote to my knowledge. The one used in the video was donated to me by [[Fiire]], who provided the code that was added into LinuxMCE 0704 to make it work. They also donated the thin clients and their LinuxMCE PC (called the Fiire Engine) and the HD camcorder for the new demo video. I didn't show the Fiire Engine in the video because you can do the same thing with a generic PC. I have no ownership or financial ties to Fiire, and encourage alternative solutions be added to this wiki. Fiire's remote itself is a custom OEM development, based off of the [[Using_the_Gyration_Remote_GYR3101US_(Non-Fiire_Chief)\|Gyration GYR3101US]]. Most features are available on both remotes with a proper event map, with exception of the "Follow Me" feature. A regular Windows MCE infrared remote is a less expensive solution. '''Please read about the long list of [[Fiire#Issues\|issues]] with Fiire hardware before purchasing.'''
	#[[Hauppauge WinTV-PVR-150 MCE]]		#[[Hauppauge WinTV-PVR-150 MCE]]
	#[[Buffalo Linkstation\|Buffalo Link Station, model HD-HG300LAN]]		#[[Buffalo Linkstation\|Buffalo Link Station, model HD-HG300LAN]]

←Older revision		Revision as of 20:00, 11 September 2010
Line 159:		Line 159:

	[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']		[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']

			[http://cargames.com.au/ '''car games''']