48
edits
EKK:LoFi Sounds in HiFi Spaces/Making connection/TeamViewer (view source)
Revision as of 09:54, 22 April 2013
, 22 April 2013→The Software
Ludwigberger (talk | contribs) |
Ludwigberger (talk | contribs) |
||
| Line 13: | Line 13: | ||
===Setup, configuration and usability=== | ===Setup, configuration and usability=== | ||
Intricate, defective and not intuitive. | |||
- One can't easily find people without their exact Alias | - One can't easily find people without their exact Alias | ||
- To start a meeting you have to create an ID and mail this number | - To start a meeting you have to create an ID and mail this number | ||
| Line 24: | Line 24: | ||
The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations. | The control available in TeamViewer for audio is limited, but has a few important features. First, it has a variable volume, separate from that of the internal mic level control built into the OSX operating system. More interestingly, the application includes a variable noise gate, with an associated volume meter, allowing a user to easily select a threshold for a noise gate. Outside this relatively noise threshold (which appears to act as a simple gate with slightly ramped amplitude crossfade when cutting in and out) there is only a selection of input and output destinations. | ||
===Quality of Transmission=== | ===Quality of Transmission=== | ||
| Line 32: | Line 31: | ||
Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation. | Sound trip latency varied, but the clearest measured data (as our audio was generally quite poor) resulted in 590 ms roundtrip latency. This software is therefore incapable of supporting any interactive performance beyond cue-less improvisation. | ||
===Subjective experience=== | |||
It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end. | It was very difficult to start a meeting and communicate. It was a relief to switch to skype at the end. | ||