I checked this out with a different file: a movie with a reported bitrate of 10063 kb/s (around 1,290,000 Bytes/sec). I streamed it to the Mezzmo app on my HTC M8 and to the PS3, from both Mezzmo 4.1.3.0 running under Windows XP 32-bit and Mezzmo 5.0.5.0 running under Windows 7 64-bit.

I've placed some screen shots of the monitoring results at [url]http://bisonica.pairserver.com/mezzmo/mezperf/[/url].

Here is the information for the file, from Mezzmo 5.0.5.0:

[CODE]ffmpeg version N-78742-gf477849 Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 4.9.2 (GCC)
  configuration: --enable-memalign-hack --arch=x86_64 --target-os=mingw32 --cross-prefix=x86_64-w64-mingw32- --enable-static --disable-shared --enable-zlib --disable-postproc --prefix=/home/peter/ffmpeg/build/gpl64 --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread -lstdc++' --enable-runtime-cpudetect --extra-cflags=-I/home/peter/cc32/include --extra-ldflags=-L/home/peter/cc64/lib --pkg-config=pkg-config --pkg-config-flags=--static --disable-w32threads --enable-libvpx --enable-libvorbis --enable-libtheora --enable-libx265 --enable-libmfx --enable-gnutls --extra-libs='-lz -lnettle -lhogweed -lgmp -lidn -lws2_32 -lcrypt32'
  libavutil      55. 19.100 / 55. 19.100
  libavcodec     57. 25.101 / 57. 25.101
  libavformat    57. 26.100 / 57. 26.100
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 36.100 /  6. 36.100
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000560520] stream 0, timescale not set
[mjpeg @ 0000000000562740] Changing bps to 8
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000560520] Stream #2: not enough frames to estimate rate; consider increasing probesize
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\\Peacock\Movies\babadook  the  (2014).mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 1
    compatible_brands: isomavc1
    creation_time   : 2015-02-25 09:44:00
    date            : 2014-01-17
    title           : The Babadook
  Duration: 01:33:46.08, start: 0.000000, bitrate: 10063 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x816, 9841 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
    Metadata:
      creation_time   : 2015-02-25 09:44:00
      handler_name    : baba3.264 - Imported with GPAC 0.5.0-rev4065
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 212 kb/s (default)
    Metadata:
      creation_time   : 2015-02-25 09:44:59
      handler_name    : GPAC ISO Audio Handler
    Stream #0:2: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 4000x3000, 90k tbr, 90k tbn, 90k tbc
At least one output file must be specified

<MEZZMO>: Child process ended with code: 109, ExitCode=1


---> DB Level Info: 41, 100
---> Frame rate: 23.98
---> Aspect ratio: 
---> Duration: 01:33:46[/CODE]

Here is what I find odd. In all cases, the rate at which the disk is being read is consistent with the bit rate of the file. With the Mezzmo app on the HTC M8, the data send rates are also consistent. With the PS3, 5-6 times as much data is being sent as is being read. This is true for both Mezzmo 4.1.3.0 and Mezzmo 5.0.5.0.

I realize there could be caching going on... but I can’t come up with a scenario that explains why the machine would be reading data from the file at approximately the real-time rate of the file, but sending data at five times that rate.