Wi-Fi WFM icon Wi-Fi WFM: details & info copyright © 2016 Adam J. Wilt  
 
An iPhone / iPad / iPod touch waveform monitor for Teradek™ H.264 transmitters
 
 HOME   SUPPORT   CONTACT   CONTROLS   HOW TO…   FAQ   ABOUT 
(This is the old Details & Info page; you should be redirected to the new About page instead in a few seconds. Stand by...)

How It Works

Wi-Fi WFM works with the 8-bit, 4:2:0, YCbCr signal sent by your Teradek. The image is resampled to a lower-resolution version for performance reasons, and the ’scopes are calculated from that version. This means that while the ’scopes are useful for setting levels and verifying colors, some fine details of the signal may be lost or distorted as a result:



Privacy policy


Wi-Fi WFM doesn’t run any onboard analytics code and won’t collect any information from you. If you’ve enabled diagnostics on your device (Settings app > Privacy > Diagnostics & Usage > Automatically Send), Apple collects anonymized information about your usage of various apps, including crash logs. I only see aggregate information across all devices with diagnostics enabled; I can’t see any info specifically about your use of the app.

If you use the links in the app or on the contact page to send me email, I get your email address, but that’s the only way I’ll ever find out who you are!




Third-party code in Wi-Fi WFM


Wi-Fi WFM uses the Teradek SDK version 3.0.2, which includes open-source code from OpenSSL and FFmpeg projects. The SDK static library is supplied in binary form and I don't have source code. If you need to obtain the specific open-source code used in the SDK library, please contact Teradek Support.

FFmpeg legal information is available at ffmpeg.org/legal.html which says, in part,

FFmpeg is licensed under the GNU Lesser General Public License (LGPL) version 2.1 or later. However, FFmpeg incorporates several optional parts and optimizations that are covered by the GNU General Public License (GPL) version 2 or later. If those parts get used the GPL applies to all of FFmpeg.

Read the license texts to learn how this affects programs built on top of FFmpeg or reusing FFmpeg. You may also wish to have a look at the GPL FAQ.

Note that FFmpeg is not available under any other licensing terms, especially not proprietary/commercial ones, not even in exchange for payment.

OpenSSL info is at www.openssl.org/docs/faq.html.The OpenSSL implementation Teradek uses includes this notice (reproduced verbatim, including apparent typos):

 /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
 * All rights reserved.
 *
 * This package is an SSL implementation written
 * by Eric Young (eay@cryptsoft.com).
 * The implementation was written so as to conform with Netscapes SSL.
 *
 * This library is free for commercial and non-commercial use as long as
 * the following conditions are aheared to.  The following conditions
 * apply to all code found in this distribution, be it the RC4, RSA,
 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
 * included with this distribution is covered by the same copyright terms
 * except that the holder is Tim Hudson (tjh@cryptsoft.com).
 *
 * Copyright remains Eric Young's, and as such any Copyright notices in
 * the code are not to be removed.
 * If this package is used in a product, Eric Young should be given attribution
 * as the author of the parts of the library used.
 * This can be in the form of a textual message at program startup or
 * in documentation (online or textual) provided with the package.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *    "This product includes cryptographic software written by
 *     Eric Young (eay@cryptsoft.com)"
 *    The word 'cryptographic' can be left out if the rouines from the library
 *    being used are not cryptographic related :-).
 * 4. If you include any Windows specific code (or a derivative thereof) from
 *    the apps directory (application code) you must include an acknowledgement:
 *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
 *
 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 * The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
 */



© 2016 Adam J. Wilt.  Last updated 2016.05.18