Transmission

insekt wrote:The windows 2.91 (14710) x64 beta build just crashes on launch for me on Windows 10 x64.

No crashes for me with that build on the exact same OS.

The Windows builds have been posted here but not on the homepage. Why not? Because of the OSX malware issue?

https://download.transmissionbt.com/files/

It wasn't published because there's a delay in getting code signing certificate. As soon as we get it the build will be there on transmissionbt.com. Unfortunately there's no ETA on this. Is it due to lack of funding for payment or something like that? Is it going to be a beta or a stable build? Wil...

2.90 is out. Where's the Windows beta?

Any news? All we know so far is that it will not have much to do with Transmission Qt by Rene Berber according to him. https://sourceforge.net/p/trqtw/discussion/1315796/thread/098bb683/ However, I do hope both projects are unified into one project so there is no confusion or inconsistency for the ...

A dev has said in another recent thread that that 2.90 will hopefully be out this year and that it will come with a Windows port.

@Calidude Same time corresponding tickets will be resolved, not in 2.90 for sure. See #2175 and #5385 . @uberfu Whether to change the client is your own decision. The way I see it the project is very much alive, but hitting a bit of hard time at the moment. As for the release timeframe, I'm hoping ...

This is amazing news! I've always wanted Transmission to get an official Windows port. Will we get support for labels, much like in the Mac port?

Update your router firmware.

The 2 conditions are unrelated. Info on 'holepunching'. https://superuser.com/questions/617263/what-is-the-difference-between-udp-hole-punching-and-upnp I assure you, disabling uTP ends up closing my port. I repeated the process this past week and it did it twice. On my other Transmission installat...

Has anybody noticed this behavior with 2.84? Disabling uTP, on numerous occasions, has resulted in the closing of a port that used to be open via UPNP. I tried disabling uTP on multiple ports and every time, within 3-4 days, Transmission will report the port as closed even though it was open for day...

I see similar behavior. Over time, the port just seems to close itself, but only when uTP is disabled. I have to keep uTP enabled to keep the port open via UPNP.

I'm thankful to whoever maintains Transmission Qt for Windows. Hopefully the Transmission devs will finally see the light and give Windows a truly official client.

I think an official Windows build would be good simply to help finally get rid of uTorrent for good.

blacke4dawn wrote:I don't know about you but for me it hovers around 70 megs of memory (both client and dbus-daemon together), I wouldn't say that is a "memory hog".

I mean compared to a native Windows BT client it is. Even moreso than qBittorrent for Windows, which is written in Qt.