HRTF panner should handle the case of no loaded HRTF database

HRTF panner should handle the case of no loaded HRTF database

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know about this implementation
detail, and we also get the correct distance and cone gains applied.

BUG=629858
TEST=

Committed: https://crrev.com/d8bfaa0cd8383d9dff73c737fe8ae19fedc40a43
Cr-Commit-Position: refs/heads/master@{#406988}

[Raymond Toy, 2016-07-21 21:04:07]

Description was changed from

==========
HRTF panner should copy data instead of zeroing.

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know, and we also get the
correct distance and cone gains applied.

BUG=
TEST=
==========

to

==========
HRTF panner should copy data instead of zeroing.

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know, and we also get the
correct distance and cone gains applied.

BUG=629858
TEST=
==========

[Raymond Toy, 2016-07-21 21:05:58]

Description was changed from

==========
HRTF panner should copy data instead of zeroing.

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know, and we also get the
correct distance and cone gains applied.

BUG=629858
TEST=
==========

to

==========
HRTF panner should handle the case of no loaded HRTF database

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know about this implementation 
detail, and we also get the correct distance and cone gains applied.

BUG=629858
TEST=
==========

[Raymond Toy, 2016-07-21 21:06:15]

rtoy@chromium.org changed reviewers:
+ hongchan@chromium.org

[Raymond Toy, 2016-07-21 21:06:16]

PTAL

[hongchan, 2016-07-21 22:03:50]

lgtm

[Raymond Toy, 2016-07-21 22:06:52]

The CQ bit was checked by rtoy@chromium.org

[commit-bot: I haz the power, 2016-07-21 22:08:16]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-21 23:27:46]

Description was changed from

==========
HRTF panner should handle the case of no loaded HRTF database

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know about this implementation 
detail, and we also get the correct distance and cone gains applied.

BUG=629858
TEST=
==========

to

==========
HRTF panner should handle the case of no loaded HRTF database

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know about this implementation 
detail, and we also get the correct distance and cone gains applied.

BUG=629858
TEST=
==========

[commit-bot: I haz the power, 2016-07-21 23:27:48]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-07-21 23:29:26]

Description was changed from

==========
HRTF panner should handle the case of no loaded HRTF database

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know about this implementation 
detail, and we also get the correct distance and cone gains applied.

BUG=629858
TEST=
==========

to

==========
HRTF panner should handle the case of no loaded HRTF database

Currently, the panner node checks to see if the HRTF database is
loaded and does the copy of the input if necessary.  This is the wrong
abstraction; the HRTF panner should copy the input if the database is
not ready.

In this way, the panner doesn't need to know about this implementation
detail, and we also get the correct distance and cone gains applied.

BUG=629858
TEST=

Committed: https://crrev.com/d8bfaa0cd8383d9dff73c737fe8ae19fedc40a43
Cr-Commit-Position: refs/heads/master@{#406988}
==========

[commit-bot: I haz the power, 2016-07-21 23:29:27]

Patchset 2 (id:??) landed as
https://crrev.com/d8bfaa0cd8383d9dff73c737fe8ae19fedc40a43
Cr-Commit-Position: refs/heads/master@{#406988}