What: ARO was rebranded to Video Optimizer. ARO 6.0 was the last version with the ARO branding.

How: Video Optimizer supports ARO features and will continue to improve all-around application optimization, but with a strong focus on video.

Why: Statistics show that mobile video consumption is growing rapidly, currently accounting for 50% of time users spend watching online video, and is expected to reach 60% in 2017 and continue to grow. So helping optimize video streaming on mobile devices is increasingly critical. Rebranding to Video Optimizer highlights our focus on video.

When: Video Optimizer 1.0 was released in Jan 2017 and had the same features as ARO 6.0. The software upgrade of both Video Optimizer 1.0 and ARO 6.0 was to Video Optimizer 1.1. Going forward this analytics tool will be branded as Video Optimizer.

Learn more about Video Optimizer.

Ensure that your Xcode version is up to date.

AT&T Video Optimizer is supported on Microsoft Windows, Mac OS X 10.6 and above, and Linux (tested with CentOS and Ubuntu).

Yes. AT&T Video Optimizer is able to look for basic data transmission security issues.  You can learn more with our best practices.

AT&T Video Optimizer does not currently support pcap.ng (PCAP Next Generation) files, and cannot display network traffic data from files in this format. The most recent versions of Wireshark (1.7 and up), contain a new version of the Dumpcap tool that captures packet data in the pcap.ng format by default, instead of the pcap format, as previous versions did. To use Wireshark to capture data that it is compatible with the Video Optimizer, you must specify the flag '-P'.

Yes, we would love that! Please fork and contribute to our open source AT&T Video Optimizer repository on Github. We want to see what you can do!

Our customers expect a fast network and blazing-fast speeds. By helping applications reduce their impact on the network, we can continue to provide that level of service.

Optimizing your app is a bit like getting in the carpool lane during rush-hour: You get to where you're going that much faster, and everyone else experiences a little less gridlock

Application traces that contain large network bursts, like those that can occur when capturing a long session with complex mapping applications or rich social media applications, may take an extremely long time to load in Video Optimizer. This issue is caused by the complex algorithms that are used to calculate the analysis of the burst data, and is not an issue with available memory. In these cases, Video Optimizer may appear to hang, but will eventually load the trace analysis.