TeamSpeak 5.0.0-beta52.x

Hello :upside_down_face: a new beta update was released.
And this is what we’ve added and changed since the last client, along with some bug fixes.

  • We decided to change the invite protocol to teamspeak://
    The invite via tsserver:// won’t work any longer work in TS5!
  • We added cid (for channel id as target) as optional invite parameter. We missed that in beta 51.

Here is an example where channel was replaced with cid as target.

teamspeak://example.com?port=9987&nickname=tester&password=secrets&cid=15&channelpassword=NotTellingYou&token=C3bcBHpSStQHFHc7UO89dKwhCSRkR7ysJN3HRTXr&addbookmark=Example%20Bookmark

  • Settings for file transfer bandwidth and parallel transfers got added to the Settings menu. There you also find the

Full changelog

* beta 52.1
* Fixed potential UI freeze on fresh installation when a member of big chats
* Fixed not attempting to connect to secondary addresses if the first one fails
*
* beta 52
* Renamed protocol from tsserver:// to teamspeak://
* Tweaked file transfer UI
* Added search to file transfer, allowing to search for files within the currently displayed folder
* Added sound notifications for whisper
* Fixed an issue with teamspeak links on Mac
* Fixed Open File not doing anything if the operating system does not know how to handle the file type
* Added settings for filetransfer speed and concurrent up/downloads
* Fixed markdown links not working correctly in some scenarios
* Fixed issues connecting to a server with a privilege key
* Fixed invite urls containing the port when not needed
* Fixed not seeing server and channel groups in some rare cases

Known

  • Bandwidth setting applies really high numbers when values like 2,5 Gbps got set before. This fix did not made it into beta 52.
  • Bandwidth default is 0 and means unlimited. We are still working on it and will add a setting to disable limitation for a better understanding.
  • teamspeak:// invite in chats are not converted but ts3server:// invites are.

Notes for this thread

  • Feedback as per always is always welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.
16 Likes

I can’t connect to servers after the update. Beta 51 worked fine. The cef.log says

[0506/181530.610:INFO:CONSOLE(2)] "Own Client does not exist", source: tsui://default/main-7008317f6045957fb2ba.js (2)
[0506/181536.123:INFO:CONSOLE(2)] "Unable to remove server from shared servers", source: tsui://default/main-7008317f6045957fb2ba.js (2)

The ts5client.log seems normal with no errors

A post was split to a new topic: Size does not restore from sys tray

How do you connect to a server? A bookmark or via contact or search filed or invite or activity. There are so many ways now.

What happen when you start the client and wait some time like 3 or 5 minutes?

2 Likes

The error seems to be related to IPv4/v6. The server I am trying to connect to is only available under a IPv4 address, but I have both. Disabling IPv6 in my network adapter allowed me to connect again. So this update must have changed something in regards to the handling of IPv4/v6 connections

Hello I have the same problem I can no longer connect to my server with the Server NickNames of MyTeamSpeak

An urgent update please.

No problem with TS3 client

We will look into this but it seems to be unrelated to this beta release.
We haven’t touched connection via server nickname in a while.

Are target server hosted on OVH ?

Edit Till we can say more use the IP or DNS of the server.

2 Likes

closely what I see in my log it comes from a problem with the IPv6 connection via MyTeamSpeak

Host : contabo.com

My problem regarding IPv4/v6 must come from this update as I was connected to the server prior to the necessary restart after the update. My server is hosted at Hetzner.

Hi, I confirm the bug with IPV6 I delete them on MyteamSpeak I only left IPV4 and everything works normally

We found the issue and our devs are working on this.

Can’t say at this point if we get new client update for this today.

6 Likes

2 posts were merged into an existing topic: Re-download Beta

Beta 52.1 with a fix for the connection issues is available.

Changelog

* beta 52.1
* Fixed potential UI freeze on fresh installation when a member of big chats
* Fixed not attempting to connect to secondary addresses if the first one fails
13 Likes

Thank you

A post was split to a new topic: Hyperlinks in pinned messages are hard to click

I hope this time that’s related to the thread… :roll_eyes:

If you’re changing the protocol names you should also change it if you share your server.
The Create Invite URL feature still contains the old protocol name.

4 Likes

Related but we did not touch this yet as we did not touch the conversation in chats (for reasons i can not tell yet).

6 Likes
twitch instagram twitter facebook