- Generated on Wed Aug 6 2025 13:38:29 for TeamTalk 5 C-API DLL by
1.10.0
|
TeamTalk 5 C-API DLL Version 5.19A
|
This section contains the list of new features and API changes in TeamTalk SDK releases.
TeamTalk 5 SDK v. 5.19a release, August 5th 2025
TeamTalk 5 SDK v. 5.18a release, May 5th 2025
TeamTalk 5 SDK v. 5.15a release, December 19th 2023
TeamTalk 5 SDK v. 5.14a release, August 16th 2023
TeamTalk 5 SDK v. 5.13a release, May 8th 2023
TeamTalk 5 SDK v. 5.12a release, December 21st 2022
TeamTalk 5 SDK v. 5.11a release, October 2nd 2022
TeamTalk 5 SDK v. 5.9a release, April 2nd 2022
TeamTalk 5 SDK v. 5.8b release, September 7th 2021
TeamTalk 5 SDK v. 5.8a release, June 24th 2021
TeamTalk 5 SDK v. 5.7a release, March 4th 2021
TeamTalk 5 SDK v. 5.6a release, August 9th 2020
TeamTalk 5 SDK v. 5.5a release, April 13 2020
TeamTalk 5 SDK v. 5.4a release, June 25th 2019
TeamTalk 5 SDK v. 5.3b release, November 11th 2018
TeamTalk 5 SDK v. 5.3a release, April 14th 2018
TeamTalk 5 SDK v. 5.2d release, June 24th 2017
TeamTalk 5 SDK v. 5.2c release, May 8th 2017
TeamTalk 5 SDK v. 5.2b release, Jan 30th 2017
TeamTalk 5 SDK v. 5.2a release, January 8th 2017
TeamTalk 5 SDK v. 5.1c release, February 29th 2016
TeamTalk 5 SDK v. 5.1b release, October 3rd 2015
TeamTalk 5 SDK v. 5.1a release, June 13th 2015
TeamTalk 5 SDK v. 5.0a release, March 15th 2015
TeamTalk 4 SDK v. 4.6b release, June 28th 2014
TeamTalk 4 SDK v. 4.6a release, February 20th 2014
TeamTalk 4 SDK v. 4.5a release, May 12th 2013
TeamTalk 4 SDK v. 4.4a release, September 25th 2012
TeamTalk 4 SDK v. 4.3a release, March 18th 2012
TeamTalk 4 SDK v. 4.2a release, November 1st 2011
TeamTalk 4 SDK v. 4.1a release, October 30th 2010
TeamTalk 4 SDK v. 4.0c release, March 7th 2010
TeamTalk 4 SDK v. 4.0a release, November 22nd 2009
TeamTalk server executable has fixed a security issue where a reused channel ID could give operator access to someone who previously had that channel ID.
A UserAccount now contains a field szLastLoginTime which shows the last time a user logged in.
WebRTC was previously based on r4332 but has now been updated to r6818. This has unfortunately caused the WebRTCAudioPreprocessor struct to become incompatible with the struct specified previous releases. Basically level estimation and voice detecting using WebRTC is no longer supported.
szLastLoginTime in UserAccountvoicedetetion from WebRTCAudioPreprocessorlevelestimation from WebRTCAudioPreprocessoradaptivedigital in WebRTCAudioPreprocessorPulseAudio sound system is now supported in the TeamTalk SDKs for Ubuntu 22 and Raspbian.
It is now possible to disable the ability to send private and channel text messages using USERRIGHT_TEXTMESSAGE_USER and USERRIGHT_TEXTMESSAGE_CHANNEL.
szOwner in BannedUserCMDERR_MAX_FILETRANSFERS_EXCEEDED in ClientError__SOUNDDEVICEEFFECTS in TTType__DESKTOPWINDOW in TTType__ABUSEPREVENTION in TTTypeSOUNDSYSTEM_PULSEAUDIO in SoundSystemAFF_MP3_320KBIT_FORMAT in AudioFileFormatUSERRIGHT_TEXTMESSAGE_USER in UserRightUSERRIGHT_TEXTMESSAGE_CHANNEL in UserRightThe maximum duration (in milliseconds) for a voice or media stream to be active can now be specified in Channel fields nTimeOutTimerVoiceMSec and nTimeOutTimerMediaFileMSec. This can be used to ensure that a single user does not block voice transmission to a channel when e.g. using CHANNEL_SOLO_TRANSMIT.
If the TeamTalk client fails to connect using an encrypted connection the event CLIENTEVENT_CON_CRYPT_ERROR is posted. The error will include an OpenSSL error code and text message regarding what failed.
If a user of type USERTYPE_ADMIN adds a new UserAccount then the event CLIENTEVENT_CMD_USERACCOUNT_NEW is posted. If a UserAccount is deleted the event CLIENTEVENT_CMD_USERACCOUNT_REMOVE is posted.
The call to TT_Connect() is no longer a blocking call when using encryption.
On Windows the following new SoundDevice related events are posted:
sounddevice in TTMessageThis release fixes a crash issue in the TeamTalk server when a user performs a channel ban on a user who is not in a channel.
Here's the list of new features in TeamTalk SDK v5.11a:
Here's the list of bug fixes in TeamTalk SDK v5.11a:
It's now possible to change log levels while the TeamTalk server is running. Setup uServerLogEvents in ServerProperties and issue TT_DoUpdateServer(). uServerLogEvents is based on ServerLogEvent.
TextMessage is limited to 511 characters but now it's possible to specify bMore on TextMessage to denote that a text message is part of a combined message.
A CHANNEL_SOLO_TRANSMIT Channel automatically switched to the next user after 500 msec of inactivity. This delay is now configurable using nTransmitUsersQueueDelayMSec on Channel.
uServerLogEvents in ServerPropertiesbMore in TextMessagenTransmitUsersQueueDelayMSec in ChannelUserAccount now includes a property that shows when it was last modified.
RemoteFile now includes a property that shows when it was uploaded.
szLastModified on UserAccount-struct.szUploadTime on RemoteFile-structPreviously it was only possible to store audio from STREAMTYPE_VOICE to either a file or AudioBlock. In TeamTalk v5.8a it's now possible to have the TeamTalk instance mix several stream types into a single audio stream.
To record multiple audio streams, i.e. STREAMTYPE_VOICE, STREAMTYPE_LOCALMEDIAPLAYBACK_AUDIO and STREAMTYPE_MEDIAFILE_AUDIO, use TT_StartRecordingMuxedStreams(). The StreamTypes can be OR'ed to mix the wanted combination.
To retrieve AudioBlock with mixed audio use TT_EnableAudioBlockEvent() or TT_EnableAudioBlockEventEx().
uStreamTypes on AudioBlock denoting which streams were mixed into the AudioBlock.Previously SpeexDSP was the only support audio preprocessor for noise suppression, echo cancellation and automatic gain control (AGC). In TeamTalk v5.7 it's now possible to use WebRTC's audio preprocessor which work significantly better than the echo cancellor in SpeexDSP and platform echo cancellors supported through SOUNDDEVICEFEATURE_AEC.
Read more about WebRTC's audio preprocessor using the WebRTCAudioPreprocessor-struct.
Previously it was only possible to control STREAMTYPE_VOICE, STREAMTYPE_MEDIAFILE, STREAMTYPE_VIDEOCAPTURE and STREAMTYPE_DESKTOP in a classroom using transmitUsers on Channel-struct. Now STREAMTYPE_CHANNELMSG has been added so it's also possible to enable/disable channel text messages sent through TT_DoTextMessage().
A new channel type CHANNEL_HIDDEN has been introduced which makes a channel invisible to users who do not have USERRIGHT_VIEW_HIDDEN_CHANNELS. Users who cannot see the channel are still able to join it given that they know its name and password. Only users with USERRIGHT_MODIFY_CHANNELS are able to create hidden channels.
Use TT_DoMakeChannel() or TT_DoJoinChannel() to create a hidden channel.
Both client and server are now able to verify that the remote end is a valid user using TLS peer verification. Peer verfication is set up in EncryptionContext and enable using TT_SetEncryptionContext() on the client and TTS_SetEncryptionContext() on the server.
Compensation for network jitter can now be enabled using JitterConfig and activated using TT_SetUserJitterControl(). The jitter configuration allows a buffer to build up before playback starts. Remember to also increase the allowed buffer size by calling TT_SetUserAudioStreamBufferSize().
TT_StartStreamingMediaFileToChannel() now support OPUS .ogg files on Windows. This allows playback of files recorded using TT_SetUserMediaStorageDir() or TT_StartRecordingMuxedAudioFile().
Previously it was only possible to set one EncryptionContext for all TeamTalk server instance, i.e. TTSInstance, but now each server instance can have its own by calling TTS_SetEncryptionContext().
webrtc in AudioPreprocessor for WebRTCAudioPreprocessor.nSoundInputDeviceDelayMSec in ClientStatistics for showing audio device delay.%starttick% for audio file names. See TT_SetUserMediaStorageDir().A new SoundDevice will appear on Android when calling TT_GetSoundDevices(). This sound device behaves the same as calling Android Java class android.media.AudioManager.setMode(AudioManager.MODE_IN_COMMUNICATION).
Most platforms today come with their own way of toggling effects on a sound device. Examples of this are echo cancellation, automatic gain control (AGC), noise suppression, 3D sound positioning.
SoundDevice now has a new property called uSoundDeviceFeatures which tells what features can be enabled on the sound device. Currently the list of SoundDeviceFeature includes:
TT_SetSoundDeviceEffects() is a new function in TeamTalk v5.6 which can be used for enabling AGC, AEC and denoising on Windows and Android.
When TT_SOUNDDEVICE_ID_SHARED_FLAG was introduced the shared sound device would default to a sample rate of 48000 and stereo.
Now it's possible to manually specify the sample rate and number of audio channels using TT_InitSoundInputSharedDevice() and TT_InitSoundOutputSharedDevice().
When AudioPreprocessor was introduced it could not be used when performing a loopback test. This is now possible using TT_StartSoundLoopbackTestEx().
Previously only SpeexDSP was available as AudioPreprocessor but now others can be chosing using TT_SetSoundInputPreprocessEx().
uSoundDeviceFeatures on SoundDevice.nWaveDeviceID on SoundDevice on non-Windows platforms. Previously this property was only shown on Windows but now it's shown on all platform. The reason for this is to have a common structure available for Python integration.uSoundDeviceFeatures on SoundDevice for showing features available when setting up a sound device.All platforms now include the property nWaveDeviceID on SoundDevice. Previously this property was only shown on Windows but now it's shown on all platform. This means the byte offset of bSupports3D and onwards have changed in the SoundDevice structure. The reason for this is to have a common structure available for Python integration.
Value of TT_SOUNDDEVICE_ID_VOICEPREPROCESSINGIO has been changed to include TT_SOUNDDEVICE_ID_SHARED_FLAG. Previously the iOS sound device that does voice preprocessing actually ran in its own shared device. However, with the introduction of TT_SOUNDDEVICE_ID_SHARED_FLAG in TeamTalk v5.5 it is simpler for iOS to use the same shared device property as on Android. Therefore ensure that TT_InitSoundInputDevice() and TT_InitSoundOutputDevice() is not called with 1 instead of the value of TT_SOUNDDEVICE_ID_VOICEPREPROCESSINGIO.
Previously the Android platform only supported one active sound input device. This meant that only one TeamTalk instance could be used on Android.
With the introduction of shared audio device it's now possible for multiple TeamTalk instances to share the same audio input device.
Also for playback the TeamTalk instance can use a shared sound device so playback is not limited to few simultaneous users talking at the same time.
The shared audio device on Android is same as TT_SOUNDDEVICE_ID_OPENSLES_DEFAULT but or'ed with the flag TT_SOUNDDEVICE_ID_SHARED_FLAG. The sound device ID flag TT_SOUNDDEVICE_ID_SHARED_FLAG tells the TeamTalk instance to create a shared audio device which distributes its audio to all other client instances.
The shared audio device which is created runs at the audio device's highest sample rate and highest number of channels. Each client which receives the audio from the shared audio device resamples the audio data to its own format. This is a CPU intensive task, so many clients at different sample rates uses more CPU. It is therefore recommended that clients which use this feature all use channels that has the same audio codec settings. Preferably nDefaultSampleRate and nMaxInputChannels and nMaxOutputChannels of the chosen SoundDevice.
To initialize a shared audio input device call like this:
TT_InitSoundInputDevice(ttInst, inputid | TT_SOUNDDEVICE_ID_SHARED_FLAG);
To initialize a shared audio output device call like this:
TT_InitSoundInputDevice(ttInst, outputid | TT_SOUNDDEVICE_ID_SHARED_FLAG);
Media files can now be played using the TeamTalk instance configured sound output device. Call TT_InitLocalPlayback() to playback a media file.
Prior to playback it's possible to set specify an offset using MediaFilePlayback and setup an AudioPreprocessor.
While the media file is playing it's possible to use TT_UpdateLocalPlayback() to change the media stream's properties. The progress of the media file playback can be monitor through CLIENTEVENT_LOCAL_MEDIAFILE.
Stop local media file playback using TT_StopLocalPlayback().
streaming to channel
When streaming media files to a channel it's now possible to specify an AudioPreprocessor to change the audio stream of the media file.
A new audio TTAudioPreprocessor is introduced with can mute left/right audio channel and change gain level.
It's also possible to change the offset and pause the media file using TT_UpdateStreamingMediaFileToChannel() and MediaFilePlayback.
To use these new features use TT_StartStreamingMediaFileToChannelEx() instead of TT_StartStreamingMediaFileToChannel().
Previously the maximum transmit interval was limited to 100 msec. With OpusCodec's introduction of 120 msec frame sizes the transmit interval has been increased to 500 msec.
OPUS v1.3 introduced additional frame sizes, i.e. 80, 100 and 120 msec. These frame sizes can now be set using the nFrameSizeMSec property of OpusCodec.
Previously TT_EnableAudioBlockEvent() could only be used to access audio from a single user. Using TT_MUXED_USERID now makes it possible to access the audio stream where all users' audio streams have been mixed together. Basically the same as recording all conversations to a single file using TT_StartRecordingMuxedAudioFile().
The STREAMTYPE_VOICE could previously only come from the configured SoundDevice passed to TT_InitSoundInputDevice(). Now it's possible to replace the, typically microphone, audio input with a custom audio stream by passing raw audio in AudioBlock to TT_InsertAudioBlock().
The audio input must be passed continuesly to TT_InsertAudioBlock() to keep the input going. Use event CLIENTEVENT_AUDIOINPUT to monitor progress. The AudioInputProgress struct hold information about the queue sizes/progress.
How often "keep alive" information should be sent depend on the type of network where the TeamTalk client is deployed. Previously the TCP and UDP keep alive settings have been controlled entirely by the TeamTalk client instance.
Now it's possible to configure the keep alive properties using ClientKeepAlive-struct and functions TT_SetClientKeepAlive() and TT_GetClientKeepAlive().
Previously it was only possible to have one active audio recording using TT_StartRecordingMuxedAudioFile().
Now it's possible to record multiple channels at the same time using TT_StartRecordingMuxedAudioFileEx(). Note that in order to get audio from channels where the TeamTalk instance is currently not participating requires the use of TT_DoSubscribe() and SUBSCRIBE_INTERCEPT_VOICE.
The TeamTalk 5 SDK Standard Edition could only connect to unencrypted TeamTalk servers, but now it's also possible to connect to encrypted servers. The TeamTalk server in TeamTalk 5 SDK, however, still cannot run in encrypted mode.
Previously the Android platform only included a shared library for Java Native Interface (JNI). But now it's also possible to use a shared library like other platforms.
nFrameSizeMSec for OpusCodec.
TeamTalk SDKs for Android now comes with a TeamTalk JNI library for 64-bit ARM and 32-bit Intel x86. Required API level is now 21 (Android 5.0).
TeamTalk SDKs for Windows now uses Microsoft Media Foundation instead of DirectShow when streaming media files and capturing from video cameras. This means that Windows 10 users can now stream from HTTP and HTTPS.
TeamTalk SDK Standard Edition can now connect to encrypted TeamTalk servers. Running an encrypted TeamTalk server, however, still requires TeamTalk SDK Professional Edition.
TeamTalk SDK Standard Edition can now stream HTTPS on macOS, Android and Linux.
TeamTalk SDK Standard Edition now requires libssl dependency (OpenSSL).
OPUS_CODEC upgraded to v1.3 on all platforms.
Record in MP3 format when using TT_SetUserMediaStorageDir() and TT_StartRecordingMuxedAudioFile().
nLoginDelayMSec to ServerPropertiesszAccessToken to ServerPropertiesFixed DesktopInput not being received in encrypted mode.
The transmitUsers array of Channel now also applies to CHANNEL_DEFAULT but unlike a channel of type CHANNEL_CLASSROOM the transmitUsers array contains the user ID of those who cannot talk. Basically the opposite of classrooms.
The following new macros have been introduced to access the transmitUsers array:
StreamType enumeration now contains:
UserRight enumeration now contains:
uBanTypes to BannedUser.abusePrevent to UserAccount.Fixed severe crash issue when audio streams are stopped. Crash was due to a race condition which occurs in rare cases.
In order to record conversations using TT_StartRecordingMuxedAudioFile() it has previously been required to initialize a real sound output device in order to process audio packets. It is still required to initialize the sound output device but now a new virtual sound device is available which processes audio packets. This virtual sound device has ID TT_SOUNDDEVICE_ID_TEAMTALK_VIRTUAL.
A new feature of the CHANNEL_SOLO_TRANSMIT channel type is that the server ensures that only one user can transmit audio and media files to the channel. The user's position in the transmission queue can be seen in Channel's transmitUsersQueue array.
The server API can now intercept when a user requests to change nickname or change status. This is done by calling TTS_RegisterUserChangeNicknameCallback() and TTS_RegisterUserChangeStatusCallback().
The TeamTalk SDK v5.2b introduced static linking of all dependencies in libTeamTalk5Pro.so but this caused problems when linking an application that already included an OpenSSL dependency. Therefore the Linux distributions now again requires that the user installs the required OpenSSL dependency. To see what OpenSSL dependency is missing run:
$ ldd Library/TeamTalk_DLL/libTeamTalk5Pro.so
The SDK's Server folder now includes daemon scripts for Debian (/etc/init.d) and systemd based Linux distributions.
transmitUsersQueue of Channel struct.Added TTS_SendTextMessage() to TeamTalk Server API.
nChannelID not being set in User-struct when using TeamTalk Server API.The server API has been updated in this release so it's possible to restrict logins to your TeamTalk server to only your own client application. If the "normal" TeamTalk client tries to connect to your TeamTalk server then it will be possible to reject it.
To limit access to your TeamTalk server you can use the szSystemID parameter of TT_StartServerSysID(). When a client has to connect then the chosen system-ID will also have to passed to TT_ConnectSysID(). If it's not then the connecting TeamTalk client will receive the CMDERR_INCOMPATIBLE_PROTOCOLS. The szSystemID of the default TeamTalk application is "teamtalk". This is what you see when you connect with Telnet on port TCP port 10333 (non-encrypted).
On top of the system-ID restriction it's now also possible to do a check on the client name connecting by using the extended TT_DoLoginEx(). When a client tries to connect to a TeamTalk server you can then check the szClientName property of User to ensure only your client application is allowed to connect.
Audio device "Voice-Processing I/O Unit" added as sound device ID 1 on iOS. The Voice-Processing I/O Unit sound device is designed to eliminate echo when using speaker output and also enable automatic gain control. Read more on audio units here: https://developer.apple.com/library/ios/documentation/MusicAudio/Conceptual/AudioUnitHostingGuide_iOS/UsingSpecificAudioUnits/UsingSpecificAudioUnits.html
The video capture API on Linux has been updated to it now uses V4L2 instead of the obsolete V4L API.
The previously used video capture API, QTkit, on Mac OS has been replaced by AVFoundation. Apple's AppStore doesn't accept apps which link to QTkit, so therefore this replacement was nescessary.
Previous releases of TeamTalk 5 shared library depended on WebM (libvpx), Speex (libspeex), OPUS (libopus), etc. Now this has been limited to C++ standard library (libstdc++) and ALSA (libasound).
The Speex sound preprocessing library (SpeexDSP) is now also supported on iOS platforms.
The SpeexDSP-struct is used by TT_SetSoundInputPreprocess() and TT_StartSoundLoopbackTest().
Previously the TeamTalk sample application (TeamTalkAndroid) was using Eclipse but this project has now been converted to Android Studio 2.0.
When storing audio to files it's now possible to specify AFF_CHANNELCODEC_FORMAT which is part of the enumeration AudioFileFormat. The AFF_CHANNELCODEC_FORMAT will store in the audio format configured by a Channel's AudioCodec.
Added nEncodeDeadline to WebMVP8Codec which specifies quality of the video encoder. Values are WEBM_VPX_DL_REALTIME, WEBM_VPX_DL_GOOD_QUALITY and WEBM_VPX_DL_BEST_QUALITY.
Added szClientName to User-struct. The client name is specified in TT_DoLoginEx().
If using TeamTalk 5 SDK Professional then a System-ID can be used to limit access to the TeamTalk server to a single client application.
Use the TeamTalk server API to setup a server with a System-ID, i.e. TTS_StartServerSysID() and then use TT_ConnectSysID().
The TeamTalk C-API DLL has been moved to Library/TeamTalk_DLL The TeamTalk .NET DLL project has been moved to Library/TeamTalk.NET. The TeamTalk JNI DLL has been moved to Library/TeamTalkJNI.
This file layout change has been made so the projects are more aligned with TeamTalk 5 on GitHub.
TeamTalk 5 for iOS application (TeamTalk for iOS (iTeamTalk)) from App Store now included with TeamTalk 5 SDKs for iOS.
TeamTalk 5 Professional SDK now includes TeamTalk 5 Java server sample application (jTeamTalkServer).
TeamTalk 5 iOS SDKs can now be compiled with "Enable Bitcode" (-fembed-bitcode).
Sound device 1 (speaker output) removed from TeamTalk iOS SDK when calling TeamTalk.GetSoundDevices(). Instead use iOS's function AVAudioSession.setMode().
Server API callback UserCreateUserAccountCallback changed so UserAccount is const.
A quite severe bug which caused files on the server to end up in the wrong channels has been fixed in this minor release. The issue only affects the standalone servers which are included in the SDK. Custom servers created by the TeamTalk server API should not be affected.
Previously it has only been possible to record own audio streams by subscribing to them. Now it's, however, possible to call TT_SetUserMediaStorageDir() with user ID 0 to record own audio stream.
Windows developers can now also use Java for client development. The TeamTalk JNI DLL is located in Library/Java/TeamTalkJNI.
The inclusion of the TeamTalk Server API has caused quite a bit of reorganization of the TeamTalk SDK's file layout. Previously the TeamTalk DLL only allowed client operations and was therefore located in the Client folder. Now that the TeamTalk DLL (in the Professional edition) also allows users to develop a TeamTalk server then the core TeamTalk library projects have been moved to the Library folder in the root of the SDK.
Library
C-API
Java
NET
Documentation
C-API
Java
NET
Examples
C-API
Java
NET
Server
Demo Client
The TeamTalk 5 Professional Edition now includes a TeamTalk Server API which enables developers to instantiate a TeamTalk server by calling the TeamTalk DLL. With the server API it's possible to do basic operations like authentication users and updating server properties.
Note that the TeamTalk server API is currently only supported in the TeamTalk C-API DLL.
Now that the TeamTalk SDK is also available for Android the Java API used for Android development has also been ported to Linux and Mac OS X.
Java is supported by using a new TeamTalk DLL with a Java Native Interface (JNI). The TeamTalk JNI DLL is located in Library/Java/TeamTalkJNI.
Open the Java documentation to see how to use the new Java API. The Java TeamTalk classes greatly ressemble the .NET classes therefore the API documentation for Java is the same as .NET. Hopefully this doesn't cause too much confusion.
The iOS platform is now also supported by the TeamTalk DLL. Please refer to TeamTalk DLL on iOS on how to use the TeamTalk DLL on iOS.
In TeamTalk 4 events were posted in a TTMessage containing a WPARAM and LPARAM where the WPARAM would typically contain an ID and the LPARAM some extended information about the event. When an event occured the client application would query the TeamTalk client instance to extract information about what had changed to the current state. Since the client instance was running in its own thread the state change could, however, have become unknown in the meantime. If e.g. a text message was received from a user and the user would immediately quit afterwards then the text message would be lost since the text message was "attached" to the user who was no longer there. In TeamTalk 5 a TTMessage now contains a copy of what changed as a cause of the event. If e.g. a text message is received from a user then the TTMessage will contain a full copy of the TextMessage which was received. Also if a new channel is created then it's no longer required to extract the Channel object through the TeamTalk client instance (using TT_GetChannel()) now the new channel is part of the TTMessage using the TTMessage's data container.
Theora video codec was used in TeamTalk 4 to encode video from webcam and media files but this has now been replaced by the more recent Google-backed WebM codec. Check out WebM website for more information about the new video codec. Currently it's only possible to configure the bitrate in the codec but should you need access to more codec configuration options then feel free to request these.
CELT is no longer being developed and has been replaced by OPUS. Check out OPUS website for more information.
TeamTalk 4 used Blowfish for encrypting audio, video and desktop sharing streams. TeamTalk 5 uses AES 256-bit for encrypting audio, video, media file and desktop sharing streams.
In TeamTalk 4 streaming a media file would replace voice input from microphone and video from a media file would replace webcam input. In TeamTalk 5 a new stream type for media files has been introduced so it's still possible to talk and show webcam video while streaming a media file to a channel.
In TeamTalk 4 all users of the default user type had the same user rights on the server which were set up in ServerProperties. The user rights (UserRight) are now part of UserAccount so each user can have different UserRights on the server.
The maximum bitrate for audio codecs where global to all users in TeamTalk 4 but now the maximum bitrate a user can use for a new channel is configured in the UserAccount.
TeamTalk 4 supported 65000 active channels/rooms but in TeamTalk 5 only 4000 channels are supported. This limited has been implemented to reduce bandwidth usage.
TeamTalk 5 doesn't support P2P connections since the 'forward through server' is required for desktop sharing to work.
In TeamTalk 4 is was not possible to update a channel's name but this is now supported. Ensure to update szInitChannel of UserAccount if you use this feature.
The TeamTalk 5 Linux server now includes a daemon script which can be put in /etc/init.d on Debian to start/stop the TeamTalk daemon (with -d option).
If a Channel was configured with an AudioConfig in TeamTalk 4 then the client instance would automatically enable this audio configuration. This is no longer the case in TeamTalk 5. Now the client application must invoke TT_SetSoundInputPreprocess() manually.
The default name for the server xml configuration file was tt4svc.xml in TeamTalk 4 but in TeamTalk 5 it's now tt5srv.xml and tt5prosrv.xml for the Professional edition.
ServerStatistics now includes the number of users served, the highest number of users and server's uptime.
The TeamTalk server in the Professional SDK (tt5prosrv) now also supports non-encrypted mode. Whether to run in encrypted or non-encrypted mode is configured when running the setup wizard. See more in TeamTalk Server Setup Guide.
FileInfo.inputSampleRates and outputSampleRates replaced by supportedSampleRates due to change of TT_GetSoundDevices() instead of TT_GetSoundInputDevices() and TT_GetSoundOutputDevices().nStreamID. Stream ID changes whenever push-to-talk or voice activation are toggled.captureFormats renamed to videoFormats.nCaptureFormatsCount renamed to nVideoFormatsCount.szFileName.frameBuffer with pointer to data and nFrameBufferSize with size of bffer.nMSecPerPacket to nTxIntervalMSec.bUseJitterBuffer.nMSecPerPacket to nTxIntervalMSec.nQualityVBR to nQuality.bUseJitterBuffer.celt and celt_vbr.opus, i.e. OpusCodec.theora.webm_vp8.szServerPasswd. Only valid UserAccount is required now.uUserRights. Now part of UserAccount.nAduioCodecBpsLimit. Now part of UserAccount.nMaxVideoTxPerSecond replaced by nMaxVideoCaptureTxPerSecond.nMaxMediaFileTxPerSecond.nVideoBytesTX replaced by nVideoCaptureBytesTX.nVideoBytesRX replaced by nVideoCaptureBytesRX.nMediaFileBytesTX.nMediaFileBytesRX.nUsersServed.nUsersPeak.nFilesTx.nFilesRx.uUserRights. See User rights now moved to user account.nAudioCodecBpsLimit. See Audio codec bitrate limit moved to user account.nVolumeVoice.nVolumeMediaFile.nGainLevelVoice.nGainLevelMediaFile.nStoppedDelayVoice.nStoppedDelayMediaFile.soundPositionVoice.soundPositionMediaFile.stereoPlaybackVoice.stereoPlaybackMediaFile.nBufferMSecVoice nBufferMSecMediaFile.szAudioFolder to szMediaStorageDir uAFF. Format in CLIENTEVENT_USER_RECORD_MEDIAFILE.szAudioFileName. File name in CLIENTEVENT_USER_RECORD_MEDIAFILE.nAudioPacketsRecv replaced by nVoicePacketsRecv.nAudioPacketsLost replaced by nVoicePacketsLost.nVideoPacketsRecv replaced by nVideoCapturePacketsRecv.nVideoFramesRecv replaced by nVideoCaptureFramesRecv.nMediaFileAudioPacketsRecv.nMediaFileAudioPacketsLost.nMediaFileVideoPacketsRecv.nMediaFileVideoFramesRecv.nMediaFileVideoFramesLost.nMediaFileVideoFramesDropped.nUserData.transmitUsers.codec to audiocodec.voiceUsers. Use transmitUsers instead.videoUsers. Use transmitUsers instead.desktopUsers. Use transmitUsers instead.voiceUsers. Use transmitUsers instead.nStatus.CELTCodec
TheoraCodec
FileInfo CaptureFormat TransmitType USERRIGHT_DOUBLE_LOGIN replaced by USERRIGHT_MULTI_LOGIN.USERRIGHT_CLIENT_BROADCAST replaced by USERRIGHT_TEXTMESSAGE_BROADCAST.USERRIGHT_FORWARD_AUDIO replaced by USERRIGHT_TRANSMIT_VOICEUSERRIGHT_FORWARD_VIDEO replaced by USERRIGHT_TRANSMIT_VIDEOCAPTUREUSERRIGHT_FORWARD_DESKTOP replaced by USERRIGHT_TRANSMIT_DESKTOPUSERRIGHT_FORWARD_DESKTOPINPUT replaced by USERRIGHT_TRANSMIT_DESKTOPINPUTUSERRIGHT_CHANNEL_CREATION. See User rights now moved to user account.USERRIGHT_CHANNEL_OPERATORS.USERRIGHT_CHANNEL_COMMANDS.USERRIGHT_SUBSCRIPTIONS. Subscriptions are now mandatory.USERRIGHT_STRICT_UTF8. UTF-8 is now mandatory.SUBSCRIBE_AUDIO replaced by SUBSCRIBE_VOICE.SUBSCRIBE_VIDEO replaced by SUBSCRIBE_VIDEOCAPTURE.SUBSCRIBE_INTERCEPT_AUDIO replaced by SUBSCRIBE_INTERCEPT_VOICE.SUBSCRIBE_INTERCEPT_VIDEO replaced by SUBSCRIBE_INTERCEPT_VIDEOCAPTURE.USERSTATE_TALKING replaced by USERSTATE_VOICE.USERSTATE_MUTE replaced by USERSTATE_MUTE_VOICE.USERSTATE_VIDEO replaced by USERSTATE_VIDEOCAPTURE.USERSTATE_MUTE_MEDIAFILE.USERSTATE_MEDIAFILE_AUDIO.USERSTATE_MEDIAFILE_VIDEO.USERSTATE_MEDIAFILE.CHANNEL_STATIC replaced by CHANNEL_PERMANENT.CHANNEL_ECHO. Use SUBSCRIBE_VOICE instead.CHANNEL_ECHO_AUDIO. Use SUBSCRIBE_VOICE instead.CHANNEL_ECHO_VIDEO. Use SUBSCRIBE_VIDEOCAPTURE instead.CHANNEL_ECHO_DESKTOP. Use SUBSCRIBE_DESKTOP instead.CMDERR_INCORRECT_SERVER_PASSWORD.CMDERR_CANNOT_CREATE_CHANNELS.CMDERR_SUBSCRIPTIONS_DISABLED.CMDERR_SERVER_HAS_USERS.CLIENT_TX_AUDIO replaced by CLIENT_TX_VOICE.CLIENT_TX_VIDEO replaced by CLIENT_TX_VIDEOCAPTURE.CLIENT_SNDINPUT_DENOISING.CLIENT_P2P_AUDIO. See Peer to peer support has been removed.CLIENT_P2P_VIDEO. See Peer to peer support has been removed.CLIENT_P2P. See Peer to peer support has been removed.CLIENT_SNDINPUT_AEC.CLIENT_SNDINPUT_AGC.AudioFileStatus uUserState changed.WM_TEAMTALK_CON_SUCCESS WM_TEAMTALK_CON_FAILED WM_TEAMTALK_CON_LOST WM_TEAMTALK_CMD_PROCESSING WM_TEAMTALK_CMD_MYSELF_LOGGEDIN WM_TEAMTALK_CMD_MYSELF_LOGGEDOUT WM_TEAMTALK_CMD_MYSELF_JOINED WM_TEAMTALK_CMD_MYSELF_LEFT WM_TEAMTALK_CMD_MYSELF_KICKED WM_TEAMTALK_CMD_USER_LOGGEDIN WM_TEAMTALK_CMD_USER_LOGGEDOUT WM_TEAMTALK_CMD_USER_UPDATE WM_TEAMTALK_CMD_USER_JOINED WM_TEAMTALK_CMD_USER_LEFT WM_TEAMTALK_CMD_USER_TEXTMSG WM_TEAMTALK_CMD_CHANNEL_NEW WM_TEAMTALK_CMD_CHANNEL_UPDATE WM_TEAMTALK_CMD_CHANNEL_REMOVE WM_TEAMTALK_CMD_SERVER_UPDATE WM_TEAMTALK_CMD_FILE_NEW WM_TEAMTALK_CMD_FILE_REMOVE WM_TEAMTALK_CMD_ERROR WM_TEAMTALK_CMD_SUCCESS WM_TEAMTALK_USER_TALKING WM_TEAMTALK_USER_VIDEOFRAME WM_TEAMTALK_USER_AUDIOFILE WM_TEAMTALK_INTERNAL_ERROR WM_TEAMTALK_VOICE_ACTIVATION WM_TEAMTALK_HOTKEY WM_TEAMTALK_HOTKEY_TEST WM_TEAMTALK_FILETRANSFER WM_TEAMTALK_USER_AUDIOBLOCK WM_TEAMTALK_USER_DESKTOPWINDOW WM_TEAMTALK_DESKTOPWINDOW_TRANSFER WM_TEAMTALK_USER_DESKTOPCURSOR WM_TEAMTALK_CON_MAX_PAYLOAD_UPDATED WM_TEAMTALK_STREAM_AUDIOFILE_CHANNEL TT_StartStreamingAudioFileToUser() replaced by TT_StartStreamingMediaFileToChannel()WM_TEAMTALK_STREAM_MEDIAFILE_CHANNEL WM_TEAMTALK_USER_DESKTOPINPUT WM_TEAMTALK_STREAM_AUDIOFILE_USER WM_TEAMTALK_CON_P2P
TT_GetSoundInputDevices and TT_GetSoundOutputDevices.TT_SetAGCSettings and TT_GetAGCSettings.TT_GetAGCSettings.TT_EnableTransmission.TT_EnableTransmission.TT_EnableTransmission.TT_GetUserVideoFrame and TT_AcquireUserVideoFrame.TT_ReleaseUserVideoFrame.TT_GetChannelFileInfo TT_SetUserStoppedTalkingDelay TT_SetUserMediaBufferSize HWND message identifier.lpTTInstance parameter.lpVideoCodec parameter.lpBitmap and nBitmapSize are now part of DesktopWindow.nUserID parameter. All in channel will receive.bEncrypted parameter.bEncrypted parameter.szServerPassword removed. User account mandatory in TeamTalk 5.lpUserIDs replaced by lpUsers parameter.lpUserIDs replaced by lpUsers parameter.lpFileInfos replaced by lpRemoteFiles lpChannelIDs replaced by lpChannels.nStreamType parameter.nStreamType parameter.nUserID and nStreamType.lpAudioBlock parameter. Now returns AudioBlock.TT_GetSoundInputDevices TT_GetSoundOutputDevices TT_StartSoundLoopbackTestEx() TT_SetUserGainLevel TT_EnableAGC TT_EnableEchoCancellation TT_SetAGCSettings TT_GetAGCSettings TT_EnableDenoising TT_SetDenoiseLevel TT_GetDenoiseLevel TT_GetUserVideoFrame TT_AcquireUserVideoFrame TT_ReleaseUserVideoFrame.TT_EnableTransmission TT_IsTransmitting TT_StartStreamingAudioFileToUser TT_StopStreamingAudioFileToUser TT_StartStreamingAudioFileToChannel TT_StopStreamingAudioFileToChannel TT_SetUserAudioFolder TT_GetUserDesktopCursor TT_GetUserDesktopInput TT_ConnectNonEncrypted TT_SetKeepAliveInterval() TT_GetKeepAliveInterval() TT_SetServerTimeout TT_GetServerTimeout TT_EnablePeerToPeer
TT_GetStatistics TT_GetPacketSize TT_GetServerStatistics TT_GetChannelFileInfo() TT_GetTextMessage() TT_GetUserVolume nVolumeVoice in User instead.TT_GetUserGainLevel nGainLevelVoice in User instead.TT_SetUserStoppedTalkingDelay TT_GetUserStoppedTalkingDelay nStoppedDelayVoice in User instead.TT_GetUserPosition soundPositionVoice in User instead.TT_GetUserStereo uUserState in User instead.TT_SetUserMediaBufferSize TT_ReleaseAllAudioBlocks The TeamTalk 4 SDK is now also available for Mac OS X 64-bit.
Released on 2014/07/20.
The TeamTalk server now also includes -l command line argument for specifying the location of the log-file. Previously only the -wd argument could be used for changing the location of the log file.
The log-file of the TeamTalk server now also includes entries for when a user acount is added or deleted and also a log entry for when users are moved between channels.
Released on 2014/02/20.
Shared desktops can now be controlled remotely using mouse and keyboard input. Check out Remote Desktop Access to read on how to control remote desktops.
WM_TEAMTALK_USER_DESKTOPINPUT USERRIGHT_FORWARD_DESKTOPINPUT TT_GetUserDesktopInput Released on 2013/05/13.
Previously it's only been possible to stream 16-bit signed PCM wave-files to a channel but in the 4.5 release it's now possible to stream mp3, mpg, avi, wma, wmv, etc. to a channel. On Windows you can basically stream whatever Windows Media Player can play to a channel. Checkout TT_StartStreamingMediaFileToChannel() for more information.
To prevent a brute force login attempt it's now possible to limit the number of login attempt before banning an IP-address. Checkout nMaxLoginAttempts property of ServerProperties. It's now also possible to limit the number of logins per IP-address by specifying nMaxLoginsPerIPAddress in ServerProperties.
Previously it was only possible to ban a user's IP-address if the user was present on the server. Now it's, however, possible to ban an IP-address using TT_DoBanIPAddress().
nMaxLoginAttempts nMaxLoginsPerIPAddress WM_TEAMTALK_STREAM_MEDIAFILE_CHANNEL Released on 2012/10/15.
Windows Audio Session is a new sound system available in Windows Vista and later versions of Windows. It's a sound system which provides significantly lower latency than both DirectSound and Windows default sound devices. Check out SOUNDSYSTEM_WASAPI for more information.
When the TeamTalk client is initially start it scan the system for all sound devices but if a user later plugs in a USB sound card then this device will not be detected automatically in TT_GetSoundInputDevices() and TT_GetSoundOutputDevices().
TT_RestartSoundSystem() can now be used to shut down the sound systems can rescan for new devices.
If a sound card doesn't support the sampling rate of a codec or if the codec requires stereo input then TeamTalk now automatically resamples audio so it fits the proper format. DirectSound e.g. had problems with input devices which only allowed mono and therefore couldn't be used with stereo codecs.
A new channel type, CHANNEL_OPERATOR_RECVONLY, has now also been introduced which only allowed administrators and operators of a channel to receive audio and video. This can be useful if bandwidth is a problem.
The client in the TeamTalk 4 Professional Edition can now also connect to non-encrypted TeamTalk server. Use TT_ConnectNonEncrypted() to do this.
VideoCaptureDevice now shows the name of the video device in Unicode on Windows.
SOUNDSYSTEM_WASAPI nDefaultSampleRate USERRIGHT_STRICT_UTF8 Released on 2012/03/26.
The major new feature in the 4.3 release is the ability to share desktop applications. When sharing a desktop application you send a bitmap, using TT_SendDesktopWindow(), to the local client instance. The bitmap is then split into in small blocks and transmitted to the server using the UDP connection. Read more about this feature in the section Desktop Sharing.
A UserAccount now has the szInitChannel property which holds the channel a user should join after login. The user can join this channel without passing a password. Use TT_GetMyUserAccount() to get the local instance's UserAccount after login has completed.
A user can automatically become operator of a Channel configured with CHANNEL_STATIC if the channel's ID is in the autoOperatorChannels property of UserAccount.
An extra message type has been added for custom messages. The MSGTYPE_CUSTOM works in the same way as MSGTYPE_USER.
Some routers don't allow UDP packets over a given size so use TT_QueryMaxPayload() after connecting to a server to detect the maximum size for UDP packets. The event WM_TEAMTALK_CON_MAX_PAYLOAD_UPDATED is triggered when the client instance has finished querying.
The raw audio, which has been playing when a user is talking, can now be accessed by calling TT_EnableAudioBlockEvent(). The event WM_TEAMTALK_USER_AUDIOBLOCK is triggered when a new AudioBlock is available.
If audio files are being recorded separately for every User, using TT_SetUserAudioFolder, the file name of the file currently being recorded to can be found in the szAudioFileName property of the User struct.
To cancel and start recording to a new audio file pass AFF_NONE as parameter to TT_SetUserAudioFolder. This will reset the current recording and generate the WM_TEAMTALK_USER_AUDIOFILE event.
A Channel can now be configured using the CHANNEL_ECHO_VIDEO flag for echoing the video stream transmitted by the local client instance.
A Channel configured using CHANNEL_CLASSROOM was previously limited to 16 people transmitting either video or audio. Now it's, however, possible to add TT_CLASSROOM_FREEFORALL to the "enabled" users properties to allow everyone to transmit.
TT_SetUserAudioFolder uAFF parameterTT_GetUserDesktopWindow() TT_GetUserDesktopCursor() desktopUsers nDesktopBytesSent nDesktopBytesRecv szMOTDRaw nMaxDesktopTxPerSecond.szInitChannel autoOperatorChannels uAFF szAudioFileName WM_TEAMTALK_USER_AUDIOBLOCK WM_TEAMTALK_USER_DESKTOPWINDOW WM_TEAMTALK_DESKTOPWINDOW_TRANSFER WM_TEAMTALK_USER_DESKTOPCURSOR WM_TEAMTALK_CON_MAX_PAYLOAD_UPDATED CHANNEL_ECHO_AUDIO CHANNEL_ECHO_VIDEO CHANNEL_ECHO_DESKTOP USERSTATE_VIDEO USERRIGHT_FORWARD_DESKTOP.Released on 2011/11/02.
It is now possible to store "muxed" audio files, i.e. audio from all users are written to the same audio file. Check out TT_StartRecordingMuxedAudioFile() on how to do this.
The Windows Firewall, included in XP and later Windows versions, can sometimes block network traffic to and from applications which uses the TeamTalk DLL. Check out the section Windows Firewall on how to use the Windows Firewall functions.
Voice activation is by default disabled if no audio has reached the voice activation level for 1.5 seconds. This option can now be changed by calling TT_SetVoiceActivationStopDelay(). Also users who are talking are set to non-talking after 0.5 seconds if no new voice data has been received. This value can now be changed by calling TT_SetUserStoppedTalkingDelay().
Speex and CELT can now be used in VBR mode by creating a Channel with the SpeexVBRCodec or CELTVBRCodec. To limit bandwidth usage it is advised to use the VBR codecs. Especially the Speex VBR codec with DTX enabled reduces throughput when there's silence.
CELT 0.5.2, which was used in v 4.1 and previous of the SDK, has been replaced by CELT 0.11. Note that encoding and decoding of CELT 0.5.2 is no longer supported. Check out http://www.celt-codec.org
Client and server now support IPv6. To make the server run in IPv6 mode the server must bind to an IPv6 address. Check out Configurating the TeamTalk Server on how to specify the bind IP-address (<bind-ip> tag).
Note that the TeamTalk DLL can no longer run on Windows 2000 since this platform does not support IPv6.
TT_SetUserStoppedTalkingDelay() TT_GetUserStoppedTalkingDelay() CELTCodec struct updated for CELT 0.11.CELTVBRCodec struct for CELT VBR.CELT_0_5_2_OBSOLETE_CODEC, SPEEX_VBR_CODEC, CELT_CODEC and CELT_VBR_CODEC.nAudioCodecBpsLimit, nMaxAudioTxPerSecond, nMaxVideoTxPerSecond and nMaxTotalTxPerSecond.nUptimeMSec.Support for "talking callback" by function pointer has been removed since it's causing problems with threads (typically UI vs. TT-threads).
TT_RegisterTalkingCallback TT_UnregisterTalkingCallback Released on 2010/10/30.
The new features in the TeamTalk 4 SDK v. 4.1a has are described in the following subsections.
Mac OS X is now supported using the C-API DLL which is compiled for i386 and uses QuickTime for video and CoreAudio for audio. Windows Mobile support is now also supported using both the C-API DLL and the .NET Framework DLL. Note, however, that the Windows Mobile is only supported in the Standard SDK and not the Professional SDK since OpenSSL is quite tricky to port to Windows Mobile.
When initializing the client instance's sound system in duplex mode it is now possible to enable echo cancellation. Note, however, that echo cancellation performs poorly on Windows whereas it's very effective on Mac OS X and Linux. Check out TT_InitSoundDuplexDevices() and TT_EnableEchoCancellation() on how to use echo cancellation.
A new channel-type called classroom has now been introduced where the channel's operator can control who is allowed to transmit audio and video to a channel. The channel operator can then work as sort of a teacher where the teacher selects the people who should answer questions. Check out CHANNEL_CLASSROOM for how to create classroom channels.
Often users have set their microphones to different audio levels so it's hard to hear certain users and others are too loud. When creating a channel it's now possible to use Channel's audiocfg member to set the same audio level for all users. Note that all users must use the v. 4.1a release for this to work.
Administrators can now query a server statistics using the command TT_DoQueryServerStats() and thereby get an overview of bandwidth usage.
Using TT_GetUserVideoFrame() is quite tricky to use since the developer must first query for how much memory must be allocated to store the video frame. In this new release it's possible to share memory with the client instance so one simply calls TT_AcquireUserVideoFrame() to get a pointer to a user's video data. when one has completed using the video frame call TT_ReleaseUserVideoFrame() to release the shared memory. Note that only one video frame can be extracted each time, therefore calling TT_AcquireUserVideoFrame() twice will simply result in getting the same video frame.
WM_TEAMTALK_CMD_SUCCESS TT_StartSoundLoopbackTestEx() TT_EnableDenoising() is enabled.TT_GetDenoiseLevel() TT_SetDenoiseLevel().TT_EnableEchoCancellation() TT_AcquireUserVideoFrame() TT_ReleaseUserVideoFrame() to release the memory referenced in the VideoFrame.TT_ReleaseUserVideoFrame() Released on 2010/03/16.
The new features in the TeamTalk 4 SDK v. 4.0c has are described in the following subsections.
The UserAccount struct now has a new member called szNote which can contain extra information about a user account. The UserAccount and User structs now also has a nUserData integer field which can be used by developers to store an application specific value. After a successful login the nUserData field on UserAccount will be transferred to the nUserData field on the User struct.
After login it's now possible to retrieve one's own UserAccount by calling TT_GetMyUserAccount(). TT_GetMyUserData() can be used to extract one's nUserData of one's UserAccount.
HWND for eventsWhen using TT_InitTeamTalk() a HWND is passed which is used for event handling. If at some point another HWND should be used for event handling this HWND can be swapped using TT_SwapTeamTalkHWND().
All users who are connected to a server can now be retrieved using TT_GetServerUsers().
The folder for audio storage has now been placed in User instead of on Channel. Audio storage is therefore user specific now instead of channel specific.
Renamed/modified functions:
TT_SetChannelAudioFolder TT_SetUserAudioFolder instead.Here a list of bugs fixed in this release:
Released on 2009/11/23.
The new features in the TeamTalk 4 SDK v. 4.0a has are described in the following subsections.
TeamTalk can now capture video from webcams and encode it for transmission. Bandwidth usage can be as low as a 2-3 KBytes/sec in low resolutions. High resultions are, of course, also supported.
To start using the new video features checkout the following new functions:
WM_TEAMTALK_USER_VIDEOFRAME event.TT_EnableTransmission to transmit video data.The TeamTalk server can now be set to only allow users to log on if they have a user account on the server. The user account also introduces user types, so some users can have administrator capabilities.
Read the section Configurating the TeamTalk Server on how to configure the server with user accounts. To see the new functions in the TeamTalk DLL for handling user accounts check out the following new functions:
When calling any of the client to server commands listed in section Client/Server Commands a command ID is returned to the user application. This command ID can be used to track when the server has started and finished processing the command using the WM_TEAMTALK_CMD_PROCESSING event.
The TeamTalk client now has better support for peer to peer data transmission and can now penetrate most NAT devices.
Check out section REMOVED for more information on P2P networking. P2P networking is enabled using the following functions:
TT_EnablePeerToPeer to enable/disable peer to peer connections.TeamTalk now not only supports the Speex codec, but also the CELT codec. The CELT codec gives much better audio quality but also requires higher bandwidth usage. If a user application is used to transmit music it is advised to use CELT since the sound quality will be must better than Speex. Speex is mainly for voice transmissions. Check out section Audio and Video Codecs to read more about the new codec.
Also note that the audio codec used by a client is now configured on a Channel and not on each individual client. This means that all users in a channel must now use the same audio settings. This restriction has been set to support echo-cancellation which is on the Known Issues.
This section outlines how TeamTalk 3 developers can adapt their existing applications to TeamTalk 4.
Renamed/modified functions:
TT_GetDefaultDevices TT_GetInputDevicesCount TT_GetSoundInputDevices instead.TT_GetInputDevice TT_GetSoundInputDevices instead.TT_GetOutputDevicesCount TT_GetSoundOutputDevices instead.TT_GetOutputDevice TT_GetSoundOutputDevices instead.TT_LaunchSoundSystem TT_IsSoundSystemInitialized TT_ShutdownSoundSystem TT_RestartSoundSystem TT_GetCurrentInputLevel TT_SetMasterVolume TT_GetMasterVolume TT_MuteAll TT_IsAllMute TT_IsDenoising CLIENT_SNDINPUT_DENOISING instead.TT_SetVoiceGainLevel TT_GetVoiceGainLevel TT_IsVoiceActivated TT_EnableAutoPositioning TT_IsConnected TT_IsConnecting TT_IsAuthorized TT_SetTcpKeepAliveInterval TT_SetKeepAliveInterval instead.TT_GetTcpKeepAliveInterval TT_GetKeepAliveInterval instead.TT_DoChangeNick TT_DoUserMessage TT_DoChannelMessage TT_GetMessageOfTheDay TT_GetServerName TT_GetChannelParentID TT_GetChannelMessage TT_GetTextMessage instead.TT_GetBroadcastMessage TT_GetTextMessage instead.TT_GetUserMessage TT_GetTextMessage instead.TT_IsUserMute USERSTATE_MUTE in uUserState of User-struct.TT_IsUserTalking USERSTATE_TALKING in uUserState of User-struct.TT_ForwardToAll TT_EnablePeerToPeer with parameter to false (the default setting).TT_IsForwardingToAll CLIENT_P2P is no enabled.TT_GetBytesReceived TT_GetStatistics instead.TT_GetBytesSent TT_GetStatistics instead.TT_StartTransmitting TT_EnableTransmission instead.TT_StopTransmitting TT_EnableTransmission instead.TT_StartTransmittingWaveFile TT_StartStreamingAudioFileToUser or TT_StartStreamingAudioFileToChannel instead.TT_StopTransmittingWaveFile TT_StopStreamingAudioFileToUser or TT_StopStreamingAudioFileToChannel instead.TT_RegisterHotKey TT_UnregisterHotKey TT_IsHotKeyActive TT_GetChannelFilesCount TT_GetChannelFileID TT_DoUserSubscribe TT_DoUserUnsubscribe Removed functions:
TT_SetEncoderComplexity TT_GetEncoderComplexity TT_GetSamplesPerPacket TT_SetPlaybackMode TT_GetPlaybackMode TT_GetChannelUserCount Renamed/modified events:
WM_TEAMTALK_CONNECTSUCCESS WM_TEAMTALK_CON_SUCCESS instead.WM_TEAMTALK_CONNECTFAILED WM_TEAMTALK_CON_FAILED instead.WM_TEAMTALK_CONNECTIONLOST WM_TEAMTALK_CON_LOST instead.WM_TEAMTALK_ACCEPTED WM_TEAMTALK_CMD_MYSELF_LOGGEDIN instead.WM_TEAMTALK_ADDUSER WM_TEAMTALK_CMD_USER_JOINED instead.WM_TEAMTALK_UPDATEUSER WM_TEAMTALK_CMD_USER_UPDATE instead.WM_TEAMTALK_REMOVEUSER WM_TEAMTALK_CMD_USER_LEFT instead.WM_TEAMTALK_ADDCHANNEL WM_TEAMTALK_CMD_CHANNEL_NEW instead.WM_TEAMTALK_UPDATECHANNEL WM_TEAMTALK_CMD_CHANNEL_UPDATE instead.WM_TEAMTALK_REMOVECHANNEL WM_TEAMTALK_CMD_CHANNEL_REMOVE instead.WM_TEAMTALK_USERMESSAGE WM_TEAMTALK_CMD_USER_TEXTMSG instead.WM_TEAMTALK_CHANNELMESSAGE WM_TEAMTALK_CMD_USER_TEXTMSG instead.WM_TEAMTALK_KICKED WM_TEAMTALK_CMD_MYSELF_KICKED instead.WM_TEAMTALK_SERVERUPDATE WM_TEAMTALK_CMD_SERVER_UPDATE instead.WM_TEAMTALK_JOINEDCHANNEL WM_TEAMTALK_CMD_MYSELF_JOINED instead.WM_TEAMTALK_ERROR WM_TEAMTALK_CMD_ERROR instead.WM_TEAMTALK_USERTALKING WM_TEAMTALK_USER_TALKING instead.WM_TEAMTALK_USERSTOPPEDTALKING WM_TEAMTALK_USER_TALKING instead.WM_TEAMTALK_DIRCONNECTIONFAILED WM_TEAMTALK_CON_P2P instead.WM_TEAMTALK_LISTCOMMAND_COMPLETED WM_TEAMTALK_CMD_PROCESSING instead.WM_TEAMTALK_LEFTCHANNEL WM_TEAMTALK_CMD_MYSELF_LEFT instead.WM_TEAMTALK_LOGGEDOUT WM_TEAMTALK_CMD_MYSELF_LOGGEDOUT instead.WM_TEAMTALK_ADDFILE WM_TEAMTALK_CMD_FILE_NEW instead.WM_TEAMTALK_REMOVEFILE WM_TEAMTALK_CMD_FILE_REMOVE instead.WM_TEAMTALK_TRANSFER_BEGIN WM_TEAMTALK_FILETRANSFER instead.WM_TEAMTALK_TRANSFER_COMPLETED WM_TEAMTALK_FILETRANSFER instead.WM_TEAMTALK_TRANSFER_FAILED WM_TEAMTALK_FILETRANSFER instead.WM_TEAMTALK_BROADCASTMESSAGE WM_TEAMTALK_CMD_USER_TEXTMSG instead.WM_TEAMTALK_USERLOGGEDIN WM_TEAMTALK_CMD_USER_LOGGEDIN instead.WM_TEAMTALK_USERLOGGEDOUT WM_TEAMTALK_CMD_USER_LOGGEDOUT instead.WM_TEAMTALK_SOUNDDEVICE_ERROR WM_TEAMTALK_INTERNAL_ERROR instead.WM_TEAMTALK_KEYTEST WM_TEAMTALK_HOTKEY_TEST instead.WM_TEAMTALK_AUDIOFILE_STATUS WM_TEAMTALK_USER_AUDIOFILE instead.WM_TEAMTALK_STREAMFILE_COMPLETED WM_TEAMTALK_STREAM_AUDIOFILE_USER instead.WM_TEAMTALK_USER_SUBSCRIBERS_RESULT 1.10.0