In Settings > Video:
I don’t have the ability to change any of the settings below the 2 switches (• Use Cisco H264 and • Use Hardware Acceleration). I can switch both of the switches on or off, but all the other options are grayed-out. Clicking anywhere has no affect.
Any ideas, guys? Thanks in advance for any help.
Edit: Windows 11 Home
Hi maybe your hardware is not supported, what are you cpu/gpu specs?
Hi ImScheinox,
—————————————————————————–
My specs:
Intel Core i5-3230M CPU @ 2.60GHz
Cores :2
Threads :4
Instructions: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, Intel 64, NX, VMX, AES, AVX
Virtualization Supported, Enabled
Hyperthreading Supported, Enabled
Bus Speed: 99.8 MHz
Stock Core Speed: 2600 MHz
GPU’s:
Intel HD Graphics 4000
Manufacturer: Intel
Model HD Graphics 4000
Device ID: 8086-0166
it also has this GPU:
NVIDIA GeForce 710M
Device ID 10DE-1140
——————————————————————————
It’s a low-spec laptop that I’m currently using for Teamspeak.
After a little research, it looks like the hardware is too old or not in the current implementation.
Your CPU supports Intel Quicksync, but only version 1.0, and this has probably not been taken into account in the current hardware acceleration implementation of TeamSpeak.
Your GPU does not yet support NVIDIA NVENC.
That’s why everything is greyed out for you and only the software encoder/decoder is used.
I just now saw this topic:
It seems this person is experiencing the same issue, but on Linux system
Let me ask this: In the changelog in Settings > About
I see this: “Note: This release includes FFmpeg licensed under LGPLv3.0…..”
Do I have to install FFmpeg manually or is the update process supposed to include a portable version of FFmpeg in the Teamspeak installation folder?
Thanks for your quick reply.
I just added a new reply seconds after you posted your reply. Does the lack of a manual installation of FFmpeg on this system maybe contribute to the issue?
Thamks for all your help, ImScheinox
FFMPEG should be installed automatically with the update.
However, you can theoretically install your own version of ffmpeg if you see an advantage in doing so.
You’re welcome, that’s just my initial guess; I’ll look into it more thoroughly tomorrow.
Hmmm… I’m not seeing it anywhere. I am already using a portable version of FFmpeg on this system, but that’s it. I searched my system for any other FFmpegs installations/versions. Nothing. It looks like the automatic Teamspeak 6 Client update did not install FFmpeg.
Question. In the changelog it says that we can use “our own” FFmpeg if we want. How do we do that? I guessing by simply replacing the ffmpeg.exe file in a specific folder…?
Have a look on the teamspeak github here:
Thanks. I read the whole thing (github link you provided) and saw this towards the end:
”…To use in the TeamSpeak 6 Client, copy the contents of package/.../lib/ (and package/.../bin/ on Win) to your TeamSpeak installation path. Backup existing libraries if anything goes wrong.”
Ok, but exactly where do I paste it in the Teamspeak 6 Client installation directory? Can you give me the default path ffmpeg.exe needs to live? Where is it on your system?
C:\Program Files\TeamSpeak\<and then?>
You absolutely do not need to compile your own ffmpeg. TeamSpeak ships with a version that should work out of the box. And I case it doesn’t it’s more likely a driver issue than an installation problem.
Do you have the NVIDIA driver installed? It should support H264 from what I could see.
I could not find explicit information about the capabilities of the CPU media engine, but I think it should also support H264 encoding. I assume all other codecs are too new for your hardware to support accelerated encoding.
Same question, do you have the Intel video drivers installed?
Gamer92000,
It’s a low-end laptop with 2 onboard gpu’s.
Can you tell me if Teampspeak 6 installs a FFmpeg,exe somewhere on the system? I’m confused as to why the changelog says we can use our own FFmpeg if we want. In anycase, I can’t find any FFmpeg other than my portable ffmpeg.exe I use frequently on this system.
Thanks for your help.
TeamSpeak doesn’t use the ffmpeg binary but the libraries, specifically avcodec-62.dll, avfilter-11.dll, avformat-62.dll, avutil-60.dll, swresample-6.dll, and swscale-9.dll.
Thank you. Yes, they are all present in the main installation directory. Ok, so Teamspeak 6 may be registering some issue with my laptop or specs and blocking me from manually changing any codec settings. Guess there is nothing we can do.
Thanks for your help, guys.
When the client starts it tests all possible hardware acceleration options and logs some data. To log the details about this you need to enable debug logging in the developer options.
Log Level to debug and restart the client.ts5client[...].log unter %localappdata%/TeamSpeak/Logs/Default/.
With your hardware I would expect it to support h264_qsv and maybe h264_nvenc.
Thanks. Here’s the log after a restart:
\[2025-10-20 23:02:54.705\] \[info\] Notifications_Windows ctor
\[2025-10-20 23:02:54.796\] \[info\] TeamSpeak Client 6.0.0-beta3.2 (2025-10-17 09:41:09)
\[2025-10-20 23:02:54.796\] \[info\] SystemInformation: Windows 11 (26100) x64 (AMD or Intel) Binary: 64bit
\[2025-10-20 23:02:54.889\] \[debug\] CEF sandbox is disabled
\[2025-10-20 23:02:55.109\] \[debug\] WebSockets Server started successfully
\[2025-10-20 23:02:55.296\] \[debug\] Renderer is ready
\[2025-10-20 23:02:55.297\] \[debug\] Sending media stream handle to renderer
\[2025-10-20 23:02:56.296\] \[warning\] sync_event, account status change: 2
\[2025-10-20 23:02:56.563\] \[debug\] Using device 8086:0166 (Intel(R) HD Graphics 4000).
\[2025-10-20 23:02:56.623\] \[debug\] Error creating a MFX session: -9.
\[2025-10-20 23:02:56.737\] \[debug\] Using device 10de:1140 (NVIDIA GeForce 710M).
\[2025-10-20 23:02:56.781\] \[debug\] Failed to create Direct 3D 12 device (887a0004)
\[2025-10-20 23:02:56.785\] \[debug\] Using device 10de:1140 (NVIDIA GeForce 710M).
\[2025-10-20 23:02:56.820\] \[debug\] Failed to create Direct 3D 12 device (887a0004)
\[2025-10-20 23:02:56.824\] \[debug\] Using device 10de:1140 (NVIDIA GeForce 710M).
\[2025-10-20 23:02:56.857\] \[debug\] Failed to create Direct 3D 12 device (887a0004)
\[2025-10-20 23:02:56.862\] \[debug\] Using device 10de:1140 (NVIDIA GeForce 710M).
\[2025-10-20 23:02:56.894\] \[debug\] Failed to create Direct 3D 12 device (887a0004)
\[2025-10-20 23:02:56.898\] \[debug\] Using device 10de:1140 (NVIDIA GeForce 710M).
\[2025-10-20 23:02:56.912\] \[info\] Hot Reload!
\[2025-10-20 23:02:56.925\] \[debug\] Failed to create Direct 3D 12 device (887a0004)
\[2025-10-20 23:02:56.928\] \[debug\] DLL amfrt64.dll failed to open
\[2025-10-20 23:02:56.928\] \[debug\] Testing encoder av1_nvenc with device type cuda and hw pixel format cuda
\[2025-10-20 23:02:56.944\] \[debug\] Cannot load nvEncodeAPI64.dll
\[2025-10-20 23:02:56.944\] \[debug\] The minimum required Nvidia driver for nvenc is 551.76 or newer
\[2025-10-20 23:02:56.950\] \[debug\] Testing encoder av1_nvenc with device type d3d11va and hw pixel format d3d11
\[2025-10-20 23:02:56.952\] \[debug\] Could not create the texture (80070057)
\[2025-10-20 23:02:56.952\] \[debug\] Failed to initialize frames context for codec av1_nvenc with device type d3d11va
\[2025-10-20 23:02:56.952\] \[debug\] Testing encoder av1_nvenc with device type cuda and hw pixel format NONE
\[2025-10-20 23:02:56.953\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.953\] \[debug\] Testing encoder av1_nvenc with device type d3d11va and hw pixel format NONE
\[2025-10-20 23:02:56.954\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.954\] \[debug\] Codec av1_qsv does not support any hardware configurations, skipping
\[2025-10-20 23:02:56.954\] \[debug\] Testing encoder av1_amf with device type d3d11va and hw pixel format d3d11
\[2025-10-20 23:02:56.954\] \[debug\] Could not create the texture (80070057)
\[2025-10-20 23:02:56.954\] \[debug\] Failed to initialize frames context for codec av1_amf with device type d3d11va
\[2025-10-20 23:02:56.955\] \[debug\] Testing encoder av1_amf with device type dxva2 and hw pixel format dxva2_vld
\[2025-10-20 23:02:56.955\] \[debug\] Unsupported pixel format: yuv420p
\[2025-10-20 23:02:56.955\] \[debug\] Error creating an internal frame pool
\[2025-10-20 23:02:56.955\] \[debug\] Failed to initialize frames context for codec av1_amf with device type dxva2
\[2025-10-20 23:02:56.956\] \[debug\] Testing encoder av1_amf with device type d3d11va and hw pixel format NONE
\[2025-10-20 23:02:56.956\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.956\] \[debug\] Testing encoder av1_amf with device type dxva2 and hw pixel format NONE
\[2025-10-20 23:02:56.956\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.956\] \[debug\] Testing encoder h264_amf with device type d3d11va and hw pixel format d3d11
\[2025-10-20 23:02:56.957\] \[debug\] Could not create the texture (80070057)
\[2025-10-20 23:02:56.957\] \[debug\] Failed to initialize frames context for codec h264_amf with device type d3d11va
\[2025-10-20 23:02:56.958\] \[debug\] Testing encoder h264_amf with device type dxva2 and hw pixel format dxva2_vld
\[2025-10-20 23:02:56.958\] \[debug\] Unsupported pixel format: yuv420p
\[2025-10-20 23:02:56.958\] \[debug\] Error creating an internal frame pool
\[2025-10-20 23:02:56.958\] \[debug\] Failed to initialize frames context for codec h264_amf with device type dxva2
\[2025-10-20 23:02:56.959\] \[debug\] Testing encoder h264_amf with device type d3d11va and hw pixel format NONE
\[2025-10-20 23:02:56.959\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.959\] \[debug\] Testing encoder h264_amf with device type dxva2 and hw pixel format NONE
\[2025-10-20 23:02:56.960\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.960\] \[debug\] Testing encoder h264_nvenc with device type cuda and hw pixel format cuda
\[2025-10-20 23:02:56.972\] \[debug\] Cannot load nvEncodeAPI64.dll
\[2025-10-20 23:02:56.973\] \[debug\] The minimum required Nvidia driver for nvenc is 551.76 or newer
\[2025-10-20 23:02:56.976\] \[debug\] Testing encoder h264_nvenc with device type d3d11va and hw pixel format d3d11
\[2025-10-20 23:02:56.976\] \[debug\] Could not create the texture (80070057)
\[2025-10-20 23:02:56.976\] \[debug\] Failed to initialize frames context for codec h264_nvenc with device type d3d11va
\[2025-10-20 23:02:56.976\] \[debug\] Testing encoder h264_nvenc with device type cuda and hw pixel format NONE
\[2025-10-20 23:02:56.977\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.977\] \[debug\] Testing encoder h264_nvenc with device type d3d11va and hw pixel format NONE
\[2025-10-20 23:02:56.977\] \[debug\] Invalid video pixel format: -1
\[2025-10-20 23:02:56.977\] \[debug\] Codec h264_qsv does not support any hardware configurations, skipping
\[2025-10-20 23:02:56.977\] \[debug\] Codec h264_qsv does not support any hardware configurations, skipping
\[2025-10-20 23:02:56.978\] \[debug\] Testing decoder av1_cuvid with device type cuda and hw pixel format cuda
\[2025-10-20 23:02:56.989\] \[debug\] GetFormat cbk for codec av1_cuvid with device type cuda and hw pixel format cuda, sw format: nv12
\[2025-10-20 23:02:56.991\] \[debug\] Cannot load cuvidGetDecodeStatus
\[2025-10-20 23:02:56.992\] \[debug\] Failed loading nvcuvid.
\[2025-10-20 23:02:56.995\] \[debug\] Codec av1_qsv does not support any hardware configurations, skipping
\[2025-10-20 23:02:56.996\] \[debug\] Codec av1_amf does not support any hardware configurations, skipping
\[2025-10-20 23:02:56.996\] \[debug\] Codec h264_amf does not support any hardware configurations, skipping
\[2025-10-20 23:02:56.996\] \[debug\] Testing decoder h264_cuvid with device type cuda and hw pixel format cuda
\[2025-10-20 23:02:57.007\] \[debug\] GetFormat cbk for codec h264_cuvid with device type cuda and hw pixel format cuda, sw format: nv12
\[2025-10-20 23:02:57.009\] \[debug\] Cannot load cuvidGetDecodeStatus
\[2025-10-20 23:02:57.010\] \[debug\] Failed loading nvcuvid.
\[2025-10-20 23:02:57.013\] \[debug\] FFmpegCodecManager initialized in 2146ms
\[2025-10-20 23:02:57.738\] \[debug\] WAS::openDevice-enter - {0.0.0.00000000}.{71fa2fd9-7287-4df5-b660-3072c5e7395e}
\[2025-10-20 23:02:57.781\] \[info\] Initialized with 2 channels in 32bit, 48kHz. - Voicemeeter AUX Input (VB-Audio Voicemeeter VAIO)
\[2025-10-20 23:02:57.784\] \[debug\] WAS::openDevice-leave - {0.0.0.00000000}.{71fa2fd9-7287-4df5-b660-3072c5e7395e}
\[2025-10-20 23:02:57.786\] \[debug\] WAS::startDevice-enter - {0.0.0.00000000}.{71fa2fd9-7287-4df5-b660-3072c5e7395e}
\[2025-10-20 23:02:57.789\] \[debug\] WAS::startDevice-leave - {0.0.0.00000000}.{71fa2fd9-7287-4df5-b660-3072c5e7395e}
\[2025-10-20 23:02:57.790\] \[info\] set device for AudioBridge.
\[2025-10-20 23:03:24.738\] \[info\] starting download for http://update.teamspeak.com/windows/x64/latest/info.json
\[2025-10-20 23:03:25.785\] \[info\] connected to push system.
————————————————————————————————-
Quite a few issues….
Based on the logs the system does not meet our current requirements for hardware acceleration, therefore defaulting back to the software encoder / decoder.
However I’ll forward this topic to our QA / dev team to further investigate this and if HWA is possible on such old system.
Thanks, LeonMarcelHD
and to everyone else for replying to my post.
So, if I am understanding your reply correctly, in my case, Teamspeak will revert back to software encoding (CPU) by default, right? If so, which codec will it be using for screensharing, the Cisco H264 Encoder?
Thanks everyone!
If I am not mistaken yes, but only running on your CPU, rather than your GPU.
Thank you.
