Hi
I'm finding Twonky 4.4.6 to be much better at displaying art (it's quicker and much less buggy) and wondered if it would be feasible to install 4.4.9, copy the file containing the Shoutcast configuration info, remove 4.4.9, install 4.4.6 and overwrite the appropriate config file with the one from 4.4.9? The worst that could happen is that it stops Twonky 4.4.6 from working; sortable be removing it and reinstalling it.
This idea sounds good on paper (well on screen) but it might be that there are other configuration options which will break it, or that the module containing the Shoutcast information also contains the bugs which are upsetting 4.4.9. Anyone for any thought on this idea?
Bri
PS If anyone has a ReadyNAS with root access, knows which file it is and can be bothered sending it to me and telling me where to stick it (on the NAS I mean) please fire it over and I'll try it out
(radio at btinternet.com)
I'm finding Twonky 4.4.6 to be much better at displaying art (it's quicker and much less buggy) and wondered if it would be feasible to install 4.4.9, copy the file containing the Shoutcast configuration info, remove 4.4.9, install 4.4.6 and overwrite the appropriate config file with the one from 4.4.9? The worst that could happen is that it stops Twonky 4.4.6 from working; sortable be removing it and reinstalling it.
I believe that should work. It is one single file which needs to be copied. See the original details on the fix on Twonky forums for details http://www.twonkyforum.com/viewtopic.php?f=2&t=5494. This file was originally a Twonky plugin (when they actually openly supported such things), so is likely to work with any version.
Hi
Thanks for the info. It seemed a good plan at the time but sadly it just didn't work. I first tried the shoutcast file from the 4.4.9 Linux build but nothing doing. I then tried installing the ReadyNAS 4.4.9 bin; Shoutcast worked (as expected) but the album art has some problems* (I've mentioned these to Davidd in a PM a few days ago). I then saved the 4.4.9 shoutcast files, performed a fresh installation of 4.4.6, copied the 4.4.9 shoutcast files back over to the NAS but still no web wireless; there must also be changes elsewhere.
I see someone else on the TM forum suggests modifying the hosts file to redirect; once I've found where the hosts file resides, I'll give it a shot and see what happens. At least I'm getting a feel for Linux now; that was way overdue.
Incidentally, I very infrequently listen to internet radio; I just thought it'd be fun to try and get it working.
Bri
* FYI Album art in 4.4.9 seems a little bit less functional than in 4.4.6: I've set the music tree album name to ABC=1. Under 'S' there are 97 albums (yes, I know of TM's 100 limit). If I start Kinsky PDA and look at the 'S' container, I see all 97 albums with artwork. If instead I first look at A, then B, then C, then look at S, I only see 85 images in the 'S' container (but do see all the titles). It's an odd one and it doesn't happen in TM 4.4.6. It's obviously a Twonky issue but easily resolved by using 4.4.6.
I see someone else on the TM forum suggests modifying the hosts file to redirect; once I've found where the hosts file resides, I'll give it a shot and see what happens.
/etc/hosts
Hi
I used Vi to add the line
207.200.98.25 http://www.shoutcast.com to the hosts file. I then did a Twonky database rebuild but nothing doing, the list is still empty. It seems that 4.4.6 is determined not to work with Shoutcast. I wondered if that chap had the IP right but nslookup shows it as
scweb-ntc0l-0.shoutcast.com which looks plausible.
Incidentally, thanks for the hosts location. I initially looked in /etc and didn't see it due to me doing something really stupid: I'm more familiar with DOS dir/p from 286/386 days and I momentarily forgot of this new-fangled 'modern' capability which enables one to scroll up in the terminal window (yes, the hosts file was just off screen and yes, I had been at the red wine). Rest assured, I feel like a complete and total Twonky for that one!
Bri
Hi
I've discovered what might be causing me the problem. I editid the hosts file and rebooted the NAS. I see that when you reboot the NAS, it builds a new hosts file with the original entries (i.e. without the shoutcast line). I've tried adding the line to the hosts file and rebuilt the TM database (without first rebooting the NAS) but that didn't work. I don't know if the NAS actually needs a reboot to pick up the new line but if so, I'll have to find out which file to update such that it writes it into the hosts file during the boot process. I'll call a Linux guru I know and ask him tonight.
Bri
It seems the NAS is booting from an in-built O/S image and copies its contents so a RAM disk for better performance. You may need to write a script to overwrite the original hosts file in RAM disk with your customized one each time you boot your NAS.
It seems the NAS is booting from an in-built O/S image and copies its contents so a RAM disk for better performance. You may need to write a script to overwrite the original hosts file in RAM disk with your customized one each time you boot your NAS.
Hi Vic
Thanks very much for that; it makes great sense. I think you can update the firmware from a memory card/stick so that might indicate sneaky a root to it. There's maybe another easy way to upload the file; I'll have a hunt through the Netgear forums as it's bound to be there somewhere.
Do you know if it needs to have the redirection line in the hosts file at boot time for it to pick it up? In other words, am I correct in thinking that simply adding it to the current hosts file will not enable it to work (just to see if it does)?
Bri
mmmmmmmmm.............................
Will need to do some research.....
Hi Vic
I've just found out that I don't need to reboot for new entries in /etc/hosts to take effect so it looks like it should have worked when I tried it without the reboot.
Incidentally, I was also told to check /etc/nsswitch.conf to see if the NAS actually looks at the hosts file and yes, it does (there's 'hosts: files dns' line) so that's OK.
Not to worry, one of my friends is a Linux guru so this is a good excuse for us both to meet up at the pub, drink lots of beer and smoke lots of roll-ups then come back and rattle keyboards late into the evening whilst attacking the wine followed by the whisky
