![]() ![]() So I had TeamViewer 11 installed in /opt/teamviewer/ and some important configuration files for it in ~/.local/share/teamviewer11/ and ~/.config/teamviewer/. We’re going to take some files from that installation and essentially replace TeamViewers’ own Wine with the one distributed by EPEL. I already had one that I needed for work anyway, namely Wine 1.8.6 from the repository, configured using. You absolutely need a working system-wide Wine setup for this. ![]() There are a multitude of proposed solutions to fix this, and since none of them worked for me as-is, I’d like to add my own to the mix. This may happen in cases where you upgrade TeamViewer from previous releases (which is what I had done, 7 -> 8 -> 9 -> 11). It was thus logical to assume that the configuration of TeamViewers’ built-in Wine was broken. Both its Linux and MacOS X versions come with a bundled Wine 1.6 distribution preconfigured to run the 32-bit TeamViewer Windows binary. Now, TeamViewer is actually not native Linux software. Playing back audio yielded nothing but silence though. TeamViewer does offer a feature to relay the audio from a remote machine to your local box, as long as the remote server has some kind of soundcard / sound chip installed. I was using TeamViewer 11 – the newest version at the time of writing – to connect from CentOS 6.8 Linux to a Windows 7 Professional machine. Since the stream meta data (like the language of an audio stream) wasn’t always there, I wanted to check it by playing back the files remotely in foobar2000 or MPC-HC. Basically, it was about video and audio transcoding on said machine. A few weeks ago I got TeamViewer access to a remote workstation machine for the purpose of processing A/V files however. I’m not exactly a big fan of TeamViewer, since you’ll never know what’s going to happen with that traffic of yours, so I prefer VNC over SSH instead. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |