(02-26-2009 03:21 PM)Jerome Wrote: [ -> ]But, why they use an old version (1.22)??? I really don't understand that.
Another thing. If i install 1.50 over this "new 1.22", exist any problem??
They have chosen the 1.22 because when the firmware upgrade was in the make the feature freeze was during version 1.40 of transmission. Transmission 1.40 had big tracker and upload problems. Better an old 1.22 then a non functioning 1.40.
You can safely upgrade 1.50 over 1.22. I think they will release a 1.51 shortly with a cpu load issue fixed.
(02-26-2009 03:26 PM)Ger Teunis Wrote: [ -> ]They have chosen the 1.22 because when the firmware upgrade was in the make the feature freeze was during version 1.40 of transmission. Transmission 1.40 had big tracker and upload problems. Better an old 1.22 then a non functioning 1.40.
You can safely upgrade 1.50 over 1.22. I think they will release a 1.51 shortly with a cpu load issue fixed.
Thanks again for the answers....
What is the problem with the "cpu load issue"??? Will this cause any trouble if i watch videos and download torrents at the same time??
Best Regards
Jerome
Ger,
Any idea why Transmission always runs 3 processes? I can't find anything relevant on the main transmission site.
The download link seems to be broken. Anyone can upload it or send it to me?
Thanks
Alright guys, it's there!
Download the 1.50(+) again and install. Hope the cpu problems are gone now.
(02-26-2009 08:15 PM)Ger Teunis Wrote: [ -> ]Alright guys, it's there!
Download the 1.50(+) again and install. Hope the cpu problems are gone now.
what is this "+" business? Is this different than 1.50 Final?
.
Version 1.51 is up
This includes the cpu speed fixes, enjoy!
(02-26-2009 08:15 PM)Ger Teunis Wrote: [ -> ]Alright guys, it's there!
Download the 1.50(+) again and install. Hope the cpu problems are gone now.
It looks like my "Egreat Transmission crash" problem is solved in this version.
More than 10 hrs works fine for me.
Thank you!
Is there any difference between versions 1.50+ and 1.51, cause the size of archived files is the same?
BR,
Victor
(02-27-2009 09:34 AM)vizavic Wrote: [ -> ]It looks like my "Egreat Transmission crash" problem is solved in this version.
More than 10 hrs works fine for me.
Thank you!
Is there any difference between versions 1.50+ and 1.51, cause the size is the same?
Victor
Hopefully 1.51 will be a good release! Good to hear you have nice results already. I've removed the 1.50+ and restored the default 1.50. The 1.51 has a couple of extra fixes but none of them are critical though.
Just wanted to say a quick thanks for the recent releases. I had the cpu issues with the original 1.50, but these seemed siginificantly better with 1.50+, which I installed last night. I did a bit of comparison between various versions - running 20 private tracker seeds with very few peers caused no problems in any build, having torrentwatch add 4 torrents with large (10,000-50,000) number of peers from a popular 'easy' site caused 1.42 to spike at about 60% cpu, and settled down around 30%, in 1.50 the cpu was pegged at 99% and the transmission interface became unresponsive, in 1.50+ it spiked to about 70% and settled down at around 40%, remaining responsive at all times. Definitely a clear improvement, and I suspect the only reason for the slightly elevated cpu usage over 1.4x builds is becuase it connects to more peers and maintains a higher average speed. I'm a happy bunny. IE compatability fixes are also now included, so, y'know, yay!
Actually while I remember... The other thing I always do, I think I've mentioned before, is chop around with the widths of stuff in the gaya interface (the files in /.transmission-nmt) so it works on an SD tv. My changes are nothing fancy - I lose the download bar, make some of the fields narrower, shrink the font size a bit, and reduce the overall width of the table - it's readable and still fits 4 torrent entries on an sd screen.
As I say, at the moment its a case of taking the existing code and just hacking it about till it looks pretty much right, but I'd be happy to share what I've got if it would be worth rolling into the standard install. Is there any way to intelligently switch between the two - some way of detecting if the screen is HD or SD? If not I guess I'd I need to keep a seperate set of pages for SD, and the installation guide could advise SD users to link to indexSD.cgi or something?
Thank you very much, Ger Teunis, 1.51 works very well for me.
(02-27-2009 12:07 PM)Squeek Wrote: [ -> ] Actually while I remember... The other thing I always do, I think I've mentioned before, is chop around with the widths of stuff in the gaya interface (the files in /.transmission-nmt) so it works on an SD tv. My changes are nothing fancy - I lose the download bar, make some of the fields narrower, shrink the font size a bit, and reduce the overall width of the table - it's readable and still fits 4 torrent entries on an sd screen.
As I say, at the moment its a case of taking the existing code and just hacking it about till it looks pretty much right, but I'd be happy to share what I've got if it would be worth rolling into the standard install. Is there any way to intelligently switch between the two - some way of detecting if the screen is HD or SD? If not I guess I'd I need to keep a seperate set of pages for SD, and the installation guide could advise SD users to link to indexSD.cgi or something?
I can create double files for everything so users can use index.cgi for HD and index_sd.cgi while adding the webservice link, good idea?
Could you send me your changes, then I can add it to the default build action.
Sounds like a plan!
Well, having blindly overwritten my changes last night in my haste to get 1.50+ on there, I'll need to hack it up again when I get back from work
Will put something together and get it to you ASAP. Fingers crossed we'll only need it for this version of the NMT firmware - if Transmission 1.51 proves stable it'll hopefully get included in the next firmware release, complete with an update to the default gaya torrent interface.
now, lets see how quickly I can remember all the places I hacked about with widths...