Squeezebox Touch -- Modifications

just a quick question, whenever I apply a mod and the Touch reboots, the IP address of the Touch changes so I cannot reconnect without re-defining the Ip address in WinSCP login. Any way to stop this (probably a very noobie type question I know)

Hi.

Yep. That's known fact.

You should "reserve" a fixed IP address for the Touch on your router.
Modern style routers let you do this easily in the network setup.

Otherwise you got to look that IP adress up everytime you reboot the Touch.

I wouldn't recomend working with static IPs, which is much less flexible
then working with reserved IPs in a DHCP environment.

Cheers
 
just a quick question, whenever I apply a mod and the Touch reboots, the IP address of the Touch changes so I cannot reconnect without re-defining the Ip address in WinSCP login. Any way to stop this (probably a very noobie type question I know)

To remedy this, best practices indicate that the IP address be reserved based on a device's MAC address. In the case of the Touch, this can be found on the sticker on the bottom of the device. When this is done, every time your device reboots and/or your router, your Touch will always be at the same IP address.

This exercise is performed differently on every router, so please consult your owner's manual for further guidance. Alternatively, Logitech has setup instructions for a number of routers on their Support site.

For Netgear routers go here

For D-LINK routers go here

For 2WIRE routers go here
 
Hi folks.

I changed from beta to normal status. Things seem to run pretty stable.

I did some little adjustments on the blog text. The toolbox itself stayed as
it was.


Cheers

Klaus,

One suggested correction to the written instructions.

In the 1.2.7. Linux/OSX (commandline) section, one line (in bold below) needs to include one correction.

4. Unpack the archive:

ssh root@Your-Touch-IP-Address:
Password: 1234
cd /
tar xf touchtoolbox2.0.tar

(not <tar xvf touchtoolbox2.0.tar> as you currently have it listed)
 
I seem to be having problems trying to set the buffer size.
here is the output from the log:
<result success="true" />
</call>
<call>
<command value="ttbuffer 4000" />
<destination value="/" />
<output value="4000
________________________________________________________________

soundcheck's SB Touch Toolbox 2.0: The buffer mod!
________________________________________________________________

Buffer set to 4000 us. Rebooting system.
________________________________________________________________
" />
<erroroutput value="sed: unmatched '/'" />
<result success="false">
<message>Server unexpectedly closed network connection.</message>
</result>
</call>
</session>


any ideas? everything else so far has been working ,
ttout -d, and tt --wlan were all successful
 
I seem to be having problems trying to set the buffer size.
here is the output from the log:
<result success="true" />
</call>
<call>
<command value="ttbuffer 4000" />
<destination value="/" />
<output value="4000
________________________________________________________________

soundcheck's SB Touch Toolbox 2.0: The buffer mod!
________________________________________________________________

Buffer set to 4000 us. Rebooting system.
________________________________________________________________
" />
<erroroutput value="sed: unmatched '/'" />
<result success="false">
<message>Server unexpectedly closed network connection.</message>
</result>
</call>
</session>


any ideas? everything else so far has been working ,
ttout -d, and tt --wlan were all successful

That looks strange!?!?
What command did you run?
 
ttbuffer 4000

Just verified it. It works in my case. You're the first one running into this.

You could try to restore first the original files by running

tt -d

after the reboot you could try to run the upgrade procedure again.

tar ...
ttinit...
...asf

Or you start off with a factory reset and do the installation again,
just to make sure that not some other stuff got shuffled.

Cheers
 
Just verified it. It works in my case. You're the first one running into this.

You could try to restore first the original files by running

tt -d

after the reboot you could try to run the upgrade procedure again.

tar ...
ttinit...
...asf

Or you start off with a factory reset and do the installation again,
just to make sure that not some other stuff got shuffled.

Cheers

after factory reset, and re-installation, everything seems
to be working. Thanks
 
2.0 Mods Very Easy to Implement

Klaus,

Just upgraded to the 2.0 mods and found the procedure very easy. I too had to change the ttbuffer to 4000 to eliminate pops. All in all, a great sound improvement. Thought I would miss the display, but was really only using it as a clock. Though not a significant issue, I was just wondering if anyone else was hearing a few clicks/pops when hitting "play" or changing between 24/96 tracks? Does not occur during 16/44 playback. Maybe an easy adjustment? Thanks for all your work.

Steve
 
I too hear the popping sound when first playing. Also not a big deal to me.

I am going to make a few more changes to my network and power supplies. At present I am using a big laboratory grade power supply for the touch. It has multiple voltage outlets and makes a big difference running the touch at 5V. I will be be using this 5V to power my router in the future. I will also use the 10V outlet to power the touch, with a superteddy reg with in a few centimeters of the unit. It will be a short connection of cat6 to the touch from the router, the entire network is now cat6. I did not get any audible difference changing to cat6 from cat5.