<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SPDIF switch</title>
	<atom:link href="http://hackaday.com/2009/04/16/spdif-switch/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2009/04/16/spdif-switch/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:27:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jeff</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-141592</link>
		<dc:creator><![CDATA[Jeff]]></dc:creator>
		<pubDate>Tue, 11 May 2010 23:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-141592</guid>
		<description><![CDATA[I was looking over my stuff, and realized I moved my content!  Its still online here:

http://kthx.ath.cx/~jkent/hackaday/toslink_switch/

Sorry for the inconvenience.]]></description>
		<content:encoded><![CDATA[<p>I was looking over my stuff, and realized I moved my content!  Its still online here:</p>
<p><a href="http://kthx.ath.cx/~jkent/hackaday/toslink_switch/" rel="nofollow">http://kthx.ath.cx/~jkent/hackaday/toslink_switch/</a></p>
<p>Sorry for the inconvenience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linux-works</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-130177</link>
		<dc:creator><![CDATA[linux-works]]></dc:creator>
		<pubDate>Tue, 16 Mar 2010 22:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-130177</guid>
		<description><![CDATA[update: I have successfully linked an HDMI switch to this spdif/audio switch!

more details to follow, but the summary is: there are some hdmi switches that have an IR-remote in and you can feed TTL 38khz IR signals over this connection and remotely select input ports on the HDMI switch.  to integrate, you simply add a member to the structure so that when you find the spdif port to switch to, you also get the hdmi IR code and you send that cover over the IR-out wire and that&#039;s all that&#039;s needed to remotely select the HDMI &#039;slave&#039; port.]]></description>
		<content:encoded><![CDATA[<p>update: I have successfully linked an HDMI switch to this spdif/audio switch!</p>
<p>more details to follow, but the summary is: there are some hdmi switches that have an IR-remote in and you can feed TTL 38khz IR signals over this connection and remotely select input ports on the HDMI switch.  to integrate, you simply add a member to the structure so that when you find the spdif port to switch to, you also get the hdmi IR code and you send that cover over the IR-out wire and that&#8217;s all that&#8217;s needed to remotely select the HDMI &#8216;slave&#8217; port.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-95431</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Mon, 21 Sep 2009 15:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-95431</guid>
		<description><![CDATA[update: we have board ordered for the lcd/arduino part of the project!  see 3d drawing for what its going to look like-

LCDuino:

http://www.flickr.com/photos/linux-works/3939835161/

after the beta test (short run of boards) we&#039;ll make a larger production run of them and provide partial and possibly full kits.

watch:

www.netstuff.org/audio

and

www.amb.org/audio

for news of the LCDuino ;)

.bl]]></description>
		<content:encoded><![CDATA[<p>update: we have board ordered for the lcd/arduino part of the project!  see 3d drawing for what its going to look like-</p>
<p>LCDuino:</p>
<p><a href="http://www.flickr.com/photos/linux-works/3939835161/" rel="nofollow">http://www.flickr.com/photos/linux-works/3939835161/</a></p>
<p>after the beta test (short run of boards) we&#8217;ll make a larger production run of them and provide partial and possibly full kits.</p>
<p>watch:</p>
<p><a href="http://www.netstuff.org/audio" rel="nofollow">http://www.netstuff.org/audio</a></p>
<p>and</p>
<p><a href="http://www.amb.org/audio" rel="nofollow">http://www.amb.org/audio</a></p>
<p>for news of the LCDuino ;)</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-89293</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Tue, 25 Aug 2009 04:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-89293</guid>
		<description><![CDATA[no new update on the switch, itself.

the next stage is to make the lcd display into a pc board; and before that, I wanted to convert it to being an i2c serial lcd with a port expander.

my flicker site shows that progress.

still on perf board but that may be the last PB before the real pcb is sent out.  working on that now.

when the &#039;backpack i2c lcd&#039; board is done, the fabric switch board would be next and that&#039;s really the last part of this project.

.bl]]></description>
		<content:encoded><![CDATA[<p>no new update on the switch, itself.</p>
<p>the next stage is to make the lcd display into a pc board; and before that, I wanted to convert it to being an i2c serial lcd with a port expander.</p>
<p>my flicker site shows that progress.</p>
<p>still on perf board but that may be the last PB before the real pcb is sent out.  working on that now.</p>
<p>when the &#8216;backpack i2c lcd&#8217; board is done, the fabric switch board would be next and that&#8217;s really the last part of this project.</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aracos</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-89174</link>
		<dc:creator><![CDATA[aracos]]></dc:creator>
		<pubDate>Mon, 24 Aug 2009 15:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-89174</guid>
		<description><![CDATA[So is there any more Progress at the Moment ?
( Cant wait to see a full Documentation about that :) )]]></description>
		<content:encoded><![CDATA[<p>So is there any more Progress at the Moment ?<br />
( Cant wait to see a full Documentation about that :) )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aracos</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84971</link>
		<dc:creator><![CDATA[Aracos]]></dc:creator>
		<pubDate>Sun, 09 Aug 2009 20:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84971</guid>
		<description><![CDATA[Damn ^^
That allready sounds like allot more work :)
And for that my understanding of all this stuff seems much too low for myself ( But getting better with the Time i read more and more of it ^^ ).]]></description>
		<content:encoded><![CDATA[<p>Damn ^^<br />
That allready sounds like allot more work :)<br />
And for that my understanding of all this stuff seems much too low for myself ( But getting better with the Time i read more and more of it ^^ ).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84959</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84959</guid>
		<description><![CDATA[if you can ensure that a signal being there at all means it should be given priority, then that could work.  in your application, if you switch devices on and off (via power line, say) then yes, only one would be talking at a time and its very do-able to have an auto-select in that case.

I suppose you would want to do a &#039;pulse detect&#039; and then get the binary address of the line it came from and assert that to the switch&#039;s addr lines.

to get fancier, maybe do something that holds onto that line (even if others &#039;come up&#039;, later) until that line drops; then the &#039;voting&#039; begins again.  that way no data would be interrupted if some new device came online (by mistake).

I wondering if an arduino could somehow be able to detect &#039;activity&#039; on the lines and have it be its own priority encoder.  perhaps the ard could tap into the switched output and have it sequence thru the inputs, in a &#039;search mode&#039;, and then lock on to the first signal it gets.

another idea that could (maybe) work; if you had a DAC local to the box and it had an &#039;spdif=valid&#039; led or some lock-on signal on the board, you could use *that* as a &#039;there is good stuff on this input&#039; detector.  that would just be a TTL line to the ard and the ard would step thru until it found the first valid spdif=ok line.  better yet, step thru them all, keep a list and then only cycle thru the inputs you saw that had &#039;valid&#039; data.

and when I say DAC, I could also be referring to a digital audio receiver chip (like the 8416).  that fully &#039;understands&#039; spdif and so its a lot smarter than a pulse detector.  I don&#039;t think it cares what the logical data is (dd, dts, pcm); but if its a valid spdif stream, I think you can get a signal from this kind of receiver chip.  its a lot more work and if you have a receiver chip, you&#039;d want to use THAT as the input switch fabric, so that changes the project dramatically ;)


.bl]]></description>
		<content:encoded><![CDATA[<p>if you can ensure that a signal being there at all means it should be given priority, then that could work.  in your application, if you switch devices on and off (via power line, say) then yes, only one would be talking at a time and its very do-able to have an auto-select in that case.</p>
<p>I suppose you would want to do a &#8216;pulse detect&#8217; and then get the binary address of the line it came from and assert that to the switch&#8217;s addr lines.</p>
<p>to get fancier, maybe do something that holds onto that line (even if others &#8216;come up&#8217;, later) until that line drops; then the &#8216;voting&#8217; begins again.  that way no data would be interrupted if some new device came online (by mistake).</p>
<p>I wondering if an arduino could somehow be able to detect &#8216;activity&#8217; on the lines and have it be its own priority encoder.  perhaps the ard could tap into the switched output and have it sequence thru the inputs, in a &#8216;search mode&#8217;, and then lock on to the first signal it gets.</p>
<p>another idea that could (maybe) work; if you had a DAC local to the box and it had an &#8216;spdif=valid&#8217; led or some lock-on signal on the board, you could use *that* as a &#8216;there is good stuff on this input&#8217; detector.  that would just be a TTL line to the ard and the ard would step thru until it found the first valid spdif=ok line.  better yet, step thru them all, keep a list and then only cycle thru the inputs you saw that had &#8216;valid&#8217; data.</p>
<p>and when I say DAC, I could also be referring to a digital audio receiver chip (like the 8416).  that fully &#8216;understands&#8217; spdif and so its a lot smarter than a pulse detector.  I don&#8217;t think it cares what the logical data is (dd, dts, pcm); but if its a valid spdif stream, I think you can get a signal from this kind of receiver chip.  its a lot more work and if you have a receiver chip, you&#8217;d want to use THAT as the input switch fabric, so that changes the project dramatically ;)</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aracos</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84930</link>
		<dc:creator><![CDATA[Aracos]]></dc:creator>
		<pubDate>Sun, 09 Aug 2009 12:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84930</guid>
		<description><![CDATA[That was what i thought to hear ^^

The reason why i was asking is, that i planned to &quot;adopt&quot; ^^ your design ( but with 8 Inputs ) for several Game Consoles and more stuff, and integrate it into a 5.1 Amplifier ( the Amp only has 1 Toslink and 1 Coax Input ) since the Sources are allways off and if running only 1 runs at the same time.]]></description>
		<content:encoded><![CDATA[<p>That was what i thought to hear ^^</p>
<p>The reason why i was asking is, that i planned to &#8220;adopt&#8221; ^^ your design ( but with 8 Inputs ) for several Game Consoles and more stuff, and integrate it into a 5.1 Amplifier ( the Amp only has 1 Toslink and 1 Coax Input ) since the Sources are allways off and if running only 1 runs at the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84916</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Sun, 09 Aug 2009 03:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84916</guid>
		<description><![CDATA[latest firmware (v2):

http://www.netstuff.org/spdif-master/firmware/arduino/v2.x/

getting the code cleaned up little by little.

it now has a backlight timeout feature.

.bl]]></description>
		<content:encoded><![CDATA[<p>latest firmware (v2):</p>
<p><a href="http://www.netstuff.org/spdif-master/firmware/arduino/v2.x/" rel="nofollow">http://www.netstuff.org/spdif-master/firmware/arduino/v2.x/</a></p>
<p>getting the code cleaned up little by little.</p>
<p>it now has a backlight timeout feature.</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84915</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Sun, 09 Aug 2009 03:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84915</guid>
		<description><![CDATA[thanks ;)

it requires the user to select which input.

the reason is: in digital, there really is no &#039;off&#039; state, even when the music is not playing.  so, if you had 4 source and they were all paused, then you unpaused one, there would be no clear way to see that one is now active.  they all transmit a &#039;carrier&#039; (loose use of the word) even when idling.

I&#039;ve seen some dacs that auto-select inputs but its not a good or reliable way to do digital audio.  most components do shut off their spdif outputs when turned OFF but if they&#039;re on and stopped, the auto-select won&#039;t work, then.  it pretty much has to be manual.

one good thing about this, though, is that I use eeprom to save the last button presses; so whatever input you selected, it stays there even on power down/up.

.bl]]></description>
		<content:encoded><![CDATA[<p>thanks ;)</p>
<p>it requires the user to select which input.</p>
<p>the reason is: in digital, there really is no &#8216;off&#8217; state, even when the music is not playing.  so, if you had 4 source and they were all paused, then you unpaused one, there would be no clear way to see that one is now active.  they all transmit a &#8216;carrier&#8217; (loose use of the word) even when idling.</p>
<p>I&#8217;ve seen some dacs that auto-select inputs but its not a good or reliable way to do digital audio.  most components do shut off their spdif outputs when turned OFF but if they&#8217;re on and stopped, the auto-select won&#8217;t work, then.  it pretty much has to be manual.</p>
<p>one good thing about this, though, is that I use eeprom to save the last button presses; so whatever input you selected, it stays there even on power down/up.</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aracos</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84899</link>
		<dc:creator><![CDATA[Aracos]]></dc:creator>
		<pubDate>Sun, 09 Aug 2009 00:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84899</guid>
		<description><![CDATA[Just wanted to say that this is a really nice project :)
Does it switch between the Inputs automatically or does it require user interaction ?]]></description>
		<content:encoded><![CDATA[<p>Just wanted to say that this is a really nice project :)<br />
Does it switch between the Inputs automatically or does it require user interaction ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-84280</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Wed, 05 Aug 2009 17:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-84280</guid>
		<description><![CDATA[more photos, all on one page (extern ref, though).

http://www.head-fi.org/forums/5905687-post5498.html

the prototype phase is now done and the next step is to make some pcb designs.

tbc..]]></description>
		<content:encoded><![CDATA[<p>more photos, all on one page (extern ref, though).</p>
<p><a href="http://www.head-fi.org/forums/5905687-post5498.html" rel="nofollow">http://www.head-fi.org/forums/5905687-post5498.html</a></p>
<p>the prototype phase is now done and the next step is to make some pcb designs.</p>
<p>tbc..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-83995</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Tue, 04 Aug 2009 03:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-83995</guid>
		<description><![CDATA[another update: I have an annotated perf board photo (top and bottom) of the completed switch fabric (main board):

http://www.flickr.com/photos/linux-works/3787776832/

http://www.flickr.com/photos/linux-works/3786964219/

its still not formal docs, but its getting closer and I did label the various header blocks.

TBC...

.bl]]></description>
		<content:encoded><![CDATA[<p>another update: I have an annotated perf board photo (top and bottom) of the completed switch fabric (main board):</p>
<p><a href="http://www.flickr.com/photos/linux-works/3787776832/" rel="nofollow">http://www.flickr.com/photos/linux-works/3787776832/</a></p>
<p><a href="http://www.flickr.com/photos/linux-works/3786964219/" rel="nofollow">http://www.flickr.com/photos/linux-works/3786964219/</a></p>
<p>its still not formal docs, but its getting closer and I did label the various header blocks.</p>
<p>TBC&#8230;</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-82689</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Wed, 22 Jul 2009 20:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-82689</guid>
		<description><![CDATA[with the caveat that its still an early pre-release version, here is the location of the C source code:

http://www.netstuff.org/spdif-master/

it uses the lcd (arduino standard) library and the pin definitions should be pretty clear from the source code.  that&#039;s most of what you&#039;d need to know, to be able to interface this to the switch chip.

I&#039;m working on the switch &#039;fabric&#039; board now.  I have already done the various i/o ports boards (coax ports need a board; toslink do not) and so once the fabric is done, that&#039;s the last part in the system.  after *that*, then I can finally document it.

.bl]]></description>
		<content:encoded><![CDATA[<p>with the caveat that its still an early pre-release version, here is the location of the C source code:</p>
<p><a href="http://www.netstuff.org/spdif-master/" rel="nofollow">http://www.netstuff.org/spdif-master/</a></p>
<p>it uses the lcd (arduino standard) library and the pin definitions should be pretty clear from the source code.  that&#8217;s most of what you&#8217;d need to know, to be able to interface this to the switch chip.</p>
<p>I&#8217;m working on the switch &#8216;fabric&#8217; board now.  I have already done the various i/o ports boards (coax ports need a board; toslink do not) and so once the fabric is done, that&#8217;s the last part in the system.  after *that*, then I can finally document it.</p>
<p>.bl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linuxworks</title>
		<link>http://hackaday.com/2009/04/16/spdif-switch/comment-page-1/#comment-82380</link>
		<dc:creator><![CDATA[linuxworks]]></dc:creator>
		<pubDate>Mon, 20 Jul 2009 16:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10394#comment-82380</guid>
		<description><![CDATA[...hoping someone can &#039;moderate&#039; my comments and let them back in.  please?

people are asking for updates.  if I can&#039;t post them here, why even bother with this site, then?

.bl]]></description>
		<content:encoded><![CDATA[<p>&#8230;hoping someone can &#8216;moderate&#8217; my comments and let them back in.  please?</p>
<p>people are asking for updates.  if I can&#8217;t post them here, why even bother with this site, then?</p>
<p>.bl</p>
]]></content:encoded>
	</item>
</channel>
</rss>

