| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Also moved FrameConsumer interface to remoting/protocol. This
will allow to implement video rendering in WebrtcConnectionToHost as
WebRTC stack is responsible for video decoding.
BUG=547158
Review URL: https://codereview.chromium.org/1559043004
Cr-Commit-Position: refs/heads/master@{#367600}
|
|
|
|
|
|
|
|
|
|
|
| |
VideoRenderer interface is going to be used by ConnectionToHost, so it
belongs to the protocol layer.
BUG=547158
Review URL: https://codereview.chromium.org/1559023003
Cr-Commit-Position: refs/heads/master@{#367588}
|
|
|
|
|
|
|
|
|
| |
BUG=138542
TBR=wez@chromium.org
Review URL: https://codereview.chromium.org/1542203002
Cr-Commit-Position: refs/heads/master@{#366684}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously PerformanceTracker was owned by VideoRenderer
implementations. Move it to ChromotingInstance and
ChromotingJniInstance because the tracker will be responsible for
tracking all performance stats that may not be related to video
rendering.
Review URL: https://codereview.chromium.org/1353443003
Cr-Commit-Position: refs/heads/master@{#349498}
|
|
|
|
|
|
|
|
|
|
| |
The class will be used directly from protocol dispatchers, so it needs
to be accessible on the protocol layer. Also renamed it so the name
reflects what the class is responsible for.
Review URL: https://codereview.chromium.org/1351723004
Cr-Commit-Position: refs/heads/master@{#349295}
|
|
|
|
|
|
|
|
|
|
| |
libyuv is now used for YUV conversions on both ends.
BUG=256850
Review URL: https://codereview.chromium.org/1290273004
Cr-Commit-Position: refs/heads/master@{#344905}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Added the interface to turn on debug mode in the latency fixture.
2. Implemented dumping image frames to local files in TestVideoRenderer
using libpng.
I didn't test the code with the test driver due to some problems with
test driver, but I'll run and test the code as soon as the test driver
becomes available.
BUG=
Review URL: https://codereview.chromium.org/1262013003
Cr-Commit-Position: refs/heads/master@{#341799}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
connection helper.
1. Moved the Open new document logic to the SetUp function to enforce
a fresh document for tests.
2. Refactored connection helper to make it as minimum as possible, and
moved the ping response verify logic to the connected client fixture.
BUG=
Review URL: https://codereview.chromium.org/1253613002
Cr-Commit-Position: refs/heads/master@{#340588}
|
|
|
|
|
|
|
|
|
|
| |
The Image pattern comparison logic is: calculate the average color of the expected rect region on the current frame and compare it to the expected color to see if it matches.
BUG=
Review URL: https://codereview.chromium.org/1219923011
Cr-Commit-Position: refs/heads/master@{#338588}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically, the following 4 steps are required to write a test:
1. Initialize(Application to be run);
2. SetExpectedImagePattern(expected rectangle (area of interets), the
average color of the area);
3. Send user inputs.
4. bool VerifyImagePatternMatched(max wait time);
The VerifyImagePatternMatched function returns true if a image pattern
matched response is received within the maximum time limit.
BUG=
Review URL: https://codereview.chromium.org/1218933004
Cr-Commit-Position: refs/heads/master@{#337713}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Spin up a separate thread to decode video packets.
Decode and Render video packets to a buffer in memory.
Add unit tests to verify video decoding for VP8, VP9, VERBATIM, as well as video packets size change.
Add unit tests to verify thread start and stop.
BUG=
Review URL: https://codereview.chromium.org/1214113009
Cr-Commit-Position: refs/heads/master@{#336897}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(patchset #7 id:120001 of https://codereview.chromium.org/1190383007/)
Reason for revert:
The new tests are failing on the DrMemory bots: see http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%283%29/builds/7009 for more details.
An example of the failure:
d:\src\chromium\src\remoting\test\test_video_renderer_unittest.cc(119): error: Expected: (error) < (error_limit), actual: 0.406962 vs 0.02
The problem is due to hard coded times in the test, at line 110. Tests shouldn't rely on waiting 'long enough' for something to happen, as 'long enough' is too variable / flaky. The test should ideally be rewritten to wait for a quit task to be posted instead.
Original issue's description:
> Updated Test Driver with video decoding capabilities so that when a video sample is received from remote host, it can be decoded and rendered to buffer in memory.
>
> BUG=
>
> Committed: https://crrev.com/497e9a05decbcd344d774e52c1b89cdece525d99
> Cr-Commit-Position: refs/heads/master@{#336445}
TBR=joedow@chromium.org,liaoyuke@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
Review URL: https://codereview.chromium.org/1219633002
Cr-Commit-Position: refs/heads/master@{#336526}
|
|
|
|
|
|
|
|
|
|
| |
sample is received from remote host, it can be decoded and rendered to buffer in memory.
BUG=
Review URL: https://codereview.chromium.org/1190383007
Cr-Commit-Position: refs/heads/master@{#336445}
|
|
will be used by the app remoting test driver in a subsequent checkin.
BUG=464808
Review URL: https://codereview.chromium.org/976233003
Cr-Commit-Position: refs/heads/master@{#320161}
|